Adding producer latency to Message Delivery Report #1076
Conversation
This file contains 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
Adding the ProducerLatency Metric where all other portions are added. Small test to make sure that producer latency is correctly added
|
|
|
|
6 tasks
|
Are there any plans to merge this from Kafka team? We also faced this problem in our systems |
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.
Originally in response to this message, and better metrics internally.
#425 (comment)
Background:
Our internal applications measure producer latency, by consuming directly from the topic and producing a diff of the message timestamp, and the event timestamp. Exposing the Producer Latency directly to the delivery report will help prevent having an unnecessary consumer to report on Producer Latency.