Why not just extend the command that sends your alerts a bit? Modifying
your notify-by-email (or equivalent) to fire off your own external
script that does what the default behaviour is, adding to it a function
to do your custom work if the $HOSTSTATE$ == CRITICAL.
/eli
Don Lewis wrote:
Very true..very true, wish they would add it myself, this is why we have
yet to have Nagios send notifs to our ticketing system, cause our admins
need to also get the other types pf notifs.
-Don
On Mon, 2006-01-23 at 13:47 -0600, Terry wrote:
Sadly, this is a lot of overhead for such a simple yet useful idea.
On 1/23/06, Don Lewis <[EMAIL PROTECTED]> wrote:
Then yes, I do believe this is what you would have to do, would be to
have 2 same services configured for what is being monitored, each with
it's own settings to send off to ticket systems. One would be with
notification_options=u,w,c,r and the service for the ticket system being
just =c.
This is the only way I know to do that, if you needed to also receive
notifications of recoveries, warning and such separately from the ticket
system.
Would be nice if that was a configurable thing so you could have a
second set of notifs go to another location with just a macro..:)
Does anyone else have any ideas ?
-Don
On Mon, 2006-01-23 at 13:18 -0600, Terry wrote:
The idea behind this is to send a single email for each "problem" to
our ticketting system for auto-creation of a ticket. Sending more
than one email for each problem could create multiple tickets.
On 1/23/06, Don Lewis <[EMAIL PROTECTED]> wrote:
If I'm not mistaken I believe you would have to set the
notification_option for that service to just one status, and if you want
the same service for yourself with different options I believe you would
have to configure 2 seperate services each with differnt
notification_options and contactgroups. If anyone knows different
please elaborate, cause this is the only way I know to do it.
-Don Lewis
On Mon, 2006-01-23 at 12:05 -0600, Terry wrote:
Hello,
I have a contact that I want only to receive a single email of each
issue. I dont want email sent to this contact for status changes.
Only new issues. How can I do this?
Thanks!
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid3432&bid#0486&dat1642
_______________________________________________
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: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
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: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
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
