Expose jmxfetch "initial refresh beans period" config. #2659
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
|
FYI the build failure doesn't seem to be related to this PR |
essobedo
changed the title
tylerbenson
changed the title
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.
Motivation
A new feature has been added to jmxfetch allowing to have a configurable period for the 1st bean refresh (for more details, please refer to the related PR DataDog/jmxfetch#349), the goal of this PR is to propagate the required changes to benefit from this new feature in the Java Agent
Modifications:
jmxfetch.initial-refresh-beans-periodto be able to set the valueResult
It is now possible to easily set a period for the 1st bean refresh from the Java Agent thanks to a System property