• Monitor Your Cluster >
• Integrate with Third-Party Monitoring Services

Integrate with Third-Party Monitoring Services

You can integrate Atlas with third-party monitoring services to receive Atlas alerts in various external monitoring services.

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:

1

Navigate to the Integrations page for your project.

1. If it is not already displayed, select the organization that contains your desired project from the office icon Organizations menu in the navigation bar.
2. If it is not already displayed, select your desired project from the Projects menu in the navigation bar.
3. Next to the Projects menu, expand the Options menu, then click Integrations.

2

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.
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: Org Name The Flowdock organization name in lower-case letters. This is the name that appears after www.flowdock.com/app/ in the URL string. Flow Name The flow name in lower-case letters. The flow name appears after the organization name in the URL string: www.flowdock.com/app/<organization-name>/<flow-name> API Token Your Flowdock “personal API token” found on the https://www.flowdock.com/account/tokens page of your Flowdock account.
Slack Settings	Sets a team name, API token and a channel name for alert notifications sent to a Slack account. You can configure a Slack integration with OAuth2 by clicking 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. You will be redirected back to the Integrations page. After initially configuring Slack with Atlas, you can Edit or Remove the integration. Editing the integration will display your team name and API token, and allow you to change your channel name. Legacy Token Deprecation Legacy tokens are deprecated and will be removed in a future version of Atlas. You cannot edit a legacy token integration. Instead, 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 Alerts resource. Atlas adds a request header called X-MMS-Event to distinguish between various alert states. The possible values for this header are: alert.open The alert was just opened. alert.close The alert was resolved. alert.update A previously opened alert is still open. alert.acknowledge The alert was acknowledged. alert.cancel The alert became invalid and was canceled. alert.inform Represents an informational alert, which is a Continuous Cloud Backup event, such as “Primary Elected.” If you specify a key in the Webhook Secret field, Atlas adds the X-MMS-Signature request header. This header contains the base64-encoded HMAC-SHA-1 signature of the request body. Atlas creates the signature using the provided secret. 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.
VictorOps Settings	Sets an API key and Routing key for alert notifications sent to a VictorOps account. This will be used as the default VictorOps settings when configuring alerts. Enter the following information from your VictorOps account. If you do not have an existing VictorOps account, you can sign up using https://help.victorops.com/knowledge-base/new-user-sign/. VictorOps API Key VictorOps Routing Key (optional)
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. Enter the following information from your OpsGenie account. If you do not have an existing OpsGenie account, you can sign up using https://www.opsgenie.com/signup : OpsGenie API Key API Region (United States or Europe)
New Relic Settings	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. Enter the following information from your New Relic account. If you do not have an existing New Relic account, you can sign up using http://newrelic.com/mongodb. Account ID License Key Insights API Insert Key Insights API Query Key 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. For a detailed list of all Atlas metrics that Datadog tracks, refer to the Datadog Integration page. Enter the following information from your Datadog account to have Datadog begin tracking your Atlas metric data. If you do not have an existing Datadog account, you can sign up at https://app.datadoghq.com/signup. Datadog API Key API Region (United States or Europe)
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.

• Integrate with a Monitoring Service
  • Build Monitoring Integrations with Atlas API
  • Integrate Atlas with Datadog
    • Prerequisites
    • Procedure
      • Navigate to your Project Integrations.
      • Link Datadog to your project using your Datadog API key.
    • Performance Metrics Available to Datadog

←   System CPU Usage Integrate with a Monitoring Service  →

© MongoDB, Inc 2008-present. MongoDB, Mongo, and the leaf logo are registered trademarks of MongoDB, Inc.