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

# Incidents

> Track production incidents caused by deployments.

export const CtaGetStarted = ({label = "Ready to make delivery flow again?"}) => <div style={{
  display: "flex",
  justifyContent: "space-between",
  alignItems: "center",
  marginTop: 80,
  background: "#1a1b1e",
  color: "#fff",
  borderRadius: 8,
  border: "1px solid #69db7c",
  padding: "10px"
}}>
    <div style={{
  display: "flex",
  justifyContent: "space-between",
  alignItems: "center",
  gap: 12,
  fontWeight: 500
}}>
      <img src="https://mintlify.s3-us-west-1.amazonaws.com/sweetrdev/logo.svg" height={24} width={24} style={{
  margin: 0
}} />
      <div>{label}</div>
    </div>
    <a href="https://github.com/apps/sweetr-dev/installations/new" rel="nofollow" className="not-prose" style={{
  padding: "8px 16px",
  background: "#69db7c",
  color: "#000",
  borderRadius: 4,
  fontSize: 14
}}>
      Try now
    </a>
  </div>;

## Demo

<Frame>
  <img src="https://mintcdn.com/sweetrdev/pcmOxpRgFjEN2lK0/images/incidents.png?fit=max&auto=format&n=pcmOxpRgFjEN2lK0&q=85&s=36a659052771a99260af4f2b759920ac" width="2560" height="1280" data-path="images/incidents.png" />
</Frame>

## How it works

Incidents represent production issues caused by a deployment. They track the full lifecycle from detection to resolution, linking back to the deployment that caused the issue and the deployment that fixed it.

## Key fields

| Field                | Description                                          |
| -------------------- | ---------------------------------------------------- |
| **Cause deployment** | The deployment that introduced the issue (required). |
| **Fix deployment**   | The deployment that resolved the issue.              |
| **Detected at**      | When the incident was detected.                      |
| **Resolved at**      | When the incident was resolved.                      |
| **Team**             | The team responsible for the incident.               |
| **Leader**           | The person leading incident response.                |
| **Postmortem URL**   | Link to the postmortem document.                     |

## Creating incidents

Incidents can be created in two ways:

* **Manually**: Create an incident from the UI, linking it to the deployment that caused it.
* **Automatically**: Use the [Incident Detection](/automations/incident-detection) automation to detect incidents from rollbacks, hotfixes, and reverts.

## Impact on metrics

Incidents directly feed into two DORA metrics:

* **Change Failure Rate**: The percentage of deployments that caused an incident.
* **Mean Time to Recovery**: The average time between incident detection and resolution.

## Archiving

Incidents that are no longer relevant can be archived. Archived incidents are excluded from metrics. You can unarchive them at any time.

## Related

<CardGroup cols={2}>
  <Card title="Incident Detection" icon="circle-dot" href="/automations/incident-detection" />

  <Card title="Deployments" icon="rocket" href="/platform/deployments" />

  <Card title="DORA Metrics" icon="chart-line" href="/metrics-and-insights/dora" />
</CardGroup>

<CtaGetStarted />