> ## Documentation Index
> Fetch the complete documentation index at: https://docs.obsy.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Create an incident

> Open an incident manually or automatically from an alert.

## Manual creation

1. Go to **Incidents** and click **New incident**.
2. Fill in:
   * **Title** — what is the impact? (e.g. "Payment service returning 503s")
   * **Severity** — SEV1 to SEV4
   * **Affected services** — select from your service catalog
   * **Description** — initial context, what's known so far
3. Click **Create incident**.

If Slack is configured with **Auto-create channel** enabled, a Slack channel is created immediately with the channel name derived from your template (e.g. `inc-2026-01-payment-sev1`).

***

## Automatic creation from alerts

Obsy can automatically create incidents when an alert fires. Configure this under **Incidents → Settings → Auto-create rules**.

Each rule matches on:

* **Alert severity** (e.g. only Critical)
* **Alert source** (Datadog, Grafana, New Relic)
* **Service name** (optional — leave blank to match any service)

When a matching alert arrives via webhook, Obsy creates the incident immediately and links the alert to it. The incident title and severity come from the alert.

***

## Updating an incident

Open the incident detail and use the **Update status** button to move through statuses:

`Open → Investigating → Identified → Monitoring → Resolved`

Each status change adds a timestamped entry to the incident timeline. You can also add free-text timeline updates by typing in the **Add update** field.

***

## Resolving an incident

Click **Resolve** in the incident header. Obsy:

1. Sets the status to Resolved and records the resolved timestamp.
2. Archives the Slack channel (if auto-archive is configured) after the configured delay (default 7 days).
3. Shows a prompt to create a postmortem.

***

## Linking to RCA and postmortem

Inside the incident detail:

* **Root cause analysis** — click **View RCA** to open the linked AI analysis, or **Run RCA** to trigger a new one.
* **Postmortem** — click **Create postmortem** to open the postmortem editor pre-filled with incident data.