[Perfparse-users] Service State

[Tim W. <Tim...@pi...>]

Greetings Programs!
I've been experimenting with perfparse for a few days now, and it's an
impressive start. Here is a suggestion I'd like to make: why don't you store
the service state anywhere? By this I mean the actual exit code as reported
by the plugin. According to the Nagios doc it's available through the
$SERVICESTATE$ macro, so adding it to the serviceperf.log file should not be
a problem. You could then simply store it in the perfdata_service_raw table.

I noticed that you do store a service state in the _bin table, but this is a
(re)calculated value, not the actual exit code (I know it should be the
same). (actually, it's not very clear to me why you recalculate and store it
there anyway, apart from possible slight speed improvement when pulling
reports?)

Storing this value would allow to use the _raw table to do availability
calculations (you could write a UDF for MySQL to do this), so up and
downtimes can be extracted using simple sql statements. This in turn would
make pulling reports out of Nagios easier and more flexible.

My EUR (or $) 0.02

Tim.