Re: pgfoundry is down

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Stefan Kaltenbrunner <stefan(at)kaltenbrunner(dot)cc>
Cc: Magnus Hagander <magnus(at)hagander(dot)net>, "Marc G(dot) Fournier" <scrappy(at)hub(dot)org>, Greg Sabino Mullane <greg(at)turnstep(dot)com>, pgsql-www(at)postgresql(dot)org
Subject: Re: pgfoundry is down
Date: 2007-11-14 20:13:58
Message-ID: 12323.1195071238@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-www

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.")

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

regards, tom lane

In response to

Responses

Browse pgsql-www by date

  From Date Subject
Next Message Stefan Kaltenbrunner 2007-11-14 20:32:04 Re: pgfoundry is down
Previous Message Joshua D. Drake 2007-11-14 19:50:53 Re: pgfoundry is down