Hi;<div><br></div><div><div>Hammering a website by referring to it on a constantly-reloading page can generate a lot of unnecessary traffic.</div><div><br><div><br></div><div>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.</div> <div><br></div><div>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.</div><div><br></div><div>The end result is a flagged event that can be detected, reported, and escalated just like any other event.</div> <div><br></div><div>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.</div> <div><br></div><div>FYC</div><div><br></div><div>If you're interested, I can flesh this out as a working model.</div><div><br></div><div>Allan</div><div><br></div><div><br></div><div><br><div class="gmail_quote">On Thu, Jan 29, 2009 at 13:06, Seth P. Low <span dir="ltr"><<a href="mailto:low@modog.com">low@modog.com</a>></span> wrote:<br> <blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">In Nagios 3.1.0 there is a new feature:<br> <br> Added automatic update check functionality - runs once a day to check for new Nagios releases<br> Splash screen on web UI now indicates whether a new update is available (requires that update checks are enabled)<br> <br> 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 <a href="http://nagios.org" target="_blank">nagios.org</a> page. Worked really well.<br> ------------------------------------------------------------------------------<br> This SF.net email is sponsored by:<br> SourcForge Community<br> SourceForge wants to tell your story.<br> <a href="http://p.sf.net/sfu/sf-spreadtheword" target="_blank">http://p.sf.net/sfu/sf-spreadtheword</a><br> _______________________________________________<br> Nagios-users mailing list<br> <a href="mailto:Nagios-users@lists.sourceforge.net">Nagios-users@lists.sourceforge.net</a><br> <a href="https://lists.sourceforge.net/lists/listinfo/nagios-users" target="_blank">https://lists.sourceforge.net/lists/listinfo/nagios-users</a><br> ::: Please include Nagios version, plugin version (-v) and OS when reporting any issue.<br> ::: Messages without supporting info will risk being sent to /dev/null<br> </blockquote></div><br><br clear="all"><br>-- <br><a href="mailto:allanc@chickenandporn.com">allanc@chickenandporn.com</a> "金鱼" <a href="http://linkedin.com/in/goldfish">http://linkedin.com/in/goldfish</a><br> please, no proprietary attachments (<a href="http://tinyurl.com/cbgq">http://tinyurl.com/cbgq</a>)<br> </div></div></div>