Overview

Issues represent active problems affecting your status page components. When an issue exists for a component, that component's status changes from Operational to either Degraded or Outage depending on severity.

How issues work

Issues are the mechanism that connects investigations to status page visibility:

Problem detected: Chat identifies an issue during investigation
Issue created: An issue is created for the affected component with a severity
Status updated: The component's health indicator changes on the status page
Issue resolved: When fixed, the issue is resolved and status returns to operational

This issue-based model ensures your status page reflects real, investigated problems rather than metric noise or transient errors.

Issue lifecycle

Every issue follows a simple lifecycle:

Created → Active → Resolved

Created: Issue is opened with a component, severity, and summary
Active: Component shows degraded or outage status while the issue is open
Resolved: Issue is closed, component returns to operational

Multiple issues can be active for the same component. The status page shows the worst severity among all active issues.

What's in this section

Severity Levels

Understand degraded and outage severity levels and how they affect displayed status.

Creating Issues

Learn how issues are created by Chat and through alert linkage.

Resolving Issues

Understand manual resolution, auto-resolution, and resolution timing best practices.