MongoDB Atlas / Cloud Manager

Route your MongoDB Atlas / Cloud manager alerts to Squadcast

Follow the below steps to configure routing of your MongoDB Atlas / Cloud manager alerts to Squadcast.

Note: MongoDB Atlas is the cloud hosted version of MongoDB offered by the company, whereas MongoDB Cloud Manager is the open source self-hosted version of MongoDB.

Using MongoDB as an Alert Source

On the Sidebar, click on Services.

You can either choose to use existing service or create a new service

Now, click on the corresponding Alert Sources button.

Select MongoCloudManager from Alert Source drop down and copy the Webhook URL shown.

📘

Select the Alert Source Integration type as MongoAtlas (For MongoDB Atlas hosted version) / MongoCloudManager (For Self hosted version).

  1. Go to your MongoDB Atlas / Cloud manager Dashboard and click on Settings and click the edit icon on Webhook settings and enter the webhook url obtained from the previous step and click Save button. (You need Account owner permissions to do this in MongoDB)
  1. Now we can add the created webhook as an alert mechanism for both new / existing alerts. Click Add -> New Alert to create a new alert.
  1. Define the alert parameters and under Send to, select Webhook and click Save button.

The Alert is configured and integrated with Squadcast and whenever it is triggered in MongoDB, an incident will be triggered in Squadcast as well.

Squadcast automatically syncs the alert status from MongoDB as defined below.

If a user Acknowledges the alert in MongoDB, Squadcast will also Acknowledge (Auto-Acknowledge) the incident in Squadcast, provided the same user (with same email ID) is also present in Squadcast.

Squadcast will Auto-Resolve the incident, if the alerts get resolved in MongoDB and doesn't require any manual intervention from the user.

Updated 6 months ago


MongoDB Atlas / Cloud Manager


Route your MongoDB Atlas / Cloud manager alerts to Squadcast

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.