> For the complete MongoDB documentation index, see www.mongodb.com/docs/llms.txt

# Configure Alert Settings

For each organization and project, you can select which conditions trigger alerts and how users are notified.

**Note:**

Free clusters and Flex clusters only trigger alerts related to the metrics supported by those clusters. For complete documentation on Free clusters and Flex clusters alert and metric limitations, see [Atlas Free Cluster Limits](https://www.mongodb.com/docs/atlas/reference/free-shared-limitations.md#std-label-atlas-free-tier), and [Atlas Flex Limitations.](https://www.mongodb.com/docs/atlas/reference/flex-limitations.md#std-label-flex-cluster-limitations)

## Required Access

To manage all organization alerts, you must have the [`Organization Owner`](https://www.mongodb.com/docs/atlas/reference/user-roles.md#mongodb-authrole-Organization-Owner) role for the organization.

The [`Organization Billing Admin`](https://www.mongodb.com/docs/atlas/reference/user-roles.md#mongodb-authrole-Organization-Billing-Admin) role grants a limited authorization to manage billing alerts.

To manage project alerts, you must have [`Project Owner`](https://www.mongodb.com/docs/atlas/reference/user-roles.md#mongodb-authrole-Project-Owner) or [`Project Alerts Manager`](https://www.mongodb.com/docs/atlas/reference/user-roles.md#mongodb-authrole-Project-Alerts-Manager) access to the project. Users with [`Organization Owner`](https://www.mongodb.com/docs/atlas/reference/user-roles.md#mongodb-authrole-Organization-Owner) access must add themselves to the project as a `Project Owner`.

## Default Alert Settings

Atlas provides the following default alerts and alert values for a new project:

- [`Cluster is missing an active mongos`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Cluster-is-missing-an-active-mongos)

- [`Connections % of configured limit is`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Connections---of-configured-limit-is), `above 80`

- [`Credit card is about to expire`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Credit-card-is-about-to-expire)

- [`Disk space % used on Data Partition is`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Disk-space---used-on-Data-Partition-is), `above 90`

  **Note:**

  This alert doesn't apply to Atlas Infinite clusters, where Atlas manages storage independently of the compute nodes. Atlas Infinite clusters use the [`Atlas Infinite: Storage Space Used % is`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Atlas-Infinite--Storage-Space-Used---is) default alert instead.

- [`Atlas Infinite: Storage Space Used % is`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Atlas-Infinite--Storage-Space-Used---is), `above 90`

  Applies to Atlas Infinite clusters only. Raised when the cluster's [logical data size](https://www.mongodb.com/docs/atlas/infinite/atlas-infinite-storage.md#std-label-atlas-logical-data-size) exceeds 90% of its [max storage limit](https://www.mongodb.com/docs/atlas/infinite/atlas-infinite-storage.md#std-label-atlas-infinite-max-storage-limit). To learn more, see [Manage Storage on an Atlas Infinite Cluster.](https://www.mongodb.com/docs/atlas/infinite/atlas-infinite-storage.md#std-label-atlas-infinite-storage)

- [`Host has index suggestions`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Host-has-index-suggestions)

- [`Query Targeting: Scanned Objects / Returned`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Query-Targeting--Scanned-Objects---Returned), `above 1000`

  **Note:**

  The default configuration sends an alert only if the ratio of documents scanned to documents returned meets or exceeds the specified threshold for at least 10 minutes.

- [`Profiler configured to capture all operations on a host, which might result in a significant performance impact.`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Profiler-configured-to-capture-all-operations-on-a-host--which-might-result-in-a-significant-performance-impact.)

- [`Replica set has no primary`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Replica-set-has-no-primary)

- [`Replication Oplog Window is`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Replication-Oplog-Window-is), `below 1 hours`

- [`System: CPU (User) % is`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-System--CPU--User----is), `above 95`

- [`Total Namespaces is`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Total-Namespaces-is), `above 10000`

- [`User joined the project`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-User-joined-the-project)

Atlas provides the following default alert for projects using [Manage Customer Keys with AWS KMS:](https://www.mongodb.com/docs/atlas/security-aws-kms.md#std-label-security-aws-kms)

- [`AWS encryption key elapsed time since last rotation is above 90 days`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-AWS-encryption-key-elapsed-time-since-last-rotation-is-above--n--days)

Atlas provides the following default alerts for projects with [External Log Sinks](https://www.mongodb.com/docs/atlas/export-logs-external-sinks.md#std-label-export-logs-external-sinks) configured:

- [`Log export has failed. Check your integration settings and credentials.`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Log-export-has-failed.-Check-your-integration-settings-and-credentials.)

- [`Log export is failing after multiple attempts. Logs are being queued and will be sent once the connection is restored.`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Log-export-is-failing-after-multiple-attempts.-Logs-are-being-queued-and-will-be-sent-once-the-connection-is-restored.)

- [`Log export replay has failed to deliver records to an external platform, even after an automatic replay attempt. These records will be permanently deleted once their retention window expires. Contact MongoDB Support to request redelivery.`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Log-export-replay-has-failed-to-deliver-records-to-an-external-platform--even-after-an-automatic-replay-attempt.-These-records-will-be-permanently-deleted-once-their-retention-window-expires.-Contact-MongoDB-Support-to-request-redelivery.)

Atlas provides the following default MongoDB Search alerts:

- [`Atlas Search: Max Number of Fields Indexed is`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Atlas-Search--Max-Number-of-Fields-Indexed-is), `above 1000`

- [`Atlas Search: Max Number of nGram Fields Indexed is`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Atlas-Search--Max-Number-of-nGram-Fields-Indexed-is), `above 100`

- [`Atlas Search: Max Number of Lucene Docs is`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Atlas-Search--Max-Number-of-Lucene-Docs-is)

- [`Insufficient disk space to support rebuilding search indexes`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Insufficient-disk-space-to-support-rebuilding-search-indexes)

- [`Atlas Search: Mongot stopped replication`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Atlas-Search--Mongot-stopped-replication)

- [`Search Process: Ran out of memory`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Search-Process--Ran-out-of-memory)

- [`Atlas Search: Mongot paused initial sync`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Atlas-Search--Mongot-paused-initial-sync)

- [`Atlas Search: Mongot is approaching replication stop threshold`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Atlas-Search--Mongot-is-approaching-replication-stop-threshold)

- [`MongoDB Search: Search Process is Overloaded`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-MongoDB-Search--Search-Process-is-Overloaded)

For a full list of MongoDB Search alerts, see [Alert Conditions for MongoDB Search.](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#std-label-alert-conditions-atlas-search)

Atlas provides the following default Atlas Stream Processing alerts:

- [`Stream Processor State is failed`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Stream-Processor-State-is-failed)

Atlas provides the following default [Intelligent Workload Management](https://www.mongodb.com/docs/atlas/intelligent-workload-management.md#std-label-intelligent-workload-management) alerts for projects that contain Dedicated clusters running MongoDB 9.0 or later:

- [`Sustained load shedding`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Sustained-load-shedding)

- [`Sustained ingress queue pressure`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Sustained-ingress-queue-pressure)

- [`Sustained execution-control queue pressure`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Sustained-execution-control-queue-pressure)

To learn more, see [Load Shedding.](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#std-label-alert-conditions-iwm)

Atlas provides default alerts for projects with clusters that experience auto-scaling events. To learn more about all auto-scaling alert events, see [Auto-scaling.](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#std-label-alert-conditions-autoscaling)

Atlas provides the following default alerts and alert values for a new project:

- [`Cluster is missing an active mongos`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Cluster-is-missing-an-active-mongos)

- [`Connections % of configured limit is`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Connections---of-configured-limit-is), `above 80`

- [`Credit card is about to expire`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Credit-card-is-about-to-expire)

- [`Disk space % used on Data Partition is`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Disk-space---used-on-Data-Partition-is), `above 90`

  **Note:**

  This alert doesn't apply to Atlas Infinite clusters, where Atlas manages storage independently of the compute nodes. Atlas Infinite clusters use the [`Atlas Infinite: Storage Space Used % is`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Atlas-Infinite--Storage-Space-Used---is) default alert instead.

- [`Atlas Infinite: Storage Space Used % is`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Atlas-Infinite--Storage-Space-Used---is), `above 90`

  Applies to Atlas Infinite clusters only. Raised when the cluster's [logical data size](https://www.mongodb.com/docs/atlas/infinite/atlas-infinite-storage.md#std-label-atlas-logical-data-size) exceeds 90% of its [max storage limit](https://www.mongodb.com/docs/atlas/infinite/atlas-infinite-storage.md#std-label-atlas-infinite-max-storage-limit). To learn more, see [Manage Storage on an Atlas Infinite Cluster.](https://www.mongodb.com/docs/atlas/infinite/atlas-infinite-storage.md#std-label-atlas-infinite-storage)

- [`Host has index suggestions`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Host-has-index-suggestions)

- [`Query Targeting: Scanned Objects / Returned`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Query-Targeting--Scanned-Objects---Returned), `above 1000`

  **Note:**

  The default configuration sends an alert only if the ratio of documents scanned to documents returned meets or exceeds the specified threshold for at least 10 minutes.

- [`Profiler configured to capture all operations on a host, which might result in a significant performance impact.`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Profiler-configured-to-capture-all-operations-on-a-host--which-might-result-in-a-significant-performance-impact.)

- [`Replica set has no primary`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Replica-set-has-no-primary)

- [`Replication Oplog Window is`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Replication-Oplog-Window-is), `below 1 hours`

- [`System: CPU (User) % is`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-System--CPU--User----is), `above 95`

- [`Total Namespaces is`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Total-Namespaces-is), `above 10000`

- [`User joined the project`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-User-joined-the-project)

Atlas provides the following default alert for projects using [Manage Customer Keys with AWS KMS:](https://www.mongodb.com/docs/atlas/security-aws-kms.md#std-label-security-aws-kms)

- [`AWS encryption key elapsed time since last rotation is above 90 days`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-AWS-encryption-key-elapsed-time-since-last-rotation-is-above--n--days)

Atlas provides the following default alerts for projects with [External Log Sinks](https://www.mongodb.com/docs/atlas/export-logs-external-sinks.md#std-label-export-logs-external-sinks) configured:

- [`Log export has failed. Check your integration settings and credentials.`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Log-export-has-failed.-Check-your-integration-settings-and-credentials.)

- [`Log export is failing after multiple attempts. Logs are being queued and will be sent once the connection is restored.`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Log-export-is-failing-after-multiple-attempts.-Logs-are-being-queued-and-will-be-sent-once-the-connection-is-restored.)

- [`Log export replay has failed to deliver records to an external platform, even after an automatic replay attempt. These records will be permanently deleted once their retention window expires. Contact MongoDB Support to request redelivery.`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Log-export-replay-has-failed-to-deliver-records-to-an-external-platform--even-after-an-automatic-replay-attempt.-These-records-will-be-permanently-deleted-once-their-retention-window-expires.-Contact-MongoDB-Support-to-request-redelivery.)

Atlas provides the following default MongoDB Search alerts:

- [`Atlas Search: Max Number of Fields Indexed is`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Atlas-Search--Max-Number-of-Fields-Indexed-is), `above 1000`

- [`Atlas Search: Max Number of nGram Fields Indexed is`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Atlas-Search--Max-Number-of-nGram-Fields-Indexed-is), `above 100`

- [`Atlas Search: Max Number of Lucene Docs is`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Atlas-Search--Max-Number-of-Lucene-Docs-is)

- [`Insufficient disk space to support rebuilding search indexes`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Insufficient-disk-space-to-support-rebuilding-search-indexes)

- [`Atlas Search: Mongot stopped replication`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Atlas-Search--Mongot-stopped-replication)

- [`Search Process: Ran out of memory`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Search-Process--Ran-out-of-memory)

- [`Atlas Search: Mongot paused initial sync`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Atlas-Search--Mongot-paused-initial-sync)

- [`Atlas Search: Mongot is approaching replication stop threshold`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Atlas-Search--Mongot-is-approaching-replication-stop-threshold)

- [`MongoDB Search: Search Process is Overloaded`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-MongoDB-Search--Search-Process-is-Overloaded)

For a full list of MongoDB Search alerts, see [Alert Conditions for MongoDB Search.](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#std-label-alert-conditions-atlas-search)

Atlas provides the following default Atlas Stream Processing alerts:

- [`Stream Processor State is failed`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Stream-Processor-State-is-failed)

Atlas provides the following default [Intelligent Workload Management](https://www.mongodb.com/docs/atlas/intelligent-workload-management.md#std-label-intelligent-workload-management) alerts for projects that contain Dedicated clusters running MongoDB 9.0 or later:

- [`Sustained load shedding`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Sustained-load-shedding)

- [`Sustained ingress queue pressure`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Sustained-ingress-queue-pressure)

- [`Sustained execution-control queue pressure`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Sustained-execution-control-queue-pressure)

To learn more, see [Load Shedding.](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#std-label-alert-conditions-iwm)

Atlas provides default alerts for projects with clusters that experience auto-scaling events. To learn more about all auto-scaling alert events, see [Auto-scaling.](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#std-label-alert-conditions-autoscaling)

Atlas provides the following default alerts for organizations that use [service accounts.](https://www.mongodb.com/docs/atlas/api/api-authentication.md#std-label-service-accounts-overview)

- [`Service Account Secrets are about to expire`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Service-Account-Secrets-are-about-to-expire)

- [`Service Account Secrets have expired`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Service-Account-Secrets-have-expired)

Atlas provides the following default alerts for organizations that use [service accounts.](https://www.mongodb.com/docs/atlas/api/api-authentication.md#std-label-service-accounts-overview)

- [`Service Account Secrets are about to expire`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Service-Account-Secrets-are-about-to-expire)

- [`Service Account Secrets have expired`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Service-Account-Secrets-have-expired)

## Notification Options

When you configure an alert, you select how notifications are sent. You can select multiple notification methods, such as email, text message, or team collaboration tools.

To use certain notification methods, you must first set up notification methods in the project's settings. If the notification method's value becomes invalid, Atlas sends an email to the project owner. The following notification methods require set up in the project's settings:

- Atlas Project

- Atlas Organization

- Atlas User

- Email

- SMS

- PagerDuty

- Datadog

- VictorOps

- Opsgenie

- Microsoft Teams

- Webhook

When you configure an alert, you select how notifications are sent. You can select multiple notification methods, such as email, text message, or team collaboration tools.

To use certain notification methods, you must first set up notification methods in the project's settings. If the notification method's value becomes invalid, Atlas sends an email to the project owner. The following notification methods require set up in the project's settings:

- Atlas Project

- Atlas Organization

- Atlas User

- Email

- SMS

- PagerDuty

- Datadog

- VictorOps

- Opsgenie

- Microsoft Teams

- Webhook

When you configure an alert, you select how notifications are sent. You can select multiple notification methods, such as email, text message, or team collaboration tools.

Atlas supports Slack as a notification method. From the organization's Settings menu, click Add to Slack in Slack Settings and log in to your preferred Slack workspace.

Atlas supports configuring all of the following notification methods during alert configuration:

- Atlas Organization

- Atlas User

- Email

- SMS

- PagerDuty

- Datadog

- VictorOps

- Opsgenie

- Microsoft Teams

When you configure an alert, you select how notifications are sent. You can select multiple notification methods, such as email, text message, or team collaboration tools.

Atlas supports Slack as a notification method. From the organization's Settings menu, click Add to Slack in Slack Settings and log in to your preferred Slack workspace.

Atlas supports configuring all of the following notification methods during alert configuration:

- Atlas Organization

- Atlas User

- Email

- SMS

- PagerDuty

- Datadog

- VictorOps

- Opsgenie

- Microsoft Teams

## Notification Credential Behavior

When Atlas sends a notification, it validates the credential by attempting to deliver the notification. If the credential is invalid or expired, the notification fails.

Atlas handles repeated notification failures as follows:

- **Immediately:** The notification fails and Atlas increments an internal failure counter.

- **After 1 hour:** Atlas sends a warning email to the project owners.

- **After 24 hours:** Atlas disables the notification method and notifies the project owners.

**Important:**

Failure handling does not escalate based on the severity of the original alert.

## Severity Levels

Every alert has a default severity level based on its event type. When you configure an alert, you can optionally select a severity level for that alert that overrides the default.

Atlas includes the following severity levels:

- Critical

- Error

- Warning

- Info

Atlas sets an alert's severity when the alert opens. If the alert configuration has a severity override, Atlas uses the override. Otherwise, Atlas uses the default severity of the alert's event type. Changing the severity override does not change the severity of alerts that are already open.

In the Atlas Administration API, the alert configuration stores the override in the `severityOverride` field, and each open alert stores the resolved value in the `severity` field. The [Return All Project Alerts](https://www.mongodb.com/docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupalerts) and [Return One Alert](https://www.mongodb.com/docs/api/doc/atlas-admin-api-v2/operation/operation-getgroupalert) endpoints return the resolved `severity`, which matches the severity that Atlas includes in webhook, PagerDuty, and Opsgenie notification payloads.

The severity levels in Atlas map to the following severity levels in our third-party notification services:

| Atlas | PagerDuty | Opsgenie | VictorOps | DataDog |
| --- | --- | --- | --- | --- |
| Critical | Critical | P1 | Critical | Error |
| Error | Error | P2 | Critical | Error |
| Warning | Warning | P4 | Warning | Warning |
| Info | Info | P5 | Info | Info |

## Configure an Alert

When you create a new alert, you can clone an existing alert. You can also update an existing alert configuration.

This section describes how to configure all types of alerts. In addition, see:

- [Configure an Auto-Scaling Alert](https://www.mongodb.com/docs/atlas/configure-alerts.md#std-label-configure-autoscaling-alert)

- [Configure a Maintenance Window Alert](https://www.mongodb.com/docs/atlas/configure-alerts.md#std-label-configure-mw-alert)

1. In Atlas, go to the Project Alerts page.

   If it's not already displayed, select the organization that contains your desired project from the  Organizations menu in the navigation bar.

   If it's not already displayed, select your desired project from the Projects menu in the navigation bar.

   In the top-right corner of the Atlas UI, click the Alerts icon.

   Click Alerts under the Project header.

   The [Project Alerts](https://cloud.mongodb.com/go?l=https%3A%2F%2Fcloud.mongodb.com%2Fv2%2F%3Cproject%3E%23%2Falerts%2FopenAlerts) page displays.

2. Choose whether to create a new alert setting, clone an existing alert setting, or update an existing alert setting.

   To create a new alert without cloning an existing setting:

   Click Add.

   Select New Alert.

   To clone an existing alert setting:

   Click the Alert Settings tab.

   Locate the alert setting you want to clone.

   Click  then Clone in that alert setting's row.

   To update an existing alert setting:

   Click the Alert Settings tab.

   Locate the alert setting you want to update.

   Click  then Edit in that alert setting's row.

3. Select the category and the condition or metric that triggers the alert.

   In the Category section, select the target component.

   In the Condition/Metric drop-down menu, select the condition. To learn more about alert conditions, see [Review Alert Conditions.](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#std-label-alert-conditions)

   (Optional) In the Severity drop-down menu, select a severity level for the alert that overrides the system default severity level.

   To learn more, see [Severity Levels.](https://www.mongodb.com/docs/atlas/configure-alerts.md#std-label-atlas-alert-severity-levels)

4. Apply the alert only to specific targets. (Optional)

   If the options in the Select Target section are available, you can optionally filter the alert to apply only to a subset of the targets.

   If you specify multiple conditions, the filter uses a logical `AND` operator, so the alert applies only to targets that match all of the specified conditions.

   The matches field can use regular expressions.

5. Select the alert recipient roles and delivery methods.

   In the Add Notification Method section:

   - Select from the list of roles.

   - (Optional) To help reduce the false positives that Atlas sends, locate the Recurrence section.

     (Optional) In the send if condition lasts at least field, specify the minutes to elapse before the condition sends the alert. The next alert check that runs after the specified time elapses sends the alert.

     (Optional) In the resend after field, specify the minutes to elapse before the condition resends the alert. The resend interval must be at least 5 minutes.

     **Note:**

     The send if condition lasts at least and resend after options are available only for [Host alerts](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#std-label-host-alerts). These options are not available for event-based alerts such as Cloud Backup alerts, Auto-scaling alerts, billing alerts, or other non-host alert types.

   In the Add Notifier drop-down menu, select from the options described in the following table.

   | Notification Option | Description |
   | --- | --- |
   | Atlas Project | Sends the alert by email or text message to users with specific roles in the Project. Atlas Project is the default alert recipient. You can configure the roles the alert is sent to and how it's delivered. You can't add a second Atlas Project as the recipient. If the [`Project Owner`](https://www.mongodb.com/docs/atlas/reference/user-roles.md#mongodb-authrole-Project-Owner) role is assigned to a human project member, Atlas delivers alerts to that member's configured email address or SMS target. If the [`Project Owner`](https://www.mongodb.com/docs/atlas/reference/user-roles.md#mongodb-authrole-Project-Owner) role is assigned programmatically, ensure you configure an explicit notification target (such as an email address, PagerDuty, Slack, or Webhook) to receive alerts. Programmatic API keys and service accounts do not receive alert notifications by default. Atlas Project is available as an option in the Add list only if it is not currently in the recipients list. Select the Project roles that should receive the alerts from the Select Role(s) check boxes or select All Roles for all users in the Project to receive the alert.; Select SMS to send these alerts to the mobile number configured for each Atlas Project user in their Account page.; Select Email to send these alerts to the email address configured for each Atlas Project user in their Account page. Email is checked by default. |
   | Atlas Organization | Sends the alert by email or text message to users with specific roles in the Organization. Select the Organization roles that should receive the alerts from the Select Role(s) check boxes or select All Roles for all users in the Organization to receive the alert.; Select SMS to send these alerts to the mobile number configured for each Atlas Organization user in Account page.; Select Email to send these alerts to the email address configured for each Atlas Organization user in Account page. Email is checked by default. |
   | Atlas User | Sends the alert by email or text message to a specified Atlas user. Select SMS to send these alerts to the mobile number configured for the Atlas user in their Account page.; Select Email to send these alerts to the email address configured for the Atlas user in their Account page. Email is checked by default. |
   | Email | Sends the alert to an email address. |
   | SMS | Sends the alert to a mobile number. Atlas removes all punctuation and letters and uses only the digits. If you are outside of the United States or Canada, include `011` and the [country code](https://countrycode.org/)  because Atlas uses the U.S.-based [Twilio](https://www.twilio.com) to send text messages. As an alternative to your non-U.S. telephone number, use a [Google Voice](https://voice.google.com) telephone number. For example, enter `01164` before the phone number to send the alert to a New Zealand mobile number. |
   | Slack | Sends the alert to a Slack channel. Enter the channel name and either an API (Application Programming Interface) token or a Bot token. To create an API (Application Programming Interface) token, see the [https://api.slack.com/web](https://api.slack.com/web) page in your Slack account. To learn more about Bot users in Slack, see [https://api.slack.com/bot-users.](https://api.slack.com/bot-users) After you create a notification that requires an API or integration key, the key appears redacted when you: View or edit the alert through the Atlas UI.; Query the alert for the notification through the Atlas Administration API. Atlas redacts all but the last four characters of the credential. The redaction formula applies to all notification types, including PagerDuty, Slack, and Datadog. The formula is stable and safe to use in automations. Any disruptive API changes would require a new API version, and previous versions should remain usable. |
   | PagerDuty | Sends the alert to a [PagerDuty](http://www.pagerduty.com/?utm_source=mongodb&utm_medium=docs&utm_campaign=partner) account. Enter only the PagerDuty service key. Define escalation rules and alert assignments directly in PagerDuty. Users can acknowledge PagerDuty alerts only from the PagerDuty dashboard. All new PagerDuty keys use their [Events API v2.](https://developer.pagerduty.com/docs/ZG9jOjExMDI5NTgw-events-api-v2-overview) If you have an Events API v1 key, you can continue to use that key with Atlas. After you create a notification that requires an API or integration key, the key appears redacted when you: View or edit the alert through the Atlas UI.; Query the alert for the notification through the Atlas Administration API. Atlas redacts all but the last four characters of the credential. The redaction formula applies to all notification types, including PagerDuty, Slack, and Datadog. The formula is stable and safe to use in automations. Any disruptive API changes would require a new API version, and previous versions should remain usable. |
   | Datadog | Sends the alert to a [Datadog](https://www.datadoghq.com/alerts/) account as a Datadog event. When the alert is first opened, Atlas sends the alert as an "error" event. Subsequent updates are sent as "info" events. When the alert is closed, Atlas sends a "success" event. Enter your DataDog API (Application Programming Interface) key under API Key and click Validate Datadog API Key.; Enter your API (Application Programming Interface) region.Atlas supports the following Datadog regions in the Atlas UI:`US1`; `US3`; `US5`; `EU1`; `AP1`Datadog uses `US1` by default.To learn more about Datadog's regions, see [Datadog Sites.](https://docs.datadoghq.com/getting_started/site/)After you create a notification that requires an API or integration key, the key appears redacted when you:View or edit the alert through the Atlas UI.; Query the alert for the notification through the Atlas Administration API.Atlas redacts all but the last four characters of the credential. The redaction formula applies to all notification types, including PagerDuty, Slack, and Datadog. The formula is stable and safe to use in automations. Any disruptive API changes would require a new API version, and previous versions should remain usable.; (Optional) To enable database metrics tracking, toggle Send Database Metrics to On.; (Optional) To enable collection latency metrics tracking, toggle Send Collection Latency Metrics to On.; (Optional) To enable query shape metrics tracking, toggle Send Query Shape Metrics to On.; Click Save. |
   | VictorOps | Sends the alert to a [VictorOps](https://victorops.com/) account. Enter the alphanumeric [API key](https://help.victorops.com/knowledge-base/rest-endpoint-integration-guide/) from VictorOps to integrate the VictorOps endpoint for alerts. Add dashes to the API key so it matches the format `xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx`. For example, `489f7he7-790b-9896-a8cf-j4757def1161`. Enter an optional [routing key](https://help.victorops.com/knowledge-base/routing-keys/) to route alerts to a specific VictorOps group. Click Post Test Alert to test the VictorOps configuration. Define escalation and routing rules directly in VictorOps. This option is available only for alerts that require acknowledgement. You can receive informational alerts from this [third-party monitoring service](https://www.mongodb.com/docs/atlas/tutorial/third-party-service-integrations.md#std-label-third-party-integrations) in Atlas. However, you must resolve these alerts within the external service. Acknowledge VictorOps alerts from the VictorOps dashboard. After you create a notification that requires an API or integration key, the key appears redacted when you: View or edit the alert through the Atlas UI.; Query the alert for the notification through the Atlas Administration API. Atlas redacts all but the last four characters of the credential. The redaction formula applies to all notification types, including PagerDuty, Slack, and Datadog. The formula is stable and safe to use in automations. Any disruptive API changes would require a new API version, and previous versions should remain usable. |
   | Opsgenie | Sends the alert to an [Opsgenie](https://www.opsgenie.com/) account. Enter only the Opsgenie API (Application Programming Interface) key. Define escalation rules and alert assignments directly in Opsgenie. This option is available only for alerts that require acknowledgement. You can receive informational alerts from this [third-party monitoring service](https://www.mongodb.com/docs/atlas/tutorial/third-party-service-integrations.md#std-label-third-party-integrations) in Atlas. However, you must resolve these alerts within the external service. Acknowledge Opsgenie alerts from the Opsgenie dashboard. After you create a notification that requires an API or integration key, the key appears redacted when you: View or edit the alert through the Atlas UI.; Query the alert for the notification through the Atlas Administration API. Atlas redacts all but the last four characters of the credential. The redaction formula applies to all notification types, including PagerDuty, Slack, and Datadog. The formula is stable and safe to use in automations. Any disruptive API changes would require a new API version, and previous versions should remain usable. |
   | Microsoft Teams | Sends the alert to a [Microsoft Teams](https://www.microsoft.com/en-us/microsoft-teams/group-chat-software/) channel as an [Adaptive Card](https://docs.microsoft.com/en-us/microsoftteams/platform/task-modules-and-cards/cards/cards-reference#adaptive-card/). To send alert notifications to a Microsoft Teams channel, you must create a Microsoft Teams incoming webhook. After creating the webhook, you can use the automatically generated URL to configure your Microsoft Teams integration in Atlas. To setup the integration, see [Integrate with Microsoft Teams.](https://www.mongodb.com/docs/atlas/tutorial/integrate-msft-teams.md#std-label-integrate-with-microsoft-teams) When you view or edit the alert for a Microsoft Teams notification, the URL appears partially redacted. |
   | Webhook | Sends an HTTP (HyperText Transport Protocol) POST request to an endpoint for programmatic processing. The request body contains a JSON (Javascript Object Notation) document that uses the same format as the Atlas Administration API [Alerts resource.](https://www.mongodb.com/docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupalerts) Atlas includes HTTP (HyperText Transport Protocol) headers with each webhook request, including `X-MMS-Event` to indicate the alert state and `X-MMS-Signature` (if a secret is configured) to verify request authenticity. For detailed information about webhook payloads, headers, authentication, and limitations, see [Integrate with Webhooks.](https://www.mongodb.com/docs/atlas/tutorial/webhook-integration.md#std-label-webhook-integration) This option is available only if you have configured Webhook settings on the [Integrations](https://www.mongodb.com/docs/atlas/tutorial/third-party-service-integrations.md#std-label-third-party-integrations) page. When you view or edit the alert for a webhook notification, the URL and secret appear redacted: **URL:** Atlas preserves the protocol, host, and port, and replaces the path with `********`. For example, `http://webhook.mycompany.com:8080/api/alerts/secret` becomes `http://webhook.mycompany.com:8080/********`.; **Secret:** If the secret is longer than 10 characters, Atlas redacts all but the last four characters. If the secret is 10 characters or fewer, Atlas fully redacts the secret. Atlas uses the secret to generate the `X-MMS-Signature` header for request verification and does not send it as an authentication header. In the Webhook URL field, specify the target URL (Uniform Resource Locator) for webhook-based alerts.; (Optional) If you set up your Webhook integration with a secret, in the Webhook Secret field, specify the secret that Atlas uses to generate the `X-MMS-Signature` header for request verification.; (Optional) To customize the webhook request headers and body content, use the Webhook Headers Template and Webhook Body Template fields with FreeMarker templates. When you view or edit an alert with configured templates, the templates appear redacted with `******` and can be overwritten. |

6. Click Save.

### Configure an Auto-Scaling Alert

You can configure alerts for projects for a list of [auto-scaling events.](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#std-label-alert-conditions-autoscaling)

1. In Atlas, go to the Project Alerts page.

   If it's not already displayed, select the organization that contains your desired project from the  Organizations menu in the navigation bar.

   If it's not already displayed, select your desired project from the Projects menu in the navigation bar.

   In the top-right corner of the Atlas UI, click the Alerts icon.

   Click Alerts under the Project header.

   The [Project Alerts](https://cloud.mongodb.com/go?l=https%3A%2F%2Fcloud.mongodb.com%2Fv2%2F%3Cproject%3E%23%2Falerts%2FopenAlerts) page displays.

2. Choose whether to create a new alert setting, clone an existing alert setting, or update an existing alert setting.

   To create a new alert without cloning an existing setting:

   Click Add.

   Select New Alert.

   To clone an existing alert setting:

   Click the Alert Settings tab.

   Locate the alert setting you want to clone.

   Click  then Clone in that alert setting's row.

   To update an existing alert setting:

   Click the Alert Settings tab.

   Locate the alert setting you want to update.

   Click  then Edit in that alert setting's row.

3. Select the category and the condition or metric that triggers the alert.

   In the Category section, select Atlas Auto Scaling as the target component.

   In the Condition/Metric, select one of the following conditions.

   You can configure the following auto-scaling alerts:

   - [`Auto-scaling: Compute auto-scaling initiated for base tier`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Auto-scaling--Compute-auto-scaling-initiated-for-base-tier)

   - [`Auto-scaling: Compute auto-scaling initiated for analytics tier`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Auto-scaling--Compute-auto-scaling-initiated-for-analytics-tier)

   - [`Auto-scaling: Compute auto-scaling down didn't initiate for base tier due to storage requirements`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Auto-scaling--Compute-auto-scaling-down-didn-t-initiate-for-base-tier-due-to-storage-requirements)

   - [`Auto-scaling: Compute auto-scaling down didn't initiate for analytics tier due to storage requirements`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Auto-scaling--Compute-auto-scaling-down-didn-t-initiate-for-analytics-tier-due-to-storage-requirements)

   - [`Auto-scaling: Compute auto-scaling didn't initiate for base tier due to maximum configured cluster tier`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Auto-scaling--Compute-auto-scaling-didn-t-initiate-for-base-tier-due-to-maximum-configured-cluster-tier)

   - [`Auto-scaling: Compute auto-scaling didn't initiate for analytics tier due to maximum configured cluster tier`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Auto-scaling--Compute-auto-scaling-didn-t-initiate-for-analytics-tier-due-to-maximum-configured-cluster-tier)

   - [`Auto-scaling: Compute auto-scaling didn't initiate for base tier due to insufficient oplog size`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Auto-scaling--Compute-auto-scaling-didn-t-initiate-for-base-tier-due-to-insufficient-oplog-size)

   - [`Auto-scaling: Compute auto-scaling didn't initiate for analytics tier due to insufficient oplog size`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Auto-scaling--Compute-auto-scaling-didn-t-initiate-for-analytics-tier-due-to-insufficient-oplog-size)

   - [`Auto-scaling: Disk auto-scaling initiated`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Auto-scaling--Disk-auto-scaling-initiated)

   - [`Auto-scaling: Disk auto-scaling didn't initiate due to the cluster reaching maximum available disk size`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Auto-scaling--Disk-auto-scaling-didn-t-initiate-due-to-the-cluster-reaching-maximum-available-disk-size)

   - [`Auto-scaling: Disk auto-scaling didn't initiate due to insufficient oplog size`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Auto-scaling--Disk-auto-scaling-didn-t-initiate-due-to-insufficient-oplog-size)

   For the alert you want to configure, click  then Edit in that alert setting's row.

4. Select the alert recipients and delivery methods.

   - In the Add Notification Method section, select from the list of roles, and also select a notification method, such as Email or SMS.

   - In the Add Notifier drop-down menu, select from the options described in the following table.

     | Notification Option | Description |
     | --- | --- |
     | Atlas Project | Sends the alert by email or text message to users with specific roles in the Project. Atlas Project is the default alert recipient. You can configure the roles the alert is sent to and how it's delivered. You can't add a second Atlas Project as the recipient. If the [`Project Owner`](https://www.mongodb.com/docs/atlas/reference/user-roles.md#mongodb-authrole-Project-Owner) role is assigned to a human project member, Atlas delivers alerts to that member's configured email address or SMS target. If the [`Project Owner`](https://www.mongodb.com/docs/atlas/reference/user-roles.md#mongodb-authrole-Project-Owner) role is assigned programmatically, ensure you configure an explicit notification target (such as an email address, PagerDuty, Slack, or Webhook) to receive alerts. Programmatic API keys and service accounts do not receive alert notifications by default. Atlas Project is available as an option in the Add list only if it is not currently in the recipients list. Select the Project roles that should receive the alerts from the Select Role(s) check boxes or select All Roles for all users in the Project to receive the alert.; Select SMS to send these alerts to the mobile number configured for each Atlas Project user in their Account page.; Select Email to send these alerts to the email address configured for each Atlas Project user in their Account page. Email is checked by default. |
     | Atlas Organization | Sends the alert by email or text message to users with specific roles in the Organization. Select the Organization roles that should receive the alerts from the Select Role(s) check boxes or select All Roles for all users in the Organization to receive the alert.; Select SMS to send these alerts to the mobile number configured for each Atlas Organization user in Account page.; Select Email to send these alerts to the email address configured for each Atlas Organization user in Account page. Email is checked by default. |
     | Atlas User | Sends the alert by email or text message to a specified Atlas user. Select SMS to send these alerts to the mobile number configured for the Atlas user in their Account page.; Select Email to send these alerts to the email address configured for the Atlas user in their Account page. Email is checked by default. |
     | Email | Sends the alert to an email address. |
     | SMS | Sends the alert to a mobile number. Atlas removes all punctuation and letters and uses only the digits. If you are outside of the United States or Canada, include `011` and the [country code](https://countrycode.org/)  because Atlas uses the U.S.-based [Twilio](https://www.twilio.com) to send text messages. As an alternative to your non-U.S. telephone number, use a [Google Voice](https://voice.google.com) telephone number. For example, enter `01164` before the phone number to send the alert to a New Zealand mobile number. |
     | Slack | Sends the alert to a Slack channel. Enter the channel name and either an API (Application Programming Interface) token or a Bot token. To create an API (Application Programming Interface) token, see the [https://api.slack.com/web](https://api.slack.com/web) page in your Slack account. To learn more about Bot users in Slack, see [https://api.slack.com/bot-users.](https://api.slack.com/bot-users) After you create a notification that requires an API or integration key, the key appears redacted when you: View or edit the alert through the Atlas UI.; Query the alert for the notification through the Atlas Administration API. Atlas redacts all but the last four characters of the credential. The redaction formula applies to all notification types, including PagerDuty, Slack, and Datadog. The formula is stable and safe to use in automations. Any disruptive API changes would require a new API version, and previous versions should remain usable. |
     | PagerDuty | Sends the alert to a [PagerDuty](http://www.pagerduty.com/?utm_source=mongodb&utm_medium=docs&utm_campaign=partner) account. Enter only the PagerDuty service key. Define escalation rules and alert assignments directly in PagerDuty. Users can acknowledge PagerDuty alerts only from the PagerDuty dashboard. All new PagerDuty keys use their [Events API v2.](https://developer.pagerduty.com/docs/ZG9jOjExMDI5NTgw-events-api-v2-overview) If you have an Events API v1 key, you can continue to use that key with Atlas. After you create a notification that requires an API or integration key, the key appears redacted when you: View or edit the alert through the Atlas UI.; Query the alert for the notification through the Atlas Administration API. Atlas redacts all but the last four characters of the credential. The redaction formula applies to all notification types, including PagerDuty, Slack, and Datadog. The formula is stable and safe to use in automations. Any disruptive API changes would require a new API version, and previous versions should remain usable. |
     | Datadog | Sends the alert to a [Datadog](https://www.datadoghq.com/alerts/) account as a Datadog event. When the alert is first opened, Atlas sends the alert as an "error" event. Subsequent updates are sent as "info" events. When the alert is closed, Atlas sends a "success" event. Enter your DataDog API (Application Programming Interface) key under API Key and click Validate Datadog API Key.; Enter your API (Application Programming Interface) region.Atlas supports the following Datadog regions in the Atlas UI:`US1`; `US3`; `US5`; `EU1`; `AP1`Datadog uses `US1` by default.To learn more about Datadog's regions, see [Datadog Sites.](https://docs.datadoghq.com/getting_started/site/)After you create a notification that requires an API or integration key, the key appears redacted when you:View or edit the alert through the Atlas UI.; Query the alert for the notification through the Atlas Administration API.Atlas redacts all but the last four characters of the credential. The redaction formula applies to all notification types, including PagerDuty, Slack, and Datadog. The formula is stable and safe to use in automations. Any disruptive API changes would require a new API version, and previous versions should remain usable.; (Optional) To enable database metrics tracking, toggle Send Database Metrics to On.; (Optional) To enable collection latency metrics tracking, toggle Send Collection Latency Metrics to On.; (Optional) To enable query shape metrics tracking, toggle Send Query Shape Metrics to On.; Click Save. |
     | VictorOps | Sends the alert to a [VictorOps](https://victorops.com/) account. Enter the alphanumeric [API key](https://help.victorops.com/knowledge-base/rest-endpoint-integration-guide/) from VictorOps to integrate the VictorOps endpoint for alerts. Add dashes to the API key so it matches the format `xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx`. For example, `489f7he7-790b-9896-a8cf-j4757def1161`. Enter an optional [routing key](https://help.victorops.com/knowledge-base/routing-keys/) to route alerts to a specific VictorOps group. Click Post Test Alert to test the VictorOps configuration. Define escalation and routing rules directly in VictorOps. This option is available only for alerts that require acknowledgement. You can receive informational alerts from this [third-party monitoring service](https://www.mongodb.com/docs/atlas/tutorial/third-party-service-integrations.md#std-label-third-party-integrations) in Atlas. However, you must resolve these alerts within the external service. Acknowledge VictorOps alerts from the VictorOps dashboard. After you create a notification that requires an API or integration key, the key appears redacted when you: View or edit the alert through the Atlas UI.; Query the alert for the notification through the Atlas Administration API. Atlas redacts all but the last four characters of the credential. The redaction formula applies to all notification types, including PagerDuty, Slack, and Datadog. The formula is stable and safe to use in automations. Any disruptive API changes would require a new API version, and previous versions should remain usable. |
     | Opsgenie | Sends the alert to an [Opsgenie](https://www.opsgenie.com/) account. Enter only the Opsgenie API (Application Programming Interface) key. Define escalation rules and alert assignments directly in Opsgenie. This option is available only for alerts that require acknowledgement. You can receive informational alerts from this [third-party monitoring service](https://www.mongodb.com/docs/atlas/tutorial/third-party-service-integrations.md#std-label-third-party-integrations) in Atlas. However, you must resolve these alerts within the external service. Acknowledge Opsgenie alerts from the Opsgenie dashboard. After you create a notification that requires an API or integration key, the key appears redacted when you: View or edit the alert through the Atlas UI.; Query the alert for the notification through the Atlas Administration API. Atlas redacts all but the last four characters of the credential. The redaction formula applies to all notification types, including PagerDuty, Slack, and Datadog. The formula is stable and safe to use in automations. Any disruptive API changes would require a new API version, and previous versions should remain usable. |
     | Microsoft Teams | Sends the alert to a [Microsoft Teams](https://www.microsoft.com/en-us/microsoft-teams/group-chat-software/) channel as an [Adaptive Card](https://docs.microsoft.com/en-us/microsoftteams/platform/task-modules-and-cards/cards/cards-reference#adaptive-card/). To send alert notifications to a Microsoft Teams channel, you must create a Microsoft Teams incoming webhook. After creating the webhook, you can use the automatically generated URL to configure your Microsoft Teams integration in Atlas. To setup the integration, see [Integrate with Microsoft Teams.](https://www.mongodb.com/docs/atlas/tutorial/integrate-msft-teams.md#std-label-integrate-with-microsoft-teams) When you view or edit the alert for a Microsoft Teams notification, the URL appears partially redacted. |
     | Webhook | Sends an HTTP (HyperText Transport Protocol) POST request to an endpoint for programmatic processing. The request body contains a JSON (Javascript Object Notation) document that uses the same format as the Atlas Administration API [Alerts resource.](https://www.mongodb.com/docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupalerts) Atlas includes HTTP (HyperText Transport Protocol) headers with each webhook request, including `X-MMS-Event` to indicate the alert state and `X-MMS-Signature` (if a secret is configured) to verify request authenticity. For detailed information about webhook payloads, headers, authentication, and limitations, see [Integrate with Webhooks.](https://www.mongodb.com/docs/atlas/tutorial/webhook-integration.md#std-label-webhook-integration) This option is available only if you have configured Webhook settings on the [Integrations](https://www.mongodb.com/docs/atlas/tutorial/third-party-service-integrations.md#std-label-third-party-integrations) page. When you view or edit the alert for a webhook notification, the URL and secret appear redacted: **URL:** Atlas preserves the protocol, host, and port, and replaces the path with `********`. For example, `http://webhook.mycompany.com:8080/api/alerts/secret` becomes `http://webhook.mycompany.com:8080/********`.; **Secret:** If the secret is longer than 10 characters, Atlas redacts all but the last four characters. If the secret is 10 characters or fewer, Atlas fully redacts the secret. Atlas uses the secret to generate the `X-MMS-Signature` header for request verification and does not send it as an authentication header. In the Webhook URL field, specify the target URL (Uniform Resource Locator) for webhook-based alerts.; (Optional) If you set up your Webhook integration with a secret, in the Webhook Secret field, specify the secret that Atlas uses to generate the `X-MMS-Signature` header for request verification.; (Optional) To customize the webhook request headers and body content, use the Webhook Headers Template and Webhook Body Template fields with FreeMarker templates. When you view or edit an alert with configured templates, the templates appear redacted with `******` and can be overwritten. |

5. Click Save.

### Configure a Maintenance Window Alert

You can configure [Maintenance Window Alerts](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#std-label-maintenance-window-alerts) for projects with [configured maintenance windows.](https://www.mongodb.com/docs/atlas/tutorial/manage-project-settings.md#std-label-atlas-modify-project-settings)

1. In Atlas, go to the Project Alerts page.

   If it's not already displayed, select the organization that contains your desired project from the  Organizations menu in the navigation bar.

   If it's not already displayed, select your desired project from the Projects menu in the navigation bar.

   In the top-right corner of the Atlas UI, click the Alerts icon.

   Click Alerts under the Project header.

   The [Project Alerts](https://cloud.mongodb.com/go?l=https%3A%2F%2Fcloud.mongodb.com%2Fv2%2F%3Cproject%3E%23%2Falerts%2FopenAlerts) page displays.

2. Choose whether to create a new alert setting, clone an existing alert setting, or update an existing alert setting.

   To create a new alert without cloning an existing setting:

   Click Add.

   Select New Alert.

   To clone an existing alert setting:

   Click the Alert Settings tab.

   Locate the alert setting you want to clone.

   Click  then Clone in that alert setting's row.

   To update an existing alert setting:

   Click the Alert Settings tab.

   Locate the alert setting you want to update.

   Click  then Edit in that alert setting's row.

3. Select the category and the condition or metric that triggers the alert.

   In the Category section, select Atlas as the target component.

   In the Condition/Metric, select one of the following conditions:

   - [`Maintenance is scheduled`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Maintenance-is-scheduled)

   - [`Maintenance started`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Maintenance-started)

   - [`Maintenance no longer needed`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Maintenance-no-longer-needed)

   - [`Maintenance has been auto-deferred`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Maintenance-has-been-auto-deferred)

   For the alert you want to configure, click  then Edit in that alert setting's row.

4. Select the alert recipients and delivery methods.

   - In the Add Notification Method section, select from the list of roles, and also select a notification method, such as Email or SMS.

   - In the Add Notifier drop-down menu, select from the options described in the following table.

   | Notification Option | Description |
   | --- | --- |
   | Atlas Project | Sends the alert by email or text message to users with specific roles in the Project. Atlas Project is the default alert recipient. You can configure the roles the alert is sent to and how it's delivered. You can't add a second Atlas Project as the recipient. If the [`Project Owner`](https://www.mongodb.com/docs/atlas/reference/user-roles.md#mongodb-authrole-Project-Owner) role is assigned to a human project member, Atlas delivers alerts to that member's configured email address or SMS target. If the [`Project Owner`](https://www.mongodb.com/docs/atlas/reference/user-roles.md#mongodb-authrole-Project-Owner) role is assigned programmatically, ensure you configure an explicit notification target (such as an email address, PagerDuty, Slack, or Webhook) to receive alerts. Programmatic API keys and service accounts do not receive alert notifications by default. Atlas Project is available as an option in the Add list only if it is not currently in the recipients list. Select the Project roles that should receive the alerts from the Select Role(s) check boxes or select All Roles for all users in the Project to receive the alert.; Select SMS to send these alerts to the mobile number configured for each Atlas Project user in their Account page.; Select Email to send these alerts to the email address configured for each Atlas Project user in their Account page. Email is checked by default. |
   | Atlas Organization | Sends the alert by email or text message to users with specific roles in the Organization. Select the Organization roles that should receive the alerts from the Select Role(s) check boxes or select All Roles for all users in the Organization to receive the alert.; Select SMS to send these alerts to the mobile number configured for each Atlas Organization user in Account page.; Select Email to send these alerts to the email address configured for each Atlas Organization user in Account page. Email is checked by default. |
   | Atlas User | Sends the alert by email or text message to a specified Atlas user. Select SMS to send these alerts to the mobile number configured for the Atlas user in their Account page.; Select Email to send these alerts to the email address configured for the Atlas user in their Account page. Email is checked by default. |
   | Email | Sends the alert to an email address. |
   | SMS | Sends the alert to a mobile number. Atlas removes all punctuation and letters and uses only the digits. If you are outside of the United States or Canada, include `011` and the [country code](https://countrycode.org/)  because Atlas uses the U.S.-based [Twilio](https://www.twilio.com) to send text messages. As an alternative to your non-U.S. telephone number, use a [Google Voice](https://voice.google.com) telephone number. For example, enter `01164` before the phone number to send the alert to a New Zealand mobile number. |
   | Slack | Sends the alert to a Slack channel. Enter the channel name and either an API (Application Programming Interface) token or a Bot token. To create an API (Application Programming Interface) token, see the [https://api.slack.com/web](https://api.slack.com/web) page in your Slack account. To learn more about Bot users in Slack, see [https://api.slack.com/bot-users.](https://api.slack.com/bot-users) After you create a notification that requires an API or integration key, the key appears redacted when you: View or edit the alert through the Atlas UI.; Query the alert for the notification through the Atlas Administration API. Atlas redacts all but the last four characters of the credential. The redaction formula applies to all notification types, including PagerDuty, Slack, and Datadog. The formula is stable and safe to use in automations. Any disruptive API changes would require a new API version, and previous versions should remain usable. |
   | PagerDuty | Sends the alert to a [PagerDuty](http://www.pagerduty.com/?utm_source=mongodb&utm_medium=docs&utm_campaign=partner) account. Enter only the PagerDuty service key. Define escalation rules and alert assignments directly in PagerDuty. Users can acknowledge PagerDuty alerts only from the PagerDuty dashboard. All new PagerDuty keys use their [Events API v2.](https://developer.pagerduty.com/docs/ZG9jOjExMDI5NTgw-events-api-v2-overview) If you have an Events API v1 key, you can continue to use that key with Atlas. After you create a notification that requires an API or integration key, the key appears redacted when you: View or edit the alert through the Atlas UI.; Query the alert for the notification through the Atlas Administration API. Atlas redacts all but the last four characters of the credential. The redaction formula applies to all notification types, including PagerDuty, Slack, and Datadog. The formula is stable and safe to use in automations. Any disruptive API changes would require a new API version, and previous versions should remain usable. |
   | Datadog | Sends the alert to a [Datadog](https://www.datadoghq.com/alerts/) account as a Datadog event. When the alert is first opened, Atlas sends the alert as an "error" event. Subsequent updates are sent as "info" events. When the alert is closed, Atlas sends a "success" event. Enter your DataDog API (Application Programming Interface) key under API Key and click Validate Datadog API Key.; Enter your API (Application Programming Interface) region.Atlas supports the following Datadog regions in the Atlas UI:`US1`; `US3`; `US5`; `EU1`; `AP1`Datadog uses `US1` by default.To learn more about Datadog's regions, see [Datadog Sites.](https://docs.datadoghq.com/getting_started/site/)After you create a notification that requires an API or integration key, the key appears redacted when you:View or edit the alert through the Atlas UI.; Query the alert for the notification through the Atlas Administration API.Atlas redacts all but the last four characters of the credential. The redaction formula applies to all notification types, including PagerDuty, Slack, and Datadog. The formula is stable and safe to use in automations. Any disruptive API changes would require a new API version, and previous versions should remain usable.; (Optional) To enable database metrics tracking, toggle Send Database Metrics to On.; (Optional) To enable collection latency metrics tracking, toggle Send Collection Latency Metrics to On.; (Optional) To enable query shape metrics tracking, toggle Send Query Shape Metrics to On.; Click Save. |
   | VictorOps | Sends the alert to a [VictorOps](https://victorops.com/) account. Enter the alphanumeric [API key](https://help.victorops.com/knowledge-base/rest-endpoint-integration-guide/) from VictorOps to integrate the VictorOps endpoint for alerts. Add dashes to the API key so it matches the format `xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx`. For example, `489f7he7-790b-9896-a8cf-j4757def1161`. Enter an optional [routing key](https://help.victorops.com/knowledge-base/routing-keys/) to route alerts to a specific VictorOps group. Click Post Test Alert to test the VictorOps configuration. Define escalation and routing rules directly in VictorOps. This option is available only for alerts that require acknowledgement. You can receive informational alerts from this [third-party monitoring service](https://www.mongodb.com/docs/atlas/tutorial/third-party-service-integrations.md#std-label-third-party-integrations) in Atlas. However, you must resolve these alerts within the external service. Acknowledge VictorOps alerts from the VictorOps dashboard. After you create a notification that requires an API or integration key, the key appears redacted when you: View or edit the alert through the Atlas UI.; Query the alert for the notification through the Atlas Administration API. Atlas redacts all but the last four characters of the credential. The redaction formula applies to all notification types, including PagerDuty, Slack, and Datadog. The formula is stable and safe to use in automations. Any disruptive API changes would require a new API version, and previous versions should remain usable. |
   | Opsgenie | Sends the alert to an [Opsgenie](https://www.opsgenie.com/) account. Enter only the Opsgenie API (Application Programming Interface) key. Define escalation rules and alert assignments directly in Opsgenie. This option is available only for alerts that require acknowledgement. You can receive informational alerts from this [third-party monitoring service](https://www.mongodb.com/docs/atlas/tutorial/third-party-service-integrations.md#std-label-third-party-integrations) in Atlas. However, you must resolve these alerts within the external service. Acknowledge Opsgenie alerts from the Opsgenie dashboard. After you create a notification that requires an API or integration key, the key appears redacted when you: View or edit the alert through the Atlas UI.; Query the alert for the notification through the Atlas Administration API. Atlas redacts all but the last four characters of the credential. The redaction formula applies to all notification types, including PagerDuty, Slack, and Datadog. The formula is stable and safe to use in automations. Any disruptive API changes would require a new API version, and previous versions should remain usable. |
   | Microsoft Teams | Sends the alert to a [Microsoft Teams](https://www.microsoft.com/en-us/microsoft-teams/group-chat-software/) channel as an [Adaptive Card](https://docs.microsoft.com/en-us/microsoftteams/platform/task-modules-and-cards/cards/cards-reference#adaptive-card/). To send alert notifications to a Microsoft Teams channel, you must create a Microsoft Teams incoming webhook. After creating the webhook, you can use the automatically generated URL to configure your Microsoft Teams integration in Atlas. To setup the integration, see [Integrate with Microsoft Teams.](https://www.mongodb.com/docs/atlas/tutorial/integrate-msft-teams.md#std-label-integrate-with-microsoft-teams) When you view or edit the alert for a Microsoft Teams notification, the URL appears partially redacted. |
   | Webhook | Sends an HTTP (HyperText Transport Protocol) POST request to an endpoint for programmatic processing. The request body contains a JSON (Javascript Object Notation) document that uses the same format as the Atlas Administration API [Alerts resource.](https://www.mongodb.com/docs/api/doc/atlas-admin-api-v2/operation/operation-listgroupalerts) Atlas includes HTTP (HyperText Transport Protocol) headers with each webhook request, including `X-MMS-Event` to indicate the alert state and `X-MMS-Signature` (if a secret is configured) to verify request authenticity. For detailed information about webhook payloads, headers, authentication, and limitations, see [Integrate with Webhooks.](https://www.mongodb.com/docs/atlas/tutorial/webhook-integration.md#std-label-webhook-integration) This option is available only if you have configured Webhook settings on the [Integrations](https://www.mongodb.com/docs/atlas/tutorial/third-party-service-integrations.md#std-label-third-party-integrations) page. When you view or edit the alert for a webhook notification, the URL and secret appear redacted: **URL:** Atlas preserves the protocol, host, and port, and replaces the path with `********`. For example, `http://webhook.mycompany.com:8080/api/alerts/secret` becomes `http://webhook.mycompany.com:8080/********`.; **Secret:** If the secret is longer than 10 characters, Atlas redacts all but the last four characters. If the secret is 10 characters or fewer, Atlas fully redacts the secret. Atlas uses the secret to generate the `X-MMS-Signature` header for request verification and does not send it as an authentication header. In the Webhook URL field, specify the target URL (Uniform Resource Locator) for webhook-based alerts.; (Optional) If you set up your Webhook integration with a secret, in the Webhook Secret field, specify the secret that Atlas uses to generate the `X-MMS-Signature` header for request verification.; (Optional) To customize the webhook request headers and body content, use the Webhook Headers Template and Webhook Body Template fields with FreeMarker templates. When you view or edit an alert with configured templates, the templates appear redacted with `******` and can be overwritten. |

5. Click Save.

To create one alert configuration in the specified project using the Atlas CLI, run the following command:

```sh

atlas alerts settings create [options]

```

To update one alert configuration in the specified project using the Atlas CLI, run the following command:

```sh

atlas alerts settings update <alertConfigId> [options]

```

To learn more about the syntax and parameters for the previous commands, see the Atlas CLI documentation for [atlas alerts settings create](https://www.mongodb.com/docs/atlas/cli/current/command/atlas-alerts-settings-create/) and [atlas alerts settings-update.](https://www.mongodb.com/docs/atlas/cli/current/command/atlas-alerts-settings-update/)

**See also: Related Links**

- [Install the Atlas CLI](https://www.mongodb.com/docs/atlas/cli/current/install-atlas-cli/)

- [Connect to the Atlas CLI](https://www.mongodb.com/docs/atlas/cli/current/connect-atlas-cli/)

To list available field types for alert configurations using the Atlas CLI, run the following command:

```sh

atlas alerts settings fields type [options]

```

To learn more about the command syntax and parameters, see the Atlas CLI documentation for [atlas alerts settings fields type.](https://www.mongodb.com/docs/atlas/cli/current/command/atlas-alerts-settings-fields-type/)

1. In Atlas, go to the Organization Alerts page.

   If it's not already displayed, select your desired organization from the  Organizations menu menu in the navigation bar.

   In the top-right corner of the Atlas UI, click the Alerts icon.

   Click Alerts under the Organization header.

   The [Organization Alerts](https://cloud.mongodb.com/go?l=https%3A%2F%2Fcloud.mongodb.com%2Fv2%23%2Forg%2F%3Corganization%3E%2Falerts%2Flist) page displays.

2. Choose whether to create a new alert setting, clone an existing alert setting, or update an existing alert setting.

   To create a new alert:

   Click Add Alert.

   To clone an existing alert setting:

   Click the Alert Settings tab.

   Locate the alert setting you want to clone.

   Click  then Clone in that alert setting's row.

   To update an existing alert setting:

   Click the Alert Settings tab.

   Locate the alert setting you want to update.

   Click  then Edit in that alert setting's row.

3. Choose the Target.

   Under Select a Target, click Service Account, Billing, or User.

4. Choose the Condition.

   Under Select a Condition:

   - If you chose Service Account:

     Select from the following options:

     - [`Service Account Secrets have expired`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Service-Account-Secrets-have-expired)

     - [`Service Account Secrets are about to expire`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Service-Account-Secrets-are-about-to-expire)

     If in  DAY(S) appears next to the option you selected, specify the number of days before your service account secret expires that you want to be notified.

   - If you chose User, select:

     - [`Organization users do not have MFA enabled`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Users-do-not-have-multi-factor-authentication-enabled)

     - [`User has joined the organization`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-User-joined-the-organization)

     - [`User has left the organization`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-User-left-the-organization)

     - [`User's role has been changed`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-User-had-their-role-changed)

   - If you chose Billing:

     Select from the following options:

     - [`Credit card is about to expire`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Credit-card-is-about-to-expire)

     - [`Amount billed yesterday is above`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Amount-billed-----yesterday-is-above-the-threshold)

     - [`Current bill for any single project is above`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Current-bill-----for-any-single-project-is-above-the-threshold)

     - [`Current bill for the organization is above`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Current-bill-----for-the-organization-is-above-the-threshold)

     - [`Organization gross spend daily change is above`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Organization-gross-spend-daily-change-----is-above-the-threshold)

     - [`Organization gross spend weekly change is above`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Organization-gross-spend-weekly-change-----is-above-the-threshold)

     - [`Organization gross spend monthly change is above`](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#mongodb-alert-Organization-gross-spend-monthly-change-----is-above-the-threshold)

     If above $ appears next to the option you selected, specify the amount in USD (United States Dollars) where Atlas should trigger the alert if the selected condition exceeds that value.

5. Click Next.

6. Select the Notification Method.

   Under the Add Notification Method heading, click the button for the particular notification method you want to use.

   | Notification Option | Service Account Alerts | User Alerts | Billing Alerts | Description |
   | --- | --- | --- | --- | --- |
   | Atlas Organization |  |  |  | Sends the alert by email or text message to users with specific roles in the Organization. Select the Organization roles that should receive the alerts from the Select Role(s) check boxes or select All Roles for all users in the Organization to receive the alert.; Select SMS to send these alerts to the mobile number configured for each Atlas Organization user in their Account page.; Select Email to send these alerts to the email address configured for each Atlas Organization user in their Account page. Email is checked by default. |
   | Atlas User |  |  |  | Sends the alert by email or text message to a specified Atlas user. Select SMS to send these alerts to the mobile number configured for the Atlas user in their Account page.; Select Email to send these alerts to the email address configured for the Atlas user in their Account page. Email is checked by default. |
   | Email |  |  |  | Sends the alert to any email address you provide. |
   | Mobile Number |  |  |  | Sends the alert to a mobile number. Atlas removes all punctuation and letters and uses only the digits. If you are outside of the United States or Canada, include `011` and the [country code](https://countrycode.org/)  because Atlas uses the U.S.-based [Twilio](https://www.twilio.com) to send text messages. As an alternative to your non-U.S. telephone number, use a [Google Voice](https://voice.google.com) telephone number. For example, for New Zealand enter `01164` before the phone number. |
   | Slack |  |  |  | Sends the alert to a Slack channel in the authorized Slack workplace for the Organization. To learn more about Slack authorization, see [Authorize Slack to Receive Organization Alerts](https://www.mongodb.com/docs/atlas/tutorial/manage-organization-settings.md#std-label-add-slack-to-organization). Enter the channel name. After you create a notification that requires an API or integration key, the key appears redacted when you: View or edit the alert through the Atlas UI.; Query the alert for the notification through the Atlas Administration API. Atlas redacts all but the last four characters of the credential. The redaction formula applies to all notification types, including PagerDuty, Slack, and Datadog. The formula is stable and safe to use in automations. Any disruptive API changes would require a new API version, and previous versions should remain usable. |
   | PagerDuty |  |  |  | Sends the alert to a [PagerDuty](http://www.pagerduty.com/?utm_source=mongodb&utm_medium=docs&utm_campaign=partner) account. Enter only the PagerDuty service key. Define escalation rules and alert assignments directly in PagerDuty. Acknowledge PagerDuty alerts from the PagerDuty dashboard. All new PagerDuty keys use their [Events API v2.](https://developer.pagerduty.com/docs/ZG9jOjExMDI5NTgw-events-api-v2-overview) If you have an Events API v1 key, you can continue to use that key with Atlas. After you create a notification that requires an API or integration key, the key appears redacted when you: View or edit the alert through the Atlas UI.; Query the alert for the notification through the Atlas Administration API. Atlas redacts all but the last four characters of the credential. The redaction formula applies to all notification types, including PagerDuty, Slack, and Datadog. The formula is stable and safe to use in automations. Any disruptive API changes would require a new API version, and previous versions should remain usable. |
   | Datadog |  |  |  | Sends the alert to a [Datadog](https://www.datadoghq.com/alerts/) account as a Datadog event. When the alert is first opened, Atlas sends the alert as an "error" event. Subsequent updates are sent as "info" events. When the alert is closed, Atlas sends a "success" event. Enter your DataDog API (Application Programming Interface) key under API Key and click Validate Datadog API Key.; Enter your API (Application Programming Interface) region.Atlas supports the following Datadog regions in the Atlas UI:`US1`; `US3`; `US5`; `EU1`; `AP1`Datadog uses `US1` by default.To learn more about Datadog's regions, see [Datadog Sites.](https://docs.datadoghq.com/getting_started/site/)After you create a notification that requires an API or integration key, the key appears redacted when you:View or edit the alert through the Atlas UI.; Query the alert for the notification through the Atlas Administration API.Atlas redacts all but the last four characters of the credential. The redaction formula applies to all notification types, including PagerDuty, Slack, and Datadog. The formula is stable and safe to use in automations. Any disruptive API changes would require a new API version, and previous versions should remain usable.; (Optional) To enable database metrics tracking, toggle Send Database Metrics to On.; (Optional) To enable collection latency metrics tracking, toggle Send Collection Latency Metrics to On.; (Optional) To enable query shape metrics tracking, toggle Send Query Shape Metrics to On.; Click Save. |
   | VictorOps |  |  |  | Sends the alert to a [VictorOps](https://victorops.com/) account. Enter the alphanumeric [API key](https://help.victorops.com/knowledge-base/rest-endpoint-integration-guide/) from VictorOps to integrate the VictorOps endpoint for alerts. Add dashes to the API key so it matches the format `xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx`. For example, `489f7he7-790b-9896-a8cf-j4757def1161`. Enter an optional [routing key](https://help.victorops.com/knowledge-base/routing-keys/) to route alerts to a specific VictorOps group. Click Post Test Alert to test the VictorOps configuration. Define escalation and routing rules directly in VictorOps. This option is available only for alerts that you must acknowledge. You can receive informational alerts from this [third-party monitoring service](https://www.mongodb.com/docs/atlas/tutorial/third-party-service-integrations.md#std-label-third-party-integrations) in Atlas. However, you must resolve these alerts within the external service. Acknowledge VictorOps alerts from the VictorOps dashboard. After you create a notification that requires an API or integration key, the key appears redacted when you: View or edit the alert through the Atlas UI.; Query the alert for the notification through the Atlas Administration API. Atlas redacts all but the last four characters of the credential. The redaction formula applies to all notification types, including PagerDuty, Slack, and Datadog. The formula is stable and safe to use in automations. Any disruptive API changes would require a new API version, and previous versions should remain usable. |
   | Opsgenie |  |  |  | Sends the alert to an [Opsgenie](https://www.opsgenie.com/) account. Enter only the Opsgenie API key from an Opsgenie REST (Representational State Transfer) API (Application Programming Interface) integration. Define escalation rules and alert assignments in Opsgenie. This option is available only for alerts that you must acknowledge. You can receive informational alerts from this [third-party monitoring service](https://www.mongodb.com/docs/atlas/tutorial/third-party-service-integrations.md#std-label-third-party-integrations) in Atlas. However, you must resolve these alerts within the external service. [Acknowledge Opsgenie alerts](https://docs.opsgenie.com/docs/acknowledge-and-unacknowledge) from the Opsgenie dashboard. After you create a notification that requires an API or integration key, the key appears redacted when you: View or edit the alert through the Atlas UI.; Query the alert for the notification through the Atlas Administration API. Atlas redacts all but the last four characters of the credential. The redaction formula applies to all notification types, including PagerDuty, Slack, and Datadog. The formula is stable and safe to use in automations. Any disruptive API changes would require a new API version, and previous versions should remain usable. |
   | Microsoft Teams |  |  |  | Sends the alert to a [Microsoft Teams](https://www.microsoft.com/en-us/microsoft-teams/group-chat-software/) channel. You can view these alerts in the [Adaptive Card](https://docs.microsoft.com/en-us/microsoftteams/platform/task-modules-and-cards/cards/cards-reference#adaptive-card/) displayed in your channel. To send alert notifications to a Microsoft Teams channel, you must create a Microsoft Teams incoming webhook. After creating the webhook, you can use the automatically generated URL to configure your Microsoft Teams integration in Atlas. To setup the integration, see [Integrate with Microsoft Teams.](https://www.mongodb.com/docs/atlas/tutorial/integrate-msft-teams.md#std-label-integrate-with-microsoft-teams) When you view or edit the alert for a Microsoft Teams notification, the URL appears partially redacted. |

7. Click Save.

There are no specific instructions for creating organization alerts using the Atlas CLI. Instead, select Atlas UI from the Interface dropdown on this page.

## View Alert Configurations

You can configure [Maintenance Window Alerts](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#std-label-maintenance-window-alerts) for projects. These alerts are effective only for projects with an active [maintenance window configured](https://www.mongodb.com/docs/atlas/tutorial/manage-project-settings.md#std-label-atlas-modify-project-settings). If you don't configure a maintenance window, you can create a maintenance window alert but maintenance tasks will not trigger the alert.

You can view open alerts, closed alerts, and alert settings on the Project Alerts page. Atlas sends notifications for all alerts that appear on the Open tab. To learn more, see [Alerts Workflow.](https://www.mongodb.com/docs/atlas/alerts.md#std-label-alerts-workflow)

To view your alert configurations:

1. In Atlas, go to the Project Alerts page.

   If it's not already displayed, select the organization that contains your desired project from the  Organizations menu in the navigation bar.

   If it's not already displayed, select your desired project from the Projects menu in the navigation bar.

   In the top-right corner of the Atlas UI, click the Alerts icon.

   Click Alerts under the Project header.

   The [Project Alerts](https://cloud.mongodb.com/go?l=https%3A%2F%2Fcloud.mongodb.com%2Fv2%2F%3Cproject%3E%23%2Falerts%2FopenAlerts) page displays.

2. Click the Alerts Settings tab.

To list all alert configurations for the specified project using the Atlas CLI, run the following command:

```sh

atlas alerts settings list [options]

```

To return the details for the specified alert settings for your project using the Atlas CLI, run the following command:

```sh

atlas alerts settings describe <alertConfigId> [options]

```

To learn more about the syntax and parameters for the previous commands, see the Atlas CLI documentation for [atlas alerts settings list](https://www.mongodb.com/docs/atlas/cli/current/command/atlas-alerts-settings-list/) and [atlas alerts settings describe.](https://www.mongodb.com/docs/atlas/cli/current/command/atlas-alerts-settings-describe/)

**See also: Related Links**

- [Install the Atlas CLI](https://www.mongodb.com/docs/atlas/cli/current/install-atlas-cli/)

- [Connect to the Atlas CLI](https://www.mongodb.com/docs/atlas/cli/current/connect-atlas-cli/)

You can view all alerts, alert settings, and deleted alerts on the Organization Alerts page. To learn more, see [Alerts Workflow.](https://www.mongodb.com/docs/atlas/alerts.md#std-label-alerts-workflow)

To view your alert configurations:

1. In Atlas, go to the Organization Alerts page.

   If it's not already displayed, select your desired organization from the  Organizations menu menu in the navigation bar.

   In the top-right corner of the Atlas UI, click the Alerts icon.

   Click Alerts under the Organization header.

   The [Organization Alerts](https://cloud.mongodb.com/go?l=https%3A%2F%2Fcloud.mongodb.com%2Fv2%23%2Forg%2F%3Corganization%3E%2Falerts%2Flist) page displays.

2. Click the Alert Settings tab.

There are no specific instructions for viewing organization alert configurations using the Atlas CLI. Instead, select Atlas UI from the Interface dropdown on this page.

## Disable an Alert

1. In Atlas, go to the Project Alerts page.

   If it's not already displayed, select the organization that contains your desired project from the  Organizations menu in the navigation bar.

   If it's not already displayed, select your desired project from the Projects menu in the navigation bar.

   In the top-right corner of the Atlas UI, click the Alerts icon.

   Click Alerts under the Project header.

   The [Project Alerts](https://cloud.mongodb.com/go?l=https%3A%2F%2Fcloud.mongodb.com%2Fv2%2F%3Cproject%3E%23%2Falerts%2FopenAlerts) page displays.

2. Click Alert Settings.

3. Choose the alert setting to disable.

   On the row for a specific alert, click  then Disable.

   **Note:**

   Click  then Enable to re-enable the alert at any time.

If you disable an alert setting, Atlas cancels active alerts related to the setting. A disabled alert setting remains visible but grayed-out. You can re-enable it at any time.

To disable one alert configuration in the specified project using the Atlas CLI, run the following command:

```sh

atlas alerts settings disable <alertConfigId> [options]

```

To learn more about the command syntax and parameters, see the Atlas CLI documentation for [atlas alerts settings disable.](https://www.mongodb.com/docs/atlas/cli/current/command/atlas-alerts-settings-disable/)

1. In Atlas, go to the Organization Alerts page.

   If it's not already displayed, select your desired organization from the  Organizations menu menu in the navigation bar.

   In the top-right corner of the Atlas UI, click the Alerts icon.

   Click Alerts under the Organization header.

   The [Organization Alerts](https://cloud.mongodb.com/go?l=https%3A%2F%2Fcloud.mongodb.com%2Fv2%23%2Forg%2F%3Corganization%3E%2Falerts%2Flist) page displays.

2. Click Alert Settings.

3. Choose the alert setting to disable.

   On the row for a specific alert, click  then Disable.

   Click  then Enable to re-enable the alert at any time.

If you disable an alert setting, Atlas cancels active alerts related to the setting. A disabled alert setting remains visible but grayed-out and can be later re-enabled.

There are no specific instructions for disabling an organization alert using the Atlas CLI. Instead, select Atlas UI from the Interface dropdown on this page.

## Enable an Alert

To enable an alert that you previously disabled:

1. In Atlas, go to the Project Alerts page.

   If it's not already displayed, select the organization that contains your desired project from the  Organizations menu in the navigation bar.

   If it's not already displayed, select your desired project from the Projects menu in the navigation bar.

   In the top-right corner of the Atlas UI, click the Alerts icon.

   Click Alerts under the Project header.

   The [Project Alerts](https://cloud.mongodb.com/go?l=https%3A%2F%2Fcloud.mongodb.com%2Fv2%2F%3Cproject%3E%23%2Falerts%2FopenAlerts) page displays.

2. Click Alert Settings.

3. Re-enable the project alert setting.

   On the row for a specific alert, click .

   Click Enable.

To enable an alert that you previously disabled:

To enable one alert configuration in the specified project using the Atlas CLI, run the following command:

```sh

atlas alerts settings enable <alertConfigId> [options]

```

To learn more about the command syntax and parameters, see the Atlas CLI documentation for [atlas alerts settings enable.](https://www.mongodb.com/docs/atlas/cli/current/command/atlas-alerts-settings-enable/)

To enable an alert that you previously disabled:

1. In Atlas, go to the Organization Alerts page.

   If it's not already displayed, select your desired organization from the  Organizations menu menu in the navigation bar.

   In the top-right corner of the Atlas UI, click the Alerts icon.

   Click Alerts under the Organization header.

   The [Organization Alerts](https://cloud.mongodb.com/go?l=https%3A%2F%2Fcloud.mongodb.com%2Fv2%23%2Forg%2F%3Corganization%3E%2Falerts%2Flist) page displays.

2. Click Alert Settings.

3. Re-enable the alert setting.

   On the row for a specific alert, click .

   Click Enable.

There are no specific instructions for enabling organization alerts using the Atlas CLI. Instead, select Atlas UI from the Interface dropdown on this page.

## Delete an Alert

**Warning:**

Don't delete the [Maintenance Window Alerts](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#std-label-maintenance-window-alerts) that are created when you configure a maintenance window.

If you delete a maintenance window alert, disable and then re-enable your [maintenance window](https://www.mongodb.com/docs/atlas/tutorial/manage-project-settings.md#std-label-atlas-modify-project-settings) to re-create the alerts.

1. In Atlas, go to the Project Alerts page.

   If it's not already displayed, select the organization that contains your desired project from the  Organizations menu in the navigation bar.

   If it's not already displayed, select your desired project from the Projects menu in the navigation bar.

   In the top-right corner of the Atlas UI, click the Alerts icon.

   Click Alerts under the Project header.

   The [Project Alerts](https://cloud.mongodb.com/go?l=https%3A%2F%2Fcloud.mongodb.com%2Fv2%2F%3Cproject%3E%23%2Falerts%2FopenAlerts) page displays.

2. Click Alert Settings.

3. Choose the alert setting to delete.

   On the row for a specific alert, click  then Delete.

   The Delete option is disabled if you don't have one of the following roles:

   - [`Project Owner`](https://www.mongodb.com/docs/atlas/reference/user-roles.md#mongodb-authrole-Project-Owner)

   - [`Organization Owner`](https://www.mongodb.com/docs/atlas/reference/user-roles.md#mongodb-authrole-Organization-Owner)

   Click Confirm in the Confirm Delete modal or click Cancel to leave the alert as configured.

**Warning:**

Don't delete the [Maintenance Window Alerts](https://www.mongodb.com/docs/atlas/reference/alert-conditions.md#std-label-maintenance-window-alerts) that are created when you configure a maintenance window.

If you delete a maintenance window alert, disable and then re-enable your [maintenance window](https://www.mongodb.com/docs/atlas/tutorial/manage-project-settings.md#std-label-atlas-modify-project-settings) to re-create the alerts.

To delete one alert configuration in the specified project using the Atlas CLI, run the following command:

```sh

atlas alerts settings delete <alertConfigId> [options]

```

To learn more about the command syntax and parameters, see the Atlas CLI documentation for [atlas alerts settings delete.](https://www.mongodb.com/docs/atlas/cli/current/command/atlas-alerts-settings-delete/)

1. In Atlas, go to the Organization Alerts page.

   If it's not already displayed, select your desired organization from the  Organizations menu menu in the navigation bar.

   In the top-right corner of the Atlas UI, click the Alerts icon.

   Click Alerts under the Organization header.

   The [Organization Alerts](https://cloud.mongodb.com/go?l=https%3A%2F%2Fcloud.mongodb.com%2Fv2%23%2Forg%2F%3Corganization%3E%2Falerts%2Flist) page displays.

2. Click Alert Settings.

3. Choose the alert setting to delete.

   On the row for a specific alert, click  then Delete.

   Click Delete in the Delete Alert modal or click Cancel to leave the alert as configured.

   **Note:**

   If you have not logged in within the five minutes of pushing Delete, you need to re-enter your password, then click Delete again.

There are no specific instructions for deleting an organization alert using the Atlas CLI. Instead, select Atlas UI from the Interface dropdown on this page.

If you delete an alert setting, Atlas cancels active alerts related to the setting. A deleted alert setting does not remain visible.