Hi all,
I wonder how to inform perfparse about lower bound thresholds.
Monitoring load, disk usage or temperatures are no issues, because the
values for warn and crit are in normal operation greater than the actual
value.
But, when perfparse processes perfdata of check_swap (reports how many
bytes are free) or a plugin that checks fan speeds, the values for warn
and crit are less than the actual value. On the perfparse overview page
they are marked as critical.
Especially for a plugin that returns fan speeds it is hardly possible to
invert the semantics from within the plugin to make perfparse behave
correctly.
Maybe, I am just missing something?!
thanks for ideas and best regards,
Rene
|