-
Notifications
You must be signed in to change notification settings - Fork 45
Open
Description
The property kieker.monitoring.setLoggingTimestamp triggers an automated adding of the current timestamp to each monitoring record:
kieker/monitoring/core/src/kieker/monitoring/core/controller/MonitoringController.java
Line 314 in 17182fb
| if (this.autoSetLoggingTimestamp) { |
For many records, like the OperationExecutionRecord with tout (
kieker/common/src-gen/kieker/common/record/controlflow/OperationExecutionRecord.java
Line 87 in 17182fb
| private long tin; |
AbstractEvent with timestamp (| private long timestamp; |
loggingTimestamp is not used (to my knowlege). Therefore, getting the logging timestamp only increases overhead.
We should have a two step approach of removing it:
- First, we should set
kieker.monitoring.setLoggingTimestamp=falsein the default configurations - Afterwards, we should remove the
loggingTimetampfrom the data model. This will further speed up the process (since also the empty long is not sent), but it will require adapting the tools that are using the logging timestamp. Eventually, this could break compatibility with old traces, so we need to be careful here.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels