Performance Data of check_snmp_raritan about health_monitoring_plugins HOT 6 CLOSED

Found the following guideline for nagios:

https://www.monitoring-plugins.org/doc/guidelines.html#AEN201

UOM...value...

from health_monitoring_plugins.

A, V, W etc. are not officially allowed UOMs. But pnp4nagios is happy with it.
Maybe I could move the UOMs to the label.

from health_monitoring_plugins.

oh, that would be so nice!

i get the following from the icinga service:

Nov 21 16:23:23 tux icinga2[25016]: Ignoring invalid perfdata value: 'Sensor 3'=955.0VA;0.0:0.0;0.0:0.0;;
Context:
(0) Processing check result for 'PDU1!PDU Health'...
Nov 21 16:23:23 tux icinga2[25016]: Ignoring invalid perfdata value: 'Sensor 5'=430330.0Wh;0.0:0.0;0.0:0.0;;
Context:
(0) Processing check result for 'PDU1!PDU Health'...
Nov 21 16:23:23 tux icinga2[25016]: Ignoring invalid perfdata value: 'Sensor 6'=50.0Hz;0.0:0.0;0.0:0.0;;
Context:
(0) Processing check result for 'PDU1!PDU Health'...

from health_monitoring_plugins.

Icinga2's GraphiteWriter actually validates if a unit is one of the allowed ones (in contrast to Icinga 1 and pnp4nagios), and ignores it if not. Moving units to the label as @rsmuc suggests seems straight and clean for now.

It's a pity to loose explicit unit information anyway. Icinga 2 guys are aware of the problem (Icinga/icinga2#6071) and are considering a "new plugin API" as foundation to solve it. If we wanted the units back we should probably contribute there.

from health_monitoring_plugins.

@crsprsp could you try the version from branch 0.1.0? that should fix your issue.

from health_monitoring_plugins.

seems to work! very good!!!

from health_monitoring_plugins.