Configure Alert Settings
On this page
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. You can also update an existing alert configuration.
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.
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. NoteAtlas 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.
|
Atlas Organization | Sends the alert by email or text message to users with specific roles in the Organization.
|
Atlas User | Sends the alert by email or text message to a specified Atlas user.
|
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 ExampleFor New Zealand enter |
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. NoteAfter you create a notification which requires an API or integration key, the key appears partially redacted when you:
|
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 Administration API Alerts resource. This option is available only if you have configured Webhook settings on the Integrations page. NoteWhen you view or edit the alert for a webhook notification, the URL appears partially redacted, and the secret appears completely redacted.
|
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.
NoteAfter you create a notification which requires an API or integration key, the key appears partially redacted when you:
|
Microsoft Teams | Sends the alert to a Microsoft Teams channel as an 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. NoteWhen you view or edit the alert for a Microsoft Teams notification, the URL appears partially redacted. |
View Alert Configurations
Disable an Alert
Enable an Alert
To enable an alert that you previously disabled: