Ben Kochie

I take it that means the error doesn't occur every scrape? How often does this error get reported?

Thanks @hoffie. If this was a consistent problem where it always returned ``, it would be something to make an effort to patch. But if it's a random/occasional error that...

Thanks for the detailed info. Yes, improving things in the procfs code would be the right place.

@discordianfish I kinda feel like this should live in the netdev collector. No need add yet another network-related collector.

A collector-specific boolean flag would work. We could have it off by default. `--collector.netdev.address-info`

Netdev, netclass, netstat, etc are are artifacts of Linux. BSDs use syscalls instead of parsing /proc/net/dev, but they're still in the netdev collector. This is all about network device level...

There is an issue for Golang support for AIX, it looks like there is work in progress, but it is not complete.

Nice! We will need to add AIX to the build tool, [promu](https://github.com/prometheus/promu).

Someone with access knowledge of AIX will have to implement collector implementations for additional metric. I have neither, so I can't help.

For reference, the IBM documentation on this: https://www.ibm.com/support/knowledgecenter/ssw_aix_72/performancetools/idprftools_perfstat.html