- name: node-exporter
- description: Prometheus exporter for hardware and OS metrics exposed by *NIX kernels, written in Go with pluggable metric collectors.
- snapcraft: link to snapcraft.yaml if publicly available
- upstream: GitHub - prometheus/node_exporter: Exporter for machine metrics
- upstream-relation: None
- interfaces:
- <proc-sys-kernel-random>:
- request-type: auto-connection
- reasoning: We need this interface as a temporary workaround to access specific files that node-exporter need to read in order to be able to export host’s metrics. I say
temporarybecause we are working with the snapd team to modify/create some interfaces that will give us the possibility to run node-exporter in a strictly confined mode.
- <proc-sys-kernel-random>:
This request has been added to the queue for review by the @reviewers team.
Hey @Abuelodelanada
The change was merged and will be available with next snapd release. Is there any really good reason to go for this workaround rather than waiting for the change in system-observe to be live? (#askForInfo)