Backport Jolokia wildcards support (#6462) to 6.2 #6738
Closed
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
When using wildcards with Jolokia, if multiple mbeans match, they will each one have their own metrics. If we only generate an event each match will overwrite the previous ones. Previous behaviour is kept for Jolokia requests without wildcards, this can be used to compose an only event from multiple specific mbeans.
…etrics A new optional `event` option is added to attribute mappings, so attributes with the same `event` are sent in the same event to Elastic and attributes with different `event` are sent in different events. Some additional related refactorings done to improve type safety.
|
Closing this as it will be backported to 6.3, not to 6.2. |
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.
Backports Jolokia wildcards support (#6462) to 6.2 branch