Are you contemplating providing access to data that's currently not stored
in the pg_ catalog tables? I currently monitor the statio data,
transactions per second, and active/idle backends. Things that I think
would be useful would be average query execution time, longest execution
time, etc.
Hmm.. also data such as what is the background writer currently doing, where
are we at in checkpoint segments, how close to checkpoint timeouts are we,
etc.
On 8/2/07, Alvaro Herrera [EMAIL PROTECTED] wrote:
Josh Tolley escribió:
On 8/2/07, Gavin M. Roy [EMAIL PROTECTED] wrote:
Are you
On Wed, 2007-08-01 at 20:41 -0600, Josh Tolley wrote:
So please respond, if you feel so inclined, describing things you like
to monitor in your PostgreSQL instances as well as things you would
like to be able to easily monitor in a more ideal world. Many thanks,
and apologies for any breach of
Josh Tolley wrote:
So please respond, if you feel so inclined, describing things you like
to monitor in your PostgreSQL instances as well as things you would
like to be able to easily monitor in a more ideal world.
I can think of a few things I'd like to be able to monitor...
Connection
I'd like to know what the age of the oldest running transaction is.
i.e. hunt look out for old idle in transaction transactions that are
holding up vacuuming.
Info on the shared buffers like % used, % that hasn't been updated or
seen in x minutes / hours / days.
% used on various tablespaces
I usually monitor blks_read and blks_hit (of block level stats), when
the latter is high
I see shared memory is doing a good job, when the former then it also
shows something
Also, database-wide number of commits and rollbacks (btw, Slony has a habit of
calling ROLLBACK when it done nothing -- I
On 8/2/07, Gavin M. Roy [EMAIL PROTECTED] wrote:
Are you contemplating providing access to data that's currently not stored
in the pg_ catalog tables? I currently monitor the statio data,
transactions per second, and active/idle backends. Things that I think
would be useful would be average
Josh Tolley escribió:
On 8/2/07, Gavin M. Roy [EMAIL PROTECTED] wrote:
Are you contemplating providing access to data that's currently not stored
in the pg_ catalog tables? I currently monitor the statio data,
transactions per second, and active/idle backends. Things that I think
would
Work is beginning on pgsnmpd v 2.0, and I figured it would be a good
time to ask folks what they typically like to monitor, so we can make
sure pgsnmpd instruments it properly. The current version of pgsnmpd
supports something called RDBMS-MIB, which is a set of data designed
to be applicable to
