Dev Meetings
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
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)
KIEKER-1983: MooBench Using Kieker-Python Does not WorkOpen → Shinhyung needs Jira and Jenkins access, and than takes care of it
Release
2024-05-29
MooBench: Since results are reasonably stable, no increase of NUM_OF_LOOPS (Refactor for Increased Usability · Issue #9 · kieker-monitoring/moobench )
Logging doesn’t work in MooBench: Kieker slf4j does not work in MooBench · Issue #12 · kieker-monitoring/moobench
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: moobench/tools/compile-results at main · kieker-monitoring/moobench
MooBench kieker-python (https://build.se.informatik.uni-kiel.de/view/Kieker/job/kieker-moobench/job/main/ fails) => David creates ticket (Created: KIEKER-1983: MooBench Using Kieker-Python Does not WorkOpen )
Gradle update to 8.7 should happen
2024-04-24
Spring boot: Still in progress (David)
Security problem in documentation: Still in progess (https://kieker-monitoring.atlassian.net/browse/KIEKER-1982 Reiner)
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
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: https://kieker-monitoring.atlassian.net/browse/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: https://kieker-monitoring.atlassian.net/browse/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
2024-01-24
MooBench
Is https://github.com/kieker-monitoring/moobench/tree/main/continuous-integration still relevant (or is this replaced by the Jenkinsfile)?
Would it make sense to migrate https://maui.se.informatik.uni-kiel.de/repo/moobench/ to github?
2024-01-10
Java 21 support requires an AspectJ update https://kieker-monitoring.atlassian.net/browse/KIEKER-1971
Hopefully, there is some way changing the classpath in the aspectj gradle plugin:https://github.com/freefair/gradle-plugins/issues/1005
Didn’t work in https://github.com/kieker-monitoring/moobench/actions/runs/7421185662/job/20194020069
Somehow magically worked in https://github.com/kieker-monitoring/moobench/actions/runs/7424136205 - maybe the update to 1.9.20.1 was already sufficient for our featureset? (https://github.com/kieker-monitoring/kieker/pull/480 )
There was still a configuration error in
compileJarIntegrationTestJava
; wait for Jenkins build and than merge
Refactoring MooBench (Refactor for Increased Usability · Issue #9 · kieker-monitoring/moobench )
Started and works basically for Kieker (except the Java 21 thing)
Adapted for OpenTelemetry-java (is this good style? https://github.com/kieker-monitoring/moobench/blob/59f09ebecb9d908b7da93613107670dbaa8053e7/frameworks/OpenTelemetry-java/functions.sh#L45
Kieker-python still needs adaption (copy OpenTelemetry-java style?)
Do we want to continue inspectIT regular execution (since the website still has the roadmap for 2022…) → Leave it running, but remove it if problems occur
Website still needs adaption → Currently failure due to unknown error; rerun on Jenkins started
In general: Change to “Kieker-java-aspectj”, “Kieker-java-DiSL”, …? → Yes
Kieker usage for Micro-company (https://github.com/DaGeRe/micro-company/tree/kieker ): How to fix logging issue?
TeeTime does not compile → We need GH actions like for Kieker: https://github.com/teetime-framework/TeeTime/pull/45
Locally, when checking out Kieker, sometimes the error “Could not find teetime-3.1.0-test.jar (de.cau.cs.se.teetime:teetime:3.1.0).” occurs. Is there a solution / workaround for this?
Ask Reiner: What is the rights situation with TeeTime? We need the rights to merge at least
If there is no TeeTime organization anymore, it might make sense to fork the core TeeTime to the kieker organization and consider it as another Kieker project
Next meeting: 24.1. 10:00
2023-12-13
Documentation: Reiner fixed quickstart guide (https://github.com/kieker-monitoring/kieker/blob/main/documentation/quick-start-guide.rst )
Open PR: Reiner has a look at https://github.com/kieker-monitoring/kieker/pull/421
AOPalliance ticket: David finalizes https://kieker-monitoring.atlassian.net/browse/KIEKER-1962https://kieker-monitoring.atlassian.net/browse/KIEKER-1962
Instrumentation research: Besides DiSL, we could try BISM (https://link.springer.com/article/10.1007/s10009-023-00708-z)
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: Refactor for Increased Usability · Issue #9 · kieker-monitoring/moobench → 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 https://kieker-monitoring.atlassian.net/browse/KIEKER-1948 and https://kieker-monitoring.atlassian.net/browse/KIEKER-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? https://kieker-monitoring.atlassian.net/browse/KIEKER-1961 (Related to https://kieker-monitoring.atlassian.net/browse/KIEKER-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 -> https://kieker-monitoring.atlassian.net/wiki/spaces/IDEAS/pages/24215606 -> @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: https://kieker-monitoring.atlassian.net/browse/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: https://kieker-monitoring.atlassian.net/browse/KIEKER-1966
MooBench No Logging / Binary Writer examination paper: Warmup experiments started, waiting for results
2023-07-31
Who will maintain Jenkins builds in future? Matthias was asking and we should find an idea to address this.
Somebody from Kiel? Otherwise Andre and David
MooBench No Logging / Binary Writer examination paper:
Data set does contain not-warmed up data → fix later
DumpQueue solves the problem
2023-07-17
Problems No Logging / Binary Writer Examination
Multithreading or using getCurrentThreadUserTime() hangs (nondeterministically)
Examine later
METHOD_TIME does not solve the problem for many configurations
Try creating a MonitoredClassLoops, or eventually in combination with getCurrentThreadUserTime()
Calibration of METHOD_TIME
Wait for feedback from Reiner
https://kieker-monitoring.atlassian.net/browse/KIEKER-1948 → Prepare reproducible next time
How to add documentation to https://kieker-monitoring.readthedocs.io/en/latest/instrumenting-software/java/Instrumentation-with-AspectJ.html ? Edit code:https://github.com/kieker-monitoring/kieker/tree/master/kieker-documentation/instrumenting-software/java
2023-07-04
Open Issues for 2.0.0?
How to add documentation to https://kieker-monitoring.readthedocs.io/en/latest/instrumenting-software/java/Instrumentation-with-AspectJ.html ? (Otherwise, interested people will always have problems getting started)
No Logging / Binary Writer Examination
Experiments are mostly succeeding (Java 11 + 17, i7-4770 and i7-6700), but values are generally not as stable as one could expect → Maybe default $NUM_OF_LOOPS should be higher?
Solution probably: METHOD_TIME should always be above 1000 → Change default parameter and print warning?
Future work: Check different Queue types? Why isn’t the effect increasing with more threads?
Next steps on https://github.com/teetime-framework/TeeTime/issues/31 ?
2023-06-20
OSHI is very outdated and should be updated: https://kieker-monitoring.atlassian.net/browse/KIEKER-1963
DiSL waiting for response
No Logging / Binary Writer Examination
First PDF and experimental results existing: https://gist.github.com/DaGeRe/c7159297bad4bd13fb556dcf696d0699
Check without optimization in JVM
perf → measure context switches
Measure dummy loop (David) and queue (Reiner) separately
Ideas for implications:
Try other queue
Callibration of dummy loops to reduce context switches
Check method time increase
Processor Pinning
Try other JVM
Related work
MooBench + Benchmark Design
Benchmark Callibration
Runtime Environment
i7-6700 → Uni Leipzig
Raspberry Pi?
Java 11 / 17?
2023-06-06
review tickets
switch to Java 11 due to logging framework logback requires at least 11, newer versions of aspectj need it too. There might be other libraries that may hit this version issue.
DiSL implementation started: https://kieker-monitoring.atlassian.net/browse/KIEKER-1961
Old DiSL instrumentation still existing https://github.com/kieker-monitoring/kieker/blob/KIEKER-1961-Support-DiSL/kieker-monitoring/src/kieker/monitoring/probe/disl/flow/operationExecution/FullInstrumentation.java and DiSL jar added manually: https://github.com/kieker-monitoring/kieker/blob/208d996b55661f2d50c8e4661835c0c588af4bc9/kieker-monitoring/build.gradle#L65 - remove? (Will not work at all, no DiSL-classes specified, and its basically 9 years old)
DiSL is currently not in maven central, so everything is experimental (for MooBench evaluation - than let’s see whether this improves performance)
implementation 'aopalliance:aopalliance:1.0' can be removed from kieker-monitoring without side-effects → remove?
MooBench questions
Whats the point of https://github.com/kieker-monitoring/moobench/blob/main/frameworks/Kieker-java/build.gradle ? I do not see any call to it while benchmarking
Whats the advantage of $MOOBENCH_BIN instead of just creating the call with java -jar … (https://github.com/kieker-monitoring/moobench/blob/72ce150aa773fc92b5aa7578781d06185ea6d269/frameworks/Kieker-java/functions.sh#L56 )? It makes different configurations (calling it with perf, starting with DiSL instrumentation) harder
TODOs
aopalliance dependency can be removed
document that CXF, JMS are unmaintained
JMS maybe newer version and better/smaller dependency
2023-05-23
Release 2.0.0
review tickets @Reiner Jung
Pull request https://github.com/kieker-monitoring/kieker/pull/383
Pull request https://github.com/kieker-monitoring/kieker/pull/407
MooBench performance tests
Integration of OceanDSL stuff https://kieker-monitoring.atlassian.net/browse/KIEKER-1959
Future proofing Kieker
Build environment
Shall we keep Jenkins?
Who will maintain and support Jenkins pipeline and docker container?
Keys/Credentials
How to store credentials?
TeeTime maintenance
Add teetime credentials to Confluence @Reiner Jung
What to do with MooBench?
2023-05-09
Kieker 4 Python on pypi https://pypi.org/project/kiekerforpython/
Create collector deployable https://kieker-monitoring.atlassian.net/browse/KIEKER-1957
MooBench has lower execution times for binary file and TCP writer than for DumpWriter; this should be examined: https://kieker-monitoring.atlassian.net/browse/KIEKER-1958
Issue regarding time unit should be checked and closed: https://kieker-monitoring.atlassian.net/browse/KIEKER-1956 (David)
Queue handling for log replayer should be fixed: https://kieker-monitoring.atlassian.net/browse/KIEKER-1948
2023-04-26
Reiner und Thomas need to fix their calendar issues
Discussed MooBench results. Question:
Why Binary TCP for Kieker faster than no logging?
Similar inconsistency for inspectIT; David to contact Tobi A.
2023-04-04
https://kieker-monitoring.atlassian.net/browse/KIEKER-1956 David provides an example; Reiner will have a look.
https://kieker-monitoring.atlassian.net/browse/KIEKER-1955 Resolved
2023-03-07
Currently bug in log replayer: https://kieker-monitoring.atlassian.net/browse/KIEKER-1948 → How do we want to handle incompatibility with Java 17?
Multiple dirs: David
Java 17: Reiner
A big portion of the trace analysis gui is in the trace-analysis project (https://github.com/kieker-monitoring/kieker/tree/master/kieker-tools/trace-analysis/src/kieker/tools/trace/analysis/gui ) → Is there a reason for this, or could it just be moved?
Move classes: David creates PR
Plan 2.0.0 release cycle (what should go in and what must be done)
How to handle next batch of tools and analyses coming in from OceanDSL?
2023-02-21
@Thomas F. Düllmann Kieker → OpenTracing
@Thomas F. Düllmann Assumed executions in Kieker4Python
Started slides for CLT: https://github.com/kieker-monitoring/resources/tree/master/talks/20230311-CLT
2023-02-07
@David Georg Reichelt’s Kieker talk at Chemnitz Linuxtage accepted. Event will be on March 11, 2023. 45 minutes talk.
@Reiner Jung to provide input from OceanDSL tools, e.g., visualization of the architecture model
@David Georg Reichelt provides TeaStore logs to @Reiner Jung
@David Georg Reichelt presents updates to MooBench
To keep on the Kieker (radar): tutorial, e.g., ECSA 2023.
2023-01-25
General idea: Probably in the future rebase and merge instead regular merge? (from the last 1000 commits, 149 are merge commits: git log --oneline | head -n 1000 | grep "Merge pull" | wc -l)
For a set of commits with smaller changes: rebase or squash
For merging back release branches, merge request
FullInstrumentation does not work with Java 17: https://kieker-monitoring.atlassian.net/browse/KIEKER-1947 we either should to refactor it or to remove it
Possible replacemenet: https://bytebuddy.net
Pending TODOs
Merge RC back to master @David Georg Reichelt
Java records for monitoring records @Holger Knoche
2023-1-10
Release 2.0.0 ticket selection and todo list
@Holger Knoche suggested new record solution https://kieker-monitoring.atlassian.net/browse/KIEKER-1935
We need an architecture/API description for this in the documentation.
We need a generator for records and factory for this new type of records.
Summary:
Nice idea
Record keyword supported >= Java 14 but not an issue as the generic factory has no dependency to record.
@Holger Knoche to check whether there are features for reflection that do need Java >8.
Would be nice to get into the Kieker core as an alternative to define records.
@Holger Knoche Prepares a new pull request.
Perspective: rename master branch into main branch. https://kieker-monitoring.atlassian.net/browse/KIEKER-1942
In progress by David and Reiner. Pending issue
TeaStore: Monitoring basically works (requires setting IP and deactivating firewall): https://github.com/DescartesResearch/TeaStore/issues/236
David to merge multiple directories distributed traces (folders) and report in the next meeting.
2022-12-20
Perspective: rename master branch into main branch. https://kieker-monitoring.atlassian.net/browse/KIEKER-1942
Merge back 1.15.2 to master. PR created, @David Georg Reichelt checks the conflicts,@Reiner Jung Could you check and eventually merge the PR?
There seems an issue with signing tasks
TeaStore: Still technical problems: https://github.com/DescartesResearch/TeaStore/issues/236
DFG proposal
2022-11-29
@Andre van Hoorn will move the Kieker/resources repo from Kiel to GitHub (as a private repo)
Tutorial: Create a folder in the repository for the tutorial; we’ll create the proposal document in there.
Perspective: rename master branch into main branch. https://kieker-monitoring.atlassian.net/browse/KIEKER-1942
Merge back 1.15.2 to master. In progress by @David Georg Reichelt
2022-11-04
Kieker SSP meeting 7.11. 16:00-18:00 (get-together 15:30!) hybrid at Vector Informatik GmbH in Stuttgart Weilimdorf, Holderäckerstraße 36, 70499 Stuttgart.
Kieker developer meeting agenda
ICPE tutorial:
Proposal deadline: Jan 22, 2023
Existing materials:
Proposal template from Kieker tutorial at ICPE 2014
Tutorial slides from Kieker tutorial at ICPE 2014 (2 hours)
Did not find the folder with the original resources. It used to be in a separate Kieker Git: https://git.se.informatik.uni-kiel.de/kieker/resources (but cannot be accessed by non members, but by @Andre van Hoorn ) @Andre van Hoorn suggests to move the repo to GitHub as a private repo.
Slides from a guest lecture at U Pavia that was after the tutorial: https://kieker-monitoring.atlassian.net/wiki/download/attachments/5865548/20140521-KiekerLectureUPavia-slides.pdf?api=v2
Contents
Motivation for monitoring
Kieker basics
Hands-on instrumentation + monitoring
Selected Use Cases
Monitoring distributed Java applications
Dynamic analysis of legacy systems (VB, .NET, COBOL, Fortran, Perl, C/C++)
…
Chemnitzer Linuxtage (David): 1 hour talk
Items for report at SSP @Reiner Jung @Wilhelm Hasselbring @David Georg Reichelt @Thomas F. Düllmann: Please complete
Research activities/projects in the (wider) Kieker scope:
Performance monitoring and analysis of data-intensive systems, particularly based on Python+TensorFlow
SPEC RG: local performance models (working with some benchmark systems and extracted architectures)
dqualizer: domain-based analysis of runtime quality attributes, e.g., including domain-based monitoring / Dispel
Kiel: Dynamic analysis of ocean models? Refer to presentation
Peass: Usage of Kieker for architecture recovery and root cause analysis → GeoMap industry case study will be presented in this SSP, which uses Kieker
Technologies/Features:
Kieker for Python: Refer to presentation and paper (presentation by Serafim, Instrumenting Python with Kieker)
Kieker for Fortran: Refer to presentation and paper (presentation by Reiner, Architecture Recovery from Fortran Code with Kieker)
Development process and environment:
Accelerated release process with minor versions (semantic versioning)
MooBench updates: https://kieker-monitoring.net/performance-benchmarks/
Performance benchmarks were updated to the current Kieker version and OpenTelemetry and inspectIT (last year)
Continuous execution of benchmarks has been automated (again) (This year)
Also for Python
Planned for C/Fortran/C++
Releases:
Kieker 1.15.2?
Change in release cycle: Bugfix releases and releases fixing security problems in dependencies will be published more often in the future
Requires automated release process (instead manual upload to sonatype)
Currently, finalizing of release process adaption happens
Build process uses only maven/gradle dependencies
Kieker 2.0.0
Finalized integration of TeeTime-based stages
Naming conventions for stages
Stage processing, data manipulation
Filter filters events (Kieker events or any other data object passed between stages)
Sink for stages that store data
Source for stages that read, load or receive data
Refactoring to support a topic-based package structure instead of a technical motivated structure, i.e,
architecture
adaptation
dependency
metrics (metrics for architecture evaluation)
recovery (architecture recovery)
repository (architecture model repository)
trace (architecture based trace analysis)
behavior (user behavior analysis)
generic
statistics
New facilities to observe and analyze user behavior based on graph clustering algorithms
Architecture model comes now with a model repository and stages processing these repositories
Architecture model supports interfaces and dataflow (beta)
As many classes have been moved, we provide a complete list of moved classes for migration to the new version
2022-10-14
TODO: What happened with release wiki page: https://kieker-monitoring.atlassian.net/wiki/spaces/DEV/pages/5865697
@David Georg Reichelt is debugging the publish and sign process locally to indentify the issues with our current setup
Use modified Jenkinsfile in case the issue is only on Jenkins
How about a 2.0.0 release?
3.11.2022 10:00 next online Kieker meeting
2022-10-07
Submit a tutorial to ICPE 2023 - deadline Jan 22, 2023
Next meeting 14.10. 8:30
Issues with release publishing due to missing keys
2022-09-23
Make release process transferable to other people to eliminate bottleneck
Make 1.15.2 release (release date 30.9.2022)
Set a date for the 2.0.0 release (release date 20.10.2022)
We need a concept for dependency updates, currently we have a none
Use dependabot
2022-09-02
New MooBench page and benchmark setup
Change file names to be more verbose (done)
First description for Kieker Java and Python @Reiner Jung (done)
Then @David Georg Reichelt for Telemetry and inspectIT
1.15.2 Release ready, must be release @Andre van Hoorn
Kieker 4 Python development / paper
Activate Dependabot for Kieker
Live Demo should move to Kiel or HH @Reiner Jung will try to set this up, support @Thomas F. Düllmann
2022-07-29
Kieker 4 python: Development ongoing
Kieker 1.15.2 Release Candidate: Waiting for release → Mail to Reiner
MooBench: Reiner is updating everything for visualization update
André and Reiner fix all the bugs
Thomas is available on August 11. and 12, David is only available on August 11 → Move meeting to 11th? @Reiner Jung
2022-07-15
Please review the package structure layed out in branch and the corresponding ticket https://kieker-monitoring.atlassian.net/browse/KIEKER-1903
The revision must check whether the location of the classes make sense and which classes must be moved (again)
We need someone to look at the structure and it cannot be @Reiner Jung who created the current package structure
We need a definite date to when this review must be finished. There are quite some depending tickets that require this to be solved.