Closed arlt closed 7 years ago
Hello,
Having to wait a little is expected, it's showing evolution of data, so you need at least two snapshot to see something (so with default settings, 10 minutes).
For the lack of query in the per-database view, I think the problem comes from here:
Speed factor for replay: 1.000 Total run time: 54.799 seconds
With current design of powa, queries that are only executed between two snapshots and never again won't be displayed in the per-database. This is usually not a problem since you don't want to analyze stuff that'll never be run again, but in your case if you want to perform some analysis on the replayed activity (I presume this is not production database), I think the easiest way is to configure powa.frequency more aggressively, like 5s.
Thanks - great hint(s). In a first try i removed parameter '-j' and set powa.frequency to 5s. Works.
Hi,
we use a schema with the same name as the database:
testdb
- i don't know why, but i am sure, that i have no chance, that we change this.I use pgreplay to replay the SQL statements:
In http://localhost:8888/overview/ i can see the database 'testdb' only with 1 call. After some time and a reload, i can see 3625 calls.
If i select the database (http://localhost:8888/database/testdb/overview/), i can't see any SQL statement.
Again, if i wait some time ... i can see 9 statements (ROLLBACK on top with 4 calls) - presumably from public schema:
Filtering works, but i can only see those statements above.
If i manually enter a query, i can't see it in powa-web, too - regardless of the timerange. The statements can be found in the powa database (powa_statements_history_current). The corresponding queryid can be found in powa_statements.
Example:
Did i miss something?!
Kind regards Michael