PostgreSQL Discussion - Database monitor (again)

Author

Database monitor (again)

Edson Vilhena de Carvalho

2005-03-31, 7:01 am

Sorry but perhaps it is a database monitorizer that
makes the monitorization on the databases.
It's my english

Edson Carvalho

____________________
____________________
__________
Converse com seus amigos em tempo real com o Yahoo! Messenger
http://br.download.yahoo.com/messenger/

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

Qingqing Zhou

2005-03-31, 8:03 pm

"Edson Vilhena de Carvalho" <edson_jvc@yahoo.com> writes
> Sorry but perhaps it is a database monitorizer that
> makes the monitorization on the databases.
> It's my english

Ok, don't worry about your English. Try to find out your questions in your
language here:

http://www.postgresql.org/docs/faq/

Regards,
Qingqing

Dann Corbit

2005-03-31, 8:03 pm

First, let us consider what is already available. Here are some tools
that perform similar purposes to what you are proposing:

1. Transaction monitor (requires custom modifications to PostgreSQL):
http://starccm.sourceforge.net/

2. Statistics monitor (this is built in to the product):
http://www.postgresql.org/docs/curr...ring-stats.html

3. You can examine the database locks here:
http://www.postgresql.org/docs/curr...ring-locks.html

4. This is a very nice general purpose administration tool:
http://www.pgadmin.org/

I think something like SQL*Server's sp_who might be useful:
http://msdn.microsoft.com/library/d...y/en-us/tsqlref
/ts_sp_wa-wz_3v8v.asp

I think intrusion detection would be nice. If (for instance) it appears
that a denial of service attack was going on, it would be good to log
the ip of the offending process.

Some more esoteric things that would be handy:
1. Index creation suggester that watches column access and notices
frequent filtered table scans that could benefit from an index. It
would give the SQL to create the suggested index. A setting could allow
automatic creation of indexes, if usage passes a user given threshold.
2. Index type suggester that notices that a hashed index would be of
benefit or a btree or an rtree or whatever.
3. Graphical tools that will depict table or query usage as a bar chart
to show where the majority of the time is going.

Probably others can think up a lot more.

Since I am not sure about the scope of your project, it is hard for me
to know what might be a good suggestion.

-----Original Message-----
From: pgsql-general-owner@postgresql.org
[mailto:pgsql-general-owner@postgresql.org] On Behalf Of Edson Vilhena
de Carvalho
Sent: Wednesday, March 30, 2005 7:23 PM
To: pgsql-general@postgresql.org
Subject: [GENERAL] Database monitor (again)

Sorry but perhaps it is a database monitorizer that
makes the monitorization on the databases.
It's my english

Edson Carvalho

____________________
____________________
__________
Converse com seus amigos em tempo real com o Yahoo! Messenger
http://br.download.yahoo.com/messenger/

---------------------------(end of broadcast)---------------------------
TIP 6: Have you searched our list archives?

http://archives.postgresql.org

---------------------------(end of broadcast)---------------------------
TIP 1: subscribe and unsubscribe commands go to majordomo@postgresql
.org

Nic Ferrier

2005-03-31, 8:03 pm

"Dann Corbit" <DCorbit@connx.com> writes:

> 2. Statistics monitor (this is built in to the product):
> http://www.postgresql.org/docs/curr...ring-stats.html

Does anyone think an SNMP interface to these would be useful?

Nic Ferrier
http://www.tapsellferrier.co.uk

---------------------------(end of broadcast)---------------------------
TIP 3: if posting/reading through Usenet, please send an appropriate
subscribe-nomail command to majordomo@postgresql
.org so that your
message can get through to the mailing list cleanly

Philip Hallstrom

2005-03-31, 8:03 pm

>
>
> Does anyone think an SNMP interface to these would be useful?

I do. Would make it easy to hook it up to MRTG, Cacti, or some other
monitoring system. Would be nice for graphing number of queries, average
query length, queries per second that sort of stuff...

-philip

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match

Nic Ferrier

2005-03-31, 8:03 pm

Philip Hallstrom <postgresql@philip.pjkh.com> writes:

>
> I do. Would make it easy to hook it up to MRTG, Cacti, or some other
> monitoring system. Would be nice for graphing number of queries,
> average query length, queries per second that sort of stuff...

I don't think it would be difficult to spec a MIB for pg's stats.

I don't have much time for pg hacking... but I would think about doing
this if someone already involved in pg development were to help out.

Nic

---------------------------(end of broadcast)---------------------------
TIP 9: the planner will ignore your desire to choose an index scan if your
joining column's datatypes do not match

Sponsored Links