I assume that there wouldn't be a macro for it due to the fact that it
is normally up to the plugin / service check to determine and know what
the thresholds are in order to know what exit code to return back to Nagios.
Your best chance may be to define those values as service macros. That
way you would be able to pass them through to your plugin (assuming your
plugin accepts WARN and CRIT as command line args) as well as your
notification command (possibly a special secondary notification command
that adds the WARN and CRIT macro values to the message).
On 08/09/2010 01:31 PM, Joel Brooks wrote:
hey all,
is there a way to include the WARNING and CRITICAL thresholds in a
notification (without including the perfdata)?
There doesn't seem to be a macro for this.
i.e., i'd like my notification to show something like:
<body of email notification>
$SERVICEDESC$ is in $SERVICESTATE$ condition.
$SERVICEOUTPUT$
Current: $SERVICEVAL$ (Warning: $SERVICEWARNING$, Critical:
$SERVICECRITICAL$)
is there a way to do something like that?
cheers,
J
------------------------------------------------------------------------------
This SF.net email is sponsored by
Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________
Nagios-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting
any issue.
::: Messages without supporting info will risk being sent to /dev/null
------------------------------------------------------------------------------
This SF.net email is sponsored by
Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________
Nagios-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting
any issue.
::: Messages without supporting info will risk being sent to /dev/null
