> ## Documentation Index
> Fetch the complete documentation index at: https://docs.sazabi.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Sentry

> Connect your Sentry organization so Sazabi can create an Internal Integration that streams issue, comment, and alert events in real time.

[All Sentry integration capabilities](https://docs.sazabi.com/catalogs/integrations/sentry)

## About

Connecting your Sentry organization creates a Sentry **Internal Integration** that streams issue and comment webhooks to Sazabi in real time. You can also add the integration as a notification destination on Issue Alert and Metric Alert rules to forward alert events. It sends events about Sentry issues (such as created, resolved, or commented on), not each error occurrence. For individual errors and stack traces, use the [Sentry SDK](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/sentry-sdk.md) setup.

> [!NOTE]
>
> Which Sentry setup do you need? For each error and exception, with stack traces and structured logs, use the [Sentry SDK](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/sentry-sdk.md) setup. You can keep sending to Sentry at the same time. With Python, sending to both copies only error events to Sazabi. For Sentry issue status changes, comments, and alert-rule events, use the Sentry integration on this page or [set it up yourself](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/sentry.md). The integration does not send every error occurrence. You can set up both.

Sentry also has a **Send to an endpoint** path where you create the Internal Integration yourself in the Sentry dashboard. See [Sentry endpoint page](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/sentry.md) for that setup.

> [!WARNING]
>
> Creating a Sentry Internal Integration requires the **`org:write`** scope, which Sentry grants only to organization **Owners** and **Managers**. Admin, Member, and Billing roles do not have this scope.

## Prerequisites

* An Owner or Manager role in your Sentry organization.
* A Sentry **User Auth Token** (not an Organization Auth Token) with these scopes:
  * **Organization: Read & Write** (`org:write`) — lets Sazabi create the Internal Integration on your behalf
  * **Project: Read** (`project:read`)
  * **Issue & Event: Read** (`event:read`)

The `org:write` scope only lets Sazabi create the Internal Integration; the integration itself receives only read-level webhook events.

## Set up in the dashboard

**Step 1**

### Create a Sentry User Auth Token

Go to [Sentry auth token settings](https://sentry.io/settings/account/api/auth-tokens/new-token/) and create a **User Auth Token** (not an Organization Auth Token). Grant it the three scopes: `org:write`, `project:read`, and `event:read`.

Before saving, confirm the Permissions Preview at the bottom of the Sentry form shows `event:read, org:write, project:read`.

**Step 2**

### Connect in Sazabi

Go to [**Settings > Log streams**](https://app.sazabi.com/settings/log-source-providers), click **Add source**, and select **Sentry**. Enter:

* **Sentry auth token** — the User Auth Token you created above
* **Sentry organization slug** — the slug from your Sentry URL: `sentry.io/organizations/<slug>/`

Click **Connect**. Sazabi validates the token and creates the Internal Integration in your Sentry organization.

**Step 3**

### Enable alert forwarding (optional)

Issue and comment webhooks stream automatically once the integration is created. To also forward alert events (`event_alert` / `metric_alert`):

1. In Sentry, open any Issue Alert or Metric Alert rule you want to forward.
2. Add the Sazabi integration as a notification destination on that rule.

Alert delivery is opt-in per rule — the integration receives alert webhooks only for rules where you add it.

## Set up with the CLI

You can also connect the Sentry log source with the [Sazabi CLI](https://docs.sazabi.com/reference/cli.md) (installed and authenticated — see [CLI reference](https://docs.sazabi.com/reference/cli/log-sources.md)).

Create a native connection by passing your User Auth Token and Sentry organization slug as metadata:

```bash theme={"system"}
sazabi log-sources create sentry_platform --mode native \
  --metadata '{"sentryAuthToken":"'"$SENTRY_AUTH_TOKEN"'","organizationSlug":"<your org slug>"}'
```

Use a **User Auth Token** with the same scopes as the dashboard flow (`org:write`, `project:read`, `event:read`). Sazabi validates it against the Sentry API for that organization and creates the log source. Then run `sazabi log-sources list` to confirm the source and its streams.

## Verify

Trigger a Sentry event — comment on an issue, change an issue's status, or create a fresh issue by throwing an exception in an instrumented project.

Open the [Intake page](https://docs.sazabi.com/guides/instrument/intake.md) in the Sazabi dashboard and confirm that records attributed to the **Sentry Platform** source appear. Events typically arrive within one to two minutes of Sentry delivering the webhook.

## Troubleshooting

**"Forbidden" (403) when connecting** — You do not have the Owner or Manager role in the Sentry organization. Ask an Owner or Manager to connect the integration, or follow the [send-to-an-endpoint path](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/sentry.md) where the `org:write` scope stays in Sentry and is never shared with Sazabi.

**Token validation fails** — Confirm the token is a **User Auth Token** (not an Organization Auth Token), and that it has all three required scopes. Organization Auth Tokens require different management and scopes.

**Alert events not arriving** — Alert forwarding is opt-in per rule. Open each Issue Alert or Metric Alert rule in Sentry and add the Sazabi integration as a notification destination.

**Issue events stop arriving** — The Internal Integration may have been deleted in Sentry, or the auth token may have been revoked. Reconnect from [**Settings > Log streams**](https://app.sazabi.com/settings/log-source-providers) in Sazabi to reprovision the integration.

## Further reading

> [card] [Intake](https://docs.sazabi.com/guides/instrument/intake.md)
>
> See per-source ingestion volume and health in the Intake page.

> [card] [Sentry (send to an endpoint)](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/sentry.md)
>
> Create the Sentry Internal Integration yourself and point it at Sazabi.

> [card] [Log sources](https://docs.sazabi.com/catalogs/log-sources.md)
>
> Browse the full log source catalog.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.