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:
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



MAILPING-LATENCY(1)						     Mailping						       MAILPING-LATENCY(1)

mailping-latency - Munin plugin to graph latency of mail deliveries SYNOPSIS
/usr/share/mailping/munin-plugins/mailping-latency {[config] | ['']} DESCRIPTION
mailping-latency is a Munin plugin that monitors the time spent between email submit and it's delivery. Configuration output When passed config, it outputs Munin configuration information. If there are no circuits defined (no subdirectories in /etc/mailping), it specifies that Munin should draw no graph either. If configuration files /etc/mailping/circuit/warnlatency and /etc/mailping/circuit/faillatency exist, the values in them are passed on to Munin, for use in Nagios alert integration. Value output When passed an empty string '', mailping-latency outputs latency of last successful probe message, for each configured circuit. FILES
/etc/mailping/ List of circuits that exist; each subdirectory is a circuit. /etc/mailping/circuit/warnlatency If latency is greater than this many seconds, a Nagios warning is triggered by Munin (assuming it has been configured to do that). Default: no warnings. /etc/mailping/circuit/faillatency If latency is greater than this many seconds, a Nagios alert is triggered by Munin (assuming it has been configured to do that). Default: no alerts. /var/lib/mailping/state/circuit/latency Amount of latency in seconds of the last successful probe for circuit. ENVIRONMENT
MAILPING_CONFIGDIR Override the location of the configuration directory. Default: /etc/mailping MAILPING_STATEDIR Override the location of the state directory. Circuit states are stored in the state subdirectory of this directory, in subdirectories named after the circuit name. Default: /var/lib/mailping SEE ALSO
mailping-success(1), mailping-cron(1), mailping-store(1), munin-run(8), munin-node(8) AUTHOR
Tommi Virtanen <> Havoc Consulting Author. COPYRIGHT
Copyright (C) 2004 Havoc Consulting mailping 0. 2004-04-16 MAILPING-LATENCY(1)