Updates
The updates module compares what is installed on each resource with what the vendors have released: how far behind a SQL Server build is on its servicing line, when support ends, which Microsoft security advisories concern it and which updates are pending. It only informs. Excubius never installs anything; the decision and the change stay with you.
What it monitors
| Area | Checks | Why it matters |
|---|---|---|
| SQL Server builds | A new build of a SQL Server version in use, from the build reference list | Shows a new cumulative or security update the day it appears |
| End of support | Days to the end of support of each product version in use, from endoflife.date: warning under 180 days, critical under 30 | Unsupported versions get no more fixes |
| Security advisories | A new monthly release of Microsoft security updates for a product in use, from the MSRC API | The starting point of every patch cycle |
| Pending updates | Security and critical updates pending on Azure VMs, from Azure Update Manager; pending patches reported by NinjaOne | Updates that are approved or available but not installed |
The installed side comes from other modules: the build of each SQL Server instance (sqlserver.build_version), the Windows version (windows.os_version), the distribution and version attributes of Linux hosts, and the pending updates checks of Windows and Linux. The Updates & advisories page puts both sides together; see Track updates and advisories.
The catalog also lists Microsoft Update Catalog searches, GitHub releases, Linux security errata and Azure updates; they are not implemented yet and are off by default.
Every check, with its rule, cause and action, is in the reference for updates checks.
Before you begin
-
The module is on. The feature
monitoring.updatescovers this module and the Updates & advisories page. -
Outbound HTTPS from the Excubius server to the feeds. The API fetches them, not the collector:
Feed Address SQL Server builds (dbatools build reference) dataplat.github.io, thenraw.githubusercontent.comEnd of support endoflife.dateMicrosoft security advisories api.msrc.microsoft.comThe API honours
HTTPS_PROXY. Without Internet access, setEXCUBIUS_FEEDS_ENABLED=false: the copies of the SQL Server builds and support dates shipped with the release are used; MSRC advisories have no shipped copy. See Environment variables. -
For Azure Update Manager, Reader on the VMs' subscriptions for the server's identity. The check is scoped to each VM's
resource_id. -
For NinjaOne patches, the NinjaOne source with Pending patches selected.
Add a resource
The feed checks raise their alerts, of category advisory, on a Monitoring platform itself resource. Add one on the entity whose people should get those alerts, usually the root:
- Open Resources › Add resource and choose Monitoring platform itself.
- Choose the entity and a name, such as
Platform, and select Create resource.
The pending updates checks appear on the Azure VMs and NinjaOne devices that the sources report. See Add a resource.