Versions Compared

Version Old Version 367 New Version Current
Changes made by

David Georg Reichelt

David Georg Reichelt

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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.


Check ticket status before the meeting and add relevant topics

...

Cleanup Tickets

...

and add relevant topics

The dev meetings minutes are now moved to https://github.com/kieker-monitoring/kieker/wiki/Kieker-Dev-Meetings-2024

2024-07-03

  • Switch to github for the ticket system

    • Reiner Jung has created a backup of the tickets and will send them to Shinhyung.

  • Cloudprofiler: Shinhyung discusses running it with MooBench

  • What to do with the content of Confluence?

    • Passwords got to an encrypted keypass file and then onto a github private repository

    • Release documentation will be moved to the readthedocs documentation

    • Meetings minutes will be moved to GitHub wiki

  • Release preparation 2.0.0

2024-06-05

2024-05-29

2024-05-17

2024-04-24

2024-04-10

2024-03-27

  • Spring web and Kieker seems to have some problem:

    Jira Legacy
    serverSystem Jira
    serverId91cef256-0ee5-36d6-b7a4-90d687f868f3
    keyKIEKER-1978

    • Check interceptors

  • Next meeting: 10. 4. 9:00

2024-02-21

  • CI / CD: Jenkins is accesible again, move process to GH actions if manpower is available

  • Instrumentation technologies

    • Buildtime instrumentation is also implemented currently → Compare performance and probably leave it as option in the code

    • Meeting for paper at next Kieker dev meeting (either camera ready planning or QRS resubmission)

  • Disruptor: Not needed for current MooBench measurements, and it would require a bigger refactoring (creation of onXRecord for each record in WriterController); therefore, we don’t do it for now (even if it would reduce GC activity)

  • 1.15.5 release is required to have a stable version of Kieker that is compatible with Java 21 (currently, AspectJ is not compatible to Java 21)

2024-02-14

2024-01-24

2024-01-10

2023-12-13

2023-11-29

  • KIEKER-1933: Reiner resolves merge conflicts, afterwards David merges the PR

    • OPAD, extension-kafka and extension-cassandra: Don’t create bundle for now, if somebody starts using it add it

    • Reiner will create example bundle

    • resource-monitor: What is it? → Ask Andre van Hoorn

  • Current approach with Brunel: Monitor https://github.com/idugalic/micro-company (With spring - we should check the spring example and create a better documentation sometimes)

  • Research idea: Support DiSL probe and create kieker-disl-jar, and evaluate it on some bigger project

    • Two requirements on project: Scala / Java or Kotlin / Java mixed, some workload definition for measurement

    • Adaptive Monitoring (Compare SSP inspectIT Stuttgart?)

2023-11-15

  • Possible refactoring of MooBench: https://github.com/kieker-monitoring/moobench/issues/9 → How to implement this changes for the UI?

    • Since inspectIT seems unmaintained, remove it?

    • OneAgent (Dynatrace) and Datadog agent both allow a 14 day trial; we can test it and compare the overheads

2023-11-06

  • Fixed

    Jira Legacy
    serverSystem Jira
    serverId91cef256-0ee5-36d6-b7a4-90d687f868f3
    keyKIEKER-1948
    and
    Jira Legacy
    serverSystem Jira
    serverId91cef256-0ee5-36d6-b7a4-90d687f868f3
    keyKIEKER-1966

  • Plan: Release the fixes as 1.15.3, but plan for soon 2.0.0 release

2023-10-09

  • TeaStore debugging

    • No results so far

  • eclipse project debugging

    • Solution is to exclude test jars which are included twice from projects from eclipse dependencies (https://github.com/eclipse/buildship/issues/1266 )

    • This works fine for Ubuntu; for Fedora, the testImplementation 'de.cau.cs.se.teetime:teetime:3.1.0:test' dependency is not recognized correctly

2023-09-22

  • To discuss:

    • How to go on with DiSL?

      Jira Legacy
      serverSystem Jira
      serverId91cef256-0ee5-36d6-b7a4-90d687f868f3
      keyKIEKER-1961
      (Related to
      Jira Legacy
      serverSystem Jira
      serverId91cef256-0ee5-36d6-b7a4-90d687f868f3
      keyKIEKER-1000
      )

      • Separate deployment jar with disl classifier

  • TeaStore debugging

    • TrackingFilter seems like TeaStore needs OperationExecutionRecord (kieker.monitoring.probe.aspectj.operationExecution.OperationExecutionAspectFull)

    • With OperationExecutionRecord: Traces are considered invalid, even though they are valid (Caused by: kieker.tools.trace.analysis.filter.traceReconstruction.InvalidTraceException: First execution must have ess 0 (found 1))

    • Minimal example with only one previously broken trace id works

    • Ideas:

      • Combine two traces, including a broken one; Afterwards incrementally increase number of traces

      • Ask Reiner for results of last debugging session (What was wrong in Filter?)

2023-09-12

  • 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

  • Logreplyer on TeaStore data still does not work on bigger traces; discuss next time

2023-08-22

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

    Jira Legacy
    serverSystem Jira
    serverId91cef256-0ee5-36d6-b7a4-90d687f868f3
    keyKIEKER-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
      serverSystem Jira
      serverId91cef256-0ee5-36d6-b7a4-90d687f868f3
      keyKIEKER-1966

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

...