Sentry
Create a Sentry Internal Integration pointed at your Sazabi intake URL to stream Sentry issue, comment, and alert events into Sazabi.
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 — the token stays in your browser only long enough to create the integration in Sentry.
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 for that setup. If you prefer the Sentry SDK path (errors, structured logs, envelope telemetry), see Sentry SDK page.
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
Create the Internal Integration
In Sentry, go to Settings > Developer Settings > Custom Integrations (open direct link) 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.
Set the webhook URL
Paste your Sazabi intake URL (shown above) into the Internal Integration's Webhook URL field.
Save the integration.
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 (installed and authenticated — see CLI reference).
Registering the source mints the same intake URL the dashboard shows above (the public key is embedded in its hostname):
sazabi log-sources create sentry_platform --mode connectionlessThe 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 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.