Re: Infrastructure monitoring

I insist cause I find it easy (even for a standard nagios)

The search failure was due to a 503 error being dispatched from the server.

GET http://search.postgresql.org and expect to recive an array of codes for
a succesfull lookup, or drop an alert.

G.-

On 1/14/06, Dave Page <dpage(at)vale-housing(dot)co(dot)uk> wrote:
>
>
>
>
> -----Original Message-----
> From: pgsql-www-owner(at)postgresql(dot)org on behalf of Marc G. Fournier
> Sent: Sat 1/14/2006 2:16 AM
> To: Josh Berkus
> Cc: John Hansen; pgsql-www(at)postgresql(dot)org; Jim C. Nasby
> Subject: Re: [pgsql-www] Infrastructure monitoring
>
> > As I've said above ... physical servers are being monitored, so if
> anyone
> > has some ideas on how we can improve "content monitoring", for lack of a
> > better word, I know I'm all ears ...
> >
> > Again, if Hyperic can offer something for this, let me know ...
>
> We also monitor a bunch of services using a nagios installation here. With
> the search though it's not always so easy because the search engine is
> tucked away behind a firewall with only the web frontend poking through.
>
> Regards, Dave
>
> ---------------------------(end of broadcast)---------------------------
> TIP 1: if posting/reading through Usenet, please send an appropriate
> subscribe-nomail command to majordomo(at)postgresql(dot)org so that your
> message can get through to the mailing list cleanly
>

--
/"\ ASCII Ribbon Campaign .
\ / - NO HTML/RTF in e-mail .
X - NO Word docs in e-mail .
/ \ -----------------------------------------------------------------