Alert Lifecycle

Every alert in YipYap follows a defined lifecycle. Understanding these states and transitions helps you respond effectively and configure your escalation policies correctly.

Alert States

State	Description
Firing	The monitor has confirmed a failure and the alert is active.
Acknowledged	A team member has acknowledged the alert but not yet resolved it.
Resolved	The issue has been fixed and the alert is closed.

State Transitions

Monitor fails (threshold reached)
        |
        v
    [ Firing ]
        |
        +--> Acknowledged (manual)
        |         |
        |         +--> Resolved (manual or auto)
        |
        +--> Resolved (auto-resolve when monitor recovers)

Firing

An alert enters the Firing state when a monitor’s confirmation threshold is reached. At this point, the escalation policy begins executing its steps.

Acknowledging

When a team member acknowledges an alert, the escalation policy pauses. No further escalation steps run. The alert remains open until it is resolved.

You can acknowledge alerts from:

• The YipYap dashboard.
• Interactive buttons in Slack, Discord, or Telegram notifications.
• The YipYap API.

Resolving

An alert can be resolved in two ways:

• Manual resolve: A team member clicks the resolve button in the dashboard or a notification.
• Auto-resolve: The monitor recovers (returns to the Up state) and YipYap automatically closes the alert.

Auto-resolve is disabled by default and can be toggled per monitor.

Timestamps

Each alert records the following timestamps:

• Fired at: When the alert first entered the Firing state.
• Acknowledged at: When a team member acknowledged the alert.
• Resolved at: When the alert was closed.

Working with Alerts

1. Open the Alerts page from the sidebar to see all active and recent alerts.
2. Click on an alert to view its details, including the monitor that fired it, the escalation steps taken, and timestamps.
3. Click Acknowledge to pause the escalation policy and signal that you are investigating.
4. Once the issue is fixed, click Resolve to close the alert. Alternatively, if auto-resolve is enabled, the alert closes automatically when the monitor recovers.
5. Review the alert timeline to see a chronological log of all notifications sent, acknowledgments, and status changes.

Note

You can also acknowledge and resolve alerts directly from Slack, Discord, or Telegram using the interactive buttons in the notification message.

Severity Levels

Each alert carries a severity level that indicates its urgency:

Severity	Label	Description
SEV1	Critical	Service is down or a critical failure occurred.
SEV2	Warning	Degraded performance or a non-critical failure.
SEV3	Info	Informational, no immediate action required.

Severity is displayed on alert cards in the dashboard and included in notification messages. The severity is determined by the monitor’s configured down severity and degraded severity settings.

Alert Rollup Graph

At the top of the Alerts page, a 7-day alert volume chart shows the number of alerts fired per day. Alongside the chart, you will see aggregate stats for Mean Time to Acknowledge (MTTA) and Mean Time to Resolve (MTTR), giving your team a quick overview of alert response performance over the past week.

Auto-Resolve

Monitors with auto-resolve enabled automatically resolve their alerts when the monitor recovers to a healthy state. Auto-resolve is disabled by default and can be toggled per monitor.

Incident Auto-Resolve

At the organization level, you can enable automatic incident resolution. When this setting is active, incidents auto-resolve when all linked alerts have recovered. Configure this in Settings > Organization under the incident settings section.

Alert History

All alerts are retained in the alert history for auditing. You can filter by monitor, state, time range, and who acknowledged or resolved the alert.