Skip to main content

Working with Alerts

View, acknowledge, resolve, and reroute alerts.

D
Written by Dave Rochwerger

The Alerts list is where you see and act on everything Phoenix Alerts is paging on. In Phoenix Alerts these are "alerts"; Jira issues are "incidents".

πŸ“Š The Alerts list

The list shows these columns:

  • Number – the alert's number.

  • Alert Key – an icon shows whether it came from a Phoenix incident or directly from a monitoring tool.

  • Severity – SEV1 to SEV5.

  • Status – the current state of the alert.

  • Service, Team, Summary, and Created.

🚦 Statuses

  • Triggered – no one has responded yet.

  • Acknowledged – someone is handling it.

  • Resolved – closed.

  • Unrouted – no service or team to page, so no one has been notified.

βš™οΈ List actions

  • Click a row to open the alert.

  • Refresh – reload the list.

  • Filter by Status, Severity, Service, Team, and Source.

  • When there are unrouted alerts, a warning banner offers Show only unrouted.

πŸ” The detail page

Opening an alert shows its status (with an action menu), key, severity, service and team, summary, source, and timestamps (created, updated, acknowledged, resolved). It also shows a link back to the source (external reference), how many times it has been deduplicated, and the linked incident if it came from Phoenix Incidents. Three tabs give you the full history:

  • Status History

  • Notification Attempts

  • Timeline

βœ… Actions by status

  • Triggered – Acknowledge or Resolve. Acknowledging stops the automatic escalation.

  • Acknowledged – Resolve.

  • Unrouted – Resolve or Re-Route. Re-Route lets you pick a service or team to page now, sending the alert to that target.

  • Resolved – final, with no further actions.

Did this answer your question?