This category contains documentation topics explaining the observability capabilities available for LaunchDarkly SDKs. These include session replay, error monitoring, logging, and tracing.
The functionality is available through observability SDKs, which are implemented as plugins to LaunchDarkly server-side and client-side SDKs. You can enable this functionality when you initialize a LaunchDarkly SDK client in your app:
After you initialize the server-side or client-side SDK and one or more observability plugins, your application automatically starts sending observability data back to LaunchDarkly. You can review this information in the LaunchDarkly user interface. To learn how, read the Observability product overview.
The observability SDKs communicate with two LaunchDarkly endpoints:
https://otel.observability.app.launchdarkly.com
This endpoint receives OpenTelemetry Protocol (OTLP) data from the SDKs over HTTPS. All telemetry data, including traces, logs, and metrics, is sent here.
The endpoint accepts data on the following paths:
All data is compressed with gzip before transmission. The default port is 4318 (OTLP HTTP). Server-side SDKs may also use gRPC on port 4317.
https://pub.observability.app.launchdarkly.com
This endpoint serves SDK configuration, including sampling rules. The SDKs query this endpoint using GraphQL over HTTPS to retrieve their sampling configuration during initialization. This allows LaunchDarkly to dynamically control sampling rates without requiring SDK restarts.
You may need to update your infrastructure to allow the SDK to reach both of these domains. To learn more, read Accessing LaunchDarkly by domain.
If requests to these endpoints are being blocked, you can set up a proxy through your own domain using CNAME records. To learn more, read Using a proxy.
