X-Original-To: pgsql-admin-postgresql.org@postgresql.org Received: from localhost (mx1.hub.org [200.46.208.251]) by postgresql.org (Postfix) with ESMTP id 0C7FE9FA5C3 for ; Sun, 11 Jun 2006 12:10:28 -0300 (ADT) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.208.251]) (amavisd-new, port 10024) with ESMTP id 07176-08 for ; Sun, 11 Jun 2006 12:10:22 -0300 (ADT) X-Greylist: domain auto-whitelisted by SQLgrey- Received: from nz-out-0102.google.com (nz-out-0102.google.com [64.233.162.193]) by postgresql.org (Postfix) with ESMTP id 9AF989F9CAA for ; Sun, 11 Jun 2006 12:10:21 -0300 (ADT) Received: by nz-out-0102.google.com with SMTP id s1so1015656nze for ; Sun, 11 Jun 2006 08:10:20 -0700 (PDT) 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=iUofCFF8htPFNPpz0lEH/gd3jNDBmjVDOO588gbAdZxH+w0+x24+j+Rd6Emx/z2ZoTLjJ+QMCUWm/etf0++lkEuADCo8v5IaVIyVHOyfdAK6j9UQ71n+j73vqknmCswDXERN+eEFdxJ5vsIZ570ln42wOyMpEunuh5aOivBeXw8= Received: by 10.65.75.2 with SMTP id c2mr3931937qbl; Sun, 11 Jun 2006 08:10:20 -0700 (PDT) Received: by 10.65.250.9 with HTTP; Sun, 11 Jun 2006 08:10:20 -0700 (PDT) Message-ID: <9e4684ce0606110810n50f8c44cjf02a273a65aac0c2@mail.gmail.com> Date: Sun, 11 Jun 2006 17:10:20 +0200 From: "hubert depesz lubaczewski" To: "Marc G. Fournier" Subject: Re: How are ppl monitoring PostgreSQL ... ? What is being monitored ... ? Cc: pgsql-admin@postgresql.org In-Reply-To: <20060610152251.M1114@ganymede.hub.org> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_46648_3433746.1150038620777" References: <20060610152251.M1114@ganymede.hub.org> X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200606/104 X-Sequence-Number: 22066 ------=_Part_46648_3433746.1150038620777 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline On 6/10/06, Marc G. Fournier wrote: > > The subject kinda says it all ... I know there are SNMP patches available > out there now, but without those ... ? > i can tell you what we do monitor: 1. general server things (free disk space, cpu-idle, load, memory used, swap used, context switches, io operations, sockets in state close_wait). 2. db stuff: - numer of transactions per second - database size - size of specific tables/indices that we know have nasty tendency to grow - number of objects in database - duration of longest query - replication lag (in events, and in time) to make mrtg graphs of db stuff we made some perl scripts, which are bound to snmp using snmp's "exec" feature. then we just grab the values using mrtg and draw. quite simple actually. depesz -- http://www.depesz.com/ - nowy, lepszy depesz ------=_Part_46648_3433746.1150038620777 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On 6/10/06, Marc G. Fournier <scrappy@postgresql.org> wrote:
The subject kinda says it all ... I know there are SNMP patches available
out there now, but without those ... ?

i can tell you what we do monitor:
1. general server things (free disk space, cpu-idle, load, memory used, swap used, context switches, io operations, sockets in state close_wait).
2. db stuff:
  - numer of transactions per second
  - database size
  - size of specific tables/indices that we know have nasty tendency to grow
  - number of objects in database
  - duration of longest query
  - replication lag (in events, and in time)

to make mrtg graphs of db stuff we made some perl scripts, which are bound to snmp using snmp's "exec" feature. then we just grab the values using mrtg and draw. quite simple actually.

depesz

--
http://www.depesz.com/ - nowy, lepszy depesz ------=_Part_46648_3433746.1150038620777--