|
|
|
google unix.com
|
|||||||
| Forums | Register | Forum Rules | Links | Albums | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| Linux RedHat, Ubuntu, SUSE, Fedora, Debian, Mandriva, Slackware, Gentoo linux, PCLinuxOS. All Linux questions here! |
More UNIX and Linux Forum Topics You Might Find Helpful
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| nanosleep returns prematurely, with return value 0 | MeMyself | High Level Programming | 1 | 12-21-2008 11:22 PM |
| Nagios 2.11 (2.x branch) | iBot | Software Releases - RSS News | 0 | 03-12-2008 07:00 PM |
| S-190: Nagios Vulnerabilities | iBot | Security Advisories (RSS) | 0 | 02-15-2008 10:30 AM |
| Nagios - How to install ! | ArabOracle.com | SUN Solaris | 2 | 03-11-2006 01:25 AM |
| Why does rexec cause while loop to end prematurely? | sadove | Shell Programming and Scripting | 2 | 02-23-2005 04:19 PM |
Powered by 
|
|
|
LinkBack | Thread Tools | Search this Thread | Rate Thread | Display Modes |
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. |
| Bookmarks |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
Threaded Mode
