Cant Calculate % DISK or SWAP Free / Used with Native Nagios Plugin, PNP and Grafana about grafana-pnp-datasource HOT 4 CLOSED

In your case MAX would be the right choice i guess. According to
https://www.monitoring-plugins.org/doc/guidelines.html#AEN201
the syntax is 'label'=value[UOM];[warn];[crit];[min];[max].
There is no such thing as total_size.

from grafana-pnp-datasource.

Thanks for the response.
I try to use MIN or MAX but in the query inspector the value is the same with Avarage. If I use WARNING or CRITICAL the value is correct.

In Nagios perfdata the Value MAX Exist:

Could the problem be that PNP4Nagios changes the MAX Value to the Maximum value recorded in the sampling period?

In the perfdata file there are the information about MAX
DATATYPE::SERVICEPERFDATA TIMET::1664486591 HOSTNAME::xxxxxxx SERVICEDESC::[COLLAUDO] - SO Admin - Agent NRPE - Check Swap Usage SERVICEPERFDATA::swap=1808MB;198;39;0;3967 SERVICECHECKCOMMAND::check_nrpe_args!check_swap!5%!1% HOSTSTATE::UP HOSTSTATETYPE::HARD SERVICESTATE::OK SERVICESTATETYPE::HARD

In the XML from PNP4Nagios the Value MAX is Present (erase Hostname for security)

from grafana-pnp-datasource.

I Resolve the problem.

In the api.php there are only configuration for Warning and Critical and I add it MAX Value.

This code modify:

$perflabels[] = array(
"label" => arr_get($value, "NAME" ),
"warn" => arr_get($value, "WARN" ),
"crit" => arr_get($value, "CRIT" ),
"max" => arr_get($value, "MAX" )
);

AND this

        foreach ( $xpd->data->row as $row=>$value){
          // timestamp in milliseconds
          $timestamp = ( $start + $i * $step ) * 1000;
          if($type == "WARNING") {
            $d = floatval($tmp_perflabel['warn']);
          } elseif($type == "CRITICAL") {
            $d = floatval($tmp_perflabel['crit']);
          } else {
            $d = floatval($tmp_perflabel['max']);
          }
          $data['targets'][$key][$hk]['datapoints'][] = array( $d, $timestamp );
          $i++;
        }

The Issue can be closed

from grafana-pnp-datasource.

is this something that needs to be fixed in the api.php from pnp4nagios? If so, could you please provide a patch?

from grafana-pnp-datasource.