pgBadger[0] log analyzer is from the same creator, and whilst not real-time, it provides great stats and breakdown with a nice web interface. I wonder why PoWa was split from it instead of integrating real-time stats into it...
They take different approaches to collecting the information. To use pgBadger, you have to enable query logging. To use POWA, you have to enable pg_stat_statements. [0]. You can get more information from pg_stat_statements than the query logs, so you'd probably choose to use that unless it's not available (e.g. it's not enabled on RDS).
I've used pgFouine (possibly the inspiration for pgBadger, given the name similarity?) to analyze posgres logs -- but it was the sort of thing where we'd enable detailed (esp. query-level) logging, capture a bunch of logs, then switch the logging back to "production mode" again and analyze the logs.
This seems targeted for constant use on production servers -- I'd love to see more info about what it costs to run (in RAM footprint, in performance, etc.). Next (as possible) would be a list of places that run it.
@sciurus, this isn't your project but you use it -- is that right?
I'm not a user, just someone who's been looking at PostgreSQL monitoring tools lately and submitted this when I saw the release announcement. Since all my databases are on RDS, I can't use pg_stat_statements and tools like this that build on it. If anyone from AWS is reading this, let us enable that extension please!
pgBadger[0] log analyzer is from the same creator, and whilst not real-time, it provides great stats and breakdown with a nice web interface. I wonder why PoWa was split from it instead of integrating real-time stats into it...
[0]https://github.com/dalibo/pgbadger