Service check latency rises when service notification event occurs frequently

[Yu Watanabe]

Sven Nierlein さんは書きました:
>On 18.10.2011 13:55, Yu Watanabe wrote:
>>    Thank you for the reply. I have used the standard os mail command '/bin/mail'
>>    Do you think the command had affected the scheduling process?
>
>How should i know? When i do a simple test, i can send up to 3 mails per seconds with local mail delivery.
>
>%> time echo "test" | mail sven
>
>real    0m0.329s
>user    0m0.010s
>sys     0m0.000s
>
>So depending on your mail configuration and the amount of notifications, you simply could calculate how long your core is blocked.

  I see. Thank you for the advice!

Thanks,
Yu

>
> Sven
>
>------------------------------------------------------------------------------
>All the data continuously generated in your IT infrastructure contains a
>definitive record of customers, application performance, security
>threats, fraudulent activity and more. Splunk takes this data and makes
>sense of it. Business sense. IT sense. Common sense.
>http://p.sf.net/sfu/splunk-d2d-oct
>_______________________________________________
>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
>


------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2d-oct
_______________________________________________
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