[Proposal] Adopt weaver for all scraping receivers #40724
Description
Component(s)
No response
Describe the issue you're reporting
As demonstrated by #40698 it is now possible to generate metadata.yaml using Weaver.
The Weaver model can help us define our metrics in a standard manner, include semantic conventions in our metric definitions, generate documentation and downstream artifacts that can help increase the quality of our repository.
This issue aims to discuss adopting Weaver across all scraping receivers. The list of scraping receivers is derived from git grep "metrics:" | grep metadata.yaml | xargs dirname | grep receiver | xargs basename | awk '{print "* "$1}'
- activedirectorydsreceiver
- aerospikereceiver
- apachereceiver
- apachesparkreceiver
- bigipreceiver
- chronyreceiver
- couchdbreceiver
- dockerstatsreceiver
- elasticsearchreceiver
- expvarreceiver
- filestatsreceiver
- flinkmetricsreceiver
- fluentforwardreceiver
- githubreceiver
- googlecloudpubsubreceiver
- haproxyreceiver
- cpuscraper
- diskscraper
- filesystemscraper
- loadscraper
- memoryscraper
- networkscraper
- nfsscraper
- pagingscraper
- processesscraper
- processscraper
- systemscraper
- httpcheckreceiver
- iisreceiver
- k8sclusterreceiver
- kafkametricsreceiver
- kafkareceiver
- kubeletstatsreceiver
- memcachedreceiver
- mongodbatlasreceiver
- mongodbreceiver
- mysqlreceiver
- nginxreceiver
- nsxtreceiver
- ntpreceiver
- opencensusreceiver
- oracledbreceiver
- podmanreceiver
- postgresqlreceiver
- rabbitmqreceiver
- rabbitmqreceiver
- redisreceiver
- riakreceiver
- saphanareceiver
- snmpreceiver
- snowflakereceiver
- solacereceiver
- splunkenterprisereceiver
- sqlserverreceiver
- sshcheckreceiver
- statsdreceiver
- statsdreceiver
- tcpcheckreceiver
- tlscheckreceiver
- vcenterreceiver
- windowsservicereceiver