Nagios escalating prematurely

Special Forums UNIX and Linux Applications Infrastructure Monitoring Nagios escalating prematurely

08-12-2009

Registered User

1, 0

Join Date: Aug 2009

Last Activity: 12 August 2009, 3:30 AM EDT

Posts: 1

Thanks Given: 0

Thanked 0 Times in 0 Posts

Nagios escalating prematurely

We are currently using Nagios 1.3 .The issue we facing is , when a alert is in Warning state and then from Warning it moves to Critical state ,the alert is escalated directly to L2,L3 L4 escalations,here nagios assumes that the time period ,the alert was in warning state as unacknowledged time (even when it is acknowledged ),and it follows the L2 ,L3 escalation path depending on the time we have defined for the esclations.

Is this a bug or a feature of nagios and is there a way to fix this problem as escalation to TOP management is major thing because it is direct impacting to our SLAs.

apatil

View Public Profile for apatil

Find all posts by apatil

Previous Thread | Next Thread

9 More Discussions You Might Find Interesting

1. Infrastructure Monitoring

Nagios check dependent on second nagios server

We have a dual Nagios server setup. One is setup for internal server monitoring on our LAN, while the second Nagios server is hosted externally and is used for external checks only such as URL and ping checks form the WAN side. I was wondering if there is any way to setup cross dependencies...

2. Infrastructure Monitoring

Nagios Auditing

Hi Folks, I have Nagios 3.0.6 which is monitoring 400+ servers in my environment and is administered by multiple administrators. I want to get notified if somebody enable or disable any notification of any of the hosts/services from GUI. Is it possible to configure? If so, how?

3. Shell Programming and Scripting

Expect script cronjob running but dying prematurely

I have an Ubuntu machine that I'd like to update automatically. I've written an expect script to run the aptitude package manager and update my packages. Essentially it does: aptitude update && aptitude upgrade while answering "yes" at the appropriate time. It works quite nicely when run...

4. Infrastructure Monitoring

Nagios Forum

What are the chances of getting a Nagios forum? The community is really lacking for a good place to work issues in Nagios. There just aren't any good places to go that I've found. Thanks, Docster

5. Infrastructure Monitoring

Nagios 3.2.2 on RHEL 5

Hi, Installed it and all seems okay except when I try to actually use it. :-( Visiting my nagios url, it says Logs and conf's follow: nagios.log is: # cat /usr/local/nagios/var/nagios.log | tail -5 Successfully shutdown... (PID=3613) Nagios 3.2.2 starting... (PID=4645)...

6. Shell Programming and Scripting

Background program exits prematurely?

Hello! I am currently attempting to build a very, very, basic program that attempts to act like a calendar for a "server." Using this program I need to have the client program connect to the server program, have the client wait for the server to respond through a socket, then exit and the server...

7. UNIX for Advanced & Expert Users

script dies prematurely and unpredictably

Hi, I have over 5 gb of data in a files structure in which month folders are in year folders, day folders are in month folders, and individual climate stations are in each day. I am trying to extract precipitation measured at 5 minute intervals for a duration of 15 years, but the script never...

8. Programming

nanosleep returns prematurely, with return value 0

Hi, I have encountered the following problem on Solaris 10: I have a thread that is asleep on nanosleep (set to 24 hours). Something that happens on another thread, causes the nanosleep to exit, even though the time has not elapsed. The returned value is 0 (so it doesn't look like it...

9. Shell Programming and Scripting

Why does rexec cause while loop to end prematurely?

I have the following korn shell script which reads the contents of an ascii file and performs an rexec command based on the line that was just read from the ascii file. The ascii file contains 6 lines, thus, the while loop should execute 6 times. The problem is that the rexec command within the...

LEARN ABOUT DEBIAN

nagircbot

NAGIRCBOT(1)						      General Commands Manual						      NAGIRCBOT(1)

NAME

       nagircbot - announce Nagios status to an IRC channel

SYNOPSIS

       nagircbot [-CdeHmRStxX] [-A REGEX] [-c CHANNEL] [-f FILE] [-F HOST[:PORT]] [-i INTERVAL] [-I INTERVAL] [-k KEYWORD] [-n NICK] [-N PREFIX]
		 [-p PASSWORD] [-P FILE] [-s HOST[:PORT]] [-T LIST] [-u USERNAME] [-U NAME] [-z USER]

DESCRIPTION

       nagircbot is an IRC bot that reads Nagios' status information and emits alerts to an IRC channel. It can filter alerts based on severity
       (CRITICAL, HARD, SOFT, and/or UNKNOWN) or by regular expression. It can connect to IRC servers protected by password or SSL, and can
       optionally set the topic to the current Nagios status.

OPTIONS

       -A REGEX
	      Filter (omit) lines that match a basic regular expression.

       -c CHANNEL
	      Channel to connect to, including the leading "#" (default: "#nagircbot").

       -C     Use colors in IRC messages.

       -d     Do not fork into the background.

       -e     Use encryption (SSL) when connecting to the IRC server.

       -f FILE
	      Path to Nagios' status.log, indicated by the 'status_file' parameter in nagios.cfg (default: "/usr/local/nagios/var/status.log").

       -F HOST[:PORT]
	      Retrieve status.log over the network. If no port is specified, the default is 33333.

       -H     Only announce alerts in 'HARD' state. This is the default.

       -i INTERVAL
	      Nagios alert check interval, in seconds (default: 60).

       -I INTERVAL
	      How often to announce Nagios global status in the channel, in seconds.  Specify an interval of 0 (the default) to disable. Do not
	      specify an interval smaller than the alert check (-i) interval.

       -k KEYWORD
	      Keyword for the channel (default: no keyword).

       -m     Display status information for an alert in separate IRC messages instead of combining on a single message.

       -n NICK
	      IRC nick to use (default: "nagircbot").

       -N PREFIX
	      Prefix for all in-channel IRC messages.

       -p PASSWORD
	      IRC server password.

       -P FILE
	      Write PID file.

       -R     Only announce CRITICAL/UNKNOWN alerts.

       -s HOST[:PORT]
	      IRC server to connect to. If not specified, the default is "localhost:6667".  If no port is specified, the default is 33333.

       -S     Also announce alerts in 'SOFT' state.

       -t     Set the channel topic to an alert summary.

       -T LIST
	      Enable checks to see if Nagios is still running. Send 'check' in a private message to invoke the check. Accepts a comma-seperated
	      list (without spaces) with the following elements: max_time_last_host_update, max_time_oldest_host_update, max_time_last_host_check,
	      max_time_oldest_host_check, max_time_last_service_check, max_time_oldest_service_check, and max_time_oldest_next_service_check.

       -u USERNAME
	      Username to log into the IRC server as.

       -U NAME
	      IRC "real" or full name (default: "nagircbot").

       -x     status.log is in Nagios 1.0 format.

       -X     status.log is in Nagios 2.0/3.0 format. This is the default.

       -z USER
	      User to run as.

AUTHOR

       nagircbot was written by Folkert van Heusden <folkert@vanheusden.com>.

       This manual page was written by John Morrissey <jwm@horde.net>, for the Debian project (and may be used by others).

								 December 13, 2010						      NAGIRCBOT(1)

Infrastructure Monitoring