[Nagios-devel] Nagios plugin real execution date (for performance data)

Support forum for Nagios Core, Nagios Plugins, NCPA, NRPE, NSCA, NDOUtils and more. Engage with the community of users including those using the open source solutions.
Locked
Guest

[Nagios-devel] Nagios plugin real execution date (for performance data)

Post by Guest »

Hi !

This is rather for perfparse-devel, but the question may concern nagios-d=
evel so I post
there too.

When a plugin ends, we have the execution date in $TIMET$ macro of the pl=
ugin. That date
is usually the date when the plugin got the data.

However, there are cases when the data is somewhere (in a log file for ex=
ample) with a
timestamp, and the plugin gets the data with the timestamp. In such a cas=
e, I don't need
the date from $TIMET$, but the timestamp that the plugin scanned.

For perfparse, there is an easy way to do it: the plugin can return the t=
imestamp as
performance data, for example:
plugin output | TIMET=3D1093338402 key1=3Dvalue1;warn1;crit1
key2=3Dvalue2UOM;warn2;crit2;min2;max2 ...

With such a line, perfparse would understand that it has to take the valu=
e from the
plugin TIMET performance data and not from the nagios $TIMET$ macro. TIME=
T would become
a keyword for perfparse. This can also become a specification for perform=
ance data in
nagios.

Guys at perfparse project, do you think that I can implement this ?
Guys at nagios project, is this the way to do it, or is there a better wa=
y ?

Yves (coder on perfparse)


--=20
- Homepage - http://ymettier.free.fr - http://www.logicacmg.com -
- GPG key - http://ymettier.free.fr/gpg.txt -
- Maitretarot - http://www.nongnu.org/maitretarot/ -
- GTKtalog - http://www.nongnu.org/gtktalog/ -








This post was automatically imported from historical nagios-devel mailing list archives
Original poster: [email protected]
Locked