Skip to main content
This feature is experimental. Behavior and configuration options may change in future releases.

Description

The Datadog Agent V2 source receives logs, metrics, and traces directly from a Datadog Agent. Unlike the original Datadog Agent source, this version provides separate output ports for each telemetry type, so you can route logs, metrics, and traces to different destinations in your pipeline.

Outputs

  • Logs: Log events from the Datadog Agent
  • Metrics: Metric events from the Datadog Agent, including sketches (distribution metrics)
  • Traces: Trace events from the Datadog Agent
Connect each output to your desired processor or destination. You can leave outputs unconnected if you don’t need that telemetry type.

Configuration

Add a source and choose Datadog Agent V2, optionally enter a Title and Description, then click Save. Under Access Key Management:
  1. Click Create new key.
  2. Enter a title.
  3. Set the type to User Defined and enter your Datadog API key.
  4. Click Create.

Datadog Agent Configuration

Configure the Datadog Agent to send data to your Mezmo pipeline URLs. The Datadog Agent V2 source uses Observability Pipelines Worker configuration options.

Requirements

The running agent version must be [ >= 6.45.0 or >= 7.45.0 ]

Configuration Options

Running the Datadog Agent via Docker

Example pipeline publishing logs, metrics, and traces to Mezmo:
Note that DD_OBSERVABILITY_PIPELINES_WORKER_LOGS_URL does not include https as the protocol is already assumed by the agent.

Running the local Datadog Agent

Configure the agent using the datadog.yaml configuration file. See the Datadog Agent configuration files documentation for file locations. Example pipeline publishing logs, metrics, and traces to Mezmo:

Example Pipeline

A common setup routes logs to Mezmo for analysis while forwarding metrics and traces back to Datadog:
  1. Add a Datadog Agent V2 source.
  2. Connect the Logs output to a Mezmo Log Analysis destination.
  3. Connect the Metrics output to a Datadog Metrics destination.
  4. Connect the Traces output to a Datadog Traces destination.