Move consumer lag monitoring to separate thread with per-partition#707
Open
Move consumer lag monitoring to separate thread with per-partition#707
Conversation
…eakdown The lag computation (get_watermark_offsets + position for each partition) was running inside the consume loop, blocking message consumption for up to N_partitions * 1.0s every 30 seconds. This caused lag to accumulate during metrics logging. - Move lag computation to a dedicated daemon thread that runs independently - Reduce watermark query timeout from 1.0s to 0.1s per partition - Log per-partition lag breakdown (partition_lags) to identify which topics contribute most to the total lag Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Logs total events, total messages, and per-source event counts every 30 seconds from KafkaToEv44Adapter. This helps correlate event rates with consumer lag to identify which detectors contribute most data. Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
Member
|
Could you remove the ev44 from this branch? We wouldn't want to do both here. |
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
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.
No description provided.