I

Usually, we have bi-weekly developer meetings. The specific dates and instructions on how to join are listed on the Meetings Home page.We recommend subscribing to Kieker's calendar.

...

• To discuss:

  • Why does MooBenchs default instrumentation create different record types (OperationExecutionRecord, ApplicationTraceMetadata, BeforeOperationEvent and AfterOperationEvent)? Shouldn’t Before/AfterOperationEvent be sufficient? Instrumentation is kieker.monitoring.probe.aspectj.flow.operationExecution.FullInstrumentation

  • Is it right that MooBenchs default instrumentation does not create empty constructor call data?

  • → Yes, its intended; flow.operationExecution does not work in Java 17+ (https://stackoverflow.com/questions/70411097/instrument-java-17-with-aspectj ); therefore, we need to restructure all the records

  • Separation of Before/After Records -> David creates ticket

• MooBench generally works again after fix, inspectIT needs fix → David Georg Reichelt contacts Novatec

• Thesis -> Theses -> Andre van Hoorn checks thesis

2023-08-22

• Log replayer and analysis for TeaStore still does not work:

  Jira Legacy
  server System Jira serverId 91cef256-0ee5-36d6-b7a4-90d687f868f3 key KIEKER-1948

  • David identifies the first wrong record and discusses this with André

• Kieker setup: eclipse does not recognize package structure

  • Reiner has a look at the problem

  • (EDIT) Issue is created:

    Jira Legacy
    server System Jira serverId 91cef256-0ee5-36d6-b7a4-90d687f868f3 key KIEKER-1966

• MooBench No Logging / Binary Writer examination paper: Warmup experiments started, waiting for results

...