-
Notifications
You must be signed in to change notification settings - Fork 25
Description
Problem
Both Dashboard and Lite collect point-in-time snapshots from sys.dm_os_waiting_tasks (Lite every 1 min, Dashboard via collect.waiting_tasks_collector), but neither app displays this data anywhere in the UI. It's only accessible via MCP tools (get_waiting_tasks).
The lock wait trend charts use sys.dm_os_wait_stats, which only records completed waits. During continuous blocking, the in-progress wait doesn't show up in dm_os_wait_stats until the block is released — so the trend charts show near-zero while sp_WhoIsActive shows 600+ seconds of LCK_M_S wait time.
Expected behavior
A "Current Waits" view (tab or section) that shows what's actively waiting right now, sourced from the collected waiting_tasks data. This complements the wait stats trend charts by showing in-progress waits rather than only completed ones.
Data available
Lite (waiting_tasks DuckDB table)
- session_id, wait_type, wait_duration_ms, blocking_session_id, resource_description, database_name, query_text, collection_time
Dashboard (collect.waiting_tasks SQL Server table)
- Similar columns collected by
collect.waiting_tasks_collector
Context
Discovered while investigating why the lock wait trend charts showed 0.1 ms/sec during continuous blocking that sp_WhoIsActive reported as 601,119ms of LCK_M_S. The data to show this exists — it's just not surfaced in the UI.