---
title: Migrate to OpenTelemetry Collector version 0.120.0+
description: Datadog, the leading service for cloud-scale monitoring.
breadcrumbs: >-
  Docs > OpenTelemetry in Datadog > OpenTelemetry Migration Guides > Migrate to
  OpenTelemetry Collector version 0.120.0+
---

# Migrate to OpenTelemetry Collector version 0.120.0+

[OTel Collector Contrib version 0.120.0](https://github.com/open-telemetry/opentelemetry-collector-contrib/releases/tag/v0.120.0) introduced breaking changes to metric names as part of the upgrade to Prometheus 3.0. After upgrading to this version of the OpenTelemetry Collector, you may notice differences in metric values displayed in Datadog.

{% alert level="info" %}
These breaking changes are not introduced by or directly related to Datadog. They impact all OpenTelemetry users who use Prometheus. For a complete list of changes, see the [update](https://github.com/open-telemetry/opentelemetry-collector-contrib/pull/36873) to the Prometheus receiver in the Collector or the Prometheus 3.0 [migration guide](https://prometheus.io/docs/prometheus/latest/migration/).
{% /alert %}

## Changes to Collector internal metric names{% #changes-to-collector-internal-metric-names %}

[Collector Internal Metrics](https://opentelemetry.io/docs/collector/internal-telemetry/) sent using the latest Collector version have the following changes:

- Dots (`.`) in internal collector metrics and resource attributes scraped by Prometheus are no longer replaced with underscores (`_`) by default.
- The `otelcol_` prefix is no longer added to metric names.

For example:

| Before 0.120.0                                    | After 0.120.0                             |
| ------------------------------------------------- | ----------------------------------------- |
| `otelcol_datadog_trace_agent_otlp_traces`         | `datadog.trace_agent.otlp.traces`         |
| `otelcol_datadog_trace_agent_otlp_spans`          | `datadog.trace_agent.otlp.spans`          |
| `otelcol_datadog_trace_agent_otlp_payload`        | `datadog.trace_agent.otlp.payload`        |
| `otelcol_datadog_trace_agent_trace_writer_events` | `datadog.trace_agent.trace_writer.events` |

As a result, Datadog has updated two out-of-the-box dashboards affected by this upgrade:

- OpenTelemetry Collector Health Dashboard
- APM Datadog Trace Agent Dashboard

### OpenTelemetry Collector health dashboard{% #opentelemetry-collector-health-dashboard %}

Queries on the [OpenTelemetry Collector health dashboard](https://docs.datadoghq.com/opentelemetry/integrations/collector_health_metrics/) were modified to be compatible with metric names sent from both older (< 0.120.0) and newer (0.120.0+) versions of the Collector.

If you are using a cloned version of this dashboard or have monitors that query metric names from older Collector versions, you may need to manually update them using the [equiv_otel() function](https://docs.datadoghq.com/opentelemetry/guide/combining_otel_and_datadog_metrics/).

{% image
   source="https://datadog-docs.imgix.net/images/opentelemetry/guide/migration/collector_health.1985e5affef618f5cadcf25312872a54.png?auto=format"
   alt="OpenTelemetry Collector Health Dashboard showing compatible queries" /%}

### APM Datadog Trace Agent dashboard{% #apm-datadog-trace-agent-dashboard %}

Queries on the [APM Datadog Trace Agent dashboard](https://docs.datadoghq.com/tracing/troubleshooting/agent_apm_metrics/) were updated with filters to exclude sources `datadogexporter` and `datadogconnector` to prevent metric collisions with OpenTelemetry sources that emit the same metric names. This dashboard is designed to show only Trace Agent data, and the update ensures that data from these sources doesn't mix with OpenTelemetry data.

Only the out-of-the-box dashboard template was updated. If you are using a cloned version of this dashboard, you may need to manually update queries on custom dashboards to exclude sources `datadogexporter` and `datadogconnector` using:

```text
source NOT IN (datadogexporter, datadogconnector)
```

## Changes to Prometheus Server reader defaults{% #changes-to-prometheus-server-reader-defaults %}

{% alert level="info" %}
If you use default configurations for your OpenTelemetry Collector's telemetry settings, you will not be impacted by these changes.
{% /alert %}

You are only impacted if you have explicitly configured the Prometheus reader with custom settings, such as:

```yaml
service:
  telemetry:
    metrics:
      level: detailed
      readers:
        - pull:
            exporter:
              prometheus:
                host: localhost
                port: 8888
```

If you are affected by these changes, you may see differences in metric names, such as suffix changes and unit additions.

To revert to the previous behavior, add these three parameters to your existing Prometheus reader configuration:

```yaml
without_scope_info: true
without_type_suffix: true
without_units: true
```

For questions or assistance, contact [Datadog support](https://docs.datadoghq.com/help/).

## Further reading{% #further-reading %}

- [Migrate to OpenTelemetry Collector version 0.95.0+](https://docs.datadoghq.com/opentelemetry/guide/switch_from_processor_to_connector)
- [OpenTelemetry Collector Health Dashboard](https://docs.datadoghq.com/opentelemetry/integrations/collector_health_metrics)
- [APM Datadog Trace Agent Dashboard](https://docs.datadoghq.com/tracing/troubleshooting/agent_apm_metrics)
- [Prometheus 3.0 Migration Guide](https://prometheus.io/docs/prometheus/latest/migration/)