Sorry if this is too little too late, but I have a real-life Nagios
system which does start issues in a tracking system when a host goes
down (via email). Here is a quick rundown of my solution (which may be
extended to services):
I have a command def. like this:
define command{
command_name host-mail-to-tracker
command_line [ $NOTIFICATIONTYPE$ = "PROBLEM" ] &&
/usr/bin/printf "%b" "{a bunch of stuff for the content}" | /bin/mail -s
"{a bunch of stuff for the issue heading}" $CONTACTEMAIL$
}
..a contact def. like this:
define contact {
contact_name tracker
alias Tracker Contact
email {email address
needed to start a an issue}
service_notification_options w,c
host_notification_options d
host_notification_commands host-mail-to-tracker
... {whatever else goes here}
}
This contact is setup in the contactgroup "trackers"
In my case, I do not start an issue right away--I give it 5 minutes then
use a hostescalation like this:
define hostescalation {
hostgroup_name {hosts to be tracked in system}
first_notification 2
last_notification 2
contact_groups trackers
}
--but you could make that the first notification, 5th notification,
whatever.
The only problem with carrying this over to services is that you have to
start issues for both warning and critical states. I have not found a
slick way to find out if a notification is the "First Critical". If
*any* Problem state warrants an issue, you would be fine extending this
concept to services.
Marc
-------------------------------------------------------
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
Nagios-users@lists.sourceforge.net
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
