custom jmxfetch bean to track number of ingested beans, attributes, and metrics #472
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
…nd metrics (#453) * added bean that tracks number of ingested beans * restructured bean creation * reverted compiler version * updated some formatting * cleaned up some formatting * simplified quoting process * removed constructor argument from jmxFetchTelem * fixed formatting * updated spacing * cleaned up debug logs * fixed long lines * updated naming * removed java object debug
scottopell
approved these changes
Aug 10, 2023
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.
This pr is part of a multi stage process to increase observability within jmxfetch. Another pr adds a check that uses proccess_regex to attach to jmxfetch's jvm in order to collect mbean data from our own application. In this pr I have added jmx MBeans that are registered for each instance of jmxfetch and track the number of beans, metrics, and attributes that each instance collects and exposes this under the jmxFetch domain where the check from my other pr will be able to pick up this data in addition to general jmfetch metrics.