How to reduce a very high latency number

[Marcel Mitsuto Fucatu Sugano]

On Wed, 2006-05-24 at 11:09 -0500, Marc Powell wrote:
[snip]
> Each submits all check results to each master in series --
> 
> $ tail -3 submit_check_result
>         /bin/echo -e "$1\t$2\t$return_code\t$4\n" |
> /usr/local/nagios/bin/send_nsca master1 -p 5668 -c
> /usr/local/nagios/etc/send_nsca.cfg
>         /bin/echo -e "$1\t$2\t$return_code\t$4\n" |
> /usr/local/nagios/bin/send_nsca master2 -p 5668 -c
> /usr/local/nagios/etc/send_nsca.cfg
>         /bin/echo -e "$1\t$2\t$return_code\t$4\n" |
> /usr/local/nagios/bin/send_nsca master3 -p 5669 -c
> /usr/local/nagios/etc/send_nsca.cfg
> 
> I've never seen failures and all checks are current on my masters.
[snip]

I've tried this setup before, but this leads to a load of stale
services. Did you check_freshness? Because i am thinking about not check
freshness at all, instead, just make a check_tcp!5667 to the masters,
from the slaves. But i am still thinking about it. 

In my setup, it is one master getting 8750 passive service results. And
there is a lot of stale services around (almost 2% of the services),
i've tried every configuration pertinent to the freshness checking, and
tailoring one freshness threshold for each service is not welcome. So,
lefting freshness threshold at 0, Nagios will refuse lots of services
results for just 1 to 30 seconds after the automatic threshold (some
services need freshness threshold, indeed), and those staled services
with little lateness is about 50% of all the staled services reported.

How people around here manage a lot of passive service staled results,
in big nagios configs?

thanks.

M.


AVISO: A informação contida neste e-mail, bem como em qualquer de seus anexos, é CONFIDENCIAL e destinada ao uso exclusivo do(s) destinatário(s) acima referido(s), podendo conter informações sigilosas e/ou legalmente protegidas. Caso você não seja o destinatário desta mensagem, informamos que qualquer divulgação, distribuição ou cópia deste e-mail e/ou de qualquer de seus anexos é absolutamente proibida. Solicitamos que o remetente seja comunicado imediatamente, respondendo esta mensagem, e que o original desta mensagem e de seus anexos, bem como toda e qualquer cópia e/ou impressão realizada a partir destes, sejam permanentemente apagados e/ou destruídos. Informações adicionais sobre nossa empresa podem ser obtidas no site http://sobre.uol.com.br/.

NOTICE: The information contained in this e-mail and any attachments thereto is CONFIDENTIAL and is intended only for use by the recipient named herein and may contain legally privileged and/or secret information. If you are not the e-mail´s intended recipient, you are hereby notified that any dissemination, distribution or copy of this e-mail, and/or any attachments thereto, is strictly prohibited. Please immediately notify the sender replying to the above mentioned e-mail address, and permanently delete and/or destroy the original and any copy of this e-mail and/or its attachments, as well as any printout thereof. Additional information about our company may be obtained through the site http://www.uol.com.br/ir/.


-------------------------------------------------------
All the advantages of Linux Managed Hosting--Without the Cost and Risk!
Fully trained technicians. The highest number of Red Hat certifications in
the hosting industry. Fanatical Support. Click to learn more
http://sel.as-us.falkag.net/sel?cmd=lnk&kid7521&bid$8729&dat1642
_______________________________________________
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