Alerts

Each time you create a new project, Sentry creates a default alert rule. Alerts are generated based upon a project’s alert rules. By default, all project members receive alert notifications via email, and all integrations specified in actions receive alert notifications.

Alerts can also be configured per-project and are based on the rules defined for that project. To modify the rules visit your Project Settings > Alerts > Rules > “New Alert Rules” or “Edit Rule”. In Rules, you’ll see a list of all active rules and can add alert rules or modify existing rules.

You can also configure various personal notifications from your personal notifications settings and any specific project’s settings in the project alerts page.

Conditions

Rules provide several conditions that you’re able to configure. These are relatively self-explanatory and range from simple state changes to more complex filters on attributes. Every time an event is received, Sentry evaluates the alert conditions.

For example, you can send a notification every single time an error happens, and the affected user’s email address ends with @sentry.io.

Dropdown of alert conditions.

List of Conditions

  • An event is seen
  • An issue is first seen
  • An issue changes state from resolved to unresolved
  • An issue changes state from ignored to unresolved
  • An event’s tags match {key} {match} {value}
    • key: any tag
    • match: equals, does not equal, starts with, ends with, contains, does not contain, is set, or is not set
    • value: any key’s value
  • An issue is seen more than {value} times in {interval}
    • value: a positive integer
    • interval: one minute, one hour, one day, one week, or 30 days
  • An issue is seen by more than {value} users in {interval}
    • value: a positive integer
    • interval: one minute, one hour, one day, one week, or 30 days
  • An event’s {attribute} value {match} {value}
    • attribute: message, platform, environment, type, exception.type, exception.value, user.id, user.email, user.username, user.ip_address, http.method, http.url, stacktrace.code, stacktrace.module, or stacktrace.filename
    • match: equals, does not equal, starts with, ends with, contains, does not contain, is set, or is not set
    • value: any attribute’s value
  • An event’s level is {match} {level}
    • match: equal to, less than or equal to, greater than or equal to
    • level: fatal, error, warning, info, debug, or sample

Actions

Actions are located in Project Settings > Alerts > Rules > “New Alert Rules” or “Edit Rule”.

Buttons to create a New Alert Rule or to Edit an existing rule.

Action Types

Currently, there are three types of actions you can take:

  • Send a notification (for all legacy integrations)
    • Per-Project Integrations are considered to be legacy integrations
  • Send a notification via {service}
    • service is one of mail and any configured per-project integration
  • Send a notification to the {workspace} Slack workspace to {channel} and show tags {tags} in notification
    • this relates to the global Slack integration, not the per-project legacy integration

Dropdown of notification actions.

Frequency

  • Perform these actions at most once every {interval} for an issue
    • interval: 5 minutes, 10 minutes, 30 minutes, 60 minutes, 3 hours, 12 hours, 24 hours, one week, or 30 days
    • Frequency configuration can get complicated. For example, if an issue changes state from resolved to unresolved, and then this issue is resolved, unresolved, and resolved again within 5 minutes, but your frequency threshold is 30 minutes, you’ll only get one notification

Dropdown of minute and hour options for frequency of notifications.

Environment

  • All Environments
  • any one of your defined (and not hidden) environments

Dropdown of environments. Currently, only All Environments is an option.

Digests

Sentry will automatically digest alerts sent by some services to avoid flooding your inbox with individual issue notifications. To control how frequently notifications are delivered, use the sliders.

Sliding time scale for intervals of notifications.

Notification Management

You can also configure various personal notifications from your personal notifications settings and any specific project’s settings in the project alerts page.

Default Project Alerts

If you have set any specific project alert to default, that means you’ve configured the notification to the Default Project Alert, which is a switch you can toggle on or off. This toggle switch controls all project alerts set to default.

You can find the Default Project Alerts switch in User Settings > Account > Notifications > Fine tune alerts by project.

Toggle for turning defaul project alerts on and off.

Per-Project Alerts

Your per-project alerts have the fine-tuning options of Default, On, or Off.

Dropdown for per-project alerts. Options include default, on, or off.

Issue Owners

The Issue Owners page is located in Project Settings > Issue Owners.

If an issue owner is specified, the email notification will go to the issue owner. If no issue owner is specified, all project members are notified.

Toggles for turning issue owner notifications on and off.

For more details, see full documentation on Issue Owners.

FAQs

  • Can I copy an alert rule to another project?
    • Unfortunately, this is not an option.
  • Can I set different default alert rules?
    • Unfortunately, this is not an option.
  • Are there issue-level filters?
    • No, all filters are event-based. For example, there aren’t configurations for alerting only if an issue is X days old, or assigned to Y, or alerted-on-before, etc.
  • What is the difference between Delete, Delete & Discard, and Ignore?
    • Delete - when you delete an issue with notifications, notifications will continue if the issue is triggered again
    • Delete & Discard - when you delete and discard, all notifications will stop
    • Ignore - while an issue is ignored, all notifications will stop. If it becomes unignored, notifications will continue. For example, if you have chosen “ignore for 30 minutes,” you won’t be notified for 30 minutes. Keep in mind; an ignored issue will still count towards your quota.