Datadog Agent ingestion

Overview

This topic explains how to send traces, metrics, and logs from the Datadog Agent to LaunchDarkly’s observability features.

LaunchDarkly’s OpenTelemetry Collector includes a Datadog-compatible receiver. If you already run the Datadog Agent in your infrastructure, you can configure it to send APM traces, metrics, and logs to LaunchDarkly without changing your application instrumentation. Once received, this telemetry is available in the Traces, Logs, and observability dashboards in the LaunchDarkly UI.

Prerequisites

Before you configure Datadog Agent ingestion, you must:

• Have LaunchDarkly observability enabled for your project
• Have the Datadog Agent v6.0 or later installed and running in your infrastructure
• Know your LaunchDarkly client-side ID

To find your client-side ID:

1. In the LaunchDarkly UI, click the project dropdown to open the project menu.
2. Select Project settings.
3. Click Environments.
4. Find the environment you want to use and copy the Client-side ID value.

Configure the Datadog Agent

To send telemetry to LaunchDarkly, configure the Datadog Agent to use LaunchDarkly’s Datadog-compatible endpoint instead of (or in addition to) the standard Datadog intake.

Endpoint: otel.observability.app.launchdarkly.com:8126

Configure using the agent configuration file

To configure the Datadog Agent using the datadog.yaml configuration file, include these lines:

1
apm_config:
2
  enabled: true
3
  apm_dd_url: http://otel.observability.app.launchdarkly.com:8126
4
5
logs_config:
6
  logs_dd_url: otel.observability.app.launchdarkly.com:8126
7
  use_http: true
8
9
dd_url: http://otel.observability.app.launchdarkly.com:8126

Configure using environment variables

If you run the Datadog Agent in a container, you can use environment variables to provide the configuration:

$
DD_APM_ENABLED=true
$
DD_APM_DD_URL=http://otel.observability.app.launchdarkly.com:8126
$
DD_DD_URL=http://otel.observability.app.launchdarkly.com:8126

Configure using Docker Compose

If you run the Datadog Agent as a Docker container, add the configuration to your docker-compose.yml file:

1
services:
2
  datadog-agent:
3
    image: gcr.io/datadoghq/agent:latest
4
    environment:
5
      - DD_APM_ENABLED=true
6
      - DD_APM_DD_URL=http://otel.observability.app.launchdarkly.com:8126
7
      - DD_DD_URL=http://otel.observability.app.launchdarkly.com:8126
8
      - DD_API_KEY=placeholder

Associate telemetry with your LaunchDarkly project

LaunchDarkly uses the launchdarkly.project_id resource attribute to route telemetry to the correct project. Set this to your LaunchDarkly client-side ID.

You can set this attribute in your application’s OpenTelemetry SDK configuration, or use the OTEL_RESOURCE_ATTRIBUTES environment variable for services that send data through the agent:

$
export OTEL_RESOURCE_ATTRIBUTES="launchdarkly.project_id=YOUR_CLIENT_SIDE_ID"

Alternatively, if you use the OpenTelemetry Collector in front of the Datadog Agent, you can inject this attribute using a resource processor. To learn more, read OpenTelemetry in server-side SDKs.

What data is collected

The Datadog Agent sends the following telemetry types to LaunchDarkly:

• Traces: APM traces from your instrumented services, visible in Traces
• Metrics: Infrastructure and application metrics
• Logs: Application logs collected by the agent log collection feature, visible in Logs

Verify that data is being received

After you configure the Datadog Agent, telemetry begins flowing to LaunchDarkly.

To verify that traces are being received:

1. In the LaunchDarkly UI, expand Observe in the left navigation.
2. Click Traces.
3. Look for traces from your Datadog-instrumented services.

To verify that logs are being received:

1. In the LaunchDarkly UI, expand Observe in the left navigation.
2. Click Logs.
3. Look for logs from your services.

It may take a few minutes for data to appear after you first configure the agent.

Filtering ingested data

You can configure ingestion filters to control which logs are stored in LaunchDarkly. This is useful for reducing noise or staying within your observability quotas.

To learn more, read Filters.