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 299C19DD8FF; Sat, 14 Jan 2006 17:01:06 -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 49401-02; Sat, 14 Jan 2006 17:01:07 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- X-Greylist: from auto-whitelisted by SQLgrey- Received: from anchor-post-34.mail.demon.net (anchor-post-34.mail.demon.net [194.217.242.92]) by postgresql.org (Postfix) with ESMTP id 8EF169DC896; Sat, 14 Jan 2006 17:01:02 -0400 (AST) Received: from mailgate.vale-housing.co.uk ([194.217.48.34] helo=vale-housing.co.uk) by anchor-post-34.mail.demon.net with esmtp (Exim 4.42) id 1ExsWF-000N4l-Fa; Sat, 14 Jan 2006 21:01:03 +0000 Received: from 192.168.7.8 ([192.168.7.8]) by ratbert.vale-housing.co.uk ([192.168.1.106]) with Microsoft Exchange Server HTTP-DAV ; Sat, 14 Jan 2006 21:01:04 +0000 User-Agent: Microsoft-Entourage/11.2.1.051004 Date: Sat, 14 Jan 2006 21:01:23 +0000 Subject: Re: Infrastructure monitoring From: Dave Page To: Guido Barosio CC: "Marc G. Fournier" , Josh Berkus , John Hansen , , "Jim C. Nasby" Message-ID: Thread-Topic: [pgsql-www] Infrastructure monitoring Thread-Index: AcYZTazd64xs64VAEdqebgARJHpWaA== In-Reply-To: Mime-version: 1.0 Content-type: multipart/alternative; boundary="B_3220117283_133638" X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.338 required=5 tests=[AWL=0.337, HTML_MESSAGE=0.001] X-Spam-Score: 0.338 X-Spam-Level: X-Archive-Number: 200601/103 X-Sequence-Number: 9291 > This message is in MIME format. Since your mail reader does not understand this format, some or all of this message may not be legible. --B_3220117283_133638 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit On 14/1/06 20:43, "Guido Barosio" wrote: > I insist cause I find it easy (even for a standard nagios) > With all due respect, insist all you want but the search engine backend does not run HTTP and is behind a firewall where we cannot monitor it from the outside without punching a hole first. From what John has said though, it is monitored from elsewhere on his private network. The frontend server is monitored by nagios, but as I knew search was being moved, I was not paying any attention to it. Regards, Dave. --B_3220117283_133638 Content-type: text/html; charset="US-ASCII" Content-transfer-encoding: quoted-printable Re: [pgsql-www] Infrastructure monitoring


On 14/1/06 20:43, "Guido Barosio" <gbarosio@gmail.com> wrot= e:

I insist cause I find it easy (even for a standard nagi= os)

With all due respect, insist all you want but the sear= ch engine backend does not run HTTP and is behind a firewall where we cannot= monitor it from the outside without punching a hole first. From what John h= as said though, it is monitored from elsewhere on his private network.

The frontend server is monitored by nagios, but as I knew search was being = moved, I was not paying any attention to it.

Regards, Dave. --B_3220117283_133638--