Sentry

Connect your Sentry organization to turn errors into issues, see how often an error happens right on the issue, get new and regressed errors in a chat channel, and resolve them in Sentry when the work is done. Open Integrations → Sentry → Configure to set it up. You need permission to manage integrations.

Connecting Sentry

There are two ways to connect:

• Connect Sentry installs the Deckbell integration in your Sentry organization (where available). Sentry sends you back to Deckbell when it's done.
• Internal integration works with sentry.io and self-hosted Sentry. In Sentry, open Settings → Developer Settings → Custom Integrations and create an internal integration with Issue & Event: Read & Write access. Copy its token and client secret into Deckbell, with your organization slug (and your Sentry address if it's self-hosted). Then copy the Webhook URL Deckbell shows into the integration, and turn on the issue webhook. For alert rules, also turn on Alert Rule Action and add the integration as an action in the alert rules you want in Deckbell.

Every webhook Sentry sends is signed, and Deckbell ignores any that aren't.

Creating issues from Sentry

• From an alert in chat: hover the alert and choose Create issue. The issue gets the error's title and details, and is linked to the Sentry issue.
• From a Sentry link: on any issue, choose Link Sentry issue or Figma design in the right sidebar and paste a Sentry issue link, its ID or its short ID (like BILLING-4F).

When an issue is linked, Deckbell links back from Sentry too: with the Deckbell integration it appears as a linked issue in Sentry; with an internal integration Deckbell adds a comment to the Sentry issue pointing to the Deckbell issue.

Sentry cards on issues

Linked Sentry issues are listed under Sentry in the issue's right sidebar, with their level, status (unresolved, resolved or ignored), number of events, affected users and when the error was last seen. They update as Sentry sends changes. Click one to open it in Sentry.

Alerts in chat

Choose a channel under Post alerts to, then pick what to post:

• New issues: the first time Sentry sees an error.
• Regressions: a resolved error comes back.
• Alert rules: issue and metric alert rules in Sentry that have the Deckbell (or your internal) integration as an action.

Each alert shows the error, where it happens, its level and how many events and users it affects, with a link to Sentry.

Resolving in Sentry

Turn on Resolve in Sentry when the issue is done, and moving a linked issue to a done column resolves its Sentry issues. If the error happens again, Sentry marks it as regressed (and posts it to your alert channel if that's on).