Review units of telemetry in metadata.yaml telemetry

[crobert-1]

Component(s)

No response

Describe the issue you're reporting

This is the contrib equivalent issue for open-telemetry/opentelemetry-collector#10556

Many metrics defined in components' metadata.yaml files have the unit of 1. This isn't meaningful or helpful to users. These metrics should be reviewed to determine a more informative unit.

Here's the list of components that currently have at least one metric with the unit of 1:

• connector/grafanacloudconnector
• connector/servicegraphconnector
• exporter/lokiexporter
• exporter/prometheusremotewriteexporter
• exporter/sumologicexporter
• pkg/stanza/fileconsumer
• processor/filterprocessor
• processor/groupbyattrsprocessor
• processor/groupbytraceprocessor - [processor/groupbytrace] Update metric units #34167
• processor/k8sattributesprocessor
• processor/probabilisticsamplerprocessor
• receiver/bigipreceiver
• receiver/dockerstatsreceiver
• receiver/elasticsearchreceiver
• receiver/expvarreceiver
• receiver/fluentforwardreceiver
• receiver/hostmetricsreceiver/internal/scraper/cpuscraper
• receiver/hostmetricsreceiver/internal/scraper/filesystemscraper
• receiver/hostmetricsreceiver/internal/scraper/memoryscraper
• receiver/hostmetricsreceiver/internal/scraper/pagingscraper
• receiver/hostmetricsreceiver/internal/scraper/processscraper
• receiver/httpcheckreceiver
• receiver/kafkametricsreceiver
• receiver/kafkareceiver
• receiver/kubeletstatsreceiver
• receiver/mongodbatlasreceiver
• receiver/mongodbreceiver
• receiver/mysqlreceiver
• receiver/oracledbreceiver
• receiver/otelarrowreceiver
• receiver/podmanreceiver
• receiver/postgresqlreceiver
• receiver/redisreceiver
• receiver/snmpreceiver
• receiver/snowflakereceiver
• receiver/solacereceiver
• receiver/sshcheckreceiver
• receiver/statsdreceiver
• receiver/zookeeperreceiver

[github-actions]

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.