Grafana Cloud



EXPERIMENTAL: This is an experimental component. Experimental components are subject to frequent breaking changes, and may be removed with no equivalent replacement.

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.


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


otelcol.receiver.datadog supports the following arguments:

endpointstringhost:port to listen for traffic on."localhost:8126"no
max_request_body_sizestringMaximum request body size the server will allow.20MiBno
include_metadatabooleanPropagate incoming connection metadata to downstream consumers.falseno
read_timeoutdurationRead timeout for requests of the HTTP server."60s"no

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 to listen on all network interfaces.


The following blocks are supported inside the definition of otelcol.receiver.datadog:

tlstlsConfigures TLS for the HTTP
corscorsConfigures CORS for the HTTP
debug_metricsdebug_metricsConfigures the metrics that this component generates to monitor its
outputoutputConfigures where to send received traces.yes

tls block

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.

The following arguments are supported:

ca_filestringPath to the CA
ca_pemstringCA PEM-encoded text to validate the server
cert_filestringPath to the TLS
cert_pemstringCertificate PEM-encoded text for client
include_system_ca_certs_poolbooleanWhether to load the system certificate authorities pool alongside the certificate authority.falseno
key_filestringPath to the TLS certificate
key_pemsecretKey PEM-encoded text for client
max_versionstringMaximum acceptable TLS version for connections."TLS 1.3"no
min_versionstringMinimum acceptable TLS version for connections."TLS 1.2"no
cipher_suiteslist(string)A list of TLS cipher suites that the TLS transport can use.[]no
reload_intervaldurationThe duration after which the certificate is reloaded."0s"no
client_ca_filestringPath to the TLS cert to use by the server to verify a client

If reload_interval is set to "0s", the certificate never reloaded.

The following pairs of arguments are mutually exclusive and can’t both be set simultaneously:

  • ca_pem and ca_file
  • cert_pem and cert_file
  • key_pem and key_file

If cipher_suites is left blank, a safe default list is used. Refer to the Go Cipher Suites documentation for a list of supported cipher suites.

client_ca_file sets the ClientCA and ClientAuth to RequireAndVerifyClientCert in the TLSConfig. Refer to the Go TLS documentation for more information.

cors block

The cors block configures CORS settings for an HTTP server.

The following arguments are supported:

allowed_originslist(string)Allowed values for the Origin header.[]no
allowed_headerslist(string)Accepted headers from CORS requests.["X-Requested-With"]no
max_agenumberConfigures the Access-Control-Max-Age response header.0no

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.

debug_metrics block

The debug_metrics block configures the metrics that this component generates to monitor its state.

The following arguments are supported:

disable_high_cardinality_metricsbooleanWhether to disable certain high cardinality metrics.trueno
levelstringControls the level of detail for metrics emitted by the wrapped collector."detailed"no

disable_high_cardinality_metrics is the Grafana Alloy equivalent to the telemetry.disableHighCardinalityMetrics feature gate in the OpenTelemetry Collector. It removes attributes that could cause high cardinality metrics. For example, attributes with IP addresses and port numbers in metrics about HTTP and gRPC connections are removed.


If configured, disable_high_cardinality_metrics only applies to otelcol.exporter.* and otelcol.receiver.* components.

level is the Alloy equivalent to the telemetry.metrics.level feature gate in the OpenTelemetry Collector. Possible values are "none", "basic", "normal" and "detailed".

output block

The output block configures a set of components to forward resulting telemetry data to.

The following arguments are supported:

logslist(otelcol.Consumer)List of consumers to send logs to.[]no
metricslist(otelcol.Consumer)List of consumers to send metrics to.[]no
traceslist(otelcol.Consumer)List of consumers to send traces to.[]no

You must specify the output block, but all its arguments are optional. By default, telemetry data is dropped. Configure the metrics, logs, and traces arguments accordingly to send telemetry data to other components.

Exported fields

otelcol.receiver.datadog does not export any fields.

Component health

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

Debug information

otelcol.receiver.datadog does not expose any component-specific debug information.


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

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.otlp.default.input]
    traces  = [otelcol.exporter.otlp.default.input]

otelcol.exporter.otlp "default" {
  client {
    endpoint = env("OTLP_ENDPOINT")

Compatible components

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


Connecting some components may not be sensible or components may require further configuration to make the connection work correctly. Refer to the linked documentation for more details.