Skip to main content

Documentation Index

Fetch the complete documentation index at: https://launchdarkly-preview.mintlify.app/llms.txt

Use this file to discover all available pages before exploring further.

​
Overview

This topic explains how to enable OpenTelemetry in client-side SDKs, using the LaunchDarkly observability plugins. OpenTelemetry (OTel) is an open source observability framework and toolkit designed to create and manage telemetry data such as traces, metrics, and logs.
For information on using OpenTelemetry in LaunchDarkly’s server-side SDKs, read OpenTelemetry in server-side SDKs.

​
Viewing Open

Telemetry data in LaunchDarkly In the LaunchDarkly UI, OpenTelemetry data is used in the observability, Experimentation, feature monitoring, and guarded rollouts features. When LaunchDarkly receives OpenTelemetry trace data, it processes and converts this data into events that LaunchDarkly metrics track over time. LaunchDarkly also automatically normalizes deprecated OpenTelemetry attribute names to their current equivalents, so you can use older attribute names and LaunchDarkly will create the corresponding current attribute names for you. To learn more, read Automatic attribute normalization.

​
Sending Open

Telemetry data to LaunchDarkly When you use one of the LaunchDarkly client-side SDKs, LaunchDarkly automatically ingests OTel data if you are using one of the observability SDKs. These are implemented as plugins that you can configure as part of initializing the client-side SDK. The SDKs send this data to LaunchDarkly at the following endpoints:
  • https://otel.observability.app.launchdarkly.com/v1/traces
  • https://otel.observability.app.launchdarkly.com/v1/logs
  • https://otel.observability.app.launchdarkly.com/v1/metrics
You may need to update your infrastructure to make sure the SDK can reach this domain. To learn more, read Accessing LaunchDarkly by domain.

​
Client-side SDKs

Learn more about client-side SDK observability support for your SDK: