See CHANGELOG.md for the summary, and docs/changelog/3.12.md for the full entries.
Read before you upgrade
- Darling: the first start after the upgrade runs store migrations V215 to V229 (schema 214 to 229).
- Lite: the DuckDB schema stays at 78. Lite has no migration in this release.
- Self-managed stores: if you set up your own PostgreSQL store, run
Darling/tools/provision-roles.sqlagain after the upgrade. - Client Timeouts alert: this alert is now on in Darling and Lite after the upgrade. If you had it off on purpose, turn it off again.
- MCP and the web dashboard: the Darling web dashboard and MCP server, and the Lite MCP server, need a token when they are on. Lite's Settings has a Copy MCP config button.
- Web Admin writes: after an upgrade they stay off until you set
web.allowAdminWritesto true. - Route edits on the 3.11.0 web dashboard: in 3.11.0, a save of an edit to an existing notification route failed with HTTP 400. 3.12.0 fixes this.
After upgrading Darling
This release adds two Darling collectors that read three msdb tables. A monitoring login set up for an earlier release does not have these grants. Until you add them, those collectors show as "no permission" in Collection Health. Run this on each SQL Server target, with your monitoring login in place of [YourLogin]:
USE [msdb];
GRANT SELECT ON dbo.sysalerts TO [YourLogin]; -- SQL Agent alert definitions and counters
GRANT SELECT ON dbo.sysnotifications TO [YourLogin]; -- the operators each Agent alert notifies
GRANT SELECT ON dbo.backupset TO [YourLogin]; -- the last full and log backup per databaseThe grants are optional. Without them, the rest of collection continues as normal. Lite does not use these collectors. The Agent alerts collector does not run on Amazon RDS, Azure SQL Database or Azure SQL Managed Instance. Those servers do not need the first two grants. See docs/permissions.md for the full list.