Re: pgfoundry is down
От | Tom Lane |
---|---|
Тема | Re: pgfoundry is down |
Дата | |
Msg-id | 12323.1195071238@sss.pgh.pa.us обсуждение исходный текст |
Ответ на | Re: pgfoundry is down (Stefan Kaltenbrunner <stefan@kaltenbrunner.cc>) |
Ответы |
Re: pgfoundry is down
DNS (was: pgfoundry is down) |
Список | pgsql-www |
Stefan Kaltenbrunner <stefan@kaltenbrunner.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
В списке pgsql-www по дате отправления: