Closed jspaleta closed 1 year ago
Pinging code owners: @dmitryax. See Adding Labels via Comments if you do not have permissions to add labels yourself.
Thanks for the detailed report. I know that metrics 6 and 7 in your list will be added in https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/12972.
Thanks @jspaleta for writing this up.
Here's the proposal to add the first metric (page faults) to the semantic conventions spec: https://github.com/open-telemetry/opentelemetry-specification/issues/2809.
This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers
. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.
Pinging code owners:
See Adding Labels via Comments if you do not have permissions to add labels yourself.
This issue has been closed as inactive because it has been stale for 120 days with no activity.
Is your feature request related to a problem? Please describe. Found while migrating from telegraf based collection to otelcol, several process metrics are missing in the otelcol hostmetrics process scraper.
Describe the solution you'd like Implement additional metrics in the hostmetrics process scraper to bring metrics coverage closer to parity with telegraf procstat. All the missing metrics are derived from gopsutil package.
Additional context While migrating supported SumoLogic dashboard apps from using telegraf based fields to otelcol native metrics names, several metrics appear to be missing from otelcol native receivers. The metrics listed are an identified subset of differences between telegraf procstat and the hostmetrics process scraper.
missing metrics
Suggested name: process.num_fds
Suggested name: process.read_count
Suggested name: process.write_count