The way Nagios knows whether something is critical or warning is based on
the exit code so if you look in chec_ganglia_metric.sh you could change
WARNING)
echo $RESULT
exit 1;;
CRITICAL)
echo $RESULT
exit 2;;
to say
WARNING)
echo $RESULT
exit 1;;
CRITICAL)
echo $RESULT
exit 1;;
basically change CRITICAL into WARNING exit code. That would be the
quickest hack.
Vladimir
On Thu, 28 Feb 2013, Maciej Lasyk wrote:
Hi,
I'm trying to integrate Nagios with Ganglia. I stucked in one place and somehow
can't find a solution.
Based on Ganglia Book, chapter 7, "Check a Single Metric on a Specific Host" we
can set a check_command like below:
check_ganglia_metric!load_one!more!5
And it is said that:
"The operators specified in the Nagios definitions for the Ganglia plug-
ins always indicate the “critical” state. If you use a notequal operator, it
means that state is critical if the value is not equal."
Now.. I'm trying to set a 'warning' state not critical. And can't find
"out-of-the-box" solution - even on the authors
webpage http://vuksan.com/linux/nagios_scripts.html
I assume that I should write my own hooks for this. Could you tell me how You
do It?
Regards,
Maciej Lasyk
GPG public key: http://maciek.lasyk.info/gpg_maciej_lasyk.asc
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________
Ganglia-general mailing list
Ganglia-general@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/ganglia-general
