> For the complete documentation index, see [llms.txt](https://docs.ilert.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ilert.com/integrations/inbound-integrations/mongodbatlas.md).
# MongoDB Atlas Integration
Connect MongoDB Atlas alerts to ilert to send notifications about replica issues, slow queries, or resource constraints to on-call teams.
[MongoDB Atlas](https://www.mongodb.com/) is a fully-managed cloud database that handles all the complexity of deploying, managing, and deployments to the preferred cloud service provider (AWS , Azure, and GCP). With the MongoDB Atlas integration, alerts about replica lag, slow queries, or resource caps are forwarded to on-call engineers via ilert. These technical alerts trigger escalation policies and deliver necessary context, helping teams maintain database performance and reliability.
## In ilert: Create a MongoDB Atlas alert source
1. Go to **Alerting** → **Alert sources** and click **Create new alert source**.
2. Search for **MongoDB Atlas**, click its tile, and click **Next**.
3. Give your alert source a name, optionally assign teams, and click **Next**.
4. Choose who gets notified: select **Use existing escalation policy** and pick a policy, or **Generate new escalation policy** to start with a basic one that notifies you first. Click **Next**.
Pick an existing escalation policy, or generate a basic one without leaving the wizard.
5. Select **Default grouping** and click **Continue setup**. It groups events by the alert key the integration sets; the other [grouping options](/alerting/configure-alerting/alert-sources.md#event-grouping) are easier to judge once events are arriving.
6. The next page shows more settings, such as notification priority and alert templates. Click **Finish setup** for now; you can change them later.
7. On the final page, ilert shows the integration key and URL for this alert source. You will need them later in this guide.
## In MongoDB Atlas
1. In the Project page, click the **Bell (Notification) Icon** on top right.
2. Add Webhook Settings in Integration if it was not configured, by clicking **Integrations** and add the Webhook Settings (there can only be one Webhook).
3. Create the Alert by navigating to **Alert -> Add New Alert**. From here any alerts can be added, and make sure that it sends the Alert to the Webhook.
4. If the Alert has been configured, it should show up in the **Alert Settings** tab and the Alert should be created in ilert.
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://docs.ilert.com/integrations/inbound-integrations/mongodbatlas.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
