At work we switched from Nagios to Icinga some while ago. Back when we were
using Nagios I wrote some shell functions which allowed scripts to disable
and later reenable various checks. For example, if a service needed to be
taken down for a short while but was going to take more than a few seconds
to bounce, the activity might look like this:
nagios DISABLE host 'Service Name'
do the deed
nagios ENABLE host 'Service Name'
After a little bit of input massage, the nagios function boiled down to a
curl command:
curl -d cmd_typ=${cmd} \
-d cmd_mod=2 \
-d host=${host} \
-d service=${svc} \
-d btnSubmit=Commit \
-s \
-u 'user:pass \
"http://nagios.server/nagios/cgi-bin/cmd.cgi";
When we switched to Icinga, I updated the URL to refer to the new server.
Everything seems to work. I get a 200 response from the server, but the
commands have no effect.
Has something changed about this (admittedly fragile, and probably
unsupported) "API"? Is there a more kosher way to achieve the same result
with Icinga, perhaps a supported Web API?
Thanks,
--
Skip Montanaro - s...@pobox.com - http://www.smontanaro.net/
------------------------------------------------------------------------------
Better than sec? Nothing is better than sec when it comes to
monitoring Big Data applications. Try Boundary one-second
resolution app monitoring today. Free.
http://p.sf.net/sfu/Boundary-dev2dev
_______________________________________________
icinga-users mailing list
icinga-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/icinga-users
