Documentation Grafana Cloud Instrument and send data Grafana Alloy Reference Components otelcol otelcol.receiver.datadog

otelcol.receiver.datadog

otelcol.receiver.datadog accepts Datadog metrics and traces over the network and forwards it to other otelcol.* components.

You can specify multiple otelcol.receiver.datadog components by giving them different labels.

Usage

Alloy Copy

otelcol.receiver.datadog "<LABEL>" {
  output {
    metrics = [...]
    traces  = [...]
  }
}

Arguments

You can use the following arguments with otelcol.receiver.datadog:

By default, otelcol.receiver.datadog listens for HTTP connections on localhost. To expose the HTTP server to other machines on your network, configure endpoint with the IP address to listen on, or 0.0.0.0:8126 to listen on all network interfaces.

Blocks

You can use the following blocks with otelcol.receiver.datadog:

output

cors

The cors block configures CORS settings for an HTTP server.

The following arguments are supported:

The allowed_headers argument specifies which headers are acceptable from a CORS request. The following headers are always implicitly allowed:

• Accept
• Accept-Language
• Content-Type
• Content-Language

If allowed_headers includes "*", all headers are permitted.

intake

The intake block configures how the /intake endpoint behaves. The Datadog Agent uses this endpoint to submit host tags and other metadata.

The following arguments are supported:

Set behavior to "proxy" to forward /intake requests to Datadog’s API. Proxying requires a nested proxy { api { ... } } block with a Datadog API key. When set to "disable", the endpoint returns an error for any incoming request.

proxy

The proxy block configures how the /intake proxy operates. It’s only used when behavior is set to "proxy". If behavior isn’t "proxy", this block is ignored.

This block has no arguments and is configured with the nested api block.

api

The api block configures the Datadog API connection used by the intake proxy.

The following arguments are supported:

debug_metrics

tls

The tls block configures TLS settings used for a server. If the tls block isn’t provided, TLS won’t be used for connections to the server.

tpm

The tpm block configures retrieving the TLS key_file from a trusted device.

The following arguments are supported:

Expand table

Name	Type	Description	Default	Required
auth	string	The authorization value used to authenticate the TPM device.	""	no
enabled	bool	Load the tls.key_file from TPM.	false	no
owner_auth	string	The owner authorization value used to authenticate the TPM device.	""	no
path	string	Path to the TPM device or Unix domain socket.	""	no

The trusted platform module (TPM) configuration can be used for loading TLS key from TPM. Currently only TSS2 format is supported.

The path attribute is not supported on Windows.

In the following example, the private key my-tss2-key.key in TSS2 format is loaded from the TPM device /dev/tmprm0:

Alloy Copy

otelcol.example.component "<LABEL>" {
    ...
    tls {
        ...
        key_file = "my-tss2-key.key"
        tpm {
            enabled = true
            path = "/dev/tpmrm0"
        }
    }
}

Exported fields

otelcol.receiver.datadog doesn’t export any fields.

Component health

otelcol.receiver.datadog is only reported as unhealthy if given an invalid configuration.

Debug information

otelcol.receiver.datadog doesn’t expose any component-specific debug information.

Example

This example forwards received telemetry through a batch processor before finally sending it to an OTLP-capable endpoint:

Alloy Copy

otelcol.receiver.datadog "default" {
  output {
    metrics = [otelcol.processor.batch.default.input]
    traces  = [otelcol.processor.batch.default.input]
  }
}

otelcol.processor.batch "default" {
  output {
    metrics = [otelcol.exporter.otlphttp.default.input]
    traces  = [otelcol.exporter.otlphttp.default.input]
  }
}

otelcol.exporter.otlphttp "default" {
  client {
    endpoint = sys.env("OTLP_ENDPOINT")
  }
}

Proxy /intake requests to Datadog

You can configure the receiver to forward /intake requests (host tags and metadata) to Datadog’s API while processing metrics and traces locally:

Alloy Copy

otelcol.receiver.datadog "default" {
  intake {
    behavior = "proxy"
    proxy {
      api {
        key  = sys.env("DD_API_KEY")
        site = "datadoghq.eu"
      }
    }
  }

  output {
    metrics = [otelcol.processor.batch.default.input]
    traces  = [otelcol.processor.batch.default.input]
  }
}

Enable authentication

You can create a otelcol.receiver.datadog component that requires authentication for requests. This is useful for limiting who can push data to the server.

Alloy Copy

otelcol.receiver.datadog "default" {
  output {
    metrics = [otelcol.processor.batch.default.input]
    traces  = [otelcol.processor.batch.default.input]
  }
  auth = otelcol.auth.basic.creds.handler
}

otelcol.auth.basic "creds" {
    username = sys.env("<USERNAME>")
    password = sys.env("<PASSWORD>")
}

Compatible components

otelcol.receiver.datadog can accept arguments from the following components:

• Components that export OpenTelemetry otelcol.Consumer