-
Notifications
You must be signed in to change notification settings - Fork 1.4k
config: support configuring jmxfetch status path #25214
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
base: main
Are you sure you want to change the base?
Conversation
5e1b272 to
1872188
Compare
hestonhoffman
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.
Small edit to release note
releasenotes/notes/Expose-JMXFetch-status-path-51d422f36330d076.yaml
Outdated
Show resolved
Hide resolved
Useful information is written in the status.yaml, for example if you are dropping metrics. Add a config option to allow configuring the jmxfetch status path from the DD agent.
1872188 to
0255edd
Compare
|
Hey guys, any idea when this will be merged? |
|
nvm some failed tests |
|
This pull request has been automatically marked as stale because it has not had activity in the past 15 days. It will be closed in 30 days if no further activity occurs. If this pull request is still relevant, adding a comment or pushing new commits will keep it open. Also, you can always reopen the pull request if you missed the window. Thank you for your contributions! |
Useful information is written in the status.yaml, for example if you are dropping metrics. Add a config option to allow configuring the jmxfetch status path from the DD agent.
What does this PR do?
Add a config option to allow configuring the jmxfetch status path from the DD agent.
Motivation
It is useful to be able to access this information without needing to run jmxfetch, for example to see if metrics are being dropped.
Possible Drawbacks / Trade-offs
None that I can think of.
Describe how to test/QA your changes
Just configuring "jmxfetch_status_path" in the config and restarting the unit should result in the status being written there.