-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
[receiver/hostmetricsreceiver] Add threads count metric #12802
Conversation
Is this metric important enough to be enabled by default? It'll be a breaking change and will change amount of data that users collect and send to backends by default after upgrade. I think this should be an optional metric |
Made it optional, thanks for the feedback! |
66ea504
to
b6bee3a
Compare
This receiver has all the metrics defined in semantic conventions. This new metric should also be submitted there first even if it's optional, just to avoid further changes if this PR is merged first |
Opened this PR to update the specification open-telemetry/opentelemetry-specification#2705 |
ca55042
to
1552f3b
Compare
This PR was marked stale due to lack of activity. It will be closed in 14 days. |
1552f3b
to
2f0b530
Compare
2f0b530
to
55d3a17
Compare
receiver/hostmetricsreceiver/internal/scraper/processscraper/metadata.yaml
Outdated
Show resolved
Hide resolved
receiver/hostmetricsreceiver/internal/scraper/processscraper/process_scraper.go
Show resolved
Hide resolved
receiver/hostmetricsreceiver/internal/scraper/processscraper/metadata.yaml
Show resolved
Hide resolved
fde9a85
to
ea7ddc5
Compare
ea7ddc5
to
1bde002
Compare
Description:
Add threads count metric to hostmetricsreceiver.
Link to tracking Issue:
#12482
Testing:
Supported with mock as part of unit tests, checking error is reported.
Documentation:
Addition to documentation of the new metric.