---
title: "Creating an Alert"
description: "Learn about every option available when you create an Alert, including sources, environments, triggers, filters, actions, and throttling."
url: https://docs.sentry.io/product/monitors-and-alerts/alerts/create-alerts/
---

# Creating an Alert | Sentry Docs

Alerts let you configure how you want to learn about issue activity like creation, resolution, or when Seer completes tasks. This page walks through each step of the **New Alert** form and the options available in each one.

To get started, go to **Monitors > [Alerts](https://sentry.io/monitors/alerts)** and click **Create Alert**.

## [Permissions](https://docs.sentry.io/product/monitors-and-alerts/alerts/create-alerts.md#permissions)

Alerts are an organization-level feature. Owners, Managers, Admins (and Team Admins) can always create and edit Alerts. By default, Members and Team Contributors can too, under **Let Members Create and Edit Monitors and Alerts**, which is enabled in your [organization settings](https://sentry.io/settings/organization/). Learn more about [roles and permissions](https://docs.sentry.io/organization/membership.md).

Alerts scoped to all projects can only be managed by Owners and Managers.

## [Step 1: Select a Source](https://docs.sentry.io/product/monitors-and-alerts/alerts/create-alerts.md#step-1-select-a-source)

The **Source** determines where issues that can trigger an Alert come from:

* **Alert on all issues in selected projects**: Pick one or more projects. The Alert evaluates every issue in those projects, no matter which Monitor created it.
* **Alert on specific monitors**: Connect individual [Monitors](https://docs.sentry.io/product/monitors-and-alerts/monitors.md) so the Alert only evaluates issues those Monitors create. Click **Connect Monitors** to search all Monitors, filter by project, and select the ones you want. Use **Edit Monitors** to change your selection later, or **Create New Monitor** to set up a new one.
* **Alert on all issues in all projects**: The Alert evaluates every issue in the organization, including issues from projects created after you save the Alert. This is the best choice for teams with simple alerting needs like feed channels in Slack or high level monitoring of newly detected issues.

Want coverage for an entire single service? Alert on a project. Want to Alert on a particular set of Monitors such as a single cron job or set of uptime checks? Select a subset of monitors. Want an Alert to apply organization-wide? Select all projects.

## [Step 2: Filter Issues by Environment](https://docs.sentry.io/product/monitors-and-alerts/alerts/create-alerts.md#step-2-filter-issues-by-environment)

Select the [environment](https://docs.sentry.io/platform-redirect.md?next=%2Fconfiguration%2Fenvironments%2F) the Alert evaluates. This filters on the `environment` tag in your events, so you can send production alerts somewhere different from staging or QA alerts.

The dropdown defaults to All Environments. You can select a specific environment from the list of environment tags across your projects. It's also possible to filter environment tag values in the IF section of the Alert Builder. Consider this option for complex routing configurations.

## [Step 3: Build the Alert](https://docs.sentry.io/product/monitors-and-alerts/alerts/create-alerts.md#step-3-build-the-alert)

The **Alert Builder** has three sections: **When** (triggers), **If** (filters), and **Then** (actions).

For example: **When** *an issue is escalated*, **If** *issue category is outage*, **Then** *send a message to the team-platform slack channel*

### [When: Triggers](https://docs.sentry.io/product/monitors-and-alerts/alerts/create-alerts.md#when-triggers)

Triggers are the issue events that start an Alert evaluation. Triggers use `ANY` logic — the Alert evaluates as soon as one of the events happens — and each trigger can only be added once.

| Trigger                                            | Runs when                                                                                                                                                                                           |
| -------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **A new issue is created**                         | An issue is created.                                                                                                                                                                                |
| **An issue escalates**                             | An event on an issue caused it to move from a lower priority to a higher one, or causes it to be [flagged as escalating](https://docs.sentry.io/product/issues/states-triage/escalating-issues.md). |
| **A resolved issue regresses**                     | An resolved issue regresses when it's seen again (cannot be triggered by manually unresolving).                                                                                                     |
| **An issue is resolved**                           | An issue is marked as resolved.                                                                                                                                                                     |
| **An event is captured**                           | Any event is captured for an issue, including events on existing issues.                                                                                                                            |
| **Seer runs on an issue and reaches the stage...** | [Seer](https://docs.sentry.io/product/ai-in-sentry/seer.md) finishes one of the stages you select.                                                                                                  |

For the Seer trigger, select one or more stages: **Root cause analysis completed**, **Planning completed**, **Coding completed**, or **Pull request created**.

Learn more about issue lifecycle in [Issue States and Triage](https://docs.sentry.io/product/issues/states-triage.md) and the [Seer Autofix process](https://docs.sentry.io/product/ai-in-sentry/seer/autofix.md#how-issue-autofix-works).

### [If: Filters](https://docs.sentry.io/product/monitors-and-alerts/alerts/create-alerts.md#if-filters)

Actions only run on issues matching the filters.

An Alert can have many **If/Then** blocks. Each **If** portion of a block evaluates filters matching a qualifier of `all`, `any`, or `none` logic. For each **If** block, you can only choose one qualifier:

* **all**: every filter must match.
* **any**: at least one filter must match.
* **none**: no filter may match.

If you don't add any filters, your Alert will fire on every Issue matching just the selected qualifying trigger event(s) - created, escalated, etc.

Frequency and event attribute filters only work with the **A new issue is created** and **An event is captured** triggers. The builder marks these filters with a warning icon when they can't be used with the triggers you've selected.

#### [Filter by Issue Attributes](https://docs.sentry.io/product/monitors-and-alerts/alerts/create-alerts.md#filter-by-issue-attributes)

| Filter               | Options                                                                                                                                                    |
| -------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Issue age**        | The issue is **older than** or **newer than** a value in **minutes**, **hours**, **days**, or **weeks**.                                                   |
| **Issue assignment** | The issue is assigned to **No One**, a **Team**, or a organization **Member**.                                                                             |
| **Issue frequency**  | The issue has happened at least a set number of times.                                                                                                     |
| **Issue category**   | The issue category is **equal to** or **not equal to** one of `error`, `feedback`, `outage`, `metric`, `db_query`, `http_client`, `frontend`, or `mobile`. |
| **Issue type**       | The issue type is **equal to** or **not equal to** a specific issue type, which is even more granular than category.                                       |
| **Issue priority**   | The current [issue priority](https://docs.sentry.io/product/issues/issue-priority.md) is greater than or equal to **high**, **medium**, or **low**.        |
| **De-escalation**    | The issue priority de-escalates (ex. high -> medium, or medium -> low).                                                                                    |

#### [Filter by Frequency](https://docs.sentry.io/product/monitors-and-alerts/alerts/create-alerts.md#filter-by-frequency)

Frequency filters compare how often something happens. Each one supports two comparison modes:

* **more than...**: an absolute count in an interval — **in 5 minutes**, **in 15 minutes**, **in one hour**, **in one day**, **in one week**, or **in 30 days**.
* **relatively higher than...**: a percentage increase over a past interval — **5 minutes ago**, **15 minutes ago**, **one hour ago**, **one day ago**, **one week ago**, or **30 days ago**.

| Filter                              | Description                                                                                                                                                                                                                                                |
| ----------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Number of events**                | How many events the issue has received.                                                                                                                                                                                                                    |
| **Number of users affected**        | How many unique users the issue has affected.                                                                                                                                                                                                              |
| **Percentage of sessions affected** | Compares the issue's event count against an estimate of project [sessions](https://docs.sentry.io/product/releases/health.md#sessions) in the selected interval. Intervals are limited to **5 minutes**, **10 minutes**, **30 minutes**, and **one hour**. |

Frequency filters also accept **sub-filters**, which scope the count to a subset of events. Add one or more sub-filters in the form `[Attribute or Tag] [is / is not] [value]`. Multiple sub-filters are combined with `and`.

#### [Filter by Event Attributes](https://docs.sentry.io/product/monitors-and-alerts/alerts/create-alerts.md#filter-by-event-attributes)

| Filter              | Options                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       |
| ------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Event attribute** | The event's [attribute](https://docs.sentry.io/concepts/search/searchable-properties.md) matches a value. Attributes include `message`, `platform`, `environment`, `type`, `error.handled`, `error.unhandled`, `error.main_thread`, `exception.type`, `exception.value`, `user.id`, `user.email`, `user.username`, `user.ip_address`, `http.method`, `http.url`, `http.status_code`, `sdk.name`, `stacktrace.code`, `stacktrace.module`, `stacktrace.filename`, `stacktrace.abs_path`, `stacktrace.package`, `unreal.crash_type`, `app.in_foreground`, `os.distribution_name`, and `os.distribution_version`. |
| **Tagged event**    | The event's [tag](https://docs.sentry.io/platform-redirect.md?next=%2Fenriching-events%2Ftags%2F) matches a value.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                            |
| **Event level**     | The event's level **equals**, is **greater than or equal**, or is **less than or equal** to `fatal`, `error`, `warning`, `info`, `debug`, or `sampling`.                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
| **Latest release**  | The issue is in the latest [release](https://docs.sentry.io/product/releases.md). This filter has no additional options.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |
| **Release age**     | The **oldest** or **newest** adopted release associated with the event's issue is **older than** or **newer than** the latest adopted release in a given environment.                                                                                                                                                                                                                                                                                                                                                                                                                                         |

Event attribute and tag filters support these match types: **contains**, **equals**, **starts with**, **ends with**, **does not contain**, **does not equal**, **does not start with**, **does not end with**, **is set**, **is not set**, **is one of**, and **is not one of**.

### [Then: Actions](https://docs.sentry.io/product/monitors-and-alerts/alerts/create-alerts.md#then-actions)

Actions are what Sentry does when the triggers and filters match. Available actions depend on the [integrations](https://docs.sentry.io/integrations.md) installed in your organization.

Read more about [Notifications](https://docs.sentry.io/product/monitors-and-alerts/alerts/create-alerts.md#notifications), [Ticket Creation](https://docs.sentry.io/product/monitors-and-alerts/alerts/create-alerts.md#ticket-creation), and [Other Integrations](https://docs.sentry.io/product/monitors-and-alerts/alerts/create-alerts.md#other-integrations).

#### [Notifications](https://docs.sentry.io/product/monitors-and-alerts/alerts/create-alerts.md#notifications)

* **Notify on preferred channel**: Notify **Suggested Assignees**, a **Team**, or a **Member**, and Sentry delivers via each recipient's [notification settings](https://docs.sentry.io/product/notifications/notification-settings.md). Suggested Assignees include current assignees, issue owners from [ownership rules](https://docs.sentry.io/product/issues/ownership-rules.md), and authors of [suspect commits](https://docs.sentry.io/product/issues/suspect-commits.md). When no suggested assignee is found, choose a fallback: **Recently Active Members** (default), **All Project Members**, or **No One**.
* **[Slack](https://docs.sentry.io/integrations/notification-incidents/slack.md)**: Select the workspace and channel. You can also add a channel or user ID to avoid [rate limiting](https://docs.sentry.io/integrations/notification-incidents/slack.md#rate-limiting-error), and optionally show **tags** (for example, `environment,my_tag`) and **notes** (for example, `@jane, @on-call-team`) in the message.
* **[Discord](https://docs.sentry.io/integrations/notification-incidents/discord.md)**: Select the server and enter a channel ID or URL — a channel name won't work. You can optionally show **tags** in the message.
* **[MS Teams](https://docs.sentry.io/integrations/notification-incidents/msteams.md)**: Select the team and channel.
* **[PagerDuty](https://docs.sentry.io/integrations/notification-incidents/pagerduty.md)**: Select the service and the **severity** to send.
* **[Opsgenie](https://docs.sentry.io/integrations/notification-incidents/opsgenie.md)**: Select the team and the **priority** to send.
* **Send a notification via an integration**: Take action via a [third party integration](https://docs.sentry.io/integrations/third-party-integrations.md) that supports Alert actions or trigger a custom webhook.

#### [Ticket Creation](https://docs.sentry.io/product/monitors-and-alerts/alerts/create-alerts.md#ticket-creation)

Create a work item in an issue tracker:

* **[Jira](https://docs.sentry.io/integrations/issue-tracking/jira.md)** and **Jira Server**
* **[GitHub](https://docs.sentry.io/integrations/source-code-mgmt/github.md)** and **GitHub Enterprise**
* **[Azure DevOps](https://docs.sentry.io/integrations/source-code-mgmt/azure-devops.md)**

Each ticket creation action has its own settings panel, where you configure the fields Sentry sets on the work item it creates. The available fields come from the issue tracker, so they differ by integration.

#### [Other Integrations](https://docs.sentry.io/product/monitors-and-alerts/alerts/create-alerts.md#other-integrations)

Take action via a [third party integration](https://docs.sentry.io/integrations/third-party-integrations.md) that supports Alert actions or to legacy integrations (plugins) configured on the project.

Click **Send Test Notification** on an **If/Then** block to send a test event through that block's actions. This verifies that your integrations are wired up correctly before you save but event based triggers may behave differently.

### [Add Multiple If/Then Blocks](https://docs.sentry.io/product/monitors-and-alerts/alerts/create-alerts.md#add-multiple-ifthen-blocks)

Click **+ If/Then Block** to add another set of filters and actions to the same Alert. Every block evaluates separately against the same triggers, so you can route different event shapes to different places from a single Alert — for example, create a Jira ticket or Slack notification for every new issue, but only page on-call when the issue is high priority.

## [Step 4: Set Throttling](https://docs.sentry.io/product/monitors-and-alerts/alerts/create-alerts.md#step-4-set-throttling)

**Throttling** (previously called the action interval) controls how often the Alert can run its actions for a given issue. If events in an issue match triggers repeatedly within the throttle window, the actions won't run again until the throttle period has elapsed.

Options are **Get notified on every trigger** (the default), **5 minutes**, **10 minutes**, **30 minutes**, **60 minutes**, **3 hours**, **12 hours**, **24 hours**, **1 week**, and **30 days**.

## [Step 5: Name and Save](https://docs.sentry.io/product/monitors-and-alerts/alerts/create-alerts.md#step-5-name-and-save)

Sentry generates a name from your configuration as you build. To change it, click the name in the header at the top of the page and enter a descriptive one, such as "Frontend high priority to #frontend-oncall".

Click **Create Alert** to save. Sentry takes you to the Alert's details page, where you can review its history, edit it, or turn it off. Learn more in [Managing Alerts](https://docs.sentry.io/product/monitors-and-alerts/alerts.md#managing-alerts).

## [Troubleshooting](https://docs.sentry.io/product/monitors-and-alerts/alerts/create-alerts.md#troubleshooting)

### [An integration I expected isn't in the actions list](https://docs.sentry.io/product/monitors-and-alerts/alerts/create-alerts.md#an-integration-i-expected-isnt-in-the-actions-list)

The **Then** section only offers [integrations](https://docs.sentry.io/integrations.md) that are installed in your organization and that support Alert actions. If one is missing, check that it's installed under **Settings > Integrations**, and that the integration supports being used as an Alert action. Some integrations support issue linking but not Alert actions.

### [Sentry won't let me save a new Alert](https://docs.sentry.io/product/monitors-and-alerts/alerts/create-alerts.md#sentry-wont-let-me-save-a-new-alert)

Sentry caps how many Alerts an organization can create so that evaluation stays fast. When you exceed one, saving fails with an error naming the limit you hit. The ceilings can be raised, so [contact support](https://sentry.io/support/) if your organization needs more. Otherwise, delete or turn off Alerts you're no longer acting on, or consolidate several narrow Alerts into one Alert with broader filters and multiple **If/Then** blocks.

Alerts that count events over a time window, such as **The issue is seen more than 100 times in one hour**, get a lower per-project ceiling than other Alerts because they're more expensive to evaluate.