X-Original-To: pgsql-www-postgresql.org@localhost.postgresql.org Received: from localhost (av.hub.org [200.46.204.144]) by postgresql.org (Postfix) with ESMTP id D5C929DD920 for ; Sat, 14 Jan 2006 16:44:00 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (av.hub.org [200.46.204.144]) (amavisd-new, port 10024) with ESMTP id 42561-09 for ; Sat, 14 Jan 2006 16:44:01 -0400 (AST) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from uproxy.gmail.com (uproxy.gmail.com [66.249.92.206]) by postgresql.org (Postfix) with ESMTP id DB94F9DD91E for ; Sat, 14 Jan 2006 16:43:57 -0400 (AST) Received: by uproxy.gmail.com with SMTP id s2so257775uge for ; Sat, 14 Jan 2006 12:43:59 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references; b=Z9+kd6f4GKcLjJwguMCTyWAY5Y6NU4PH9lCHGBDIv2NViPnAdvTuM86S3dUrYKNFvSGFoyXwasztRlWOncGk//As3LF/E7B5Dp2jLGJx/5Pd/AAu0SEJsYPg/WjJIrFjteyThxxfWWnxJOVxVIItrmrsOGVKZZWjDqHByXjlXVo= Received: by 10.48.247.7 with SMTP id u7mr151362nfh; Sat, 14 Jan 2006 12:43:58 -0800 (PST) Received: by 10.48.108.20 with HTTP; Sat, 14 Jan 2006 12:43:58 -0800 (PST) Message-ID: Date: Sat, 14 Jan 2006 20:43:58 +0000 From: Guido Barosio To: Dave Page Subject: Re: Infrastructure monitoring Cc: "Marc G. Fournier" , Josh Berkus , John Hansen , pgsql-www@postgresql.org, "Jim C. Nasby" In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_25828_25942325.1137271438502" References: X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.503 required=5 tests=[AWL=0.502, HTML_MESSAGE=0.001] X-Spam-Score: 0.503 X-Spam-Level: X-Archive-Number: 200601/100 X-Sequence-Number: 9288 ------=_Part_25828_25942325.1137271438502 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline 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 wrote: > > > > > -----Original Message----- > From: pgsql-www-owner@postgresql.org on behalf of Marc G. Fournier > Sent: Sat 1/14/2006 2:16 AM > To: Josh Berkus > Cc: John Hansen; pgsql-www@postgresql.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. Wit= h > 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@postgresql.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 . / \ ----------------------------------------------------------------- ------=_Part_25828_25942325.1137271438502 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
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 se= rver.
 
GET http://search.postgresq= l.org and expect to recive an array of codes for a succesfull look= up, or drop an alert.
 
G.-
 
 


On 1/14/06, = Dave Page <dpage@vale-ho= using.co.uk > wrote:=20



-----Original Messag= e-----
From: pgsql-www-owner@postgresql.org on behalf of Marc G. Fournier
Sent: S= at 1/14/2006 2:16 AM
To: Josh Berkus
Cc: John Hansen; pgsql-www@postgresql.org; Jim C. Nasby
Subject: Re: [pgsql-www] Infr= astructure monitoring

> As I've said above ... physical servers = are being monitored, so if anyone
> has some ideas on how we can impr= ove "content monitoring", for lack of a
> better word, I know I'm all ears ...
>
> Again, if Hy= peric can offer something for this, let me know ...

We also monitor = a bunch of services using a nagios installation here. With the search thoug= h it's not always so easy because the search engine is tucked away behind a= firewall with only the web frontend poking through.=20

Regards, Dave

---------------------------(end of broadcast)-= --------------------------
TIP 1: if posting/reading through Usenet, ple= ase send an appropriate
      subscribe-no= mail command to majordomo@postgresql.org so that your
     =  message can get through to the mailing list cleanly
<= /div>


--
/"\   ASCII Ribbon Cam= paign  .
\ / - NO HTML/RTF in e-mail  .=20
X  - NO Word docs in e-mail .
/ \ ------------------------= -----------------------------------------=20 ------=_Part_25828_25942325.1137271438502--