Limiting mail notification for clock drift

Kenneth Holter kenneho.ndu at gmail.com
Wed Nov 12 16:03:12 CET 2008


I think I found one of the causes for the excessive notifacations - the
notification_interval was set to 0. For almost all our services we have a
high number (such as 1440), but this current value of zero must have made
it's way into the code somehow. This is my current definition:

 define service {
        use                             generic-service
        service_description             Current load for virtual servers
        servicegroups                   performance
        hostgroups                      virtual-servers
        is_volatile                     0
        check_period                    24x7
        max_check_attempts              3
        normal_check_interval           5
        retry_check_interval            1
        notification_interval           0
        notification_period             24x7
        check_command
check_remote_load!/home/nagios/.ssh/id_rsa!nagios!13.0,8.0,3.0!15.0,10.0,5.0
}


Setting this attribute to a higher value should make me get a lot less
notifications, but I will still get more or less duplicate notifications.
Help on avoiding this will be appreciated.

Regarding your specific questions: I think the service definition above
answers most of them. We don't run multiple Nagios daemons on the same
machine. I didn't find anything unusual in objects.cache.

On 11/12/08, Marc Powell <marc at ena.com> wrote:
>
>
> On Nov 12, 2008, at 2:43 AM, Kenneth Holter wrote:
>
> >
> > Thanks for your reply.
> >
> > The "is_volatile" options is actually already set to "0". :/
>
> That's interesting. That's about the only option that would cause the
> behavior you are reporting that I can think of. Are you using event
> handlers for notifications? Is your notification_interval the same or
> similar to your normal_check_interval? Make sure that you don't have
> multiple nagios daemons running at the same time and that the service
> definition in objects.cache is as you expect it to be.
>
> The only case in which nagios cares about the _text_ of the plugin
> output is when state stalking is enabled. Even then, it only provides
> logging of that change, not a notification. There are only two
> conditions under which notifications will be sent out (
> http://nagios.sourceforge.net/docs/3_0/notifications.html)--
>
> "When Do Notifications Occur?
>
> The decision to send out notifications is made in the service check
> and host check logic. Host and service notifications occur in the
> following instances...
>
>     * When a hard state change occurs. More information on state
> types and hard state changes can be found here.
>     * When a host or service remains in a hard non-OK state and the
> time specified by the <notification_interval> option in the host or
> service definition has passed since the last notification was sent out
> (for that specified host or service)."
>
> > I think it would be correct to sum up what I'm in need of like this:
> > Whenever there is a transition from one hard error state to another
> > hard error state, or when there has been a recovery from such an
> > error, I'd like a notification.
>
> Yup. Standard Operating Procedure for nagios. You have to do something
> unusual to not get this behavior. Perhaps you should post some config
> information from objects.cache for inspection. service definition,
> contact definition and notification command definition.
>
> --
> Marc
>
>
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's
> challenge
> Build the coolest Linux based applications with Moblin SDK & win great
> prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> _______________________________________________
> Nagios-users mailing list
> Nagios-users at lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nagios-users
> ::: Please include Nagios version, plugin version (-v) and OS when
> reporting any issue.
> ::: Messages without supporting info will risk being sent to /dev/null
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20081112/2c55f5df/attachment.html>
-------------- next part --------------
-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
-------------- next part --------------
_______________________________________________
Nagios-users mailing list
Nagios-users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nagios-users
::: Please include Nagios version, plugin version (-v) and OS when reporting any issue. 
::: Messages without supporting info will risk being sent to /dev/null


More information about the Users mailing list