Overview

The Datadog Extension allows you to view OpenTelemetry Collector configuration and build information directly within Datadog on the Infrastructure List and Resource Catalog. When used with the Datadog Exporter, this extension gives you visibility into your Collector fleet without leaving the Datadog UI.

Key features

• Collector Configuration Visibility: View the complete configuration for any Collector in your infrastructure.
• Build Information: See Collector version, build details, and component information.
• Fleet Management: Monitor and manage your OpenTelemetry Collector fleet from the Datadog UI.
• Local Inspection Endpoint: Use an HTTP endpoint for local debugging and configuration verification.

Setup

1. Add the Datadog Extension to your Collector configuration

Configure the Datadog Extension in your OpenTelemetry Collector configuration file:

extensions:
  datadog:
    api:
      key: ${env:DD_API_KEY}
      site: 
    # hostname: "my-collector-host"  # Optional: must match Datadog Exporter hostname if set

service:
  extensions: [datadog]

2. Configure the Datadog Exporter

This feature requires the Datadog Exporter to be configured and enabled in an active pipeline (traces or metrics). The extension uses the exporter’s telemetry to associate the Collector’s configuration with a specific host in Datadog.

exporters:
  datadog/exporter:
    api:
      key: ${env:DD_API_KEY}
      site: 
    # hostname: "my-collector-host"  # Optional: must match Datadog Extension hostname if set

3. Enable the extension in your service configuration

Add the Datadog Extension to your service extensions:

service:
  extensions: [datadog]
  pipelines:
    traces:
      receivers: [otlp]
      processors: [batch]
      exporters: [datadog/exporter]
    metrics:
      receivers: [otlp]
      processors: [batch]
      exporters: [datadog/exporter]

Configuration options

Complete configuration example

extensions:
  datadog:
    api:
      key: ${env:DD_API_KEY}
      site: 
    hostname: "my-collector-host"
    http:
      endpoint: "localhost:9875"
      path: "/metadata"
    proxy_url: "http://proxy.example.com:8080"
    timeout: 30s
    tls:
      insecure_skip_verify: false

exporters:
  datadog/exporter:
    api:
      key: ${env:DD_API_KEY}
      site: 
    hostname: "my-collector-host"

service:
  extensions: [datadog]
  pipelines:
    traces:
      receivers: [otlp]
      processors: [batch]
      exporters: [datadog/exporter]
    metrics:
      receivers: [otlp]
      processors: [batch]
      exporters: [datadog/exporter]

Viewing Collector configuration

Once configured, you can view your OpenTelemetry Collector configuration and build information in two locations:

Infrastructure List (Host List)

1. Navigate to Infrastructure > Hosts in your Datadog account.
2. Click on any host running the OpenTelemetry Collector (Note: Filter by field:apps:otel to only show Collector instances).
3. In the host details panel, select the OTel Collector tab to see build info and full Collector configuration.

Resource Catalog

1. Navigate to Infrastructure > Resource Catalog in your Datadog account
2. Filter for hosts or search for your Collector instances.
3. Click on any host running the OpenTelemetry Collector.
4. Scroll down to Collector to see build info and full Collector configuration.

Local HTTP server

The Datadog Extension includes a local HTTP server for debugging and inspection:

# Access collector metadata locally
curl http://localhost:9875/metadata

This endpoint provides:

• Collector configuration (scrubbed of sensitive information)
• Build information and version details
• Active component list
• Extension status

Troubleshooting

Configuration not appearing in Datadog

1. Check hostname matching: Ensure hostnames match between the Datadog Extension and Datadog Exporter.
2. Verify API key: Confirm the API key is valid and has appropriate permissions.
3. Check Collector logs: Look for extension initialization and data submission logs.
4. Confirm extension is enabled: Verify the extension is listed in the service configuration.

HTTP server issues

1. Port conflicts: Ensure port 9875 is available or configure a different port.
2. Network access: Verify the HTTP server is accessible from your debug location.
3. Check logs: Review extension logs for HTTP server startup issues.

Further reading

Más enlaces, artículos y documentación útiles:

Setting Up the OpenTelemetry CollectorDOCUMENTATION Infrastructure ListDOCUMENTATION Resource CatalogDOCUMENTATION