Message-ID: <46010A95.4010707@archonet.com>
Date: Wed, 21 Mar 2007 10:36:05 +0000
From: Richard Huxton <dev@archonet.com>
User-Agent: IceDove 1.5.0.9 (X11/20061220)
MIME-Version: 1.0
To: Tobias Brox <tobias@nordicbet.com>
Cc: Joe Healy <joe@omc-international.com.au>,
	Dan Harris <fbsd@drivefaster.net>,
	PostgreSQL Performance <pgsql-performance@postgresql.org>
Subject: Re: OT: Munin (was Re: Determining server load from client)
References: <460080A2.20800@drivefaster.net>
	<46008931.8060605@omc-international.com.au>
	<4600E13F.3070806@archonet.com> <20070321101340.GI10137@oppetid.no>
In-Reply-To: <20070321101340.GI10137@oppetid.no>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Tobias Brox wrote:
> I have my postgres munin monitoring script at
> http://oppetid.no/~tobixen/pg_activity.munin.txt (had to suffix it with
> .txt to make the local apache happy).
> 
> I would like to see what others have done as well.

Well, I use Perl rather than shell, but that's just me.

The main difference is that although I downloaded a couple of simple 
pg-monitoring scripts from the web, I've concentrated on monitoring the 
application(s) instead. Things like:
  - number of news items posted
  - searches run
  - logins, logouts

The main limitation with it for me is the fixed 5-min time interval. It 
provides a slight irritation that I've got hourly/daily cron jobs that 
are being monitored continually.
-- 
   Richard Huxton
   Archonet Ltd