The netbsd_exporter retrieves system metrics such as disk I/O, network I/O, RAM and filesystem usage, as well as CPU load from the running system and exposes them in the format of Prometheus metrics. It is designed to be integrated into inetd, providing a lightweight, NetBSD-focused alternative to the node_exporter.
BSD 2-Clause "Simplified" License
0
stars
0
forks
source link
Change metric: Use labels for load window instead of 3 individual load metrics #5
The snmp_exporter against my Fritzbox returns the load as a
value with labels, so:
laLoadInt{laNames="Load-1"} 10
laLoadInt{laNames="Load-15"} 17
laLoadInt{laNames="Load-5"} 10
The netbsd_exporter has 3 metrics for this:
netbsd_load1 0.059082
netbsd_load5 0.083496
netbsd_load15 0.141113
I find this a bit more convenient with labels, because I can
graph construction I only have to include one metric.
Not a big deal and if you disagree, that's ok too, I just
just wanted to mention it.
The snmp_exporter against my Fritzbox returns the load as a value with labels, so: laLoadInt{laNames="Load-1"} 10 laLoadInt{laNames="Load-15"} 17 laLoadInt{laNames="Load-5"} 10
The netbsd_exporter has 3 metrics for this: netbsd_load1 0.059082 netbsd_load5 0.083496 netbsd_load15 0.141113
I find this a bit more convenient with labels, because I can graph construction I only have to include one metric.
Not a big deal and if you disagree, that's ok too, I just just wanted to mention it.
(Reported by Thomas Klausner)