> For the complete documentation index, see [llms.txt](https://notara.gitbook.io/notara-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://notara.gitbook.io/notara-docs/connectors/sentry.md).

# Sentry

The Sentry connector gives the agent access to your error monitoring data — listing issues, reading stack traces, and pulling recent event occurrences from any project.

## What It Enables

| Tool               | Capability | Description                                                     |
| ------------------ | ---------- | --------------------------------------------------------------- |
| `list_projects`    | `read`     | List all Sentry projects the token can access                   |
| `list_issues`      | `read`     | Search issues in a project by status, query, or keyword         |
| `get_issue`        | `read`     | Get full issue detail including the latest stack trace and tags |
| `get_issue_events` | `read`     | Get recent event occurrences for an issue                       |

## Setup

**Required:** Sentry Auth Token with `project:read` and `event:read` scopes.

**Where to find it:** In Sentry, go to **Settings → Account → API → Auth Tokens** and create a new token. Select at minimum `project:read` and `event:read`.

1. In the Notara dashboard, go to **Tools**.
2. Click the **Sentry** tile.
3. Go to [sentry.io → Settings → Auth Tokens](https://sentry.io/settings/account/api/auth-tokens/) and create a token.
4. Paste it into the credential field and click **Verify & Save**.

Your auth token is encrypted at rest with AES-256-GCM.

## Example Prompts

> "What are the top unresolved errors in the API project this week?"

> "Show me the stack trace for Sentry issue 12345."

> "Have there been any new TypeError issues in the frontend project since Monday?"


---

# 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://notara.gitbook.io/notara-docs/connectors/sentry.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.