Fixed JMX exporter config for kafka server quota metrics for users and clients #801
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.
What's in this PR?
When setting Kafka quotas, user level only quota metrics would not be properly caught by the JMX config and would end up in a catch-all rule (instead of the quota specific ones). As such I added a new JMX rule that captures quota metrics for user only quota (default-entity) and rearranged the rules to properly catch all cases (<user, clientId>, , ).
Checklist