Date: Sun, 13 May 2007 15:46:41 -0500
From: "Jim C. Nasby" <decibel@decibel.org>
To: Heikki Linnakangas <heikki@enterprisedb.com>
Cc: Greg Smith <gsmith@gregsmith.com>, pgsql-hackers@postgresql.org
Subject: Re: Performance monitoring
Message-ID: <20070513204640.GL60707@nasby.net>
References: <Pine.GSO.4.64.0704010051050.14920@westnet.com>
	<200704030814.33999.peter_e@gmx.net>
	<Pine.GSO.4.64.0704030927180.5732@westnet.com>
	<46443F02.6060300@enterprisedb.com>
	<Pine.GSO.4.64.0705111009080.18685@westnet.com>
	<46448DC8.4050102@enterprisedb.com>
	<20070512211948.GA58786@nasby.net>
	<4646B61C.1010103@enterprisedb.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4646B61C.1010103@enterprisedb.com>
User-Agent: Mutt/1.5.13 (2006-08-11)

On Sun, May 13, 2007 at 07:54:20AM +0100, Heikki Linnakangas wrote:
> Maybe we should improve the stats system so that we can collect events 
> with timestamps and durations, but in my experience log files actually 
> are the most reliable and universal way to collect real-time performance 
> information. Any serious tool has a generic log parser. The other 
> alternative is SNMP. I welcome the efforts on pgsnmpd..

Having timing information in the stats system would be useful, but I'm
not sure how it could actually be done. But at least if the information
is in the stats system it's easy to programatically collect and process.
SNMP is just one example of that (fwiw I agree with Magnus that it
probably doesn't make sense to turn pgsnmpd into a log parser...)
-- 
Jim Nasby                                      decibel@decibel.org
EnterpriseDB      http://enterprisedb.com      512.569.9461 (cell)