Alerts

Alerts is one domain with three facets: Inbox, Monitors, and Delivery. Alerts are raised by monitors you define. Configuration policies select the devices a monitor reaches.

Inbox

Open Alerts to review active problems. Filter by severity, device, status or time, then open an alert to see its context and history. Acknowledge an alert when someone takes responsibility; resolve it when the problem is fixed. Suppression and maintenance windows affect notification/evaluation behavior according to their configured scope. Correlations remain available when enabled.

Condition-based alerts trace to a monitor. Feature engines such as compliance, warranty, security, patching and backup also raise alerts; their configuration remains with those features.

Monitors

Open Alerts → Monitors to create a condition, choose its severity and noise settings, add device-bound responses, and choose delivery and escalation. Attach the monitor to a configuration policy and assign that policy to devices. See Monitors for kinds, deployment and legacy retirement.

Per-monitor responses run on the device whose alert triggered them. For a broad workflow such as “any critical CPU alert → triage,” open Jobs → Alert workflows. Optional severity and monitor-kind filters narrow which alerts start that workflow. Compiler-managed automations are hidden from the Jobs list.

Delivery

Open Alerts → Delivery for Channels, Routing, and Escalation policies. A monitor’s Notify setting takes precedence; otherwise routing selects the first matching row. The explicit Everything else row supplies the default. New channels receive no alerts until added to a routing row or monitor override. See Notifications and delivery.

Legacy alerting retirement

The legacy policy alert and service/process tabs have been removed. Create and test conditions in Alerts → Monitors, then attach them on a policy’s Monitors tab. The previous release offered conversion previews; this release processes remaining legacy sources at startup. Items that cannot convert are retired with a reason and listed on Alerts → Monitors for review.

Open alerts from unconvertible retired sources stay open until someone resolves them. Source rows and history are retained, but Conversion history → Undo is unavailable for sources whose runtime was removed in this release. See Monitors for replacement and review guidance.