- Monitor Your Cluster >
- Configure and Resolve Alerts >
- Resolve Alerts
Resolve Alerts¶
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.
View Alerts¶
To view all open alerts, click Alerts in the Project section of the left navigation.
Acknowledge Alerts¶
To acknowledge an alert, click Alerts in the Project section of the left navigation, locate the alert, and click Acknowledge.
If an alert uses PagerDuty for alert notifications, you can acknowledge the alert only on your PagerDuty dashboard.
When you acknowledge an alert, Atlas sends no further notifications until either the acknowledgement period ends, you resolve the alert condition, or you unacknowledge alert. If an alert condition ends during an acknowledgment period, Atlas sends a notification.
Increase Cluster Capacity¶
To resolve an alert by increasing your cluster’s capacity, see Modify a Cluster.
View All Activity¶
To view cluster events, click Activity Feed in the Project section of the left navigation. You can filter the list by date and by activity type. To view a complete list of all actions captured in the Activity Feed, click the Types input above the activity list.
Resolutions for Specific Alerts¶
The following sections describe Atlas alert conditions and suggest steps for resolving them.
| Alert Type | Description |
|---|---|
| Connection Alerts | Number of connections to a MongoDB process exceeds the allowable maximum. |
| Disk I/O % Utilization Alerts | Percentage of disk IOPS utilized reaches a specified threshold. |
| Disk Space % Used Alerts | Percentage of used disk space on a partition reaches a specified threshold. |
| Query Targeting Alerts | Indicates inefficient queries. |
| Replica Set Has No Primary | No primary is detected in replica set. |
| Replication Oplog Alerts | Amount of oplog data generated on a primary cluster member is larger than the cluster’s configured oplog size. |
| System CPU Usage Alerts | CPU usage of the MongoDB process reaches a specified threshold. |