Skip to content

Conversation

@facetoe
Copy link

@facetoe facetoe commented Apr 28, 2024

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.

@facetoe facetoe requested review from a team as code owners April 28, 2024 11:29
@facetoe facetoe requested a review from a team April 28, 2024 11:29
@bits-bot
Copy link
Collaborator

bits-bot commented Apr 28, 2024

CLA assistant check
All committers have signed the CLA.

@github-actions github-actions bot added this to the Triage milestone Apr 28, 2024
@facetoe facetoe force-pushed the jmxfetch_status_path branch from 5e1b272 to 1872188 Compare April 28, 2024 11:33
Copy link
Contributor

@hestonhoffman hestonhoffman left a 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

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.
@facetoe facetoe force-pushed the jmxfetch_status_path branch from 1872188 to 0255edd Compare April 30, 2024 00:55
@facetoe
Copy link
Author

facetoe commented Jun 24, 2024

Hey guys, any idea when this will be merged?

@facetoe
Copy link
Author

facetoe commented Jun 24, 2024

nvm some failed tests

@facetoe facetoe marked this pull request as draft June 24, 2024 02:18
@dd-octo-sts
Copy link
Contributor

dd-octo-sts bot commented Oct 18, 2025

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!

@dd-octo-sts dd-octo-sts bot added the stale label Oct 18, 2025
@jacjtito jacjtito removed the stale label Dec 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants