Docs Menu
Docs Home
/ /

Configure Alert Settings

For each organization and project, you can select which conditions trigger alerts and how users are notified.

Note

M0 Free clusters and Flex clusters only trigger alerts related to the metrics supported by those clusters. For complete documentation on M0 and Flex clusters alert and metric limitations, see Atlas M0 (Free Cluster) Limits, and Atlas Flex Limitations.

To manage all organization alerts, you must have the Organization Owner role for the organization.

The Organization Billing Admin role grants a limited authorization to manage billing alerts.

To manage project alerts, you must have Project Owner or Project Alerts Manager access to the project. Users with Organization Owner access must add themselves to the project as a Project Owner.

Every alert has a default security level. When you configure an alert, you can optionally select a severity level for that alert that overrides the system default severity level.

Atlas includes the following severity levels:

  • Critical

  • Error

  • Warning

  • Info

The severity levels in Atlas map to the following severity levels in our third-party notification services:

Atlas

PagerDuty
Opsgenie
VictorOps
DataDog

Critical

Critical

P1

Critical

Error

Error

Error

P2

Critical

Error

Warning

Warning

P4

Warning

Warning

Info

Info

P5

Info

Info

When you create a new alert, you can clone an existing alert. You can also update an existing alert configuration.

You can configure Maintenance Window Alerts for projects. These alerts are effective only for projects with an active maintenance window configured. If you don't configure a maintenance window, you can create a maintenance window alert but maintenance tasks will not trigger the alert.

If you delete an alert setting, Atlas cancels active alerts related to the setting. A deleted alert setting does not remain visible.

Back

Review Alert Conditions

On this page