Correct latency metrics in AxonIQ Console#103
Merged
CodeDrivenMitch merged 1 commit intomainfrom Aug 5, 2025
Merged
Conversation
First, we set the expiry time of ingest and commit latencies to two minutes, instead of 30 minutes. This prevents alarms from triggering and statistics to be strange. I think 2 minutes is a balanced approach; generally batches will take under 10 seconds, so 2 minutes is already more than enough. Second, we will now clean up the current message on cleanup, not on after commit. This will prevent hanging current latencies on errors. Third, the commit latency is now the time between ingest of the first message of the batch and the commit time of it. As such, this represents the batch time.
|
stefanmirkovic
approved these changes
Aug 5, 2025
Contributor
stefanmirkovic
left a comment
stefanmirkovic
left a comment
There was a problem hiding this comment.
The changes look good.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
First, we set the expiry time of ingest and commit latencies to two minutes, instead of 30 minutes. This prevents alarms from triggering and statistics to be strange. I think 2 minutes is a balanced approach; generally batches will take under 10 seconds, so 2 minutes is already more than enough.
Second, we will now clean up the current message on cleanup, not on after commit. This will prevent hanging current latencies on errors.
Third, the commit latency is now the time between ingest of the first message of the batch and the commit time of it. As such, this represents the batch time.