public inbox for [email protected]
help / color / mirror / Atom feedFrom: Guido Barosio <[email protected]>
To: Dave Page <[email protected]>
Cc: Marc G. Fournier <[email protected]>
Cc: Josh Berkus <[email protected]>
Cc: John Hansen <[email protected]>
Cc: [email protected]
Cc: Jim C. Nasby <[email protected]>
Subject: Re: Infrastructure monitoring
Date: Sat, 14 Jan 2006 20:43:58 +0000
Message-ID: <[email protected]> (raw)
In-Reply-To: <E7F85A1B5FF8D44C8A1AF6885BC9A0E4850837@ratbert.vale-housing.co.uk>
References: <E7F85A1B5FF8D44C8A1AF6885BC9A0E4850837@ratbert.vale-housing.co.uk>
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 <[email protected]> wrote:
>
>
>
>
> -----Original Message-----
> From: [email protected] on behalf of Marc G. Fournier
> Sent: Sat 1/14/2006 2:16 AM
> To: Josh Berkus
> Cc: John Hansen; [email protected]; 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 [email protected] 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 .
/ \ -----------------------------------------------------------------
view thread (33+ messages) latest in thread
reply
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: [email protected]
Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
Subject: Re: Infrastructure monitoring
In-Reply-To: <[email protected]>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox