Alerts

Purpose

• Review the root-cause alerts the ITSM engine has raised across the platform.
• Triage by severity (critical, down, degraded, warning, info) and by status (open, acknowledged, resolved).
• See each alert's affected configuration items (CIs) and their dependency graph.
• Read the engine's AI root-cause analysis, confidence, justification, and proposed remediations.

Prerequisites

• Minimum permission to view: platform.alerts.read.
• Root account only; non-root accounts see no alerts.
• Alerts are produced by the vmease-itsm engine from correlated monitoring signals; this surface only displays them and never writes to them.

View alerts

1. Open Alerts from the bell icon in the top bar (root account only), or go to /alerts.
2. Read the severity summary cards; select one or more to filter the list by severity.
3. Adjust the date range and the "Show resolved alerts" toggle to widen or narrow the list (resolved alerts are hidden by default).
4. Expected result: the current alerts listed worst-first.

Open an alert

1. Select an alert row, or pick one from the top-bar bell menu (opens /alerts/{id}).
2. On the Details tab, read the AI root cause, confidence, justification, dependency graph, and proposed remediations.
3. Open the Events tab for the linked events and the CIs they affect.
4. Open the Timeline tab for the chronological triage and engine actions.
5. Expected result: the full context behind the alert, presented read-only.

Best Practices

• Do not look for acknowledge, resolve, execute, or alert-rule controls; the alert lifecycle is owned entirely by the ITSM engine and only reflected here.
• Treat remediations as proposals; run them yourself through the appropriate resource, never from this page.
• Use Compute → Monitoring for the underlying live metrics; Alerts show the engine's correlated conclusions drawn from that telemetry.
• Copy a suggested remediation command with the copy icon rather than retyping it.