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 7031A9DC80C for ; Fri, 13 Jan 2006 21:05:02 -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 34826-06 for ; Fri, 13 Jan 2006 21:05:04 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from noel.decibel.org (noel.decibel.org [67.100.216.10]) by postgresql.org (Postfix) with ESMTP id 5BBFB9DC81B for ; Fri, 13 Jan 2006 21:04:59 -0400 (AST) Received: by noel.decibel.org (Postfix, from userid 1001) id D68E53983D; Fri, 13 Jan 2006 19:05:02 -0600 (CST) Date: Fri, 13 Jan 2006 19:05:02 -0600 From: "Jim C. Nasby" To: pgsql-www@postgresql.org Subject: Infrastructure monitoring Message-ID: <20060114010502.GW9017@pervasive.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Operating-System: FreeBSD 6.0-RELEASE amd64 X-Distributed: Join the Effort! http://www.distributed.net User-Agent: Mutt/1.5.11 X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.09 required=5 tests=[AWL=0.090] X-Spam-Score: 0.09 X-Spam-Level: X-Archive-Number: 200601/90 X-Sequence-Number: 9278 Search has been down for at least 2 days now, and this certainly isn't the first time it's happened. There's also been cases of archives getting stuck, and probably other outages besides those that went on until someone email'd about it. Would it be difficult to setup something to monitor these various services? I know there's at least one OSS tool to do it, though I have no idea how hard it would be to tie that into the current infrastructure. -- Jim C. Nasby, Sr. Engineering Consultant jnasby@pervasive.com Pervasive Software http://pervasive.com work: 512-231-6117 vcard: http://jim.nasby.net/pervasive.vcf cell: 512-569-9461