Invalid perfdata warnings (check_pgactivity) (InfluxDBWriter)

Using the InfluxDBwriter feature, we see the check_pgactivity (https://github.com/OPMDG/check_pgactivity) plugin generating lots of ‘invalid perfdata’ errors in the Icinga main log.

It seems that U (which is here used for an ‘unknown’ value) is indeed an invalid perfdata value according to the nagios guidelines, and it generates this error in logs, such as the one below:

 warning/InfluxdbWriter: Ignoring invalid perfdata for checkable 'host.example.com!postgresql-running-queries' and command 'pgactivity_by_ssh' with value: 'dbname_obscured avg'=Us;900;172800
	(0) Processing check result for 'host.example.com!postgresql-running-queries'

I addressed this issue via a bug report (https://github.com/OPMDG/check_pgactivity/issues/227), and the issue got fixed, so in case of an ‘unknown’ value it returns ‘NaN’ instead of ‘U’.
Unfortunately, the errors persist:

warning/InfluxdbWriter: Ignoring invalid perfdata for checkable 'host.example.com!postgresql-running-queries' and command 'pgactivity_by_ssh' with value: 'dbname_obscured avg'=NaNs;900;172800
	(0) Processing check result for 'host.example.com!postgresql-running-queries'

Some questions:

  • What is causing these errors? Is the plugin still not living up to the Nagios spec, or is something else going on?

  • Is there a way to direct these warning messages out of icinga2.log main log? It is of course convenient to know that plugins are returning invalid perfdata, but the sheer amount of errors makes the icinga2.log difficult to read.

Thanks for any input you may have!

Bas

Please take a look at the guidelines.

Thanks for your reply. I am aware of the Nagios guidelines, and now I see that i somehow mixed up the situation in my original post (don’t ask me why); the situation is exactly opposite: The plugin reports a valid ‘U’ for ‘unknown’, but we still receive these errors
I unfortunately see no option to edit my post, and i dont have permission to delete it.
I’ll just edit and post it again below:

Using the InfluxDBwriter feature, we see the check_pgactivity (https://github.com/OPMDG/check_pgactivity) plugin generating lots of ‘invalid perfdata’ errors in the Icinga main log.

It seems that NaN (which is here used for an ‘unknown’ value) is indeed an invalid perfdata value according to the nagios guidelines, and it generates this error in logs, such as the one below:

 warning/InfluxdbWriter: Ignoring invalid perfdata for checkable 'host.example.com!postgresql-running-queries' and command 'pgactivity_by_ssh' with value: 'dbname_obscured avg'=NaNs;900;172800
	(0) Processing check result for 'host.example.com!postgresql-running-queries'

I addressed this issue via a bug report (https://github.com/OPMDG/check_pgactivity/issues/227), and the issue got fixed, so in case of an ‘unknown’ value it returns ‘U’ instead of ‘NaN’.
Unfortunately, the errors persist:

warning/InfluxdbWriter: Ignoring invalid perfdata for checkable 'host.example.com!postgresql-running-queries' and command 'pgactivity_by_ssh' with value: 'dbname_obscured avg'=U;900;172800
	(0) Processing check result for 'host.example.com!postgresql-running-queries'

Some questions:

  • What is causing these errors? Is the plugin still not living up to the Nagios spec, or is something else going on?
  • Is there a way to direct these warning messages out of icinga2.log main log? It is of course convenient to know that plugins are returning invalid perfdata, but the sheer amount of errors makes the icinga2.log difficult to read.

Thanks for any input you may have!