diff --git a/CHANGELOG.md b/CHANGELOG.md index e7eb833893..abc87128a4 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -33,6 +33,21 @@ Releases before 3.0.0 are not archived: those entries carry no prose to move. - **People can give feedback on investigation reports** ([#5926]) - A report can be marked right, partly right or wrong, with a corrected verdict, the step the agent missed and a comment, from the Viewer's Investigations window (Report Feedback tab, admin login) or the web Admin page's new Report Feedback tab (recorded only under an admin store login; list-only otherwise). `get_investigation_reports` now returns each report's feedback and, per alert family, how many investigations ended as false positives before and after people's corrections. - **Lite: Level 1 agent investigations** ([#5820]) - when an alert fires on a notification route whose agent level is 1, Lite opens an investigation request for it, and when `mcp_allow_investigations` is on with MCP writes off it serves four tools (`list_investigation_requests`, `claim_investigation_request`, `submit_investigation_report`, `get_investigation_reports`) so a local agent can claim the request, read its brief, and file a report that Lite keeps beside the alert. Requests, reports, notes and the journal live in Lite's own DuckDB file; nothing writes to a monitored server; with both MCP settings on the investigation tools stay off and Lite logs one Critical line saying so. - **Deadlock graph window: a visible Copy button for the SQL text** ([#5663]) - the only ways to copy a process's SQL text were the right-click "Copy SQL Text" menu item or selecting the text box and pressing Ctrl+C, and the menu was easy to miss. The Properties panel now has a Copy button on the same row as the "SQL Text" heading, in Lite and the Darling viewer. It copies the same full SQL text as the menu item, through the same code, and is only shown when the process has SQL text. +- **The web dashboard charts file I/O throughput, tempdb size and I/O, and collector duration** ([#6296], [#6297], [#6298]) - a new I/O Trends tab (up to the last 7 days) charts file I/O throughput per file, tempdb allocated size and per-file tempdb I/O latency, and Collection Health charts collector duration over time for the five slowest collectors, as the desktop viewer does. +- **The web dashboard compares Top Queries, Top Procedures and Query Store with an earlier period** ([#6300]) - each of the three grids, and the Top Queries and Top Procedures cards on the CPU tab, has a Compare picker (Yesterday, Last week, Same day last week) that shows each row's change in executions, average duration and average CPU against the earlier period, with NEW and GONE badges. Each window is its own top 100, so a row ranked below 100 in the earlier window reads NEW; the card says so. +- **The web Blocking page shows the lead-blocker tree of a blocked process report** ([#6292]) - each row has a new Block chain button that opens the lead-blocker tree of that report, as the desktop viewer does. The Darling Viewer and Lite block chain windows now show transaction start times in the chosen display mode (Server, Local or UTC); they showed the raw server clock in every mode. The web serves them in UTC. +- **The web System Events tab charts the corruption and contention counters** ([#6295]) - it now charts bad pages, dump requests, access violations, write access violations, non-yielding tasks, latch warnings and sick spinlocks over time, as the desktop viewer does. +- **The web Active Queries tab picks a stored snapshot** ([#6302]) - the tab now opens on the latest stored snapshot and has a picker over the snapshots in the window, with an "All snapshots in window" choice, and a chart's "Active queries at this time" opens on the nearest snapshot. The Darling MCP tool `get_active_queries` takes two new optional parameters: `snapshots_only` lists the window's snapshot times, newest first, with each snapshot's row count, and `collection_time` returns one snapshot's rows. Lite's `get_active_queries` is unchanged. +- **Alerts show how many days in a row they fired at the same time of day** ([#6261]) - in Darling and Lite, `get_alert_history` takes a new optional `include_streak` (default false) that adds `streak_days` (days in a row an alert fired within 30 minutes of the same time of day, counting muted fires, up to 7) to each row, and investigation briefs show the same streak beside the recurrence counts. +- **The web server page shows the Daily Health Calendar as a month calendar** ([#6294]) - the web showed the daily summary without a calendar. It is now a month calendar of daily health bands with month buttons, a day detail that gives the reasons, and buttons that open the matching tab at that day. +- **The web dashboard draws the Query Heatmap as a colour grid** ([#6293]) - the web showed the heatmap only as a table of its cells. It now draws the grid as the desktop viewer does: time across and duration buckets down, a one-hue shade by query count, a metric picker, hover details for each cell, a jump from a selected cell to Active Queries at that time, and a Show as table switch. A window up to 600 px wide opens on the table. The heatmap read returns up to 1000 cells, up from 500, and bins get wider on long windows so the grid stays near 144 columns. +- **The web Memory tab charts memory grant sizing and activity, and `get_memory_grants` can return the same series** ([#6299]) - the web Memory tab had no chart of grants. It now draws memory available, granted, used and target over the selected window, one line per resource pool. The Darling MCP tool `get_memory_grants` takes two new optional parameters, `chart` and `bucket_minutes`; with `chart` true it answers the same series, one point per bucket per resource pool. Lite's `get_memory_grants` is unchanged. +- **The web dashboard opens a per-row history for Top Queries and Top Procedures** ([#6303]) - each row has a History button that opens that query's or procedure's trend (procedures include average CPU), as double-clicking a row does in the desktop viewer. The Darling MCP tool `get_procedure_duration_trend` takes an optional `procedure_name` to read one procedure. Lite's `get_procedure_duration_trend` is unchanged. +- **The web Overview draws five strips on one time axis** ([#6291]) - CPU, waits per second, blocking and deadlocks, buffer pool and file I/O latency are drawn as five stacked strips with a shared crosshair and a drag-zoom across all five. As in the desktop viewer, a baseline band (mean plus or minus 2 deviations) sits behind CPU, waits, blocking and I/O latency, and CPU, waits and I/O points outside it get a red dot; with too little history the strip says there is no baseline yet. The Overview no longer shows its separate CPU, Memory, Blocked report and Deadlocks charts or its File I/O panel; those stay on their own tabs. + +### Changed + +- **Lite's Query Store regressions now show timeouts and errors beside cost, and no longer report logical reads** ([#6308]) - Lite's get_query_store_regressions averaged every run type into one figure and returned logical reads, so a query whose timeouts or errors rose could be hidden and the same tool named differed from Darling's. It now compares Regular runs per execution (weighted by execution count), shows Aborted and Exception runs side by side, lists a query for cost, timeouts or errors with a regression_reason, uses Darling's thresholds, and drops baseline_reads, recent_reads and io_regression_percent. The shared tool description changed with it. ### Fixed @@ -40,6 +55,13 @@ Releases before 3.0.0 are not archived: those entries carry no prose to move. - **A collector that recovered no longer stays at WARNING** ([#5665]) - the 7-day failure rate gave WARNING above 20% errors and a later success never cleared it, so a new target with 2 errors in its first 8 runs stayed WARNING until its tenth run. The rate now counts only once the window holds 10 runs, or fewer when a collector runs so rarely that a full 7-day window holds fewer (7 for a daily collector, so a daily collector that failed 6 days of 7 and succeeded today stays WARNING), and a collector whose newest 3 runs in a row succeeded is HEALTHY with a note "recovered: the last 3 runs succeeded; last failure