diff --git a/content/en/metrics/open_telemetry/query_metrics.md b/content/en/metrics/open_telemetry/query_metrics.md index c48948b4b89..7e78cb4be8d 100644 --- a/content/en/metrics/open_telemetry/query_metrics.md +++ b/content/en/metrics/open_telemetry/query_metrics.md @@ -38,13 +38,13 @@ Choose between two modes: Imagine you're monitoring system load using two different metrics: -- **OTel native**: `otel.system.cpu.load_average.15m` +- **OTel native**: `system.cpu.load_average.15m` - **Datadog Agent**: `system.load.15` -If you query for `otel.system.cpu.load_average.15m`, apply a max space aggregation, and set the Semantic Mode to **Combine data from all telemetry sources**, Datadog automatically: +If you query for `system.cpu.load_average.15m`, apply a max space aggregation, and set the Semantic Mode to **Combine data from all telemetry sources**, Datadog automatically: 1. Identifies the equivalent Datadog metric: `system.load.15`. -2. Combines the timeseries from both `otel.system.cpu.load_average.15m` and `system.load.15`. +2. Combines the timeseries from both `system.cpu.load_average.15m` and `system.load.15`. 3. Applies the max aggregation across all datapoints from both sources. ## Understand metric sources and mappings @@ -53,7 +53,7 @@ To provide clarity when querying, the metric source and equivalent metrics are d - **Source pill**: In the query editor, a **Datadog** or **OTel** pill appears next to the metric name, indicating its origin. -- **Equivalent metrics list**: The editor also shows a list of metrics considered equivalent to the one you've queried. This includes complex one-to-many mappings. For example, `otel.system.cpu.utilization` maps to multiple Datadog CPU state metrics (`system.cpu.idle`, `system.cpu.iowait`, etc.). +- **Equivalent metrics list**: The editor also shows a list of metrics considered equivalent to the one you've queried. This includes complex one-to-many mappings. For example, `system.cpu.utilization` maps to multiple Datadog CPU state metrics (`system.cpu.idle`, `system.cpu.iowait`, etc.). {{< img src="/metrics/otel/source.png" alt="Source pill and equivalent metrics list" style="width:75%;" >}} @@ -67,11 +67,11 @@ For a comprehensive view of how specific OTel and Datadog metrics relate, check Alternatively, click **Edit in Metrics Summary** when inputting a metric in the query editor. -This panel displays metric mappings, including complex relationships. For example, it shows how `otel.system.cpu.utilization` maps to multiple Datadog metrics like `system.cpu.idle`, `system.cpu.user`, and others. +This panel displays metric mappings, including complex relationships. For example, it shows how `system.cpu.utilization` maps to multiple Datadog metrics like `system.cpu.idle`, `system.cpu.user`, and others. {{< img src="/metrics/otel/mappings.png" alt="Metrics Summary Details panel showing OTel and Datadog mappings" style="width:100%;" >}} -You can also see the tag-based logic used for these mappings. Hover over an equivalent metric to see the specific conditions. For example, hovering over `system.cpu.idle` shows that it maps to `otel.system.cpu.utilization` when `state=idle`, and the value is multiplied by 100. +You can also see the tag-based logic used for these mappings. Hover over an equivalent metric to see the specific conditions. For example, hovering over `system.cpu.idle` shows that it maps to `system.cpu.utilization` when `state=idle`, and the value is multiplied by 100. {{< img src="/metrics/otel/tooltip.png" alt="Hover-over tooltip showing tag-based mapping logic" style="width:100%;" >}} diff --git a/content/en/opentelemetry/integrations/kafka_metrics.md b/content/en/opentelemetry/integrations/kafka_metrics.md index 3a4223e1a0a..01b70012d88 100644 --- a/content/en/opentelemetry/integrations/kafka_metrics.md +++ b/content/en/opentelemetry/integrations/kafka_metrics.md @@ -269,7 +269,7 @@ In order to ensure this attribute only gets added to your Kafka logs, use [inclu {{< mapping-table resource="kafka-consumer.csv">}} -**Note:** In Datadog `-` gets translated to `_`. For the metrics prepended by `otel.`, this means that the OTel metric name and the Datadog metric name are the same (for example, `kafka.producer.request-rate` and `kafka.producer.request_rate`). In order to avoid double counting for these metrics, the OTel metric is then prepended with `otel.`. +**Note:** In Datadog `-` gets translated to `_`. For example, `kafka.producer.request-rate` becomes `kafka.producer.request_rate`. See [OpenTelemetry Metrics Mapping][9] for more information. diff --git a/content/en/opentelemetry/integrations/runtime_metrics/_index.md b/content/en/opentelemetry/integrations/runtime_metrics/_index.md index 287427d4400..6335df7bec3 100644 --- a/content/en/opentelemetry/integrations/runtime_metrics/_index.md +++ b/content/en/opentelemetry/integrations/runtime_metrics/_index.md @@ -111,19 +111,12 @@ When using OpenTelemetry runtime metrics with Datadog, you receive both: - Original OpenTelemetry runtime metrics - Mapped Datadog runtime metrics for equivalent metrics -The OpenTelemetry runtime metrics have the following prefixes based on their source: - -| Source | Prefix | -| --- | --- | -| [OTel Collector Datadog Exporter][100] | `otel.process.runtime.*` | -| [Datadog Agent OTLP Ingest][101] | `process.runtime.*` | +OpenTelemetry runtime metrics use the `process.runtime.*` prefix. The following tables list the Datadog runtime metrics that are supported through OpenTelemetry mapping. "N/A" indicates that there is no OpenTelemetry equivalent metric available.
OpenTelemetry runtime metrics are mapped to Datadog by metric name. Do not rename host metrics for OpenTelemetry runtime metrics as this breaks the mapping.
-[100]: /opentelemetry/setup/collector_exporter/ -[101]: /opentelemetry/setup/otlp_ingest_in_the_agent {{< tabs >}} {{% tab "Java" %}} diff --git a/content/en/opentelemetry/mapping/metrics_mapping.md b/content/en/opentelemetry/mapping/metrics_mapping.md index 3593d88c9ae..254bdda01a6 100644 --- a/content/en/opentelemetry/mapping/metrics_mapping.md +++ b/content/en/opentelemetry/mapping/metrics_mapping.md @@ -19,12 +19,6 @@ Datadog products and visualizations are built on metrics and tags that follow sp
Want to unify OpenTelemetry and Datadog metrics in your queries? Learn how to query across Datadog and OpenTelemetry metrics from the Metrics Query Editor.
-## How OpenTelemetry metrics appear in Datadog - -To differentiate metrics from the OpenTelemetry Collector's [hostmetrics][12] receiver and the Datadog Agent, Datadog prepends `otel.` to any received metric that starts with `system.` or `process.`. Datadog does not recommend monitoring the same infrastructure with both the Datadog Agent and the OpenTelemetry Collector - -
Datadog is evaluating ways to improve the OTLP metric experience, including potentially deprecating this otel prefix.
- ## Metrics mappings The following table shows the metric mappings for various integrations. Use the search and filter controls to find the mappings for a specific integration. @@ -48,5 +42,4 @@ For more information, see [OpenTelemetry integrations][11]. [9]: /opentelemetry/otel_collector_datadog_exporter/?tab=onahost#containers-overview-dashboard [10]: /tracing/trace_explorer/trace_view/ [11]: /opentelemetry/integrations/ -[12]: /opentelemetry/integrations/host_metrics/