Integrate with Third-Party Monitoring Services¶
You can integrate Atlas with third-party monitoring services to receive Atlas alerts in various external monitoring services.
Currently, serverless instance metrics don't support any third-party monitoring services (for example, Datadog).
Required Access¶
To view third-party integration settings, you must have
Organization Owner or Project Owner access to
the project.
View / Modify Third-Party Settings¶
To modify third-party integration settings:
Navigate to the Integrations page for your project.¶
- If it is not already displayed, select the organization that contains your desired project from the Organizations menu in the navigation bar.
- If it is not already displayed, select your desired project from the Projects menu in the navigation bar.
- Next to the Projects menu, expand the Options menu, then click Integrations.
Configure the third-party integrations you want to enable.¶
Click Configure for the third-party service you wish to modify. You can set one or more of the following:
Third-Party Service | Configuration Details | ||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
PagerDuty Service Key | Sets a default service key for alert notifications sent to a PagerDuty account. Atlas enters the key by default when you add a PagerDuty notification to an alert configuration. If you add PagerDuty notifications and if the key used to send the notifications becomes invalid, Atlas sends an email to the project owner and eventually removes the key. You can add PagerDuty notifications only for alerts that require user acknowledgement. Informational alerts, such as the alert that a user has joined a project, cannot use this notification method. Users can acknowledge PagerDuty alerts only from the PagerDuty dashboard. Note PagerDuty decommissioned their v1 API key in October 2018. If you have a v1 key, you can continue to use that key with Atlas. All new PagerDuty keys use their v2 API, but Atlas does not support their v2 key. If you don't have their v1 key, use Webhook instead of PagerDuty. | ||||||||||||||
Flowdock Settings | Sets default values for alert notifications sent to Flowdock. Atlas enters the values by default when you add a Flowdock notification to an alert configuration. If you add Flowdock notifications, and if credentials to send notifications become invalid, Atlas sends an email to the project owner and eventually removes the credentials. Set the following:
| ||||||||||||||
Slack Settings | Sets a team name, API token and a channel name for alert notifications sent to a Slack account. To configure a Slack integration with OAuth2, click Configure and then Sign in with Slack. When you sign in, you are taken to a Slack landing page where you may select a workspace and configure permissions. After configuring Slack to connect to Atlas, your API token is automatically generated and maintained. Atlas redirects you back to the Integrations page. After initially configuring Slack with Atlas, you can Edit or Remove the integration. When you edit the integration, Atlas displays your team name and API token, and allow you to change your channel name. Important Legacy Token Deprecation Atlas deprecated legacy tokens. They will be removed in a future version of Atlas. You cannot edit a legacy token integration. You must reconfigure your Slack integration with OAuth2. | ||||||||||||||
Webhook Settings | Adds a Webhook URL endpoint to which Atlas can
send alert notifications for programmatic processing. Atlas
sends an alert notification as an HTTP POST request. The
request body contains a JSON document that uses the same
format as the Atlas API Atlas adds a request header called
If you specify a key in the Webhook Secret field,
Atlas adds the To send alert notifications to a Webhook, select the Webhook notification option when creating or editing an alert. If you add a Webhook notification and the URL or optional key becomes invalid, Atlas sends an email to the project owner and eventually removes the Webhook settings. Important If your firewall configuration requires it, allow access from Atlas IP addresses so that Atlas can communicate with your webhook. | ||||||||||||||
VictorOps Settings | Sets an API key and Routing key for alert notifications sent to a Splunk On-Call (formerly VictorOps) account. Atlas uses this information as the default settings when configuring alerts.
| ||||||||||||||
OpsGenie API Key | Sets an API key for alert notifications sent to an OpsGenie account. This will be used as the default OpsGenie API key when configuring alerts.
| ||||||||||||||
New Relic Settings | Important Effective Wednesday, June 16th, 2021, New Relic no longer supports the plugin-based integration with MongoDB. We do not recommend that you sign up for the plugin-based integration. To learn more, see the New Relic Plugin EOL Statement. Consider configuring an alternative monitoring integration before June 16th to maintain visibility into your MongoDB deployments. Configures Atlas to send metric data about your deployment to New Relic for viewing through the New Relic MongoDB plugin. You can also use Insights for New Relic to run analytics on the collected data. Atlas sends New Relic the same metric data as displayed in Atlas cluster metrics.
If any of the keys later become invalid, Atlas sends an email to the project owner and eventually removes the invalid credentials. | ||||||||||||||
Datadog Settings | Configures Atlas to send metric data about your deployment to Datadog. You can view these metrics in your Datadog dashboards. To discover the detailed list of all Atlas metrics that Datadog tracks, refer to the Datadog Integration page.
| ||||||||||||||
SumoLogic Settings | Connects you to the relevant SumoLogic documentation for
configuring SumoLogic with Atlas. You don't need to
configure any settings within Atlas to set up a SumoLogic
integration. |