Resolve Alerts
- OAuth 2.0 authentication for programmatic access to Cloud Manager is available as a Preview feature.
- The feature and the corresponding documentation might change at any time during the Preview period. To use OAuth 2.0 authentication, create a service account to use in your requests to the Cloud Manager Public API.
Cloud Manager issues an alert for each condition configured in your alert settings when an alert condition occurs, such as an unresponsive host or an outdated agent.
To view all alert notifications:
In MongoDB Cloud Manager, go to the Organization Settings page.
If it's not already displayed, select your desired organization from the Organizations menu in the navigation bar.
Click the Organization Settings icon next to the Organizations menu.
The Organization Settings page displays.
Go to the Organization Alerts page.
Click Alerts in the sidebar.
The Organization Alerts page displays.
In MongoDB Cloud Manager, go to the Project Alerts page.
If it's not already displayed, select the organization that contains your desired project from the Organizations menu in the navigation bar.
If it's not already displayed, select your desired project from the Projects menu in the navigation bar.
Do one of the following steps:
Click the Project Alerts icon in the navigation bar.
Next to the Projects menu, expand the Options menu, click Project Settings, and click Alerts in the sidebar.
The Project Alerts page displays.
When a condition triggers an alert, you receive the alert at regular intervals until the alert resolves or Cloud Manager cancels it. You can acknowledge an alert for a period of time, but if the alert condition persists, you will again receive notifications once the acknowledgment period ends.
You can temporarily suspend alerts on a resource by creating an alert maintenance window. For example, you can create a maintenance window that suspends host alerts while you shut down hosts for maintenance.
Cloud Manager administrators define alert configurations on a per-project basis.
To learn more, see Alerts Workflow and Manage Alerts.
Resolved Alerts
Alerts resolve when the alert condition no longer applies. For example, if a replica set's primary goes down, Cloud Manager issues an alert that the replica set does not have a primary. When a new primary is elected, the alert condition no longer applies, and the alert will resolve. Cloud Manager sends a notification of the alert's resolution.
Cancelled Alerts
Cloud Manager cancels an alert if the alert configuration that triggered the alert is deleted, disabled, edited, or if the open alert becomes invalid. Some examples of an alert becoming invalid are:
There is an open "Host Down" alert, and then you delete the target host.
There is an open "Replication Lag" alert, and the target host becomes the primary.
There is an open "Replica set has no primary" alert for a replica set whose name is "rs0," and the target replica set is renamed to "rs1."
When an alert is canceled, Cloud Manager does not send a notification and does not record an entry on the Cloud Manager Alerts lists.