The Sentry Workflow — Alert
Sentry automatically sets up a default alert rule that notifies you any time an error is first encountered. The first time a new issue is generated by an error, we’ll notify you of it via whatever services you have connected to Sentry.
The default alert is great, sure, but you can also customize alerts according to your organization’s specific workflow, stack, communication style, and objectives. Actually, organizations that configure at least one alert rule are four times more likely to successfully triage that issue and 13 times more likely to resolve an issue.
By tailoring alert rules and integrating into the tools you already use, you can receive alerts when (and if) you want them, without disruption.
Alerts are configured per project and are based on the rules defined for that project. To modify the rules visit your Project Settings > Alerts > Rules tab. On this page, you’ll see a list of all active rules, including conditions and actions, which you can modify.
Rules provide several configurable conditions. These are fairly self-explanatory and range from simple state changes to more complex filters on attributes.
Once you configure custom tags, you can also customize alerts to receive a notification every time an important customer runs into an issue.
Or every time those customers experience an issue specifically on your checkout page.
You can also get notifications any time your website sees a spike of errors within a certain duration.
Additional conditions exist for things like issue state changes and event attributes, which allow you to mark issues as ‘resolved,’ ‘unresolved,’ or ‘ignored’ to keep you organized.
If you do decide to take action on addressing a certain issue, you can send notifications to three types of places:
While you’re at it, keep yourself organized by integrating with Slack to receive error alerts directly in your team’s Slack channel.
Or get paged in real-time with our PagerDuty integration.
Contextual alerts can lead to increased accountability for the customer’s experience. Visibility into previously hidden issues means a more timely remediation process in your existing workflow and a much higher signal-to-noise ratio (plus happier developers).