Skip to content

jmx scraper: add missing relevant config options #1979

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

Merged
merged 4 commits into from
Jun 30, 2025

Conversation

SylvainJuge
Copy link
Contributor

Description:

jmx-scraper relies on the SDK and thus supports most of the SDK configuration options.

The otel.service.name and otel.resource.attributes are commonly used and were missing from documentation, this PR adds them.

Copy link
Contributor

@breedx-splk breedx-splk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

One small comment, the phrasing was a little clunky as well, but fine. This might need a rebase after we figure out the markdown link check stuff.

Co-authored-by: jason plumb <75337021+breedx-splk@users.noreply.github.com>
@trask
Copy link
Member

trask commented Jun 30, 2025

@SylvainJuge ignore the link check failure, but can you check out the "lint" check failure?

@breedx-splk
Copy link
Contributor

@SylvainJuge ignore the link check failure, but can you check out the "lint" check failure?

I thinks that's on me....my suggestion had some junk in it. Fixing.

@trask trask enabled auto-merge June 30, 2025 20:14
@trask trask added this pull request to the merge queue Jun 30, 2025
Merged via the queue into open-telemetry:main with commit 88f07b6 Jun 30, 2025
29 of 30 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants