Re: pgfoundry is down

Tom Lane wrote:
> Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc> writes:
>> Magnus Hagander wrote:
>>> Stefan Kaltenbrunner wrote:
>>>> well it would be fairly easy to drive such a feed from our nagios
>>>> instance (and even extract stuff like scheduled downtime from it) ...
>>> Not as sure about that one. Basically, not sure we want to publish the
>>> automated stuff there, and Nagios really isn't a nice interface to do
>>> edits from...
>
>> hmm well - there is certainly a lot of stuff on nagios that is probably
>> not appropriate for fully automatic publishing but we could say use the
>> nagios escalation feature for certain services and let that drive the feed.
>
> Automated publication of status data on a public website scares me;
> it seems like a great way to invite breakins. (Black hat: "whaddya
> know, their DNS server is down, maybe I can inject some bogus info.")

well that would only include stuff that is publically available(or
rather a public facing service) anyway (there is nothing that stops
somebody to check the availability of say our DNS-servers or say of
wwwmaster by himself). There is at least one precedence for doing this too:

http://monitoring.apache.org/status/

>
> I'm for manual entries only on a public-facing page.

fair enough - I'm just not too happy about having too many things one
has to deal with in such a case (updating a wiki, scheduling
maintainance in nagios to avoid people getting alerted, send mail to
-www and -hackers, ...).
Too complex procedures will hurt and not encourage all involved people
to handle planned stuff in the way it should ...

Stefan