Re: [Nagios-users] check_http with multiple outcomes?
Terry: on 23:37 Mon 08 Aug, Terry Carmen (te...@cnysupport.com) wrote: Quoting Edward Morbius dredmorb...@gmail.com: When some things are going well and others aren't fully up to speed (slow database), we'll get a DATABASE_TEST_RAN_LONG, which isn't ideal, but at least for a few occurances (n = 5) we can live with. In particular, we DON'T want a single result sounding off pagers in the middle of the night. You can specify -e OK,DATABASE_TEST_RAN_LONG, then let the plugin decide if it's slow or not, with the -w, -c and -t parameters. Terry Thanks. I'd considered that. It doesn't quite match what we want to test. I'm thinking we may need to have a few different tests, possibly related to one another. If there's a 4xx/5xx error, it's a hard fail. If there's no 4xx/5xx error, but we get the DATABASE_TEST_RAN_LONG result, it's a soft fail, turning hard on 6 repeats. That string appears in our application, it's not a nagios-determined slowness. Alternately, we might want to have a separate test for DB performance (there may well be, I'm still digging through rules and tests). If there's an OK result, there's no error. The 4xx/5xx errors are exclusive of the other two possible results. If there's no 4xx/5xx error, we've got the option of either of the other two conditions. So: is this a three-check test? How would I set precedence among them? -- Dr. Ed Morbius, Chief Scientist /| Robot Wrangler / Staff Psychologist| When you seek unlimited power Krell Power Systems Unlimited| Go to Krell! -- uberSVN's rich system and user administration capabilities and model configuration take the hassle out of deploying and managing Subversion and the tools developers use with it. Learn more about uberSVN and get a free download at: http://p.sf.net/sfu/wandisco-dev2dev ___ 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
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
