Configure Alert Settings¶

On this page

Default Alert Settings

Notification Options
Configure an Alert
Configure a Maintenance Window Alert
Disable an Alert
Delete an Alert

Important

Required Privileges

To manage alerts, you must have the Project Owner role for the project.

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

Note

M0 free clusters and M2/M5 shared clusters only trigger alerts related to the metrics supported by those clusters. See Atlas M0 (Free Cluster), M2, and M5 Limitations for complete documentation on M0/M2/M5 alert and metric limitations.

Default Alert Settings¶

Notification Options¶

Configure an Alert¶

When you create a new alert, you can clone an existing alert.

Configure a Maintenance Window Alert¶

You can configure Maintenance Window Alerts for projects with configured maintenance windows.

Navigate to the Alerts page for your project.¶

If it is not already displayed, select the organization that contains your desired project from the Organizations menu in the navigation bar.
If it is not already displayed, select your desired project from the Projects menu in the navigation bar.
Click the Project Alerts icon in the navigation bar, or click Alerts in the sidebar.

Click Alert Settings.¶

Select the maintenance window alerts you want to configure.¶

You can configure the following maintenance window alerts:

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

Select the alert recipients and delivery methods.¶

In the Send to section, click Add and 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. Note 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. 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 because Atlas uses the U.S.-based Twilio to send text messages. As an alternative to your non-U.S. telephone number, use a Google Voice telephone number. Example For New Zealand enter `01164` before the phone number.
Slack	Sends the alert to a Slack channel. Enter the channel name and either an API token or a Bot token. To create an API token, see the 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.
Flowdock	Sends the alert to a Flowdock account. Enter the following: Org Name: The Flowdock organization name in lower-case letters. This is the name that appears after `www.flowdock.com/app/` in the URL string. Flow Name: The flow name in lower-case letters. The flow name appears after the organization name in the URL string: `www.flowdock.com/app/<organization-name>/<flow-name>` User API Token: Your Flowdock personal API token found on the https://www.flowdock.com/account/tokens page of your Flowdock account.
Webhook	Sends an HTTP POST request to an endpoint for programmatic processing. The request body contains a JSON document that uses the same format as the Atlas API Alerts resource. This option is available only if you have configured Webhook settings on the Integrations page.
Datadog	Sends the alert to a Datadog 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. If prompted, enter your Datadog API key under API Key and click Validate Datadog API Key.

Click Save.¶

Disable an Alert¶

Delete an Alert¶

← Review Alert Conditions Resolve Alerts →