Feature · /query-activity
查询活动
你的数据库此刻在做什么 — 又在等谁。
In one line
1Hz 实时流式传送活跃会话,附等待事件、锁链与慢查询告警。
What you get
- 1 Hz sampling of pg_stat_activity / SHOW PROCESSLIST / db.currentOp() / v$session
- Wait-event flame graphs by signature, by host, by database
- Long-running query detection with configurable thresholds
- Lock chain visualization — see which session is blocking which
- Per-session attribution to app, user, query digest
- Alert on activity patterns: 'more than N sessions in LWLock for 60s'
vs Datadog DBM
FAQ
How much load does 1 Hz sampling add?+
Under 1% CPU on a Postgres host with 200 concurrent sessions. The pg_stat_activity view is in-memory.
Can I see historic activity, not just live?+
Yes — every sample is persisted in ClickHouse for 30 days (Team) or 90 days (Business). You can scrub backward to any moment.
Related reading
Postgres
Postgres lock chains: how to find the session blocking yours
A practical walkthrough of pg_locks, pg_blocking_pids, and the recursive CTE that gives you the full chain — including the AccessExclusiveLocks that quietly take your DB down.
Postgres
Postgres slow queries: 12 causes and how to find each one
A field-tested playbook for diagnosing a slow Postgres query in production — from missing indexes to plan flips to bloated tables — with the SQL to find each cause and the fix.
MongoDB
MongoDB performance monitoring in production: a 2026 guide
Four surfaces (serverStatus, db.stats, currentOp, profiler), a sane default for what to scrape from each, and how to reason about replica lag, oplog window, and aggregation pipeline cost.