# Sentry

## About the integration <img src="/files/-M8J3wcbQjTrR2AhSkWE" alt="" data-size="line">

Sentry is an error monitoring service that helps DevOps teams discover, triage, and prioritize their errors in real-time. Before you start, you should already have a Sentry account and your environment setup and running. If not, head over to [Sentry](https://sentry.io/signup/) to get things started. Once you're done, return to Sleuth so you can complete setup of the integration.

## Setting up the integration

To add the Sleuth Sentry integration:

* Click **Integrations** in the sidebar.
* Click the *Error Trackers* tab, then **enable** in the Sentry card.
* Enter the Sentry Auth Token, then press **Save**.

{% hint style="info" %}
The Sentry Auth Token can be found in Sentry, under **Settings > Account Details > API > Auth Token**, as shown below.
{% endhint %}

![Sentry Auth Token in the Sentry dashboard.](/files/-M8J9DL4BS6iBe1SuKui)

![Sentry auth token entry field in Sleuth](/files/-M8J9L2Eydgn-O04XMdB)

* Once the Sentry integration is successful, you will see **Sentry enabled** displayed in the integration card.

## Configuring the integration

* Click \*\*Add impact \*\*to select the Sleuth project that will be processing your application errors. All projects within the organization will be displayed in the dropdown.

{% hint style="warning" %}
Sleuth will not auto-populate the **Environment** field dropdown due to the way the Sentry API handles environment data. Check your Sentry project first before populating this field. Environments are created when a deployed application monitored by Sentry sends environment data (e.g., in Javascript, the application could send`environment: 'staging'`) back to Sentry by tagging issues via your SDK.\
\
For more information,[ read more](https://docs.sentry.io/enriching-error-data/environments/?platform=browser#how-to-send-environment-data) about how Sentry receives environment data.
{% endhint %}

![Impact entry dialog for Sentry](/files/-M8JGHeXlwESgmyG22b7)

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

* The Sentry logo in the Change Source card turns to green when the integration is successful.

That's it! Sleuth will now start verifying your deploys health by tracking the error counts from Sentry. Head over to the Dashboard to start seeing your data in action in the project and deploy health graphs.

## Removing the integration

#### To dissolve the **Sentry** integration for the organization:

1. Click on **Integrations** in the left sidebar, then on **Error Trackers**.
2. In the Sentry integration card, click **disable**. The message **Sentry disabled** is displayed in the Sentry integration card once the integration is dissolved.

The Sentry integration is disconnected and no longer available to any projects within that organization. Any project-level modifications you made to the Sentry integration will be lost.


---

# Agent Instructions: 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/errors/sentry.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.