> For the complete documentation index, see [llms.txt](https://docs.telm.ai/telmai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.telm.ai/telmai/monitoring-data/incident-portal.md).

# Incidents

Triage incidents across all your assets — what happened, how far it reaches, and what to do next.

The **Incidents** page lists the incidents raised by your monitors across all assets. Open it from **Incidents** in the side menu; the number next to it is the count of open incidents.

<figure><img src="https://604868671-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkO3-a8YVu1iq1jP__S%2Fuploads%2Fgit-blob-26527550dceae3a16e8ac0ee5e890b34f7dd7072%2Fincidents-page-2026-11-04.png?alt=media" alt="The Incidents page with filters, the Open incidents and Resolution time cards, the Open incidents per day chart and the incidents table"><figcaption><p>The Incidents page.</p></figcaption></figure>

## Filters

| Filter                                      | Description                                                                                                       |
| ------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- |
| Date                                        | The period to cover: last 7, 14 or 30 days, or a custom range of up to 100 days. The default is the last 30 days. |
| Project, Connection type, Connection, Asset | Limit the page to some of your assets.                                                                            |
| Impact                                      | Show only incidents with the chosen impact.                                                                       |
| Status                                      | **Open** (the default), **Closed** or **All**.                                                                    |

To find an incident by name, use **Search monitors or assets** above the table. To see one asset's incidents, click the asset in the table, choose it in the **Asset** filter, or open the asset's **Incidents** tab. **Share** copies a link to the page with its filters and dates.

## Cards and chart

* **Open incidents** — the incidents open now, the change since the start of the period, how many closed in the period, and a bar showing the mix of impacts.
* **Resolution time** — the mean time between opening and closing an incident, shown against **Target under 1 day**. Only closed incidents are measured.
* **Open incidents by tag** — open incidents for each monitor tag. An incident can carry several tags, so the counts can add up to more than the open incidents.
* **Open incidents per day** — how many incidents were open each day, by impact. Switch between **All incidents** and **Impact set only**.

## The incidents table

| Column  | Description                                                                                                                 |
| ------- | --------------------------------------------------------------------------------------------------------------------------- |
| Monitor | The monitor that raised the incident. Click it for the incident's details.                                                  |
| Asset   | The asset. Click it to show only that asset's incidents.                                                                    |
| Impact  | The monitor's impact: **HIGH**, **MEDIUM**, **LOW** or **NOT SET**.                                                         |
| Ticket  | **Create ticket** to open a Jira issue for an open incident, or the linked issue's key. **Unlink ticket** removes the link. |
| Created | When the incident opened.                                                                                                   |
| Status  | **Open** or **Closed**.                                                                                                     |

Open incidents are listed newest first.

{% hint style="info" %}
You don't close incidents by hand. A monitor keeps one open incident per asset and adds new alerts to it; the incident closes when a later scan comes back within the expected or predicted range.
{% endhint %}

## Incident details

Click an incident to open its details.

<figure><img src="https://604868671-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MkO3-a8YVu1iq1jP__S%2Fuploads%2Fgit-blob-ced5242478ba579f7faafa957793aed93bc396ce%2Fincident-drawer-2026-11-04.png?alt=media" alt="The incident details panel with Summary, AI root cause, Blast radius, Metadata and Status history" width="640"><figcaption><p>Incident details.</p></figcaption></figure>

* **Summary** — what was found in plain words, for example *Pass rate of valid\_dates was 0%, outside the expected 55% to 56%*, with how long the incident has been open and when it was last seen. Monitors with fixed thresholds compare against an *expected* range; monitors with ML thresholds compare against a *predicted* range. For row checks, **See failed rows** opens the failing rows in [Reports > Row checks](/telmai/monitoring-data/reports.md#row-check-details).
* **AI root cause** — click **Investigate with AI** to have the AI agent explain what most likely caused the incident and suggest a next step, such as creating a Jira ticket, adjusting the monitor, or treating it as an expected change. **Continue in chat** opens the Ask AI panel with the incident attached. See [Ask AI](/telmai/ask-ai.md). Shown when AI is turned on for your tenant.
* **Blast radius** — how many downstream assets read from this asset, from its lineage. **View lineage** opens the asset's lineage.
* **Catalog** — the asset's catalog details, such as its steward, sensitive data and downstream tables, when a catalog is connected.
* **Metadata** — the asset, project, impact, monitor, description and tags. **Create ticket** opens a Jira issue for an open incident; once linked, the issue's key is shown here, and **Unlink ticket** removes the link.
* **Status history** — each scan that updated the incident, newest first and in local time, back to **FIRST SEEN**. Click an entry to see that scan's alerts.
* **Data observations** — a chart of the monitor's metric over recent scans, with the expected or predicted range and this incident marked. For a scan failure, this section is **Error details**.

Use **Share** to copy a link to the incident. **Ask AI** in the page header opens the Ask AI panel with the open incident attached.

## Create a Jira issue

Click **Create ticket** in the incident's row or in its **Metadata**. In the **Create Jira issue** dialog:

1. Under **Where it goes**, pick a **Template (optional)** if you use one, then the **Jira project** and **Issue type**.
2. Under **What it says**, fill in the **Summary** and **Description**.
3. Click **Create ticket**.

Needs the [Jira integration](/telmai/integrations/jira-integration.md). Monitors can also create issues automatically; see [Creating a Monitor](/telmai/monitoring-data/monitors-management/creating-a-monitor.md#step-3-create-a-ticket).

## Related

* [Alerts](/telmai/monitoring-data/data-trends-and-alerts.md)
* [Home](/telmai/readme/home.md)
* [Creating a Monitor](/telmai/monitoring-data/monitors-management/creating-a-monitor.md)
