On this page
Atlas issues alerts for the database and server conditions configured in your alert settings. When a condition triggers an alert, Atlas displays a warning symbol on the cluster and sends alert notifications. Your alert settings determine the notification methods. Atlas continues sending notifications at regular intervals until the condition resolves or you delete or disable the alert. You should fix the immediate problem, implement a long-term solution, and view metrics to monitor your progress.
If you integrate with VictorOps, OpsGenie, or DataDog, you can recieve informational alerts from these third-party monitoring services in Atlas. However, you must resolve these alerts within each external service.
When you acknowledge an alert, Atlas sends no further notifications until either the acknowledgement period ends, you resolve the alert condition, or you unacknowledge the alert. If an alert condition ends during an acknowledgment period, Atlas sends a notification.
You can unacknowledge an alert that you previously acknowledged. After you unacknowledge an active alert, Atlas resumes sending notifications at regular intervals until the condition resolves or you delete, disable, or re-acknowledge the alert.
To resolve an alert by increasing your cluster's capacity, see Modify a Cluster.
To view and filter the activity feed for an organization or project, see View the Activity Feed.
The following sections describe Atlas alert conditions and suggest steps for resolving them.
Amount of CPU and memory used by Atlas Search processes reach a specified threshold.
Number of connections to a MongoDB process exceeds the allowable maximum.
Percentage of disk IOPS utilized reaches a specified threshold.
Percentage of used disk space on a partition reaches a specified threshold.
Indicates inefficient queries.
No primary is detected in replica set.
CPU usage of the MongoDB process reaches a specified threshold.