> For the complete documentation index, see [llms.txt](https://support.incidentlake.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.incidentlake.com/everyday-tools/analytics.md).

# Incident Analytics

Read incident volume, response times, and recurring patterns.

**Incident Analytics** is for looking across many incidents — not for running a single response. Open it from the sidebar.

## Choose a period

Use a quick range (day, week, month, quarter, year) or set a custom start and end, then apply. Comparisons to the prior period use the same length of time immediately before your selection.

## What the dashboard shows

You can turn sections on or off with **Manage Widgets**. Common sections include:

* **Total incidents** and a breakdown by status and severity
* **Average and median time** to temporary and permanent response
* Incidents over time
* Workload by assignee
* Which configuration items appear most often
* Frequency by tag
* **Recurring patterns** — groups of incidents that look similar, so you can see problems that keep coming back
* Postmortem health — how often reports are finished after the incident closes

Cancelled and merged incidents are not counted in these totals.

{% hint style="info" %}
If a chart is empty, check the time range and whether those incidents have response times filled in. Analytics can only measure stages that were recorded.
{% endhint %}

## Use it in a review

A weekly operations review usually looks at:

1. Volume and status (are we accumulating stalled work?)
2. Time to temporary and permanent response
3. The longest cases in the period
4. Recurring patterns and the tags that dominate the period

From any incident name on the dashboard you can jump back to the incident page.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://support.incidentlake.com/everyday-tools/analytics.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.