OpenTelemetry is a vendor-agnostic standard for telemetry data. Datadog supports ingesting OpenTelemetry data through the OpenTelemetry Collector and the Datadog Agent. This tile documents how to export data to Datadog through the OpenTelemetry Collector with Datadog Exporter OpenTelemetry collector Datadog exporter. Also see OTLP ingest in Datadog Agent for further information on ingesting OTLP traces with Datadog Agent.
The OpenTelemetry Collector is a vendor-agnostic agent process that, through the Datadog exporter, exports telemetry data directly to Datadog servers (no Agent installation required). It reports metrics and traces from instrumented applications as well as general system metrics.
Host metrics are shown in the OTel Host Metrics default dashboard, but you can send arbitrary metrics to Datadog using the OpenTelemetry Collector. Metrics under system.* and process.*, such as those generated by the host metrics receiver, are renamed to otel.system.* and otel.process.* to prevent collisions with metrics from the Datadog Agent. Additionally, OpenTelemetry Collector metrics are shown in the OTel Collector Metrics default dashboard.
Follow the OpenTelemetry Collector documentation to install the opentelemetry-collector-contrib distribution, or any other distribution that includes the Datadog Exporter.
The Datadog Agent is not needed to export telemetry data to Datadog in this setup. See OTLP Ingest in Datadog Agent if you want to use the Datadog Agent instead.
To export telemetry data to Datadog from the OpenTelemetry Collector, add the Datadog exporter to your metrics and traces pipelines. The only required setting is your API key.
A minimal configuration file to retrieve system metrics is as follows.
receivers:
hostmetrics:
scrapers:
load:
cpu:
disk:
filesystem:
memory:
network:
paging:
process:
processors:
batch:
timeout: 10s
exporters:
datadog:
api:
key: "<Your API key goes here>"
service:
pipelines:
metrics:
receivers: [hostmetrics]
processors: [batch]
exporters: [datadog]For further information on the Datadog exporter settings and how to configure the pipeline, see Datadog exporter for OpenTelemetry Collector.
See the Metrics section for metrics types and metadata.csv for a list of metrics provided by this check. If you're using the hostmetrics receiver as in the sample configuration above. You can send arbitrary metrics with other OpenTelemetry Collector components.
Different groups of metrics can be enabled and customized by following the hostmetrics receiver instructions. CPU and disk metrics are not available on macOS.
Check the OpenTelemetry Collector logs to see the Datadog exporter being enabled and started correctly. For example, with the configuration above you should find logging messages similar to the following.
Exporter is enabled. {"component_kind": "exporter", "exporter": "datadog"}
Exporter is starting... {"component_kind": "exporter", "component_type": "datadog", "component_name": "datadog"}
Exporter started. {"component_kind": "exporter", "component_type": "datadog", "component_name": "datadog"}
Everything is ready. Begin running and processing data.
See metadata.csv for a list of metrics provided by this integration.
The OpenTelemetry Collector does not include any service checks.
The OpenTelemetry Collector does not include any events.
Need help? Contact Datadog support.