Skip to main content
Version: 0.4 · current

Acknowledge and work an alert

How-to guideReviewed October 11, 2026
Applies to:Excubius 0.4Roles: Operator, Editor, Entity admin
PlansFree · Core · Pro · EnterpriseDeploymentSelf-hosted

When an alert fires, the first thing your team needs to know is that someone has it. This guide shows how to acknowledge an alert in the Alert inbox, and then silence, assign or resolve it.

Before you begin​

  • You need the Operator role or higher on the alert's entity. A Viewer can read alerts but not act on them; the detail panel says Your role on this entity lets you read this alert; operators and above act on it.

How an alert moves​

Acknowledge an alert​

  1. Open the Alert inbox. It shows active alerts you have not seen yet, most severe first.
  2. Select the alert. The detail panel opens and the alert is marked as seen by you.
  3. Read three things before acting: the rule it broke and where that threshold is set, the Suggested action from the check catalog, and the root cause if the alert depends on another one.
  4. Select Acknowledge. Your name and the time are recorded.

The alert now shows Acknowledged for everyone, with your name in its timeline. Acknowledging does not mute the alert: Excubius still tells the channel if its severity rises and when it resolves.

Silence, assign or resolve​

ActionWhen to use itWhat happens
Silence for 1 hour, 4 hours or 1 day, or Silence for another duration… from 1 minute to 30 days with an optional noteYou know the cause and need quiet while you fix itNo notifications until the time is up, except the resolution. If the condition still holds then, the alert opens again
Assign: Assign to me, a person with access to the entity, or Remove the assigneeSomeone else should own itThe assignee is shown in the inbox, which filters by Assignee › Me
Resolve, with an optional noteYou fixed it and do not want to wait for the next checkThe alert closes with your note. If the condition still holds, the next check run opens a new alert
Create Jira ticketThe work needs a ticketThe ticket is prefilled from the alert and its key is stored on it. Available when the Jira integration is on, in the Pro and Enterprise plans
tip

When one failure explains others, the detail panel names the root cause under Caused by and lists the alerts that depend on it. Work the cause; when it clears, the dependents it explained resolve with their next check.