Activity Monitor

functional

Live sessions, blocking chains, expensive queries, and wait stats over the engine's own session views - SQL Server, PostgreSQL, MySQL, ClickHouse, Oracle, and Redis.

A live admin pane over the connection's dynamic management views. Four tabs, each a real grid: Sessions, Blocking, Expensive Queries (top 20 by total elapsed time), and Waits - the wait tab adding a delta column per counter that shows the change since the previous refresh rather than raw lifetime totals.

Sessions and Blocking get a computed triage column, Root blocker, Blocked, Blocking cycle, Long-running, Idle in transaction, with the blocking root and chain depth resolved for you, and a filter button that cycles through those categories. The toolbar also holds the refresh interval (2, 5, or 15 seconds), Pause/Resume, Copy SQL and Open as Query for the selected row, and Copy Diagnostic for a read-only engine-native diagnostic script.

Killing a session is script-first. Script Termination opens the KILL (or pg_terminate_backend, KILL QUERY, ALTER SYSTEM KILL SESSION, CLIENT KILL) statement, commented with what it will do, for review in a tab, the pane itself never executes it.
Scope-aware. Opened from a database, the Sessions view lists only connections on that database. Opened from the server, it shows every session on the instance.

Rank by attention

With the optional decision model enabled and result-data sharing allowed, a Rank by attention switch (off on every launch) adds an Attention filter: rows judged to need intervention first, then the ones worth watching, with normal activity hidden. While that switch is on, the visible rows - including their SQL text, logins, and hosts - are sent to TypeSafe AI on each ranking pass; nothing is ever sent otherwise.

SQLly
SQLly Activity Monitor sessions grid
Activity Monitor: the Sessions grid over sys.dm_exec_sessions, with tabs for blocking, expensive queries, and waits.

Sources per engine: SQL Server DMVs; PostgreSQL pg_stat_activity with pg_blocking_pids; MySQL and MariaDB the processlist and Performance Schema (MariaDB reads InnoDB's native lock tables rather than assuming the optional sys schema); ClickHouse system.processes, with KILL QUERY scripted; Oracle V$SESSION and V$SQL, with ALTER SYSTEM KILL SESSION scripted; Redis CLIENT LIST, with CLIENT KILL. SQLite has no server activity, DuckDB runs inside SQLly with no server sessions to monitor, and libSQL / Turso serves each request on its own with no session list, the menu says so plainly on each.