From 60f5aae34a014fdf3d6ef42fc38cc428fc81b61d Mon Sep 17 00:00:00 2001 From: Andrey Zheltovskiy Date: Fri, 19 Dec 2025 15:54:18 +0100 Subject: [PATCH 01/14] add CCRID eng documentation draft --- content/en/opentelemetry/mapping/_index.md | 1 + .../en/opentelemetry/mapping/ccrid_mapping.md | 63 +++++++++++++++++++ 2 files changed, 64 insertions(+) create mode 100644 content/en/opentelemetry/mapping/ccrid_mapping.md diff --git a/content/en/opentelemetry/mapping/_index.md b/content/en/opentelemetry/mapping/_index.md index d0a45f96806..9679e5daa0f 100644 --- a/content/en/opentelemetry/mapping/_index.md +++ b/content/en/opentelemetry/mapping/_index.md @@ -18,6 +18,7 @@ The following documentation describes how OpenTelemetry and Datadog conventions {{< nextlink href="/opentelemetry/mapping/host_metadata/" >}}Infrastructure Host Mapping{{< /nextlink >}} {{< nextlink href="/opentelemetry/mapping/hostname/" >}}Hostname Mapping{{< /nextlink >}} {{< nextlink href="/opentelemetry/mapping/service_entry_spans/" >}}Service-entry Spans Mapping{{< /nextlink >}} + {{< nextlink href="/opentelemetry/mapping/ccrid_mapping/" >}}Canonical Cloud Resources ID Mapping{{< /nextlink >}} {{< /whatsnext >}} ## Further reading diff --git a/content/en/opentelemetry/mapping/ccrid_mapping.md b/content/en/opentelemetry/mapping/ccrid_mapping.md new file mode 100644 index 00000000000..47e5d709db3 --- /dev/null +++ b/content/en/opentelemetry/mapping/ccrid_mapping.md @@ -0,0 +1,63 @@ +--- +title: Mapping Canonical Cloud Resources ID to OpenTelemetry resource attributes +aliases: +further_reading: +- link: "/opentelemetry/" + tag: "Documentation" + text: "OpenTelemetry Support in Datadog" +--- + +
+This feature is in Preview. If you have any feedback, contact Datadog support. +
+ +## Overview +Canonical Cloud Resource IDs (CCRIDs) are cloud provider-assigned resource IDs that uniquely identify a cloud resource. CCRIDs, once added across different observability types, can be used to easily and consistently link different types of data for a given cloud resource. CCRIDs can be added in the same format across all cloud resource types. Widespread addition and adoption of CCRIDs will unlock a variety of use cases across customers and internal teams. + +Enable to seamlessly jump between resources and their associated metrics, traces and logs for all resource types, eliminating context switching and giving users an end-to-end view of their resources within the same workflow. + +The Datadog exporter supports sending CCRID information to Datadog. +This is supported under any [deployment pattern][1] including gateway deploys. + +
Only metadata sent through the Datadog Exporter will populate the Infrastructure Host List. Metadata sent using the direct OTLP ingest endpoint does not support this feature.
+ +## Requirements +- Datadog Distribution of OpenTelemetry Collector v**TODO** or greater + +## Opting in to the feature +To use this feature, set the `datadog.ccrid` resource attribute to value of CCRID in all OTLP payloads. + +See below for the list of identifier formats per-cloud: +| Cloud | Identifier Type | Example | +|---------|--------------------|----------------------------------------------------------------------------------------------------------------------------------------------| +| AWS | ARN | `arn:aws:sns:us-east-1:123456789012:example-sns-topic-name` | +| Azure | Resource ID | `/subscriptions/0b62a232-b8db-4380-9da6-640f7272ed6d/resourcegroups/lfotriggertest/providers/microsoft.web/sites/resources-task-19cb7afdcbbc`| +| GCP | CAI Resource Name | `//file.googleapis.com/projects/datadog-sandbox/locations/us-central1/backups/kevin-test-backup` | +| OCI | OCID | `ocid1.bucket.oc1.eu-frankfurt-1.aaaaaaaa5b5d7phlob22x4xin2lopq33ugriqiglek2ecxecrjx2awceb7eq` | + + +For example, to set AWS CCRID for all resources in metrics, traces, and logs, use the [transform processor][2] with the following configuration: +```yaml +processors: + transform: + metric_statements: + - context: resource + statements: + - set(attributes["datadog.ccrid"], "arn:aws:sns:us-east-1:123456789012:example-sns-topic-name") + trace_statements: + - context: resource + statements: + - set(attributes["datadog.ccrid"], "arn:aws:sns:us-east-1:123456789012:example-sns-topic-name") + log_statements: + - context: resource + statements: + - set(attributes["datadog.ccrid"], "arn:aws:sns:us-east-1:123456789012:example-sns-topic-name") +``` + +## Further reading + +{{< partial name="whats-next/whats-next.html" >}} + + +[1]: https://opentelemetry.io/docs/collector/deployment/ +[2]: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/transformprocessor#transform-processor From ab3057726e7a8eb718dd65170b2b26ca65728b9c Mon Sep 17 00:00:00 2001 From: Andrey Zheltovskiy Date: Fri, 19 Dec 2025 16:52:20 +0100 Subject: [PATCH 02/14] add CCRID eng documentation draft v2 --- content/en/opentelemetry/mapping/_index.md | 1 - .../en/opentelemetry/mapping/ccrid_mapping.md | 63 ------------------- .../en/opentelemetry/mapping/host_metadata.md | 37 +++++++++++ 3 files changed, 37 insertions(+), 64 deletions(-) delete mode 100644 content/en/opentelemetry/mapping/ccrid_mapping.md diff --git a/content/en/opentelemetry/mapping/_index.md b/content/en/opentelemetry/mapping/_index.md index 9679e5daa0f..d0a45f96806 100644 --- a/content/en/opentelemetry/mapping/_index.md +++ b/content/en/opentelemetry/mapping/_index.md @@ -18,7 +18,6 @@ The following documentation describes how OpenTelemetry and Datadog conventions {{< nextlink href="/opentelemetry/mapping/host_metadata/" >}}Infrastructure Host Mapping{{< /nextlink >}} {{< nextlink href="/opentelemetry/mapping/hostname/" >}}Hostname Mapping{{< /nextlink >}} {{< nextlink href="/opentelemetry/mapping/service_entry_spans/" >}}Service-entry Spans Mapping{{< /nextlink >}} - {{< nextlink href="/opentelemetry/mapping/ccrid_mapping/" >}}Canonical Cloud Resources ID Mapping{{< /nextlink >}} {{< /whatsnext >}} ## Further reading diff --git a/content/en/opentelemetry/mapping/ccrid_mapping.md b/content/en/opentelemetry/mapping/ccrid_mapping.md deleted file mode 100644 index 47e5d709db3..00000000000 --- a/content/en/opentelemetry/mapping/ccrid_mapping.md +++ /dev/null @@ -1,63 +0,0 @@ ---- -title: Mapping Canonical Cloud Resources ID to OpenTelemetry resource attributes -aliases: -further_reading: -- link: "/opentelemetry/" - tag: "Documentation" - text: "OpenTelemetry Support in Datadog" ---- - -
-This feature is in Preview. If you have any feedback, contact Datadog support. -
- -## Overview -Canonical Cloud Resource IDs (CCRIDs) are cloud provider-assigned resource IDs that uniquely identify a cloud resource. CCRIDs, once added across different observability types, can be used to easily and consistently link different types of data for a given cloud resource. CCRIDs can be added in the same format across all cloud resource types. Widespread addition and adoption of CCRIDs will unlock a variety of use cases across customers and internal teams. - -Enable to seamlessly jump between resources and their associated metrics, traces and logs for all resource types, eliminating context switching and giving users an end-to-end view of their resources within the same workflow. - -The Datadog exporter supports sending CCRID information to Datadog. -This is supported under any [deployment pattern][1] including gateway deploys. - -
Only metadata sent through the Datadog Exporter will populate the Infrastructure Host List. Metadata sent using the direct OTLP ingest endpoint does not support this feature.
- -## Requirements -- Datadog Distribution of OpenTelemetry Collector v**TODO** or greater - -## Opting in to the feature -To use this feature, set the `datadog.ccrid` resource attribute to value of CCRID in all OTLP payloads. - -See below for the list of identifier formats per-cloud: -| Cloud | Identifier Type | Example | -|---------|--------------------|----------------------------------------------------------------------------------------------------------------------------------------------| -| AWS | ARN | `arn:aws:sns:us-east-1:123456789012:example-sns-topic-name` | -| Azure | Resource ID | `/subscriptions/0b62a232-b8db-4380-9da6-640f7272ed6d/resourcegroups/lfotriggertest/providers/microsoft.web/sites/resources-task-19cb7afdcbbc`| -| GCP | CAI Resource Name | `//file.googleapis.com/projects/datadog-sandbox/locations/us-central1/backups/kevin-test-backup` | -| OCI | OCID | `ocid1.bucket.oc1.eu-frankfurt-1.aaaaaaaa5b5d7phlob22x4xin2lopq33ugriqiglek2ecxecrjx2awceb7eq` | - - -For example, to set AWS CCRID for all resources in metrics, traces, and logs, use the [transform processor][2] with the following configuration: -```yaml -processors: - transform: - metric_statements: - - context: resource - statements: - - set(attributes["datadog.ccrid"], "arn:aws:sns:us-east-1:123456789012:example-sns-topic-name") - trace_statements: - - context: resource - statements: - - set(attributes["datadog.ccrid"], "arn:aws:sns:us-east-1:123456789012:example-sns-topic-name") - log_statements: - - context: resource - statements: - - set(attributes["datadog.ccrid"], "arn:aws:sns:us-east-1:123456789012:example-sns-topic-name") -``` - -## Further reading - -{{< partial name="whats-next/whats-next.html" >}} - - -[1]: https://opentelemetry.io/docs/collector/deployment/ -[2]: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/transformprocessor#transform-processor diff --git a/content/en/opentelemetry/mapping/host_metadata.md b/content/en/opentelemetry/mapping/host_metadata.md index 6b8cfed5eeb..6b463c74542 100644 --- a/content/en/opentelemetry/mapping/host_metadata.md +++ b/content/en/opentelemetry/mapping/host_metadata.md @@ -90,6 +90,43 @@ To collect these conventions with the OpenTelemetry Collector, set up the [recom **Note:** You need to add these processors and receivers in the Collector running on the host that you want to monitor. A gateway host does not collect this information from remote hosts. + +## Canonical Cloud Resource IDs + +Canonical Cloud Resource IDs (CCRIDs) are cloud provider-assigned resource IDs that uniquely identify a cloud resource. CCRIDs, once added across different observability types, can be used to easily and consistently link different types of data for a given cloud resource. CCRIDs can be added in the same format across all cloud resource types. Widespread addition and adoption of CCRIDs will unlock a variety of use cases across customers and internal teams. + +Enable to seamlessly jump between resources and their associated metrics, traces and logs for all resource types, eliminating context switching and giving users an end-to-end view of their resources within the same workflow. + +To use this feature, set the `datadog.ccrid` resource attribute to value of CCRID in all OTLP payloads. + +See below for the list of identifier formats per-cloud: +| Cloud | Identifier Type | Example | +|---------|--------------------|----------------------------------------------------------------------------------------------------------------------------------------------| +| AWS | ARN | `arn:aws:sns:us-east-1:123456789012:example-sns-topic-name` | +| Azure | Resource ID | `/subscriptions/0b62a232-b8db-4380-9da6-640f7272ed6d/resourcegroups/lfotriggertest/providers/microsoft.web/sites/resources-task-19cb7afdcbbc`| +| GCP | CAI Resource Name | `//file.googleapis.com/projects/datadog-sandbox/locations/us-central1/backups/kevin-test-backup` | +| OCI | OCID | `ocid1.bucket.oc1.eu-frankfurt-1.aaaaaaaa5b5d7phlob22x4xin2lopq33ugriqiglek2ecxecrjx2awceb7eq` | + + +For example, to set AWS CCRID for all resources in metrics, traces, and logs, use the [transform processor][2] with the following configuration: +```yaml +processors: + transform: + metric_statements: + - context: resource + statements: + - set(attributes["datadog.ccrid"], "arn:aws:sns:us-east-1:123456789012:example-sns-topic-name") + trace_statements: + - context: resource + statements: + - set(attributes["datadog.ccrid"], "arn:aws:sns:us-east-1:123456789012:example-sns-topic-name") + log_statements: + - context: resource + statements: + - set(attributes["datadog.ccrid"], "arn:aws:sns:us-east-1:123456789012:example-sns-topic-name") +``` + + ## Further reading {{< partial name="whats-next/whats-next.html" >}} From 5c453944bee28fa7ce4ad8df631d2e2c75eec1ce Mon Sep 17 00:00:00 2001 From: Andrey Zheltovskiy Date: Fri, 19 Dec 2025 17:04:34 +0100 Subject: [PATCH 03/14] fixes according vale --- content/en/opentelemetry/mapping/host_metadata.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/en/opentelemetry/mapping/host_metadata.md b/content/en/opentelemetry/mapping/host_metadata.md index 6b463c74542..cd663be9af6 100644 --- a/content/en/opentelemetry/mapping/host_metadata.md +++ b/content/en/opentelemetry/mapping/host_metadata.md @@ -91,11 +91,11 @@ To collect these conventions with the OpenTelemetry Collector, set up the [recom **Note:** You need to add these processors and receivers in the Collector running on the host that you want to monitor. A gateway host does not collect this information from remote hosts. -## Canonical Cloud Resource IDs +## Canonical cloud resource IDs -Canonical Cloud Resource IDs (CCRIDs) are cloud provider-assigned resource IDs that uniquely identify a cloud resource. CCRIDs, once added across different observability types, can be used to easily and consistently link different types of data for a given cloud resource. CCRIDs can be added in the same format across all cloud resource types. Widespread addition and adoption of CCRIDs will unlock a variety of use cases across customers and internal teams. +Canonical cloud resource IDs (CCRIDs) are cloud provider-assigned resource IDs that uniquely identify a cloud resource. CCRIDs, once added across different observability types, can be used to consistently link different types of data for a given cloud resource. CCRIDs can be added in the same format across all cloud resource types. Widespread addition and adoption of CCRIDs gives access to a variety of use cases across customers and internal teams. -Enable to seamlessly jump between resources and their associated metrics, traces and logs for all resource types, eliminating context switching and giving users an end-to-end view of their resources within the same workflow. +Enable to seamlessly jump between resources and their associated metrics, traces, and logs for all resource types, eliminating context switching and giving users an end-to-end view of their resources within the same workflow. To use this feature, set the `datadog.ccrid` resource attribute to value of CCRID in all OTLP payloads. From 401a4da272dc32f3410e515de954519418917e5a Mon Sep 17 00:00:00 2001 From: Andrey Zheltovskiy Date: Mon, 22 Dec 2025 12:41:48 +0100 Subject: [PATCH 04/14] add extra CCRID information --- .../en/opentelemetry/mapping/host_metadata.md | 16 ++++++++++++---- 1 file changed, 12 insertions(+), 4 deletions(-) diff --git a/content/en/opentelemetry/mapping/host_metadata.md b/content/en/opentelemetry/mapping/host_metadata.md index cd663be9af6..399c9a059fb 100644 --- a/content/en/opentelemetry/mapping/host_metadata.md +++ b/content/en/opentelemetry/mapping/host_metadata.md @@ -102,11 +102,17 @@ To use this feature, set the `datadog.ccrid` resource attribute to value of CCRI See below for the list of identifier formats per-cloud: | Cloud | Identifier Type | Example | |---------|--------------------|----------------------------------------------------------------------------------------------------------------------------------------------| -| AWS | ARN | `arn:aws:sns:us-east-1:123456789012:example-sns-topic-name` | +| AWS | ARN | `arn:aws:sns:us-east-1:123456789012:instance/example-sns-topic-name` | | Azure | Resource ID | `/subscriptions/0b62a232-b8db-4380-9da6-640f7272ed6d/resourcegroups/lfotriggertest/providers/microsoft.web/sites/resources-task-19cb7afdcbbc`| | GCP | CAI Resource Name | `//file.googleapis.com/projects/datadog-sandbox/locations/us-central1/backups/kevin-test-backup` | | OCI | OCID | `ocid1.bucket.oc1.eu-frankfurt-1.aaaaaaaa5b5d7phlob22x4xin2lopq33ugriqiglek2ecxecrjx2awceb7eq` | +How to form a CCRID: + * AWS (EC2 Instance): `arn:aws:ec2:{region}:{accountId}:instance/{instanceId}` + * [Azure][11]: `/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/{resourceProviderNamespace}/{resourceType}/{resourceName}` + * GCP: `//compute.googleapis.com/projects/{projectID}/zones/{zoneName}/instances/{instanceName}"` + * OCI/Oracle: CCRID can be obtained by [sending a request][12] at: `http://169.254.169.254/opc/v2/instance/id` + For example, to set AWS CCRID for all resources in metrics, traces, and logs, use the [transform processor][2] with the following configuration: ```yaml @@ -115,15 +121,15 @@ processors: metric_statements: - context: resource statements: - - set(attributes["datadog.ccrid"], "arn:aws:sns:us-east-1:123456789012:example-sns-topic-name") + - set(attributes["datadog.ccrid"], "arn:aws:sns:us-east-1:123456789012:instance/example-sns-topic-name") trace_statements: - context: resource statements: - - set(attributes["datadog.ccrid"], "arn:aws:sns:us-east-1:123456789012:example-sns-topic-name") + - set(attributes["datadog.ccrid"], "arn:aws:sns:us-east-1:123456789012:instance/example-sns-topic-name") log_statements: - context: resource statements: - - set(attributes["datadog.ccrid"], "arn:aws:sns:us-east-1:123456789012:example-sns-topic-name") + - set(attributes["datadog.ccrid"], "arn:aws:sns:us-east-1:123456789012:instance/example-sns-topic-name") ``` @@ -141,3 +147,5 @@ processors: [8]: https://opentelemetry.io/docs/specs/semconv/resource/os/ [9]: https://opentelemetry.io/docs/collector/deployment/ [10]: /opentelemetry/schema_semantics/hostname/ +[11]: https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/move-resource-group-and-subscription?tabs=azure-cli +[12]: https://docs.oracle.com/en-us/iaas/Content/Compute/Tasks/gettingmetadata.htm \ No newline at end of file From 81eb08a7bfc6507e85d7545ef12f527ea6296f0e Mon Sep 17 00:00:00 2001 From: Andrey Zheltovskiy Date: Mon, 22 Dec 2025 12:57:55 +0100 Subject: [PATCH 05/14] add extra info --- content/en/opentelemetry/mapping/host_metadata.md | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-) diff --git a/content/en/opentelemetry/mapping/host_metadata.md b/content/en/opentelemetry/mapping/host_metadata.md index 399c9a059fb..a05a2570cce 100644 --- a/content/en/opentelemetry/mapping/host_metadata.md +++ b/content/en/opentelemetry/mapping/host_metadata.md @@ -108,7 +108,10 @@ See below for the list of identifier formats per-cloud: | OCI | OCID | `ocid1.bucket.oc1.eu-frankfurt-1.aaaaaaaa5b5d7phlob22x4xin2lopq33ugriqiglek2ecxecrjx2awceb7eq` | How to form a CCRID: - * AWS (EC2 Instance): `arn:aws:ec2:{region}:{accountId}:instance/{instanceId}` + * [AWS (EC2 Instance)][13]: `arn:aws:ec2:{region}:{accountId}:instance/{instanceId}`, To retrieve the `instanceId`: + ```bash + ec2metadata --instance-id + ``` * [Azure][11]: `/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/{resourceProviderNamespace}/{resourceType}/{resourceName}` * GCP: `//compute.googleapis.com/projects/{projectID}/zones/{zoneName}/instances/{instanceName}"` * OCI/Oracle: CCRID can be obtained by [sending a request][12] at: `http://169.254.169.254/opc/v2/instance/id` @@ -148,4 +151,5 @@ processors: [9]: https://opentelemetry.io/docs/collector/deployment/ [10]: /opentelemetry/schema_semantics/hostname/ [11]: https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/move-resource-group-and-subscription?tabs=azure-cli -[12]: https://docs.oracle.com/en-us/iaas/Content/Compute/Tasks/gettingmetadata.htm \ No newline at end of file +[12]: https://docs.oracle.com/en-us/iaas/Content/Compute/Tasks/gettingmetadata.htm +[13]: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/iam-policies-for-amazon-ec2.html#policy-syntax \ No newline at end of file From 4ab7459056406ca2edc9e92a716da88747e20a8e Mon Sep 17 00:00:00 2001 From: Andrey Zheltovskiy Date: Tue, 23 Dec 2025 16:58:31 +0100 Subject: [PATCH 06/14] add cloud.resource_id attr doc --- .../en/opentelemetry/mapping/host_metadata.md | 16 +++++++++++++++- 1 file changed, 15 insertions(+), 1 deletion(-) diff --git a/content/en/opentelemetry/mapping/host_metadata.md b/content/en/opentelemetry/mapping/host_metadata.md index a05a2570cce..203d77ae154 100644 --- a/content/en/opentelemetry/mapping/host_metadata.md +++ b/content/en/opentelemetry/mapping/host_metadata.md @@ -135,6 +135,18 @@ processors: - set(attributes["datadog.ccrid"], "arn:aws:sns:us-east-1:123456789012:instance/example-sns-topic-name") ``` +The OpenTelemetry semantic conventions also define the [cloud.resource_id][14] attribute , which can be mapped in the configuration using the [attributes processor][15]. + +Example: +```yaml +processors: + attributes/example: + actions: + - key: datadog.ccrid + from_attribute: cloud.resource_id + action: upsert +``` + ## Further reading @@ -152,4 +164,6 @@ processors: [10]: /opentelemetry/schema_semantics/hostname/ [11]: https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/move-resource-group-and-subscription?tabs=azure-cli [12]: https://docs.oracle.com/en-us/iaas/Content/Compute/Tasks/gettingmetadata.htm -[13]: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/iam-policies-for-amazon-ec2.html#policy-syntax \ No newline at end of file +[13]: https://docs.aws.amazon.com/AWSEC2/latest/UserGuide/iam-policies-for-amazon-ec2.html#policy-syntax +[14]: https://opentelemetry.io/docs/specs/semconv/registry/attributes/cloud/#cloud-resource-id +[15]: https://github.com/open-telemetry/opentelemetry-collector-contrib/tree/main/processor/attributesprocessor \ No newline at end of file From 89bb8533e92707bef311f257b20d5b4ba785145d Mon Sep 17 00:00:00 2001 From: Andrey Zheltovskiy Date: Fri, 2 Jan 2026 18:14:24 +0100 Subject: [PATCH 07/14] Update content/en/opentelemetry/mapping/host_metadata.md Co-authored-by: Heston Hoffman --- content/en/opentelemetry/mapping/host_metadata.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/opentelemetry/mapping/host_metadata.md b/content/en/opentelemetry/mapping/host_metadata.md index 203d77ae154..69766a8213b 100644 --- a/content/en/opentelemetry/mapping/host_metadata.md +++ b/content/en/opentelemetry/mapping/host_metadata.md @@ -93,7 +93,7 @@ To collect these conventions with the OpenTelemetry Collector, set up the [recom ## Canonical cloud resource IDs -Canonical cloud resource IDs (CCRIDs) are cloud provider-assigned resource IDs that uniquely identify a cloud resource. CCRIDs, once added across different observability types, can be used to consistently link different types of data for a given cloud resource. CCRIDs can be added in the same format across all cloud resource types. Widespread addition and adoption of CCRIDs gives access to a variety of use cases across customers and internal teams. +Canonical cloud resource IDs (CCRIDs) are cloud provider-assigned resource IDs that uniquely identify a cloud resource. After adding CCRIDs across your different observability types, you can use them to consistently link different types of data for a given cloud resource. You can add CCRIDs in the same format across all cloud resource types. Widespread addition and adoption of CCRIDs gives you access to a variety of use cases across customers and internal teams. Enable to seamlessly jump between resources and their associated metrics, traces, and logs for all resource types, eliminating context switching and giving users an end-to-end view of their resources within the same workflow. From 5e3ef838089a34c9ec928e9cd0b8e643bb169f99 Mon Sep 17 00:00:00 2001 From: Andrey Zheltovskiy Date: Fri, 2 Jan 2026 18:14:58 +0100 Subject: [PATCH 08/14] Update content/en/opentelemetry/mapping/host_metadata.md Co-authored-by: Heston Hoffman --- content/en/opentelemetry/mapping/host_metadata.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/opentelemetry/mapping/host_metadata.md b/content/en/opentelemetry/mapping/host_metadata.md index 69766a8213b..718ed26bd55 100644 --- a/content/en/opentelemetry/mapping/host_metadata.md +++ b/content/en/opentelemetry/mapping/host_metadata.md @@ -95,7 +95,7 @@ To collect these conventions with the OpenTelemetry Collector, set up the [recom Canonical cloud resource IDs (CCRIDs) are cloud provider-assigned resource IDs that uniquely identify a cloud resource. After adding CCRIDs across your different observability types, you can use them to consistently link different types of data for a given cloud resource. You can add CCRIDs in the same format across all cloud resource types. Widespread addition and adoption of CCRIDs gives you access to a variety of use cases across customers and internal teams. -Enable to seamlessly jump between resources and their associated metrics, traces, and logs for all resource types, eliminating context switching and giving users an end-to-end view of their resources within the same workflow. +Enable CCRIDs to jump between resources and their associated metrics, traces, and logs for all resource types, eliminating context switching and giving you an end-to-end view of your resources within the same workflow. To use this feature, set the `datadog.ccrid` resource attribute to value of CCRID in all OTLP payloads. From 9c637046db4927160c3fbbef16972e1540186ef0 Mon Sep 17 00:00:00 2001 From: Andrey Zheltovskiy Date: Fri, 2 Jan 2026 18:15:42 +0100 Subject: [PATCH 09/14] Update content/en/opentelemetry/mapping/host_metadata.md Co-authored-by: Heston Hoffman --- content/en/opentelemetry/mapping/host_metadata.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/content/en/opentelemetry/mapping/host_metadata.md b/content/en/opentelemetry/mapping/host_metadata.md index 718ed26bd55..1f95c75dcbb 100644 --- a/content/en/opentelemetry/mapping/host_metadata.md +++ b/content/en/opentelemetry/mapping/host_metadata.md @@ -108,7 +108,8 @@ See below for the list of identifier formats per-cloud: | OCI | OCID | `ocid1.bucket.oc1.eu-frankfurt-1.aaaaaaaa5b5d7phlob22x4xin2lopq33ugriqiglek2ecxecrjx2awceb7eq` | How to form a CCRID: - * [AWS (EC2 Instance)][13]: `arn:aws:ec2:{region}:{accountId}:instance/{instanceId}`, To retrieve the `instanceId`: + * [AWS (EC2 Instance)][13]: `arn:aws:ec2:{region}:{accountId}:instance/{instanceId}`. + Use this command to retrieve the `instanceId`: ```bash ec2metadata --instance-id ``` From 357ad39105b345aaba3a7dccc75834da345c4be6 Mon Sep 17 00:00:00 2001 From: Andrey Zheltovskiy Date: Fri, 2 Jan 2026 18:16:01 +0100 Subject: [PATCH 10/14] Update content/en/opentelemetry/mapping/host_metadata.md Co-authored-by: Heston Hoffman --- content/en/opentelemetry/mapping/host_metadata.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/opentelemetry/mapping/host_metadata.md b/content/en/opentelemetry/mapping/host_metadata.md index 1f95c75dcbb..0b07b2d26d6 100644 --- a/content/en/opentelemetry/mapping/host_metadata.md +++ b/content/en/opentelemetry/mapping/host_metadata.md @@ -97,7 +97,7 @@ Canonical cloud resource IDs (CCRIDs) are cloud provider-assigned resource IDs t Enable CCRIDs to jump between resources and their associated metrics, traces, and logs for all resource types, eliminating context switching and giving you an end-to-end view of your resources within the same workflow. -To use this feature, set the `datadog.ccrid` resource attribute to value of CCRID in all OTLP payloads. +To use this feature, set the `datadog.ccrid` resource attribute to the value of the CCRID in all OTLP payloads. See below for the list of identifier formats per-cloud: | Cloud | Identifier Type | Example | From 1a94f7a54658a616f18b12a559d63fc21bcaf46a Mon Sep 17 00:00:00 2001 From: Andrey Zheltovskiy Date: Fri, 2 Jan 2026 18:16:33 +0100 Subject: [PATCH 11/14] Update content/en/opentelemetry/mapping/host_metadata.md Co-authored-by: Heston Hoffman --- content/en/opentelemetry/mapping/host_metadata.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/opentelemetry/mapping/host_metadata.md b/content/en/opentelemetry/mapping/host_metadata.md index 0b07b2d26d6..2f31adbe778 100644 --- a/content/en/opentelemetry/mapping/host_metadata.md +++ b/content/en/opentelemetry/mapping/host_metadata.md @@ -136,7 +136,7 @@ processors: - set(attributes["datadog.ccrid"], "arn:aws:sns:us-east-1:123456789012:instance/example-sns-topic-name") ``` -The OpenTelemetry semantic conventions also define the [cloud.resource_id][14] attribute , which can be mapped in the configuration using the [attributes processor][15]. +The OpenTelemetry semantic conventions also define the [cloud.resource_id][14] attribute, which can be mapped in the configuration using the [attributes processor][15]. Example: ```yaml From 410302c883db47a560510b8e55d81c5366871dcc Mon Sep 17 00:00:00 2001 From: Andrey Zheltovskiy Date: Fri, 2 Jan 2026 18:16:50 +0100 Subject: [PATCH 12/14] Update content/en/opentelemetry/mapping/host_metadata.md Co-authored-by: Heston Hoffman --- content/en/opentelemetry/mapping/host_metadata.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/opentelemetry/mapping/host_metadata.md b/content/en/opentelemetry/mapping/host_metadata.md index 2f31adbe778..90a173432d8 100644 --- a/content/en/opentelemetry/mapping/host_metadata.md +++ b/content/en/opentelemetry/mapping/host_metadata.md @@ -118,7 +118,7 @@ How to form a CCRID: * OCI/Oracle: CCRID can be obtained by [sending a request][12] at: `http://169.254.169.254/opc/v2/instance/id` -For example, to set AWS CCRID for all resources in metrics, traces, and logs, use the [transform processor][2] with the following configuration: +For example, to set an AWS CCRID for all resources in metrics, traces, and logs, use the [transform processor][2] with the following configuration: ```yaml processors: transform: From fee5d94cacf670b471e4516e830096425e65982e Mon Sep 17 00:00:00 2001 From: Andrey Zheltovskiy Date: Fri, 2 Jan 2026 18:17:02 +0100 Subject: [PATCH 13/14] Update content/en/opentelemetry/mapping/host_metadata.md Co-authored-by: Heston Hoffman --- content/en/opentelemetry/mapping/host_metadata.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/opentelemetry/mapping/host_metadata.md b/content/en/opentelemetry/mapping/host_metadata.md index 90a173432d8..4af567861b7 100644 --- a/content/en/opentelemetry/mapping/host_metadata.md +++ b/content/en/opentelemetry/mapping/host_metadata.md @@ -115,7 +115,7 @@ How to form a CCRID: ``` * [Azure][11]: `/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/{resourceProviderNamespace}/{resourceType}/{resourceName}` * GCP: `//compute.googleapis.com/projects/{projectID}/zones/{zoneName}/instances/{instanceName}"` - * OCI/Oracle: CCRID can be obtained by [sending a request][12] at: `http://169.254.169.254/opc/v2/instance/id` + * OCI/Oracle: The CCRID can be obtained by [sending a request][12] at: `http://169.254.169.254/opc/v2/instance/id` For example, to set an AWS CCRID for all resources in metrics, traces, and logs, use the [transform processor][2] with the following configuration: From 5b41182c360aa51d7c2114cdd6584a2ec8e5cc8b Mon Sep 17 00:00:00 2001 From: Andrey Zheltovskiy Date: Fri, 2 Jan 2026 18:17:15 +0100 Subject: [PATCH 14/14] Update content/en/opentelemetry/mapping/host_metadata.md Co-authored-by: Heston Hoffman --- content/en/opentelemetry/mapping/host_metadata.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/en/opentelemetry/mapping/host_metadata.md b/content/en/opentelemetry/mapping/host_metadata.md index 4af567861b7..ba8bf8551ec 100644 --- a/content/en/opentelemetry/mapping/host_metadata.md +++ b/content/en/opentelemetry/mapping/host_metadata.md @@ -110,9 +110,9 @@ See below for the list of identifier formats per-cloud: How to form a CCRID: * [AWS (EC2 Instance)][13]: `arn:aws:ec2:{region}:{accountId}:instance/{instanceId}`. Use this command to retrieve the `instanceId`: - ```bash - ec2metadata --instance-id - ``` + ```shell + ec2metadata --instance-id + ``` * [Azure][11]: `/subscriptions/{subscriptionId}/resourceGroups/{resourceGroupName}/providers/{resourceProviderNamespace}/{resourceType}/{resourceName}` * GCP: `//compute.googleapis.com/projects/{projectID}/zones/{zoneName}/instances/{instanceName}"` * OCI/Oracle: The CCRID can be obtained by [sending a request][12] at: `http://169.254.169.254/opc/v2/instance/id`