Alerts

Alerts tell you when something needs attention. concorbit RMM scores alerts by severity and recency so the most urgent problems surface first.

Alert policies

An alert policy defines what triggers an alert. Go to Settings > Alert policies to create one.

Each policy has:

• Conditions: metric, operator, and threshold (e.g. "CPU above 90% for 5 minutes")

• Severity: emergency, critical, warning, or info

• Scope: organisation-wide, per site, per device type, or per individual device

• Notification channels: which channels receive this alert

• Cooldown: minimum time between repeated alerts for the same condition

The most specific scope wins. A device-level policy overrides a site-level one.

Today view

The default alerts page shows scored alerts that need human attention. Scoring combines severity weight and recency: a critical alert from 10 minutes ago scores higher than a warning from yesterday.

The top alerts display as cards with severity badge, device name, alert message, and action buttons. Below them, a collapsible section shows remaining active alerts.

All alerts view

Switch to All alerts for a paginated table with filters for severity, acknowledgement status, and sort order. Export the current view as CSV.

Acknowledging an alert

Acknowledging tells your team someone has seen the alert and is handling it. Click Ack and optionally add a note. Acknowledged alerts dim and drop from the Today view.

Suppressing an alert

Suppressing silences an alert for a set time: 30 minutes, 1 hour, 4 hours, 8 hours, or 24 hours. Use it for planned maintenance or known issues.

Notification channels

Go to Settings > Notification channels to configure where alerts are delivered.

Each channel can be tested before going live. Failed deliveries retry automatically.

Quiet hours

Define quiet hours per site in Settings > Maintenance windows. During quiet hours, non-emergency alerts are held. Emergency and critical alerts still deliver immediately.