-
Notifications
You must be signed in to change notification settings - Fork 14.8k
KAFKA-19882: Cleaning client level metric tags #20906
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
KAFKA-19882: Cleaning client level metric tags #20906
Conversation
|
@gensericghiro the failure is related - looks like one test missed the constructor update |
mjsax
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the cleanup. LGTM.
bbejeck
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for the fix @gensericghiro! LGTM
|
Merged #20906 into trunk |
## Summary As a follow-up to #20906, also removing the process-id tag from 4.1. This is because when working on KIP-1091, we mistakenly applied the process-id tag to all client-level metrics, rather than just the client-state, thread-state, and recording-level metrics as specified in the KIP. ## Tests Unit tests in `ClientMetricsTest.java` and `StreamsMetricsImplTest.java` Reviewers: Matthias Sax <[email protected]>, Bill Bejeck<[email protected]>
As a follow-up to #20906, also removing the process-id tag from 4.1. This is because when working on KIP-1091, we mistakenly applied the process-id tag to all client-level metrics, rather than just the client-state, thread-state, and recording-level metrics as specified in the KIP. Unit tests in `ClientMetricsTest.java` and `StreamsMetricsImplTest.java` Reviewers: Matthias Sax <[email protected]>, Bill Bejeck<[email protected]>
Summary
When working on
KIP-1091,
we mistakenly applied the
process-idtag to all client-level metrics,rather than just the
client-state,thread-state, andrecording-levelmetrics as specified in the KIP. This issue came tolight while working on KIP-1221, which aimed to add the
application-idas a tag to the
client-statemetric introduced by KIP-1091. This PRremoves these tags from all metrics by default, and adds them to only
the
client-state(application-id + process-id) and therecording-level(process-id only)Reviewers: Matthias Sax[email protected] Bill
Bejeck[email protected]
Tests
Unit tests in
ClientMetricsTest.javaandStreamsMetricsImplTest.java