Check behavior during the notification event

[Yu Watanabe]

It would be a great help if you could help me out with my additional question.

I was trying to find how does nagios determine the interval time between the high priority events
in the source code but I couldn't find the part.

I found was the following line in the event.c 

    958                 /* handle high priority events */
    959                 if(event_list_high!=NULL && (current_time>=event_list_high->run_time)){
    960
    961                         /* remove the first event from the timing loop */
    962                         temp_event=event_list_high;
    963                         event_list_high=event_list_high->next;
    964
    965                         /* handle the event */
    966                         handle_timed_event(temp_event);
    967
    968                         /* reschedule the event if necessary */
    969                         if(temp_event->recurring==TRUE)
    970                                 reschedule_event(temp_event,&event_list_high);
    971
    972                         /* else free memory associated with the event */
    973                         else
    974                                 free(temp_event);
    975                         }

Do you have any idea how does nagios determine the value 30 seconds,
between the high priority events?

Thank you for reading.

Thanks,
Yu

Stuart Browne さんは書きました:
>> -----Original Message-----
>> From: Yu Watanabe [mailto:yu.watanabe at jp.fujitsu.com]
>> Sent: Thursday, 6 January 2011 5:04 PM
>> To: nagios-users at lists.sourceforge.net
>> Subject: [Nagios-users] Check behavior during the notification event
>> 
>> Hello all.
>> 
>> I would like to ask a question regarding to the behavior of check
>> scheduling
>> during the massive number of notification event is occuring.
>> 
>> I have couple of notification group defeined in each service but when
>> notification
>> alerts occur consecutively among multiple services, it seems that nagios
>> sequentially
>> process the notification events, not simultaneously.
>> 
>> [2010-12-19 15:08:26] SERVICE ALERT: host1;
>> [2010-12-19 15:08:26] SERVICE NOTIFICATION:
>> jdoe;proact1;ssh_proc_mem_Search;CRITICAL;notify-by-email;
>> [2010-12-19 15:08:56] SERVICE NOTIFICATION:
>> nagiosadmin;proact1;ssh_proc_mem_Search;CRITICAL;notify-by-email;
>> [2010-12-19 15:09:26] SERVICE ALERT:
>> host2;ssh_proc_alv_TrafficAgent_3;CRITICAL;HARD;3;
>> [2010-12-19 15:09:26] SERVICE NOTIFICATION:
>> jdoe;traffic01;ssh_proc_alv_TrafficAgent_3;CRITICAL;notify-by-email;
>> [2010-12-19 15:09:56] SERVICE NOTIFICATION:
>> nagiosadmin;traffic01;ssh_proc_alv_TrafficAgent_3;CRITICAL;notify-by-
>> email;
>> [2010-12-19 15:10:26] SERVICE ALERT:
>> host3;ssh_proc_alv_EAM_GbE_MC_5;CRITICAL;HARD;3;
>> [2010-12-19 15:10:26] SERVICE NOTIFICATION:
>> jdoe;eam03;ssh_proc_alv_EAM_GbE_MC_5;CRITICAL;notify-by-email;
>> [2010-12-19 15:10:56] SERVICE NOTIFICATION:
>> nagiosadmin;eam03;ssh_proc_alv_EAM_GbE_MC_5;CRITICAL;notify-by-email;
>> [2010-12-19 15:11:26] SERVICE ALERT:
>> host4;ssh_proc_alv_EAM_CX2600_220_40;CRITICAL;HARD;3;
>> [2010-12-19 15:11:26] SERVICE NOTIFICATION:
>> jdoe;eam01;ssh_proc_alv_EAM_CX2600_220_40;CRITICAL;notify-by-email;
>> [2010-12-19 15:11:56] SERVICE NOTIFICATION:
>> nagiosadmin;eam01;ssh_proc_alv_EAM_CX2600_220_40;CRITICAL;notify-by-email;
>> 
>> Is this a normal behavior with nagios ? (The version is 2.10)
>> I found a chapter in Nagios manual describes about the check delay of high
>> priority events but
>> wasn't sure if the situation corresponds to the manual or not.
>> 
>> "Examples of high priority events include log file rotations, external
>> command checks, and service reaper events. Additionally, host checks will
>> slow down the execution
>> and processing of service checks."
>> 
>> Thanks,
>> Yu Watanabe
>
>This is normal behaviour.
>
>A lot of people end up writing external notification handlers to take the load off of Nagios so the scheduled checks can continue whilst the external app 
queues and processes the notifications.
>
>Generally an email notification should be quick (less than a second), but if you're trying to send 20 emails or you start sending SMS' directly etc., it 
can get bogged down. 
>
>Stuart
>
>------------------------------------------------------------------------------
>Learn how Oracle Real Application Clusters (RAC) One Node allows customers
>to consolidate database storage, standardize their database environment, and, 
>should the need arise, upgrade to a full multi-node Oracle RAC database 
>without downtime or disruption
>http://p.sf.net/sfu/oracle-sfdevnl
>_______________________________________________
>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
>


------------------------------------------------------------------------------
Learn how Oracle Real Application Clusters (RAC) One Node allows customers
to consolidate database storage, standardize their database environment, and, 
should the need arise, upgrade to a full multi-node Oracle RAC database 
without downtime or disruption
http://p.sf.net/sfu/oracle-sfdevnl
_______________________________________________
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