> For the complete MongoDB documentation index, see www.mongodb.com/docs/llms.txt # Integrate with OpenTelemetry (OTel) You can configure Atlas to send metric data about your project to your OpenTelemetry [collector](https://opentelemetry.io/docs/collector/), providing a unified interface to metrics platforms such as [Dynatrace](https://docs.dynatrace.com/docs) and [New Relic.](https://docs.newrelic.com/) ## Required Access To integrate Atlas with OTel metrics, you must have [`Project Owner`](https://www.mongodb.com/docs/atlas/reference/user-roles.md#mongodb-authrole-Project-Owner) access to the project. Users with [`Organization Owner`](https://www.mongodb.com/docs/atlas/reference/user-roles.md#mongodb-authrole-Organization-Owner) access must add themselves to the project as a `Project Owner`. ## Network Requirements The OTel metrics endpoint integration connects only to public IP addresses. Configure your OTel collector to allow inbound traffic from the Atlas outbound IP addresses for the provider and region in which your project is deployed. To learn how to identify these addresses, see [Networking.](https://www.mongodb.com/docs/atlas/atlas-stream-processing/security.md#std-label-atlas-sp-security-networking) **Note:** Atlas enforces TLS when connecting to OTLP endpoints and requires certificates signed by a public Certificate Authority (CA). Self-signed certificates are not supported. ## Prerequisites To integrate Atlas with OTel metrics you must have one of the following: - An [OTLP Endpoint](https://opentelemetry.io/docs/languages/sdk-configuration/otlp-exporter/), if you want to integrate with a custom OTel provider. - A [Dynatrace API](https://docs.dynatrace.com/docs/dynatrace-api) token and [Environment ID](https://docs.dynatrace.com/docs/discover-dynatrace/get-started/monitoring-environment) to export to Dynatrace - A [New Relic API](https://docs.newrelic.com/docs/apis/intro-apis/new-relic-api-keys/) key to export to New Relic. ## Procedure To configure an Atlas integration with a custom OTLP endpoint: 1. In Atlas, go to the Project Settings page. If it's not already displayed, select the organization that contains your desired project from the Organizations menu in the navigation bar. If it's not already displayed, select your desired project from the Projects menu in the navigation bar. In the sidebar, click the icon next to Project Overview. The [Project Settings](https://cloud.mongodb.com/go?l=https%3A%2F%2Fcloud.mongodb.com%2Fv2%2F%3Cproject%3E%23%2Fsettings%2FgroupSettings) page displays. 2. In Atlas, go to the Project Integrations page. Click the Integrations tab. The [Project Integrations](https://cloud.mongodb.com/go?l=https%3A%2F%2Fcloud.mongodb.com%2Fv2%2F%3Cproject%3E%23%2Fintegrations) page displays. 3. Configure your custom OTel provider. Click Configure for the OpenTelemtry Metrics integration card. From the Provider dropdown menu, select Custom. Provide your OTLP Endpoint. Provide your OTLP Headers as a series of key-value pairs. For each additional header after the first, click + Add Header to display new input fields. From the Aggregation Temporality dropdown menu, select the appropriate [temporality](https://opentelemetry.io/docs/specs/otel/metrics/data-model/#temporality) for your OTLP endpoint. (Optional) To enable Atlas Stream Processing metrics tracking, check the Atlas Stream Processing box under the Select Metrics to Send heading. Click Save. To configure an Atlas integration with Dynatrace via OTel: 1. In Atlas, go to the Project Settings page. If it's not already displayed, select the organization that contains your desired project from the Organizations menu in the navigation bar. If it's not already displayed, select your desired project from the Projects menu in the navigation bar. In the sidebar, click the icon next to Project Overview. The [Project Settings](https://cloud.mongodb.com/go?l=https%3A%2F%2Fcloud.mongodb.com%2Fv2%2F%3Cproject%3E%23%2Fsettings%2FgroupSettings) page displays. 2. In Atlas, go to the Project Integrations page. Click the Integrations tab. The [Project Integrations](https://cloud.mongodb.com/go?l=https%3A%2F%2Fcloud.mongodb.com%2Fv2%2F%3Cproject%3E%23%2Fintegrations) page displays. 3. Configure your Dynatrace provider. Click Configure for the OpenTelemtry Metrics integration card. From the Provider dropdown menu, select Dynatrace. Provide your Dynatrace Environment ID. Provide your Dynatrace API Token. (Optional) To enable Atlas Stream Processing metrics tracking, check the Atlas Stream Processing box under the Select Metrics to Send heading. Click Save. To configure an Atlas integration with New Relic via OTel: 1. In Atlas, go to the Project Settings page. If it's not already displayed, select the organization that contains your desired project from the Organizations menu in the navigation bar. If it's not already displayed, select your desired project from the Projects menu in the navigation bar. In the sidebar, click the icon next to Project Overview. The [Project Settings](https://cloud.mongodb.com/go?l=https%3A%2F%2Fcloud.mongodb.com%2Fv2%2F%3Cproject%3E%23%2Fsettings%2FgroupSettings) page displays. 2. In Atlas, go to the Project Integrations page. Click the Integrations tab. The [Project Integrations](https://cloud.mongodb.com/go?l=https%3A%2F%2Fcloud.mongodb.com%2Fv2%2F%3Cproject%3E%23%2Fintegrations) page displays. 3. Configure your New Relic provider. Click Configure for the OpenTelemtry Metrics integration card. From the Provider dropdown menu, select New Relic. Provide your New Relic API Key. From the Aggregation Temporality dropdown menu, select the appropriate [temporality.](https://opentelemetry.io/docs/specs/otel/metrics/data-model/#temporality) (Optional) To enable Atlas Stream Processing metrics tracking, check the Atlas Stream Processing box under the Select Metrics to Send heading. Click Save. ## Behavior The Otel integration forwards the metrics Atlas Stream Processing emits to OpenTelemetry. The Otel integration does not process any of these metrics. Upon creating, updating, or triggering a test of your integration, Atlas Stream Processing issues a test metric to validate that the integration is operational. Atlas Stream Processing can simultaneously support up to: - One New Relic OTel sink - One Dynatrace OTel sink - Two custom OTel sinks The availability of each sink type is unaffected by the usage of any other.