Nagios escalating prematurely

 
Thread Tools Search this Thread
Special Forums UNIX and Linux Applications Infrastructure Monitoring Nagios escalating prematurely
# 1  
Old 08-12-2009
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.
Login or Register to Ask a Question

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... (1 Reply)
Discussion started by: eugenes18t
1 Replies

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? (0 Replies)
Discussion started by: SiddhV
0 Replies

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 Replies)
Discussion started by: CluelessPerson
4 Replies

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 (27 Replies)
Discussion started by: Docster
27 Replies

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)... (7 Replies)
Discussion started by: smcracraft
7 Replies

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... (2 Replies)
Discussion started by: Entelexia
2 Replies

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... (2 Replies)
Discussion started by: mlw63@me.com
2 Replies

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... (1 Reply)
Discussion started by: MeMyself
1 Replies

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... (2 Replies)
Discussion started by: sadove
2 Replies
Login or Register to Ask a Question
Nagios::Object::Config(3pm)				User Contributed Perl Documentation			       Nagios::Object::Config(3pm)

NAME
Nagios::Object::Config - Perl objects to represent Nagios configuration DESCRIPTION
This is a module for parsing and processing Nagios object configuration files into perl objects. METHODS
new() Create a new configuration object. If Version is not specified, the already weak validation will be weakened further to allow mixing of Nagios 1.0 and 2.0 configurations. For now, the minor numbers of Version are ignored. Do not specify any letters as in '2.0a1'. To enable regular expression matching, use either the "regexp_matching" or "true_regexp_matching" arguments to new(). See enable_regexp_matching() and enable_true_regexp_matching() below. my $objects = Nagios::Object::Config->new(); my $objects = Nagios::Object::Config->new( Version => 1.2 ); my $objects = Nagios::Object::Config->new( Version => 2.0, regexp_matching => 1, true_regexp_matching => 2 ); parse() Parse a nagios object configuration file into memory. Although Nagios::Objects will be created, they are not really usable until the register() method is called. $parser->parse( "myfile.cfg" ); find_object() Search through the list of objects' names and return the first match. The second argument is optional. Always using it can considerably reduce the size of the list to be searched, so it is recommended. my $object = $parser->find_object( "localhost" ); my $object = $parser->find_object( "oracle", "Nagios::Service" ); find_objects() Search through the list of objects' names and return all the matches. The second argument is required. my @object_list = $parser->find_objects( "load", "Nagios::Service" ); find_objects_by_regex() Search through the list of objects' names and return a list of matches. The first argument will be evaluated as a regular expression. The second argument is required and specifies what kind of object to search for. The regular expressions are created by translating the "*" to ".*?" and "?" to ".". For now (v0.9), this code completely ignores Nagios's use_regexp_matching and use_true_regexp_matching and does full RE matching all the time. my @objects = $parser->find_objects_by_regex( "switch_*", "Nagios::Host" ); my @objects = $parser->find_objects_by_regex( "server0?", "Nagios::Host" ); all_objects_for_type() Obtain a reference to all objects of the specified Nagios object type. Usage: $objects = all_objects_for_type($object_type) Parameters: $object_type - A specific Nagios object type, i.e. "Nagios::Contact".. Returns: A reference to an array of references to all objects of the specified type associated with this configuration. Objects of this type added to the configuration following the call to this method _will_ be accessible through this reference after the fact. Note that the array reference by the return value may be empty. Example: my $contacts = $config->all_objects_for_type("Nagios::Contact"); if (scalar(@$contacts) == 0) { print "No contacts have yet been defined "; } else { foreach $contact (@$contacts) { ... } } all_objects() Returns an arrayref with all objects parsed from the config in it. my $everything = $config->all_objects; find_attribute() Search through the objects parsed thus far, looking for a particular textual name. When found, return that object. If called with two arguments, it will search through all objects currently loaded until a match is found. A third argument may specify the type of object to search for, which may speed up the search considerably. my $object = $parser->find_attribute( "command_name", "check_host_alive" ); my $object = $parser->find_attribute( "command_name", "check_host_alive", 'Nagios::Host' ); resolve() Resolve the template for the specified object. Templates will not work until this has been done. $parser->resolve( $object ); register() Examine all attributes of an object and link all of it's references to other Nagios objects to their respective perl objects. If this isn't called, some methods will return the textual name instead of a perl object. $parser->register( $host_object ); my $timeperiod_object = $host_object->notification_period; resolve_objects() Resolve all objects currently loaded into memory. This can be called any number of times without corruption. $parser->resolve_objects(); register_objects() Same deal as resolve_objects(), but as you'd guess, it registers all objects currently loaded into memory. $parser->register_objects(); enable_regexp_matching()/disable_regexp_matching() This correlates to the "use_regexp_matching" option in nagios.cfg. When this option is enabled, Nagios::Object::Config will translate "*" to ".*?" and "?" to "." and evaluate the result as a perl RE, anchored at both ends for any value that can point to multiple other objects (^ and $ are added to either end). $parser->enable_regexp_matching; $parser->disable_regexp_matching; enable_true_regexp_matching()/disable_true_regexp_matching() This correlates to the "use_true_regexp_matching" option in nagios.cfg. This is very similar to the enable_regexp_matching() option, but matches more data and allows more powerful RE syntax. These modules will allow you the full power of perl RE's - this is probably more than is available in Nagios, so don't blame me if something works here but not in Nagios (it's usually the other way around anyways). The generated RE's have the same translation as above, but do not have the anchors to ^ and $. This option always supercedes enable_regexp_matching. $parser->enable_true_regexp_matching; $parser->disable_true_regexp_matching; list_hosts(), list_hostgroups(), etc. Returns an array/arrayref of objects of the given type. $config->list_hosts $config->list_hostgroups $config->list_services $config->list_timeperiods $config->list_commands $config->list_contacts $config->list_contactgroups $config->list_hostdependencies $config->list_servicedependencies $config->list_hostescalations $config->list_hostgroupescalations $config->list_serviceescalations $config->list_servicegroups $config->list_hostextinfo $config->list_serviceextinfo AUTHOR
Al Tobey <tobeya@cpan.org> Contributions From: Lynne Lawrence (API & bugs) perl v5.12.4 2011-10-22 Nagios::Object::Config(3pm)