OpenTelemetry Semantic Conventions and Datadog Conventions

Docs > OpenTelemetry dans Datadog > Schema and Semantics > OpenTelemetry Semantic Conventions and Datadog Conventions

Cette page n'est pas encore disponible en français, sa traduction est en cours.
Si vous avez des questions ou des retours sur notre projet de traduction actuel, n'hésitez pas à nous contacter.

OpenTelemetry makes use of a number of semantic conventions that specify names for different types of data. This page lists mappings for OpenTelemetry semantic conventions to Datadog’s semantic conventions.

Unified service tagging

OpenTelemetry convention	Datadog convention
`deployment.environment` ¹	`env`
`deployment.environment.name` ²	`env`
`service.name`	`service`
`service.version`	`version`

For more information, see Unified Service Tagging.

1: deployment.environment has been deprecated in favor of deployment.environment.name in OpenTelemetry semantic conventions v1.27.0
2: deployment.environment.name is supported in Datadog Agent 7.58.0+ and Datadog Exporter v0.110.0+

Containers

OpenTelemetry convention	Datadog convention
`container.id`	`container_id`
`container.name`	`container_name`
`container.image.name`	`image_name`
`container.image.tag`	`image_tag`

Additional cloud provider-specific attributes are also mapped.

Cloud

OpenTelemetry convention	Datadog convention
`cloud.provider`	`cloud_provider`
`cloud.region`	`region`
`cloud.availability_zone`	`zone`

ECS

OpenTelemetry convention	Datadog convention
`aws.ecs.task.family`	`task_family`
`aws.ecs.task.arn`	`task_arn`
`aws.ecs.cluster.arn`	`ecs_cluster_name`
`aws.ecs.task.revision`	`task_version`
`aws.ecs.container.arn`	`ecs_container_name`

Kubernetes

OpenTelemetry convention	Datadog convention
`k8s.container.name`	`kube_container_name`
`k8s.cluster.name`	`kube_cluster_name`
`k8s.deployment.name`	`kube_deployment`
`k8s.replicaset.name`	`kube_replica_set`
`k8s.statefulset.name`	`kube_stateful_set`
`k8s.daemonset.name`	`kube_daemon_set`
`k8s.job.name`	`kube_job`
`k8s.cronjob.name`	`kube_cronjob`
`k8s.namespace.name`	`kube_namespace`
`k8s.pod.name`	`pod_name`

Kubernetes labels

Kubernetes convention	Datadog convention
`app.kubernetes.io/name`	`kube_app_name`
`app.kubernetes.io/instance`	`kube_app_instance`
`app.kubernetes.io/version`	`kube_app_version`
`app.kuberenetes.io/component`	`kube_app_component`
`app.kubernetes.io/part-of`	`kube_app_part_of`
`app.kubernetes.io/managed-by`	`kube_app_managed_by`

HTTP

OpenTelemetry convention	Datadog convention
`client.address`	`http.client_ip`
`http.response.body.size`	`http.response.content_length`
`http.response.header.<header-name>`	`http.response.headers.<header-name>`
`http.response.status_code`	`http.status_code`
`http.request.body.size`	`http.request.content_length`
`http.request.header.referrer`	`http.referrer`
`http.request.header.<header-name>`	`http.request.headers.<header-name>`
`http.request.method`	`http.method`
`http.route`	`http.route`
`network.protocol.version`	`http.version`
`server.address`	`http.server_name`
`url.full`	`http.url`
`user_agent.original`	`http.useragent`

Metrics attribute mapping

For metrics, by default, Datadog only maps the OpenTelemetry resource attributes listed in the previous sections to Datadog metric tags. To map all resource attributes to tags, enable the metrics::resource_attributes_as_tags setting:

exporters:
  datadog:
    # Other configuration goes here...
    metrics:
      # Add all resource attributes as tags for metrics
      resource_attributes_as_tags: true

otlp_config:
  # Other configuration goes here...
  metrics:
    # Add all resource attributes as tags for metrics
    resource_attributes_as_tags: true