Ben Kochie

I would be happy to see AIX support added to the node_exporter. I don't think it's that niche, just niche enough that I don't have access to any AIX hardware...

@nigelargriffiths Know anyone willing to donate some POWER hardware to Prometheus?

@thorhs I would like to see it implemented in the node_exporter directly as Go code if we can. The best option would be to have full access to hardware so...

Seems like a good feature to me. To start, we would want to add parsing of this file to the Prometheus procfs library. https://github.com/prometheus/procfs

Yes, we changed the "success" to not be true if the output is empty. Can you dump a `--log.level=debug` to see what is going on?

Ahh, yes, procfs [ignores missing, rather than returning an error](https://github.com/prometheus/procfs/blob/4f613c67c6f5bca1f4cd25e3442c12e21e71c40a/sysfs/system_cpu.go#L152-L161). We could work around this by checking `len(cpuFreqs)`, but we may want to fix this in procfs.

That looks like systemd stopped responding. Can you give more information about the system this is running on? Hardware? VM Hypervisor type?

I wonder if this is something we should add to the exporter-toolkit.

This has been proposed in the past and we have not accepted it.

You don't need to run the exporter as root to gain privileged ports. A normal setcap `CAP_NET_BIND_SERVICE` on the node_epxorter binary should be sufficient. But running on the default port...