...
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
TeaStore
OpenTelemetry compability
Bachelor thesis (not reusable): Create a TeeTime stage that exports Kieker OperationExecutionRecords to OpenTelemetry span https://github.com/Col20s/kieker/blob/main/OpenTelemetryStage.java
Willli suggest: Use IRL for compatibility DSL / Xtext
Python (Serafims work)
→ Shinhyung needs Jira and Jenkins access, and than takes care of itJira Legacy server System Jira serverId 91cef256-0ee5-36d6-b7a4-90d687f868f3 key KIEKER-1983
Release
Jira Legacy server System Jira serverId 91cef256-0ee5-36d6-b7a4-90d687f868f3 key KIEKER-1809
2024-05-29
MooBench: Since results are reasonably stable, no increase of NUM_OF_LOOPS (https://github.com/kieker-monitoring/moobench/issues/9 )
Logging doesn’t work in MooBench: https://github.com/kieker-monitoring/moobench/issues/12
Whats the matter with PutStrategy and InsertBehaviour? (Default value currently makes multiple thread monitoring hard)
2024-05-17
PR Spring Extraction
MooBench: JDK 11 to 21 update -> Examine changes in SSP paper
MooBench Jenkins data: https://maui.se.informatik.uni-kiel.de/repo/moobench/
MooBench Jenkins data analysis: https://github.com/kieker-monitoring/moobench/tree/main/tools/compile-results
MooBench kieker-python (https://build.se.informatik.uni-kiel.de/view/Kieker/job/kieker-moobench/job/main/ fails) => David creates ticket (Created:
)Jira Legacy server System Jira serverId 91cef256-0ee5-36d6-b7a4-90d687f868f3 key KIEKER-1983 Gradle update to 8.7 should happen
2024-04-24
Spring boot: Still in progress (David)
Security problem in documentation: Still in progess (
Reiner)Jira Legacy server System Jira serverId 91cef256-0ee5-36d6-b7a4-90d687f868f3 key KIEKER-1982 build.gradle publishing: Try to move to parent build.gradle (David)
Spring probe extraction: Wait for build in https://build.se.informatik.uni-kiel.de/view/Kieker/job/kieker-dev/view/change-requests/job/PR-548/, whether
implementation "net.kieker-monitoring:kieker:${kiekerVersion}:spring"
worksgit command not found for main release check (https://build.se.informatik.uni-kiel.de/view/Kieker/job/kieker-release-check/job/main/75/console) → David contacts Matthias
Open tickets for 2.0.0
(wait for Matthias)Jira Legacy server System Jira serverId 91cef256-0ee5-36d6-b7a4-90d687f868f3 key KIEKER-1809 Jira Legacy server System Jira serverId 91cef256-0ee5-36d6-b7a4-90d687f868f3 key KIEKER-1933
2024-04-10
Should be ready to merge
Spring: Interceptors still don’t work for spring boot, because they don’t select the methods → Is there something missing?
There is a security vulnerability:
Jira Legacy server System Jira serverId 91cef256-0ee5-36d6-b7a4-90d687f868f3 key KIEKER-1982 Duplicated publishing information necessary? https://kieker-monitoring.atlassian.net/jira/software/c/projects/KIEKER/issues/KIEKER-1979?
2024-03-27
Spring web and Kieker seems to have some problem:
Jira Legacy server System Jira serverId 91cef256-0ee5-36d6-b7a4-90d687f868f3 key KIEKER-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
MooBench memory leak: Based on analysis of heap dumps, it seems like the RotatingLogFilePoolHandler caused the problem: https://github.com/kieker-monitoring/kieker/blob/371a9095a1bc212dbd422afdf831197bd50794cf/monitoring/src/kieker/monitoring/writer/filesystem/RotatingLogFilePoolHandler.java#L85 (We have ~5000 files in the ArrayList)
First solution: increase
kieker.monitoring.writer.filesystem.FileWriter
maxLogSize
,maxEntriesInFile
and decreasemaxLogFiles
for MooBenchLong-term solution: Change default parameters in Kieker (currently, we have only 25 000 entries in one file, resulting in files of ~1.5 MB): https://github.com/kieker-monitoring/kieker/blob/371a9095a1bc212dbd422afdf831197bd50794cf/monitoring/src-resources/META-INF/kieker.monitoring.default.properties#L338
Overall architecture: Have one monitoring module with submodules monitoring-core and one module for each agent: monitoring-aspectj, monitoring-disl, monitoring-javassist, monitoring-bytebuddy
Each agent should be provided as individual jar
Only the required classes should be contained (no analysis classes)
Java 11 PR problem: Was caused by a deprecated test → Removed and try again
DiSL PR problem: Was caused by missing Kieker license header for DiSL → Changed and try again
...