According to https://nagios-plugins.org/doc/guidelines.html#AEN200 if a nagios check wants to provide an explicitly undefined value it is able to return U however we have a script that does this and it appears that when accessed through the REST API the value 0 is returned.
Basically create a script that outputs as a command:
OK | label=U%;;;; label2=100%;;;;
Expected Behavior
The API should return "U" as the value so that PNP4Nagios knows to disregard the result and not plot that sample
Actual Behavior
The API returns 0, PNP4Nagios plots 0 and therefore effectively breaks the graph.
Details
NSClient++ version: 0.5.2.41
OS and Version: Windows Server 2012R2 & 2019
Checking from: OMD
Checking with: check_nsc_web
Additional Details
Additionally check_nsc_web does float parse the output, however I am about to raise an issue there with the same problem
Issue and Steps to Reproduce
According to https://nagios-plugins.org/doc/guidelines.html#AEN200 if a nagios check wants to provide an explicitly undefined value it is able to return U however we have a script that does this and it appears that when accessed through the REST API the value 0 is returned.
Basically create a script that outputs as a command:
Expected Behavior
The API should return "U" as the value so that PNP4Nagios knows to disregard the result and not plot that sample
Actual Behavior
The API returns 0, PNP4Nagios plots 0 and therefore effectively breaks the graph.
Details
Additional Details
Additionally check_nsc_web does float parse the output, however I am about to raise an issue there with the same problem