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

> Create a Sentry Internal Integration pointed at your Sazabi intake URL to stream Sentry issue, comment, and alert events into Sazabi.

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

## About

Stream Sentry issue, comment, and alert events into Sazabi by creating a Sentry Internal Integration yourself and pointing its webhook URL at a Sazabi endpoint. Sazabi never receives a Sentry auth token on this path. This integration 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 [connect your account](https://docs.sazabi.com/catalogs/log-sources/connect-your-account/sentry.md) to have Sazabi create it for you. The integration does not send every error occurrence. You can set up both.

Sentry also has a **Connect your account** path where Sazabi provisions the Internal Integration for you using a Sentry auth token you supply. See [Sentry account connection page](https://docs.sazabi.com/catalogs/log-sources/connect-your-account/sentry.md) for that setup. If you prefer the Sentry SDK path (errors, structured logs, envelope telemetry), see [Sentry SDK page](https://docs.sazabi.com/catalogs/log-sources/send-to-an-endpoint/sentry-sdk.md).

> [!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 cannot create Internal Integrations (Sentry returns 403). On this path, the scope never leaves Sentry — you give Sazabi no auth token.

## Prerequisites

* **Owner or Manager** role in your Sentry organization.
* Your Sazabi intake URL (shown above).

## Set up in the dashboard

**Step 1**

### Create the Internal Integration

In Sentry, go to **Settings > Developer Settings > Custom Integrations** ([open direct link](https://sentry.io/settings/developer-settings/)) and choose **New Internal Integration**.

Under **Webhooks**, enable webhooks and subscribe to the **Issue** and **Comment** resources.

To route alerts as well, enable **Alert Rule Action** so the integration can be added as a notification destination on Issue Alert and Metric Alert rules. Alert delivery is opt-in — you must add the integration to each alert rule separately.

**Step 2**

### Set the webhook URL

Paste your Sazabi intake URL (shown above) into the Internal Integration's **Webhook URL** field.

Save the integration.

**Step 3**

### Verify delivery

Trigger an event — comment on an issue, change an issue's status, or create a fresh issue by throwing an exception in an instrumented project. `issue` and `comment` webhooks arrive within a few minutes.

To stream `event_alert` or `metric_alert` webhooks, edit each Issue Alert or Metric Alert rule in Sentry and add this integration as a notification destination.

## Set up with the CLI

You can also register 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)).

Registering the source mints the same intake URL the dashboard shows above (the public key is embedded in its hostname):

```bash theme={"system"}
sazabi log-sources create sentry_platform --mode manual
```

The command prints the intake URL for the new source — copy the whole URL and point your sender at it using the configuration shown above. Run `sazabi log-sources get <log-source-id>` at any time to reprint the endpoint, or `sazabi log-sources list` to see every log source in the project.

## Verify

Comment on a Sentry issue or change its status. Open the [Intake page](https://docs.sazabi.com/guides/instrument/intake.md) in the Sazabi dashboard and confirm events from the **Sentry** source appear. Events typically arrive within a few minutes of the action in Sentry.

## Troubleshooting

**"You don't have the required permissions"** — Creating an Internal Integration requires the `org:write` scope. Confirm you are an Owner or Manager in the Sentry organization, not an Admin, Member, or Billing role.

**Issue events appear but no alert events** — Alert delivery is opt-in. Edit each Issue Alert or Metric Alert rule in Sentry and add the Internal Integration as a notification destination to receive `event_alert` and `metric_alert` webhooks.

**No events appear after creating the integration** — Verify the webhook URL saved in the Sentry Internal Integration matches your Sazabi intake URL exactly. Check Sentry's webhook delivery log for the integration to see failed POST attempts.

## Further reading

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

> [card] [Connect your Sentry account](https://docs.sazabi.com/catalogs/log-sources/connect-your-account/sentry.md)
>
> Let Sazabi provision the Sentry Internal Integration automatically.

> [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.