# Resolve Alerts

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.

<Tabs>

<Tab name="Organization Alerts">

</Tab>

<Tab name="Project Alerts">

</Tab>

</Tabs>

## View Alerts

<Tabs>

<Tab name="Organization Alerts">

You can view all alerts, alert settings, and deleted alerts on the Organization Alerts page. To learn more, see Alerts Workflow.

To view all open alerts:

### Navigate to the Alerts page for your organization.

- If it is not already displayed, select your desired organization from the  Organizations menu in the navigation bar.

- Click Alerts in the sidebar.

### If it is not already displayed, click the All Alerts tab.

</Tab>

<Tab name="Project Alerts">

<Tabs>

<Tab name="Atlas CLI">

To list all alerts for the specified Atlas project using the Atlas CLI, run the following command:

```sh

atlas alerts list [options]

```

To return the details for one alert in the project you specify using the Atlas CLI, run the following command:

```sh

atlas alerts describe <alertId> [options]

```

To learn more about the syntax and parameters for the previous commands, see the Atlas CLI documentation for atlas alerts list and atlas alerts describe.

- Install the Atlas CLI

- Connect to the Atlas CLI

</Tab>

<Tab name="Atlas UI">

You can view open alerts, closed alerts, and alert settings on the Project Alerts page. Atlas sends notifications for all alerts that appear on the Open tab. To learn more, see Alerts Workflow.

To view all open alerts using the Atlas UI:

### 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.

### If it is not already displayed, click the Open Alerts tab.

</Tab>

</Tabs>

</Tab>

</Tabs>

## Acknowledge Alerts

<Tabs>

<Tab name="Organization Alerts">

To acknowledge alerts:

### Navigate to the Alerts page for your organization.

- If it is not already displayed, select your desired organization from the  Organizations menu in the navigation bar.

- Click Alerts in the sidebar.

### Select the alert you want to acknowledge, then click Mark Acknowledge.

If an alert uses PagerDuty for alert notifications, you can acknowledge the alert only on your PagerDuty dashboard.

</Tab>

<Tab name="Project Alerts">

<Tabs>

<Tab name="Atlas CLI">

To acknowledge one alert for the specified project using the Atlas CLI, run the following command:

```sh

atlas alerts acknowledge <alertId> [options]

```

To learn more about the command syntax and parameters, see the Atlas CLI documentation for atlas alerts acknowledge.

- Install the Atlas CLI

- Connect to the Atlas CLI

</Tab>

<Tab name="Atlas UI">

To acknowledge alerts using the Atlas UI:

### 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.

### Locate the alert you want to acknowledge, then click Acknowledge.

If an alert uses PagerDuty for alert notifications, you can acknowledge the alert only on your PagerDuty dashboard.

</Tab>

</Tabs>

</Tab>

</Tabs>

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.

## Unacknowledge Alerts

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.

<Tabs>

<Tab name="Organization Alerts">

To unacknowledge alerts:

### Navigate to the Alerts page for your organization.

- If it is not already displayed, select your desired organization from the  Organizations menu in the navigation bar.

- Click Alerts in the sidebar.

### Select the alert you want to acknowledge, then click Unacknowledge on the right side of the alert.

If an alert uses PagerDuty for alert notifications, you can acknowledge the alert only on your PagerDuty dashboard.

</Tab>

<Tab name="Project Alerts">

<Tabs>

<Tab name="Atlas CLI">

To unacknowledge one alert for the specified project using the Atlas CLI, run the following command:

```sh

atlas alerts unacknowledge <alertId> [options]

```

To learn more about the command syntax and parameters, see the Atlas CLI documentation for atlas alerts unacknowledge.

- Install the Atlas CLI

- Connect to the Atlas CLI

</Tab>

<Tab name="Atlas UI">

To unacknowledge alerts using the Atlas UI:

### 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.

### Locate the alert you want to acknowledge, then click Unacknowledge on the right side of the alert.

If an alert uses PagerDuty for alert notifications, you can acknowledge the alert only on your PagerDuty dashboard.

</Tab>

</Tabs>

</Tab>

</Tabs>

## Increase Cluster Capacity

To resolve an alert by increasing your cluster's capacity, see Modify a Cluster.

## View All Activity

To view and filter the activity feed for an organization or project, see View the Activity Feed.

## Retrieve the Activity Feed

<Tabs>

<Tab name="Organization Alerts">

You can retrieve events for an organization using the get all API (Application Programming Interface) resource.

</Tab>

<Tab name="Project Alerts">

You can retrieve events for a project using the get all API (Application Programming Interface) resource.

</Tab>

</Tabs>

## Resolutions for Specific Alerts

The following sections describe Atlas
alert conditions and suggest steps for resolving them.

<table>
<tr>
<th id="Alert%20Type">
Alert Type

</th>
<th id="Description">
Description

</th>
</tr>
<tr>
<td headers="Alert%20Type">
Atlas Search Alerts

</td>
<td headers="Description">
Amount of CPU and memory used by Atlas Search processes reach a specified threshold.

</td>
</tr>
<tr>
<td headers="Alert%20Type">
Connection Alerts

</td>
<td headers="Description">
Number of connections to a MongoDB process exceeds the allowable maximum.

</td>
</tr>
<tr>
<td headers="Alert%20Type">
Disk Space % Used Alerts

</td>
<td headers="Description">
Percentage of used disk space on a partition reaches a specified threshold.

</td>
</tr>
<tr>
<td headers="Alert%20Type">
Query Targeting Alerts

</td>
<td headers="Description">
Indicates inefficient queries.

The change streams cursors that the Atlas Search process (`mongot`) uses to keep Atlas Search indexes updated can contribute to the query targeting ratio and trigger query targeting alerts if the ratio is high.

</td>
</tr>
<tr>
<td headers="Alert%20Type">
Replica Set Has No Primary

</td>
<td headers="Description">
No primary is detected in replica set.

</td>
</tr>
<tr>
<td headers="Alert%20Type">
Replication Oplog Alerts

</td>
<td headers="Description">
Amount of oplog data generated on a primary cluster member is larger than the cluster's configured oplog size.

</td>
</tr>
<tr>
<td headers="Alert%20Type">
System CPU Usage Alerts

</td>
<td headers="Description">
CPU usage of the MongoDB process reaches a specified threshold.

</td>
</tr>
</table>