Today, I'd like to introduce a brand-new tool, pgstatview.
- pgstatview (pre-alpha)
http://www2.uptimeforce.com/pgstatview/
pgstatview allows DBA to visualize database activities with using several metrics both inside and outside PostgreSQL: transaction commit/rollbacks, tuple inserts/updates/deletes, cache hit ratio, bgwriter writes, WAL writes, and so on. You can see some sample reports here: Sample 1, Sample 2.
pgstatview has its unique advantages.
(1) Easy to use, in a minute
Once you submit those log files through the pgstatview web service, a pgstatview report generated from the statistics data you submitted will be published with several colorful charts, and you can read it on your browser.
(2) No impact for the running system
So, you don't worry about any impact for your database system even in the production server.
(3) No need for maintaining tools
So, DBA doesn't need to care about maintaining the tool anymore, and no longer be frustrated with version dependency and/or compilation issues.
Are you interested in? It's very easy to use, so you can try it in a minute.
Download pgstat.sh from the pgstatview web site, and run it as following (with 5 second interval):
$ ./pgstat.sh Usage: pgstat.sh [ <INTERVAL> | stop ] $ ./pgstat.sh 5 <Run your workload on PostgreSQL here.> $ ./pgstat.sh stopThen, submit `vmstat.log', `mpstat.log', `iostat.log' and `pgstat.log' files generated in the current working directory.
Please try it, and if you have any comments, requests or have found a bug (unfortunately), please tell me by e-mail or this comment form.
Enjoy!
2 comments:
and what sense? why dont use for example munin?
Of course, Munin is one of the possible options to monitor PostgreSQL. However, from DBA point of view, I think I need to observe PostgreSQL deeper and easier than general monitoring tools. Not implemented yet though.
Post a Comment