SQL System Monitor

The SQL System Monitor is a live view over the server's own catalog of currently-running work — the queries in flight, the process list, and every server variable and status counter — polled straight from the server. No agent, no extra instrumentation. It's the tab you keep open in a second window while you're debugging why the app got slow five minutes ago.

Opening the Monitor

The activity is scoped to a specific SQL connection — open it from the connection's action bar in the SQL sidebar. Every open connection gets its own tab.

The tab is titled DB System Monitor, with a Connected badge and a Refresh button. Three cards across the top show the full server version string, how long the server has been up, and the number of active connections. Each tab below carries a count of its rows.

Current Queries Tab

A live table of queries the server is currently running. Rows carry a status pill: Running (green pulse) for in-flight statements and Done (dimmed) for statements that have finished since the last render — so you can see something completing between polls instead of it just vanishing.

• Refresh interval selector — Off, 1s, 2s, 5s, 10s, 30s. Default is 2s. A green pulsing dot next to the selector reads "Streaming" while polling is active; picking Off shows "Paused".
• Columns — driver-provided (typically ID, User, Host, DB, Command, Time, State, Info/Query on MySQL). The Info/query cell wraps and uses a monospace font so long statements stay readable.
• Open in SQL Editor — every row with a captured query has an "open" icon that copies the query into a new SQL Editor tab, ready to EXPLAIN or edit.

Processes Tab

Full process list from the server (e.g. SHOW FULL PROCESSLIST on MySQL). This is a superset of Current Queries — includes idle sessions, replication connections, and workers not currently executing a statement — and the column set is whatever the driver returns.

Variables Tab

Every server variable (e.g. SHOW VARIABLES). A filter box at the top narrows the list by substring — handy when you're hunting for a specific tunable (innodb_buffer_pool_size, max_connections, etc.) without scrolling through hundreds of entries.

Status Tab

Server status counters (e.g. SHOW STATUS) — Threads_connected, Questions, Innodb_rows_read, and so on. Same filter box as the Variables tab.

Pro Tips

1. Bump the interval to 5s or higher on busy servers. 1s or 2s is fine for local dev; on a production connection it means one SHOW PROCESSLIST per second per open monitor tab.
2. Use the Info/query column as the funnel. Long-running rows that stay Running across several polls are the ones to open in the SQL Editor and EXPLAIN.
3. Pair Current Queries with Query Profiling. The monitor shows what's running right now; the SQL Profiling activity shows a historical feed of slow queries the server has already captured.
4. Bookmark specific variables. Filter the Variables tab to a single name and keep the tab open — it's the fastest way to spot a runtime config change.

Related Features

• SQL Profiling - Captured slow-query feed to complement the live view here.
• Server Build Info - Static server metadata (version, driver, per-database sizes) to complement the live counters.
• SQL Editor - Where the "Open in SQL Editor" action from the query row lands.