> 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/blameless.md).

# Blameless

## About the integration

Blameless is an SRE software platform that helps organizations and engineers streamline their reliability efforts.

## Setting up the integration

To add the Sleuth Blameless integration:

* Click **Integrations** in the sidebar.
* Click the *Incidents* tab, then **add** in the *Blameless* card.
* Enter a fully qualified URL to your Blameless instance
* Enter your OAuth Client ID and Client secret (in order to obtain those please reach out to your Customer Success Manager (CSM) \[[1](https://docs.blameless.com/api/authentication/#prerequisites)])
* Press **Save**.

## Configuring the integration

* Click **Add incident source** and select a Sleuth project that will track Blameless incidents. All projects within your organization will be displayed in the dropdown.

![](/files/Xjajmq5USjxJJsJjM54F)

* Configure impact source by selecting desired Blameless incident type and/or severity threshold to track with Sleuth.\
  Incidents with matching or lower severities will be considered a failure in Sleuth.
* Under advanced settings, you can control the historic data population. If checked Sleuth will populate all incidents that happened in the last 30 days and recalculate the project's Failure Rate and MTTR metrics.

{% hint style="info" %}
Integrations are made at the Sleuth organization level and are available for all projects within that organization. Individual settings for integration are made at the project level.
{% endhint %}

* That's it! Sleuth will now start tracking incidents declared in Blameless.


---

# 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://help.sleuth.io/sleuth-dora/integrations-1/impact-sources/incident-tracker-integrations/blameless.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.