- Monitoring and Alerts >
- Configure Alert Settings
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 Tier and M2/M5
shared starter clusters
only trigger alerts related to the metrics supported by
those clusters. See Atlas M0 (Free Tier), M2, and M5 Limitations for complete documentation
on M0/M2/M5
alert and metric limitations.
- Organization Alerts
- Project Alerts
Default Alert Settings¶
Atlas provides no default alerts for organizations.
Atlas provides the following default alerts for a new project:
Replica set has no primary
Cluster is missing an active mongos
Disk space % used on Data Partition is
Disk I/O % utilization on Data Partition is
User joined the project
Credit card is about to expire
Query Targeting: Scanned Objects / Returned
Connections % of configured limit is
System: CPU (Steal) % is
System: CPU (User) % is
Atlas provides the following default alert for projects using Customer Key Management with AWS KMS:
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.
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
- SMS
- PagerDuty
- Flowdock
- Datadog
- VictorOps
- Opsgenie
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 Organization
- Atlas User
- SMS
- PagerDuty
- Flowdock
- Datadog
- VictorOps
- Opsgenie
Configure an Alert¶
When you create a new alert, you can clone an existing alert.
Choose whether to create a new alert setting or clone an existing one.¶
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 ellipsis h icon then Clone in that alert setting’s row.
Choose the Target.¶
Click User or Billing under Select a Target.
Choose the Condition.¶
Under Select a Condition:
- If you chose User, select:
- If you chose Billing:
- Select from the following options:
- If above $ appears next to the option you selected, specify the amount in USD where Atlas should trigger the alert if the selected condition exceeds that value.
Select the Notification Method.¶
Under the Add Notification Method heading, click the button for the particular notification method you want to use.
Notification Option | User Alerts | Billing Alerts | Description |
---|---|---|---|
Atlas Organization | check icon | check icon | Sends the alert by email or text message to users with specific roles in the Organization.
|
Atlas User | check icon | check icon | Sends the alert by email or text message to a specified Atlas user.
|
check icon | check icon | Sends the alert to any email address you provide. | |
Mobile Number | check icon | check icon | 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 Example For New Zealand enter |
Slack | check icon | check icon | 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. Enter the channel name. |
Flowdock | check icon | check icon | Sends the alert to a Flowdock account. Enter the following:
|
PagerDuty | check icon | Sends the alert to a PagerDuty account. Enter only the PagerDuty service key. Define escalation rules and alert assignments directly in PagerDuty. This option is available only for alerts that require acknowledegment. Informational alerts, such as the alert that a Atlas user has joined a project, cannot use this notification method. Atlas users can acknowledge PagerDuty alerts only from the PagerDuty dashboard. |
|
Datadog | check icon | check icon | 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. |
VictorOps | check icon | Sends the alert to a VictorOps account. Enter a VictorOps API key to integrate the VictorOps endpoint for alerts and an optional routing key to route alerts to a specific VictorOps group. Click Post Test Alert to test VictorOps configuration. Define escalation and routing rules directly in VictorOps. Users can acknowledge VictorOps alerts only from the VictorOps dashboard. |
|
Opsgenie | check icon | Sends the alert to an Opsgenie account. Enter only the Opsgenie API key. Define escalation rules and alert assignments directly in Opsgenie. Users can acknowledge Opsgenie alerts only from the Opsgenies dashboard. |
Click Save.¶
Choose whether to create a new alert setting or clone an existing one.¶
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 ellipsis h icon then Clone in that alert setting’s row.
Select the condition that triggers the alert.¶
In the Alert if section, select the target component and the condition. To learn more about alert conditions, see Alert Conditions.
Apply the alert only to specific targets. (Optional)¶
If the options in the For section are available, you can optionally filter the alert to apply only to a subset of the targets.
The matches field can use regular expressions.
Select the alert recipients and delivery methods.¶
In the Send to section, click Add and select from the options described in the following table.
To help eliminate false positives, set the time to elapse before the condition triggers the alert.
Notification Option | Description |
---|---|
Atlas Project | Sends the alert by email or text message to users with specific roles in the Project.
|
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.
|
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 Example For 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. |
Flowdock | Sends the alert to a Flowdock account. Enter the following:
|
PagerDuty | Sends the alert to a PagerDuty account. Enter only the PagerDuty service key. Define escalation rules and alert assignments directly in PagerDuty. This option is available only for alerts that require acknowledegment. Informational alerts, such as the alert that a user has joined a project, cannot use this notification method. Users can acknowledge PagerDuty alerts only from the PagerDuty dashboard. |
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. |
VictorOps | Sends the alert to a VictorOps account. Enter a VictorOps API key to integrate the VictorOps endpoint for alerts and an optional routing key to route alerts to a specific VictorOps group. Click Post test issue to VictorOps to test VictorOps configuration. Define escalation and routing rules directly in VictorOps. This option is available only for alerts that require acknowledgement. Informational alerts, such as the alert that a user has joined a project, cannot use this notification method. Users can acknowledge VictorOps alerts only from the VictorOps dashboard. |
Opsgenie | Sends the alert to an Opsgenie account. Enter only the Opsgenie API key. Define escalation rules and alert assignments directly in Opsgenie. This option is available only for alerts that require acknowledgement. Informational alerts, such as the alert that a user has joined a project, cannot use this notification method. Users can acknowledge Opsgenie alerts only from the Opsgenie dashboard. |
Click Save.¶
Disable an Alert¶
Choose the alert setting to disable.¶
On the row for a specific alert, click ellipsis h icon then Disable.
Note
Click ellipsis h icon 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.
Delete an Alert¶
Navigate to Alert Settings.¶
Click Alerts then Alert Settings.
Choose the alert setting to delete.¶
- On the row for a specific alert, click ellipsis h icon then Delete.
- Click Confirm in the Confirm Delete modal or click Cancel to leave the alert as configured.
If you delete an alert setting, Atlas cancels active alerts related to the setting. A deleted alert setting does not remain visible.