Events are the audit trail of the alerting system. Every time an issue is opened or closed, a notification is sent, or an incident is acknowledged, Atatus records an event with a timestamp and relevant metadata.

Event types

Event Type Description Metadata
Issue Opened A new metric violation was detected Incident ID, target name
Issue Closed A metric violation was resolved Incident ID, target name
Notification A notification was sent to a channel Channel name, channel type, incident ID
Incident Acknowledged A user acknowledged an incident User name

Event details

Every event contains:

Field Description
Title A human-readable summary of what happened
Description Additional context about the event
Type One of the four event types above
Product The monitoring product involved (Browser, APM, Infrastructure, Kubernetes, etc.)
Timestamp When the event occurred

Viewing events

Navigate to Alerting > Events to see the full event history. You can filter by:

  • Incident — View all events for a specific incident
  • Search — Search by event title or description

Events are displayed in reverse chronological order (newest first).

Example timeline

Here is a typical sequence of events for a single alert lifecycle:

Time Event Type Title
14:05 Issue Opened Web Response Time exceeded 2s on checkout-service
14:05 Notification Sent to Slack channel #api-alerts
14:05 Notification Sent to PagerDuty (On-Call)
14:08 Incident Acknowledged Acknowledged by Sarah
14:15 Issue Opened Web Response Time exceeded 2s on payment-service
14:15 Notification Sent to Slack channel #api-alerts
14:22 Issue Closed Web Response Time returned to normal on checkout-service
14:28 Issue Closed Web Response Time returned to normal on payment-service

This timeline shows how events capture the full story of an alert — from initial detection through notification, acknowledgment, and resolution. Each event is permanent and provides an audit trail for post-incident review.