Set up the host metrics receiver on each node from which metrics need to be collected. To collect host metrics from every node in your cluster, deploy the host metrics receiver as a DaemonSet collector. Add the following in the Collector configuration:
Note: To correlate trace and host metrics, configure Universal Service Monitoring attributes for each service, and set the host.name resource attribute to the corresponding underlying host for both service and collector instances.
The following table shows which Datadog host metric names are associated with corresponding OpenTelemetry host metric names, and, if applicable, what math is applied to the OTel host metric to transform it to Datadog units during the mapping.
OTEL
DATADOG
DESCRIPTION
FILTER
TRANSFORM
system.cpu.load_average.15m
system.load.15
Average CPU Load over 15 minutes.
system.cpu.load_average.1m
system.load.1
Average CPU Load over 1 minute.
system.cpu.load_average.5m
system.load.5
Average CPU Load over 5 minutes.
system.cpu.utilization
system.cpu.idle
Difference in system.cpu.time since the last measurement per logical CPU, divided by the elapsed time (value in interval [0,1]).
state: idle
× 100
system.cpu.utilization
system.cpu.iowait
Difference in system.cpu.time since the last measurement per logical CPU, divided by the elapsed time (value in interval [0,1]).
state: wait
× 100
system.cpu.utilization
system.cpu.stolen
Difference in system.cpu.time since the last measurement per logical CPU, divided by the elapsed time (value in interval [0,1]).
state: steal
× 100
system.cpu.utilization
system.cpu.system
Difference in system.cpu.time since the last measurement per logical CPU, divided by the elapsed time (value in interval [0,1]).
state: system
× 100
system.cpu.utilization
system.cpu.user
Difference in system.cpu.time since the last measurement per logical CPU, divided by the elapsed time (value in interval [0,1]).