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

# Incidents

> Learn how to manage incidents in Cachet.

In Cachet, an incident represents any ongoing issue or event that affects the service. Incidents can be managed via
the dashboard. Incidents consist of:

* **Name**: A brief description of the incident.
* **Status**: The current status of the incident.
* **Message**: A detailed description of the incident.
* **Occurred At**: The time the incident occurred. This can be left empty if the incident happened at the time of reporting.
* **Visibility**: Whether the incident should be visible to users, guests or always be hidden.

The Cachet dashboard provides a simple interface to manage incidents. You can quickly record a new incident by clicking the
"New Incident" link in the top navigation bar. You can also view and manage existing incidents by clicking the "Incidents"
link in the sidebar.

### Incident Statuses

Incidents and updates in Cachet can have one of the following statuses:

* <Tooltip tip="Status ID: 0"><Icon icon="square-0" /></Tooltip> **Reported**: The incident has been reported.
* <Tooltip tip="Status ID: 1"><Icon icon="square-1" /></Tooltip> **Investigating**: The incident is actively being investigated.
* <Tooltip tip="Status ID: 2"><Icon icon="square-2" /></Tooltip> **Identified**: The cause of the incident has been identified.
* <Tooltip tip="Status ID: 3"><Icon icon="square-3" /></Tooltip> **Watching**: The incident or the resolution is being watched.
* <Tooltip tip="Status ID: 4"><Icon icon="square-4" /></Tooltip> **Fixed**: The incident is fully resolved.

## Incident Components

Incidents don't typically occur in isolation. They often affect one or more [components](/v3.x/guide/components) of the service. Cachet allows you
to link incidents to components to provide more context about the incident.

Once you’ve created an incident, you can link it to a component by editing the incident and clicking "Attach" in the "Components"
panel on the incident page. When attaching a component, you may also select what status to update the component to.

## Incident Updates

Typically, incidents are ongoing events that require updates to keep users informed. Incident updates can be added to
an incident to provide more information. Incident updates consist of:

* **Message**: A detailed description of the update.
* **Status**: The [status](#incident-statuses) of the incident after the update.

To update an incident, head to the "Incidents" panel in the dashboard and click "Record Update" on the incident you want to update.

<Note>
  Updates cannot be provided for "Fixed" incidents.
</Note>

## Incident Templates

Cachet allows you to build incident templates so you can create incidents quickly. Cachet supports creating incident
templates with two templating languages:

<CardGroup>
  <Card icon="symfony" title="Twig" defaultOpen={true} href="https://twig.symfony.com" horizontal img="https://twig.symfony.com/images/logo.png">
    Twig is a flexible, fast, and secure template engine for PHP.\
    Click to learn about Twig.
  </Card>

  <Card icon="laravel" title="Laravel Blade" href="https://laravel.com/docs/blade" horizontal img="https://laravel.com/img/og-image.jpg">
    Laravel Blade is the templating engine used in Laravel.\
    Click to learn about Blade.
  </Card>
</CardGroup>

Incident templates are particularly powerful when combined with the API as they allow you to create a new incident by passing
a template and variables. An incident will be created with the template filled in with the variables you provide.