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

nagios::plugin::functions

Nagios::Plugin::Functions(3pm)				User Contributed Perl Documentation			    Nagios::Plugin::Functions(3pm)

NAME

       Nagios::Plugin::Functions - functions to simplify the creation of Nagios plugins

SYNOPSIS

	   # Constants OK, WARNING, CRITICAL, and UNKNOWN exported by default
	   use Nagios::Plugin::Functions;

	   # nagios_exit( CODE, $message ) - exit with error code CODE,
	   # and message "PLUGIN CODE - $message"
	   nagios_exit( CRITICAL, $critical_error ) if $critical_error;
	   nagios_exit( WARNING, $warning_error )   if $warning_error;
	   nagios_exit( OK, $result );

	   # nagios_die( $message, [$CODE] ) - just like nagios_exit(),
	   # but CODE is optional, defaulting to UNKNOWN
	   do_something()
	     or nagios_die("do_something() failed horribly");
	   do_something_critical()
	     or nagios_die("do_something_critical() failed", CRITICAL);

	   # check_messages - check a set of message arrays, returning a
	   # CODE and/or a result message
	   $code = check_messages(critical => @crit, warning => @warn);
	   ($code, $message) = check_messages(
	     critical => @crit, warning => @warn,
	     ok => @ok );

	   # get_shortname - return the default short name for this plugin
	   #   (as used by nagios_exit/die; not exported by default)
	   $shortname = get_shortname();

DESCRIPTION

       This module is part of the Nagios::Plugin family, a set of modules for simplifying the creation of Nagios plugins. This module exports
       convenience functions for the class methods provided by Nagios::Plugin. It is intended for those who prefer a simpler functional interface,
       and who do not need the additional functionality of Nagios::Plugin.

   EXPORTS
       Nagios status code constants are exported by default:

	   OK
	   WARNING
	   CRITICAL
	   UNKNOWN
	   DEPENDENT

       as are the following functions:

	   nagios_exit
	   nagios_die
	   check_messages

       The following variables and functions are exported only on request:

	   %ERRORS
	   %STATUS_TEXT
	   get_shortname
	   max_state
	   max_state_alt

   FUNCTIONS
       The following functions are supported:

       nagios_exit( <CODE>, $message )
	   Exit with return code CODE, and a standard nagios message of the form "PLUGIN CODE - $message".

       nagios_die( $message, [CODE] )
	   Same as nagios_exit(), except that CODE is optional, defaulting to UNKNOWN.	NOTE: exceptions are not raised by default to calling
	   code.  Set $_use_die flag if this functionality is required (see test code).

       check_messages( critical => @crit, warning => @warn )
	   Convenience function to check a set of message arrays and return an appropriate nagios return code and/or a result message. Returns
	   only a return code in scalar context; returns a return code and an error message in list context i.e.

	       # Scalar context
	       $code = check_messages(critical => @crit, warning => @warn);
	       # List context
	       ($code, $msg) = check_messages(critical => @crit, warning => @warn);

	   check_messages() accepts the following named arguments:

	   critical => ARRAYREF
	       An arrayref of critical error messages - check_messages() returns CRITICAL if this arrayref is non-empty. Mandatory.

	   warning => ARRAYREF
	       An arrayref of warning error messages - check_messages() returns WARNING if this arrayref is non-empty ('critical' is checked
	       first). Mandatory.

	   ok => ARRAYREF | SCALAR
	       An arrayref of informational messages (or a single scalar message), used in list context if both the 'critical' and 'warning'
	       arrayrefs are empty. Optional.

	   join => SCALAR
	       A string used to join the relevant array to generate the message string returned in list context i.e. if the 'critical' array @crit
	       is non-empty, check_messages would return:

		   join( $join, @crit )

	       as the result message. Optional; default: ' ' (space).

	   join_all => SCALAR
	       By default, only one set of messages are joined and returned in the result message i.e. if the result is CRITICAL, only the
	       'critical' messages are included in the result; if WARNING, only the 'warning' messages are included; if OK, the 'ok' messages are
	       included (if supplied) i.e. the default is to return an 'errors-only' type message.

	       If join_all is supplied, however, it will be used as a string to join the resultant critical, warning, and ok messages together
	       i.e.  all messages are joined and returned.

       get_shortname
	   Return the default shortname used for this plugin i.e. the first token reported by nagios_exit/nagios_die. The default is basically

	       uc basename( $ENV{NAGIOS_PLUGIN} || $0 )

	   with any leading 'CHECK_' and trailing file suffixes removed.

	   get_shortname is not exported by default, so must be explicitly imported.

       max_state(@a)
	   Returns the worst state in the array. Order is: CRITICAL, WARNING, OK, UNKNOWN, DEPENDENT

	   The typical usage of max_state is to initialise the state as UNKNOWN and use it on the result of various test. If no test were
	   performed successfully the state will still be UNKNOWN.

       max_state_alt(@a)
	   Returns the worst state in the array. Order is: CRITICAL, WARNING, UNKNOWN, DEPENDENT, OK

	   This is a true definition of a max state (OK last) and should be used if the internal tests performed can return UNKNOWN.

SEE ALSO

       Nagios::Plugin; the nagios plugin developer guidelines at http://nagiosplug.sourceforge.net/developer-guidelines.html.

AUTHORS

       This code is maintained by the Nagios Plugin Development Team: http://nagiosplug.sourceforge.net

COPYRIGHT AND LICENSE

       Copyright (C) 2006 by Nagios Plugin Development Team

       This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself.

perl v5.14.2							    2011-12-23					    Nagios::Plugin::Functions(3pm)

Infrastructure Monitoring