Feature Request: Additional External Commands for Managing Scheduled Downtime

Hendrik Baecker andurin at process-zero.de
Thu Mar 26 07:02:30 CET 2009


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1



Bryan Dove schrieb:
> I would really like to see additional external commands for managing downtime.
> 
>     * DEL_HOSTGROUP_HOST_DOWNTIME
>     * DEL_HOSTGROUP_SVC_DOWNTIME
>     * DEL_SERVICEGROUP_HOST_DOWNTIME
>     * DEL_SERVICEGROUP_SVC_DOWNTIME
>     * DEL_HOST_SVC_DOWNTIME
> 
> These commands would parallel their equivalent commands for initiating
> scheduled downtime, but would be used to delete batches of scheduled
> downtime (e.g. when you finish maintenance early).
> 

Hi Bryan,

that might be a problem, because each groupdowntime breaks down into
single Host/Service downtimes on insert.
After the external group downtime command is processed a bunch of new
downtime ids is generated for each host or service. Deletions currently
works currently with the usage of that id.
Sure, it is possible to grep all downtime IDs for a grouping downtime
from the past and bulk delete them, but if you think about having more
than one downtime at a time, f.e. maintenance at the begin of a month
and another in the middle of that month, you'll get into problems if you
delete both of them.

We got a workaround for that. We are using some small shellscripts to
generate an external command against a servicegroup for example and we
add a uuid (http://www.manpagez.com/man/1/uuidgen/) to the comment line
for nagios and save us that uuid.
After maintenance another script executes the downtime cgi localy (not
via web) and greps out all downtime IDs for a particular UUID, generate
a bunch of external commands to delete the downtimes.

If you, or someone else, is interested in that workaround I will post
that creepy workaround.

Regards,
Hendrik
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.8 (Darwin)

iEUEARECAAYFAknLGnYACgkQlI0PwfxLQjnNqgCXSkz+KH3lHy3+VwdlhVQbDzoW
twCfS/UStuDuibBhkpXtow4QThmSMnQ=
=3tHt
-----END PGP SIGNATURE-----

------------------------------------------------------------------------------




More information about the Developers mailing list