Notes on Integrating with Specific Observability Platforms

Most major APM/Observability platforms support OpenTelemetry ingestion with minimal configuration. Depending on the specific tool, you use, you may need to add specific headers in order for ingestion to work correctly.

Datadog

Datadog now supports tracing integration via OpenTelemetry natively. In order to set this up, you’ll need to know which Datadog site you use and your API key.

• Datadog’s OpenTelemetry URLs are specified as https://otlp.{SITE}/v1/traces, e.g., https://otlp.datadoghq.com/v1/traces for the US1 site.
• dd-api-key header must be included and set to a valid API key.

See Datadog OTLP Intake documentation  for more details.

Coralogix

Coralogix OpenTelemetry integration generally works by adding the following custom headers to your OpenTelemetry configuration:

• CX-Application-Name (Should be set to the environment name that produces the data)
• CX-Subsystem-Name (Should be set to the name of the service that produces the data)

See Coralogix OpenTelemetry documentation  for further details.

New Relic

New Relic also offers support for consuming OpenTelemetry Data, but you will need to add the following custom header to your configuration:

• api-key (Must be set to your license key)

See New Relic OpenTelemetry documentation  for further details.

For additional instructions on how to integrate your specific observability platform with OpenTelemetry, please refer to your specific provider’s documentation or contact Svix support .