[receiver/hostmetrics] new scraper in hostmetricsreceiver: nfsscraper

[johnleslie]

Component(s)

hostmetricsreceiver

Describe the issue you're reporting

Suggested scraper nfsscraper will scrape NFS client and server metrics.

Initial version is based on Linux kernel metrics in /proc, but these largely overlap with other OS' NFS metrics including FreeBSD and MacOS/Darwin.

[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.

[braydonk]

Thanks @johnleslie, I support adding this as a scraper in hostmetricsreceiver.

To ease the contribution and review process, I think this should be done in two PRs: Scraper skeleton, and implementation

Skeleton PR:

• Create a new package in hostmetricsreceiver/internal/scraper called nfsscraper
• Implement the skeleton of the scraper (I'd recommend basing this off of the systemscraper which is the most barebones scraper example) with no metrics and without adding it to the main hostmetricsreceiver setup. In the metadata.yaml, make the scraper development stability.

Implementation:

• Implement the scraper so you can validate your planned metric schema. Follow the other scrapers for handling OS-specific behaviours, processscraper has some pretty good examples for this.
• When the scraper is ready, follow the pattern that other scrapers to add it to hostmetricsreceiver/factory.go. This will allow you to run a collector and actually configure the receiver via hostmetrics::scrapers::nfs in the Collector config.
• Submit the PR as a draft, and block it based on the NFS Semantic Conventions being accepted, which we discussed in a separate forum.

Please ensure you look through CONTRIBUTING.md before making the contribution. Feel free to reach out if you run into any issues contributing.

Thanks, looking forward to this!

[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.

Pinging code owners:

• receiver/hostmetricsreceiver: @dmitryax @braydonk

See Adding Labels via Comments if you do not have permissions to add labels yourself.