Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enhancement proposition #49

Open
menardorama opened this issue Sep 3, 2014 · 3 comments
Open

Enhancement proposition #49

menardorama opened this issue Sep 3, 2014 · 3 comments

Comments

@menardorama
Copy link

Hi,
I'm glad to see that dalibo is trying to build a tool that is lacking actually on postgresql.

We worked on a similar approach in my company few month ago and added several enhancements that I would like to propose :

  • Implement pg_proctab (https://github.com/markwkm/pg_proctab) to add metrics for the sessions (cpu, memory, IO ...). This help a lot on identifing heavy sessions
  • Add per object and per database statistics
  • Add the functionnality to graph on all the metrics available
  • Add a centralised repository
  • Add a feature to send metrics to statd in order to generates dashboard in graphite (this help a lot for very big production systems). : http://pgxn.org/dist/pg_statsd
  • Add an alerting system that we can couple with a nagios or zabbix....
  • And even if it's not the same project : couple pgbadger to this tool !
@marco44
Copy link
Contributor

marco44 commented Sep 3, 2014

Hi, and thanks for these ideas.

The centralized repository is already the subject of issue powa-team/powa#16.

Adding system metrics is already something we were thinking of. pg_proctab may be the right tool for the job, thanks.

The rest is harder to decide (and not a priority for the moment). We don't want to make a mess of the GUI too fast, so we are cautious about what metrics to add :)

pgbadger is made to generate static pages, so it would be hard to do this coupling. We discussed it with Gilles Darold, as he is one of the Dalibo crew too, while building POWA. I can't say "never", but not for now.

@menardorama
Copy link
Author

OK thanks for your reply

@rjuju
Copy link
Member

rjuju commented Feb 7, 2022

I'm moving this issue to powa-archivist repository.

Note also that the centralised repository has been introduced as of 4.0.0.

@rjuju rjuju transferred this issue from powa-team/powa Feb 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants