We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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/hostmetrics
process.cpu.utilization optional metric is not scraped if process.cpu.time is disabled.
process.cpu.utilization
process.cpu.time
Enable hostmetricsreceiver with process.cpu.time disabled and process.cpu.utilization enabled:
hostmetricsreceiver
receivers: hostmetrics: collection_interval: 20s scrapers: process: metrics: process.cpu.utilization: enabled: true process.cpu.time: enabled: false
process.cpu.utilization metric should be sent.
process.cpu.utilization metric is not sent.
5fff104
OS: Ubuntu 20.04, Macos 13.4 Compiler: go 19.1
No response
While debugging this I created a PR that fixes the bug. Feel free to review and merge it :)
#23451
The text was updated successfully, but these errors were encountered:
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself.
Sorry, something went wrong.
Fixed in #23451
No branches or pull requests
Component(s)
receiver/hostmetrics
What happened?
Description
process.cpu.utilization
optional metric is not scraped ifprocess.cpu.time
is disabled.Steps to Reproduce
Enable
hostmetricsreceiver
withprocess.cpu.time
disabled andprocess.cpu.utilization
enabled:Expected Result
process.cpu.utilization
metric should be sent.Actual Result
process.cpu.utilization
metric is not sent.Collector version
5fff104
Environment information
Environment
OS: Ubuntu 20.04, Macos 13.4
Compiler: go 19.1
OpenTelemetry Collector configuration
Log output
No response
Additional context
While debugging this I created a PR that fixes the bug. Feel free to review and merge it :)
#23451
The text was updated successfully, but these errors were encountered: