Node-exporter: autoconnect interfaces

Hello @jslarraz @cav

This request goes in tandem with this one for OpenTelemetry-collector

  • name: node-exporter
  • description:Exporter for hardware and OS metrics exposed by *NIX kernels, written in Go with pluggable metric collectors.
  • snapcraft: node-exporter-snap/snap/snapcraft.yaml at master · canonical/node-exporter-snap · GitHub
  • upstream: GitHub - prometheus/node_exporter: Exporter for machine metrics
  • upstream-relation: no formal relation
  • interfaces:
    • <hardware-observe>:
      • request-type: auto-connection
      • reasoning: The node-exporter snap uses this interface to be able to read and export hardware metrics.
    • <mount-observe>:
      • request-type: auto-connection
      • reasoning: The node-exporter snap uses this interface to be able to read and export metrics about mount points and quotas
    • <network-observe>:
      • request-type: auto-connection
      • reasoning: The node-exporter snap uses this interface to be able to read and export network metrics.
    • <system-observe>:
      • request-type: auto-connection
      • reasoning: The node-exporter snap uses this interface to be able to read and export process and system info metrics
    • <time-control>:
      • request-type: auto-connection
      • reasoning: The node-exporter snap uses this interface to be able to read and export query system date and time.

This request has been added to the queue for review by the @reviewers team.

Linking the grafana-agent topic for reference.

+1 (#voteFor) from me for granting auto-connection of these interfaces given the description provided (similar to grafana-agent).

1 Like

I also #voteFor granting auto-connection to the requested interfaces. Those align with the expected functionality and precedents (grafana-agent)

+2 votes for, 0 votes against, granting auto-connect of hardware-observe, mount-observe,network-observe, system-observe, and time-control to node-exporter. This is now live.

1 Like