> For the complete MongoDB documentation index, see www.mongodb.com/docs/llms.txt

# Monitoring, Logging and Alerts

## Monitoring

You must have the [`Project Owner`](https://docs.atlas.mongodb.com/reference/user-roles/#mongodb-authrole-Project-Owner) role to configure a third-party monitoring integration.

**Tip:**

AtlasGov user roles are the same as [Atlas User Roles.](https://www.mongodb.com/docs/atlas/reference/user-roles/)

See the Atlas documentation to [Integrate with Third-Party Monitoring Services](https://www.mongodb.com/docs/atlas/tutorial/third-party-service-integrations/)

### Datadog

When integrated with Datadog, AtlasGov uses the Datadog for Government site (US1-FED).

To learn more about US1-FED, see the [Datadog documentation.](https://docs.datadoghq.com/getting_started/site/#the-datadog-for-government-site)

## Logging

In addition to the standard Atlas logging, AtlasGov logs the username and IP address associated with all failed login attempts, temporary lockouts and failed API (Application Programming Interface) digest authentications.

See the Atlas documentation to [View and Download MongoDB Logs](https://www.mongodb.com/docs/atlas/mongodb-logs/)

## Alerts and Communications

You receive emails from a different MongoDB account depending on the region to which your resources are deployed and the type of communication.

### AWS GovCloud and GCP Assured Workloads Regions

- Alerts come from `mongodb-atlasgov-alerts@mongodb.com`.

- All other emails come from `mongodb-atlasgov-support@mongodb.com`.

### AWS Commercial

- Alerts come from `mongodb-cloud-alerts@mongodb.com`.

- All other emails come from `mongodb-cloud-support@mongodb.com`.

See the Atlas documentation to [Configure and Resolve Alerts](https://www.mongodb.com/docs/atlas/alerts/)