Ask A BotAlert Routing With Integrations
By customizing alert rules and integrating the tools you already use, you can receive alerts when, where (and if) you want them, without disruption. Alert notifications can be routed to Slack, multiple supported integrations, and custom integrations through webhooks. When creating alert rules, you can use these integrations to configure who to notify and how.
Sentry’s integrations provide you with the option to route your alerts through commonly-used applications like Slack, Discord, PagerDuty, and Microsoft Teams. You can find these integrations in Settings > Integrations and install them for your entire organization.
A Sentry organization owner, manager, or admin can install and configure the Slack integration in their Sentry account. Once the integration is configured, the following action will be available in issue alert rules: Send a notification to the \{workspace\} Slack workspace to \{channel\} and show tags \{tags\} in notification. In metric alerts, your Slack teams will be available in one of the action dropdown lists.
This alert action allows you to route alert notifications to selected channels (using the # prefix), or to a specific user in a direct message (using the @ prefix) in your Slack workspaces.
Then, once you receive a Slack notification, you can use the "Resolve", "Archive", or "Assign" buttons to update the issue in sentry.io directly from Slack.
A Sentry organization owner, manager, or admin can install and configure the Discord integration in their Sentry account. Once the integration is configured, the Send a notification to the \{server\} Discord server with ID: \{channel-id\} and show tags \{tags\} in notification action will become available in issue alert rules. To be notified about metric alerts via Discord, look for and add your Discord teams in the action dropdown lists.
This alert action will allow you to route alert notifications to selected channels in your Discord server.
You'll be able to "Resolve", "Archive", or "Assign" Sentry issues directly from your Discord notifications.
A Sentry organization owner, manager, or admin can install and configure the PagerDuty integration in their Sentry account. Once the integration is configured, the following action will be available in issue alert rules: Send a notification to PagerDuty account \{account\} and service \{service\}. In metric alerts, your PagerDuty accounts will be available in one of the action dropdown lists.
A Sentry organization owner, manager, or admin can install and configure the Microsoft Teams in their Sentry account. Once the integration is configured, the following action will be available in issue alert rules: Send a notification to \{team\} Team to \{channel(s)\}. In metric alerts, your Microsoft teams will be made available in one of the action dropdown lists.
If you would like to route alert notifications to other solutions that Sentry doesn't have an out-of-the-box integration with, you can use our integration platform. The integration platform provides a way for external services to interact with the Sentry SaaS service using the REST API and webhooks.
Sending alerts to webhooks can also be helpful if you want to do things like aggregate alerts from your different monitoring systems or write custom rules to route alerts more intelligently.
When you create a new integration and enable the "Alert Rule Action" option on it, your integration will show up as a service when you select the Send a notification via an integration action during issue alert rule creation. In metric alerts, your integrations are available in one of the action dropdown lists.
The gif below shows how to set up an integration that can receive Sentry alerts.
Legacy integrations (also known as plugins) are extensions of Sentry packaged as Python libraries and configured at the project level. To send an alert to a legacy integration, select the Send a notification via an integration or Send a notification to all legacy integrations action in an issue alert. You cannot route metric alerts to legacy integrations.
Our documentation is open source and available on GitHub. Your contributions are welcome, whether fixing a typo (drat!) or suggesting an update ("yeah, this would be better").