Third-Party Service Integrations

Default service key for alert notifications sent to a PagerDuty account. Ops Manager 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, Ops Manager 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 replica set has elected a new primary, cannot use PagerDuty notification.

Users can acknowledge PagerDuty alert notifications only from the PagerDuty dashboard.

IMPORTANT: Changing the Integration Key doesn't change any alerts that use this integration. Those alerts still use the previous Integration Key. Remove and re-add each PagerDuty notification to use the new key.

All new PagerDuty keys use their Events API v2. If you have an Events API v1 key, you can continue to use that key with Ops Manager.

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 Ops Manager, your API token is automatically generated and maintained. You will be redirected back to the Integrations page.

After initially configuring Slack with Ops Manager, 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.

IMPORTANT: Legacy tokens are deprecated and will be removed in a future version of Ops Manager. You cannot edit a legacy token integration. Instead, you must reconfigure your Slack integration with OAuth2.

API key and Routing key for alert notifications sent to a VictorOps account. Ops Manager uses these values 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.

• VictorOps API Key

• VictorOps Routing Key (optional)

API key for alert notifications sent to an Opsgenie account. Ops Manager uses this value as the default OpsGenie Alert 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.

• Opsgenie API Key

• API Region (United States only)

Configuration Ops Manager uses to send metric data about your deployment to Datadog. You can view these metrics in your Datadog dashboards.

Enter the following information from your Datadog account to have Datadog begin tracking your Ops Manager metric data. If you do not have an existing Datadog account, you can sign up at DataDog.

• Datadog API Key

  You might see an inaccurate health status in the following scenarios:

  • If you have a network partition and the MongoDB Agent lives on an isolated nde in a replica set, only pings from the isolated node reach Datadog. The isolated node and Ops Manager UI report the other nodes as down.

  • If you have a network partition and the MongoDB Agent lives outside the impacted nodes, pings from all the nodes reach Datadog, but report different statuses.

  • If all nodes are unresponsive or their state is hanging, no new pings come in. The Ops Manager UI reports these nodes as down, but Datadog reports them as healthy and the status gets older.

  IMPORTANT: If the health status is 1 but no other metrics appear in Datadog, the replica set might be down.

Webhook URL endpoint to which Ops Manager can send alerts for programmatic processing. Ops Manager sends an alert as an HTTP POST request in which the request body contains a JSON document that uses the same format as the Ops Manager API Alerts resource.

Ops Manager adds a request header called X-MMS-Event to distinguish between various alert states. The possible values for this header are:

If you specify a key in the Webhook Secret field, MongoDB Ops Manager adds the X-MMS-Signature request header. This header contains the base64-encoded HMAC-SHA-1 signature of the request body. MongoDB Ops Manager 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 configuration. If you add a Webhook notification and the URL or optional key becomes invalid, Ops Manager sends an email to the Project Owner and eventually removes the Webhook settings.

If your webhook requires HTTPS, you must import your CA certificate into the Ops Manager trust store.

Sets default values for alert notifications sent to Flowdock. Ops Manager 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, MongoDB Atlas sends an email to the project owner and eventually removes the credentials.

Enter the following information from your CA Flowdock account. If you do not have an existing CA Flowdock account, you can sign up.

• Org Name

• Flow Name

• API Token

Configures Ops Manager to send alerts about your project to your Microsoft Teams channel. You can view these alerts in the Adaptive Card displayed in your channel.

To send alert notifications to a Microsoft Teams channel, you must create a Microsoft Teams incoming webhook. After creating the webhook, you can use the automatically generated URL to configure your Microsoft Teams integration in Ops Manager.

To setup the integration, see Integrate with Microsoft Teams.