> For the complete documentation index, see [llms.txt](https://help.sleuth.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.sleuth.io/sleuth-dora/integrations-1/impact-sources/incident-tracker-integrations.md).

# Incident tracker integrations

**Incident trackers** are used by Sleuth to automatically track change failure and its associated MTTR when your systems are having an incident.

| Integration                                                                                                                   |
| ----------------------------------------------------------------------------------------------------------------------------- |
| [Blameless](/sleuth-dora/integrations-1/impact-sources/incident-tracker-integrations/blameless.md)                            |
| [PagerDuty](/sleuth-dora/integrations-1/impact-sources/incident-tracker-integrations/pagerduty.md)                            |
| [Datadog Monitors](/sleuth-dora/integrations-1/impact-sources/incident-tracker-integrations/datadog.md)                       |
| [Statuspage](/sleuth-dora/integrations-1/impact-sources/incident-tracker-integrations/statuspage.md)                          |
| [Opsgenie](/sleuth-dora/integrations-1/impact-sources/incident-tracker-integrations/opsgenie.md)                              |
| [Jira (Coud/Data Center)](/sleuth-dora/integrations-1/impact-sources/incident-tracker-integrations/jira-cloud-data-center.md) |
| [FireHydrant](/sleuth-dora/integrations-1/impact-sources/incident-tracker-integrations/firehydrant.md)                        |
| [Rootly](/sleuth-dora/integrations-1/impact-sources/incident-tracker-integrations/rootly.md)                                  |
| [ServiceNow](/sleuth-dora/integrations-1/impact-sources/incident-tracker-integrations/servicenow.md)                          |
| [Custom](/sleuth-dora/integrations-1/impact-sources/incident-tracker-integrations/custom.md)                                  |

### Updating incidents over time

Sleuth will pick up on changes you make to incidents after they've come into Sleuth. Each day, Sleuth will re-evaluate 30 days of incident history looking for incident deletion, the merging of 2 incidents into 1, or updates to incident metadata (start/end dates, severity, incident types, etc.) and will recalculate Failure and MTTR metrics accordingly.


---

# 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:

```
GET https://help.sleuth.io/sleuth-dora/integrations-1/impact-sources/incident-tracker-integrations.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.