Nagios 3.1.0 - Update check feature

[Allan Clark]

Hi;
Hammering a website by referring to it on a constantly-reloading page can
generate a lot of unnecessary traffic.


If Nagios' DNS held a TXT record indicating the latest released version in a
given trend, then it can be checked in a way that is much gentler -- a DNS
RR is cached automatically by the DNS servers used, depending on how
Nagios.org defines the RR.

An "update check" can simply compare the current revision versus the latest,
and respond with the standard Nagios WARN/FAIL responses as desired by the
users.

The end result is a flagged event that can be detected, reported, and
escalated just like any other event.

This seems to leverage existing support structures yet pose zero additional
load to the nagios website, very little additional load on a decentralized
and very scalable resource.  Failures in Nagios' website, if such happened,
would not affect this sort of check.  Response time would typically be quite
fast.

FYC

If you're interested, I can flesh this out as a working model.

Allan



On Thu, Jan 29, 2009 at 13:06, Seth P. Low <low at modog.com> wrote:

> In Nagios 3.1.0 there is a new feature:
>
> Added automatic update check functionality - runs once a day to check for
> new Nagios releases
> Splash screen on web UI now indicates whether a new update is available
> (requires that update checks are enabled)
>
> Question - Where do you enable the "update checks" and are there any other
> steps? for years I have just had a check http check that ran a few times a
> day and looked for the current version as a string somewhere on the
> nagios.org page. Worked really well.
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword
> _______________________________________________
> 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
>



-- 
allanc at chickenandporn.com  "金鱼" http://linkedin.com/in/goldfish
please, no proprietary attachments (http://tinyurl.com/cbgq)
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://www.monitoring-lists.org/archive/users/attachments/20090129/2b11f29e/attachment.html>
-------------- next part --------------
------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
-------------- 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