The Live Monitor and flight recorder

The Live Monitor samples your database every few seconds and shows what is happening right now: active queries, the blocking tree, waiting locks and key metrics. You can cancel or terminate a runaway backend right from the list.

A flight recorder that is always on

Because a lock pile-up can flare and clear in thirty seconds, the Monitor keeps an always-on rolling buffer of roughly the last twenty minutes per connection. The recent past is there the moment you reach for it.

Save and replay an incident

1. The moment something flares up, click Save incident to freeze the recent history into a saved capture — before it is gone.
2. Or hit Record to keep every sample from now until you stop, seeded with the lead-up so you never miss the start.
3. Open any capture and scrub back and forth on a timeline: step sample by sample, watch the blocking queries and waiting locks evolve, and keep your findings in notes that stay with the capture.

Which databases it works on

The Monitor reads each engine’s own live views rather than a lowest common denominator, so what it can show differs by engine. Sessions, queries and cancellation are real on PostgreSQL and everything on its wire (CockroachDB, YugabyteDB, TimescaleDB, AlloyDB, Cloud SQL), the MySQL family, SQL Server, Oracle, MongoDB, Redis, Cassandra and ScyllaDB, Neo4j and Memgraph, Elasticsearch and OpenSearch, Couchbase, ClickHouse, Trino and Presto, and Snowflake.

Some engines have no sessions to show but do report storage: SQLite, DuckDB, BigQuery, DynamoDB, Qdrant, Weaviate and Pinecone feed the size metrics and their alerts, and say plainly that there is no session view. Where an engine exposes neither, the Monitor shows a "not supported on this engine" panel instead of an empty one — each engine’s guide says exactly which case it is.