This is a multi-part message in MIME format.
------_=_NextPart_001_01C8E069.103E10B0
Content-Type: multipart/alternative;
boundary="----_=_NextPart_002_01C8E069.103E10B0"
------_=_NextPart_002_01C8E069.103E10B0
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
This is the exact situation an eventhandler is meant for. Why would you =
want to go creating another method when the logic is already laid out =
for you? At best you could have the plugin spit out the name of the =
flag file to be removed so your eventhandler could do an rm -f filename =
or however you want to go about it.
=20
Stephen Valdinger
MIS Helpdesk Coordinator
330.365.3622 -O
740.491.0958 - C
[email protected]
=20
_____ =20
From: Xavier LEVRAT [mailto:[email protected]]=20
Sent: Monday, July 07, 2008 11:11 AM
To: [email protected]
Subject: [Nagios-devel] [NAGIOS-DEVEL] trigger a plugin on acknowledge
=20
Hi List !=20
We'd like to trigger a plugin when we acknowledge a service problem. We =
don't want to use a eventhandler because this operation has to be =
manual. (ex : When a flag file is present in a directory, nagios raises =
a service problem. Acknowledging this problem will trigger a plugin that =
do a rm on the file.)
Is it possible to do it with the curent NAGIOS logic ?=20
I 've started writing a patch to add a 'acknowledge_handler' directive =
in the service definition, but I don't like the idea of using a custom =
NAGIOS on a production sytem ...
Thx
Xavier
=20
_____ =20
Envoy=E9 avec Yahoo! Mail =
.
Une boite mail plus intelligente.=20
------_=_NextPart_002_01C8E069.103E10B0
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
This is the exact situation an
eventhandler is meant for. Why would you want to go creating another =
method
when the logic is already laid out for you? At best you could have=A0 =
the plugin
spit out the name of the flag file to be removed so your eventhandler =
could do
an rm –f filename =
or however you
want to go about it.
<font size=3
...[email truncated]...
This post was automatically imported from historical nagios-devel mailing list archives
Original poster: avier LEVRAT [mailto:[email protected]]=2