I should mention: I took every cell number address (ex. 15551234...@carrier.net) and added them as a contact in Active Directory. Then I created an alias which forwards to that contact (ex. em...@company.com) and Nagios uses this to send messages out.
I am in the process of ordering a PC and iSMS box to dedicate to Nagios and get it out of the server room. -----Original Message----- From: Dr. Ed Morbius [mailto:dredmorb...@gmail.com] Sent: Thursday, February 17, 2011 2:58 PM To: nagios-users@lists.sourceforge.net Subject: Re: [Nagios-users] Nagios Alert Format? Possible alternate solution: Does your cell phone and/or carrier provide MMS service? Messages will arrive in a format more similar to email, with more context, etc. You still could benefit by rewriting the standard Nagios alerts (which I find to be rather uninformative), but could avoid other limitations of SMS (160 character limit, etc.). on 12:59 Thu 17 Feb, Engelmann, Austin (aengelm...@libertymgt.com) wrote: > This is a small question. I have been editing the Nagios alert commands > to get a nice, simple format to our cell phones. I am trying to get the > notification type to be on the "MSG:" line. In my command, the > notification type always gets place on the next line. My current command > and the format of the SMS alert are listed below, anybody see what I can > change and if it's possible? > > > > #'notify-service-by-email' command definition > > define command{ > > command_name notify-service-by-email > > command_line /usr/bin/printf "%b" > "$NOTIFICATIONTYPE$\nSVC: $SERVICEDESC$\nHost: $HOSTALIAS$\nState: > $SERVICESTATE$\n$SERVICEOUTPUT$" | /bin/mail -s "Service Alert" > $CONTACTEMAIL$ > > } > > > > FRM:nagiosadmin > > SUBJ:Service Alert > > MSG: > > RECOVERY > > SVC: Ping Test > > Host: Hostname > > State: OK > > PING OK - Packet loss = 0%, > > RTA = 14.29 ms > > > > Austin > > > > ------------------------------------------------------------------------ ------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > _______________________________________________ > 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 -- Dr. Ed Morbius, Chief Scientist / | Robot Wrangler / Staff Psychologist | When you seek unlimited power Krell Power Systems Unlimited | Go to Krell! ------------------------------------------------------------------------ ------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ 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 ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ 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