Add stability level per metric

[ChrsMark]

Component(s)

No response

Describe the issue you're reporting

open-telemetry/opentelemetry-collector#13756 added support for exposing metrics' stability level in the generated documentation.

We should consider start making use of this functionality. Sample PR for hostmetricsreceiver: #42793

If all metrics in contrib explicitly set their stability level we can discuss about making the stability level a required field for metrics. Alternatively, we can think of setting the default stability to development (less aggressive approach): open-telemetry/opentelemetry-collector#13870

Tip

_{React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.}

[Frapschen]

I use this command to filter all metadata.yaml need to set stability level for metrics: find . -name metadata.yaml -exec grep -l "metrics:" {} \;

./scraper/zookeeperscraper/metadata.yaml
./processor/tailsamplingprocessor/metadata.yaml
./processor/probabilisticsamplerprocessor/metadata.yaml
./processor/logdedupprocessor/metadata.yaml
./processor/groupbyattrsprocessor/metadata.yaml
./processor/filterprocessor/metadata.yaml
./processor/groupbytraceprocessor/metadata.yaml
./processor/deltatocumulativeprocessor/metadata.yaml
./processor/k8sattributesprocessor/metadata.yaml
./internal/otelarrow/metadata.yaml
./receiver/splunkenterprisereceiver/metadata.yaml
./receiver/kafkareceiver/metadata.yaml
./receiver/saphanareceiver/metadata.yaml
./receiver/bigipreceiver/metadata.yaml
./receiver/solacereceiver/metadata.yaml
./receiver/elasticsearchreceiver/metadata.yaml
./receiver/hostmetricsreceiver/internal/scraper/processscraper/metadata.yaml
./receiver/hostmetricsreceiver/internal/scraper/loadscraper/metadata.yaml
./receiver/hostmetricsreceiver/internal/scraper/processesscraper/metadata.yaml
./receiver/hostmetricsreceiver/internal/scraper/networkscraper/metadata.yaml
./receiver/hostmetricsreceiver/internal/scraper/nfsscraper/metadata.yaml
./receiver/hostmetricsreceiver/internal/scraper/systemscraper/metadata.yaml
./receiver/hostmetricsreceiver/internal/scraper/cpuscraper/metadata.yaml
./receiver/hostmetricsreceiver/internal/scraper/diskscraper/metadata.yaml
./receiver/hostmetricsreceiver/internal/scraper/filesystemscraper/metadata.yaml
./receiver/hostmetricsreceiver/internal/scraper/memoryscraper/metadata.yaml
./receiver/hostmetricsreceiver/internal/scraper/pagingscraper/metadata.yaml
./receiver/vcenterreceiver/metadata.yaml
./receiver/tlscheckreceiver/metadata.yaml
./receiver/rabbitmqreceiver/metadata.yaml
./receiver/expvarreceiver/metadata.yaml
./receiver/aerospikereceiver/metadata.yaml
./receiver/snowflakereceiver/metadata.yaml
./receiver/nsxtreceiver/metadata.yaml
./receiver/sqlserverreceiver/metadata.yaml
./receiver/ntpreceiver/metadata.yaml
./receiver/couchdbreceiver/metadata.yaml
./receiver/fluentforwardreceiver/metadata.yaml
./receiver/tcpcheckreceiver/metadata.yaml
./receiver/mongodbreceiver/metadata.yaml
./receiver/nginxreceiver/metadata.yaml
./receiver/postgresqlreceiver/metadata.yaml
./receiver/statsdreceiver/metadata.yaml
./receiver/githubreceiver/metadata.yaml
./receiver/kubeletstatsreceiver/metadata.yaml
./receiver/haproxyreceiver/metadata.yaml
./receiver/redisreceiver/metadata.yaml
./receiver/podmanreceiver/metadata.yaml
./receiver/kafkametricsreceiver/metadata.yaml
./receiver/memcachedreceiver/metadata.yaml
./receiver/mysqlreceiver/metadata.yaml
./receiver/sshcheckreceiver/metadata.yaml
./receiver/sqlqueryreceiver/metadata.yaml
./receiver/mongodbatlasreceiver/metadata.yaml
./receiver/filestatsreceiver/metadata.yaml
./receiver/activedirectorydsreceiver/metadata.yaml
./receiver/chronyreceiver/metadata.yaml
./receiver/snmpreceiver/metadata.yaml
./receiver/httpcheckreceiver/metadata.yaml
./receiver/windowsservicereceiver/metadata.yaml
./receiver/dockerstatsreceiver/metadata.yaml
./receiver/googlecloudpubsubreceiver/metadata.yaml
./receiver/apachereceiver/metadata.yaml
./receiver/apachesparkreceiver/metadata.yaml
./receiver/iisreceiver/metadata.yaml
./receiver/oracledbreceiver/metadata.yaml
./receiver/flinkmetricsreceiver/metadata.yaml
./receiver/k8sclusterreceiver/metadata.yaml
./receiver/riakreceiver/metadata.yaml
./connector/servicegraphconnector/metadata.yaml
./connector/grafanacloudconnector/metadata.yaml
./exporter/loadbalancingexporter/metadata.yaml
./exporter/tinybirdexporter/metadata.yaml
./exporter/elasticsearchexporter/metadata.yaml
./exporter/kafkaexporter/metadata.yaml
./exporter/prometheusremotewriteexporter/metadata.yaml
./exporter/sumologicexporter/metadata.yaml
./pkg/stanza/fileconsumer/metadata.yaml

I agree that we can set development as the default stability level, and add a verification rule to the make generate command to require new metrics to explicitly specify their stability level.

[github-actions]

Pinging code owners for receiver/hostmetrics: @dmitryax @braydonk. See Adding Labels via Comments if you do not have permissions to add labels yourself. For example, comment '/label priority:p2 -needs-triaged' to set the priority and remove the needs-triaged label.

[ChrsMark]

I agree that we can set development as the default stability level, and add a verification rule to the make generate command to require new metrics to explicitly specify their stability level.

I think we will need to update all components to explicitly set their stability to development, and then introduce the requirement in mdatagen.