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 2FFB69DD92B; Sat, 14 Jan 2006 16:58:40 -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 48005-02; Sat, 14 Jan 2006 16:58:40 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- X-Greylist: from auto-whitelisted by SQLgrey- Received: from hosting.commandprompt.com (128.commandprompt.com [207.173.200.128]) by postgresql.org (Postfix) with ESMTP id 990489DD8FF; Sat, 14 Jan 2006 16:58:37 -0400 (AST) Received: from [192.168.1.100] (or-67-76-146-141.sta.sprint-hsd.net [67.76.146.141]) (authenticated bits=0) by hosting.commandprompt.com (8.13.4/8.13.4) with ESMTP id k0EKnNuA002799; Sat, 14 Jan 2006 12:49:24 -0800 Message-ID: <43C96636.3070606@commandprompt.com> Date: Sat, 14 Jan 2006 12:59:34 -0800 From: "Joshua D. Drake" User-Agent: Thunderbird 1.5 (X11/20051201) MIME-Version: 1.0 To: Guido Barosio CC: Dave Page , "Marc G. Fournier" , Josh Berkus , John Hansen , pgsql-www@postgresql.org, "Jim C. Nasby" Subject: Re: Infrastructure monitoring References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeded SMTP AUTH authentication, not delayed by milter-greylist-1.6 (hosting.commandprompt.com [192.168.1.101]); Sat, 14 Jan 2006 12:49:25 -0800 (PST) X-Virus-Scanned: by amavisd-new at hub.org X-Spam-Status: No, score=0.063 required=5 tests=[AWL=0.063] X-Spam-Score: 0.063 X-Spam-Level: X-Archive-Number: 200601/102 X-Sequence-Number: 9290 Hello, I believe the biggest issue is not the monitoring but the fact that these machines are not managed. All due respect to John (I believe he does the search) but if he is often on the road for 12 hours then someone else needs to be hosting those machines. The machines need to be hosted by companies that manage servers. There are several in the PostgreSQL community and yes CMD is one of them. I am not trying to take any kudos from anyone or suggest that they are not doing a bang up job. I am saying that all of the communities machines should be managed. Outside of a hardware failure there is zero reason for these machines to have extended outages unless scheduled. Sincerely, Joshua D. Drake -- The PostgreSQL Company - Command Prompt, Inc. 1.503.667.4564 PostgreSQL Replication, Consulting, Custom Development, 24x7 support Managed Services, Shared and Dedicated Hosting Co-Authors: PLphp, PLperl - http://www.commandprompt.com/