Hi
we are using global event handler to throw alerts if particular host or services is down.
on successful track we got proper alerts if hosts or services is down.
but unfortunately we found if the hosts is down for more than 3 days upto 200 days. we are not getting any notifications for that hosts.
how to resolve this pls suggest
attached screen shot is a sample for your ref..
the check is happening properly but due to stable host the alert is not triggering. pls suggest , we need alerts for this kind of hosts..
Notifications
-
wiproltdwiv
- Posts: 281
- Joined: Sat Sep 08, 2012 12:52 am
Notifications
You do not have the required permissions to view the files attached to this post.
Re: Notifications
Nagios should stop notifying you if the state has not changed (and you have not set the check to 'volatile'). Could you clarify the issue?
Former Nagios employee
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
"It is turtles. All. The. Way. Down. . . .and maybe an elephant or two."
VI VI VI - The editor of the Beast!
Come to the Dark Side.
-
wiproltdwiv
- Posts: 281
- Joined: Sat Sep 08, 2012 12:52 am
Re: Notifications
yeah. we used xiwizard_genericnetdevice_ping_service template for services
and volatile we did not enabled.
whether we need to enable volatile on this template to trigger notification for this kind of services
and volatile we did not enabled.
whether we need to enable volatile on this template to trigger notification for this kind of services
You do not have the required permissions to view the files attached to this post.
-
slansing
- Posts: 7698
- Joined: Mon Apr 23, 2012 4:28 pm
- Location: Travelling through time and space...
Re: Notifications
You may want to set those services to volatile if they are going to be in a hard non ok state for extended periods of time. It looks you you have one that has been that way for 3-4 days:
Cited: http://nagios.sourceforge.net/docs/3_0/ ... vices.htmlVolatile services differ from "normal" services in three important ways. Each time they are checked when they are in a hard non-OK state, and the check returns a non-OK state (i.e. no state change has occurred)...
The non-OK service state is logged
Contacts are notified about the problem (if that's what should be done). Note: Notification intervals are ignored for volatile services.
The event handler for the service is run (if one has been defined)
These events normally only occur for services when they are in a non-OK state and a hard state change has just occurred. In other words, they only happen the first time that a service goes into a non-OK state. If future checks of the service result in the same non-OK state, no hard state change occurs and none of the events mentioned take place again.