RATATOSK
← All releases

OpenTelemetryv0.146.0

Security 1Breaking changes 3Deprecations 1Important fixes 3Enhancements 7Other changes 3

Get OpenTelemetry alerts

Email is sent weekly only when there are changes to check; critical security advisories are sent immediately.

Check before upgrading

Known issues1
Builder telemetry field is for custom SDKs

Security1

Confighttp bounds request-method cardinality in server span names

Affectsserver internal telemetry from pkg/config/confighttp

Previously, raw methods such as FOOBAR could appear in span names, producing high cardinality.

Show release-note lines
- `pkg/config/confighttp`: Fix high cardinality span name from request method from confighttp server internal telemetry (#14516)
  Follow spec to bound request method cardinality.
github.com/open-telemetry/opentelemetry-collector/releases/tag/v0.146.0

Breaking changes3

Minimum Go version for builds raised to 1.25

AffectsCollector builds using Go earlier than 1.25(Inferred)
Action requiredGo 1.25 or later must be available to build the project.

Previously, the project used Go 1.24.* with a module Go version of 1.24.0.

Show release-note lines
- `all`: Increase minimum Go version to 1.25 (#14567)
github.com/open-telemetry/opentelemetry-collector/releases/tag/v0.146.0

Metric stability field flattened in cmd/mdatagen

Affectsmetric metadata in metadata.yaml processed by cmd/mdatagen(Inferred)

Previously, stability was a group containing level and could contain since when the level was deprecated. Deprecation is now represented in a separate deprecated group, where additional deprecation data is set.

Evidence“Currently, we define `stability` as a group that typically includes only the `level` field. The only additional field used is `since`, which applies to the `deprecated` stability level.” open-telemetry/opentelemetry-collector/issues/14113 ↗
Show release-note lines
- `cmd/mdatagen`: Flatten the metric stability field (#14113)
  So we better match the weaver schema. Additional deprecation data can be set within the `deprecated` field.
github.com/open-telemetry/opentelemetry-collector/releases/tag/v0.146.0

Entity-association requirement for cmd/mdatagen metrics and events

Affectscmd/mdatagen metadata defining entities alongside metrics or events

The generated config can disable individual resource attributes without considering their entity associations, which can disable an identifying entity attribute and produce invalid entity data. When entities are defined, metadata for metrics and events must meet the entity-association requirement.

Show release-note lines
- `cmd/mdatagen`: Add entity association requirement for metrics and events when entities are defined (#14284)
github.com/open-telemetry/opentelemetry-collector/releases/tag/v0.146.0

Deprecations1

pprofile aggregation API deprecated

Affectscode using pdata/pprofile aggregation elements(Inferred)
Removed innot stated

AggregationTemporality, its constants, and its String method are marked deprecated; the Profiles signal has no replacement for them.

Show release-note lines
- `pdata/pprofile`: Declare removed aggregation elements as deprecated. (#14528)
- `pdata/pprofile`: Declare removed aggregation elements as deprecated. (#14528)
github.com/open-telemetry/opentelemetry-collector/releases/tag/v0.146.0

Important fixes3

  • Duplicate entries in otelcol components fixed
    Affectsgenerated collectors with component aliases(Inferred)

    In v0.144.0, running otelcol components in a generated collector could list OTLP exporters such as otlp_grpc and otlp_http twice.

    - `pkg/otelcol`: Ignore component aliases in the `otelcol components` command (#14492)
    github.com/open-telemetry/opentelemetry-collector/releases/tag/v0.146.0
  • Generated metrics reset aggDataPoints during initialization
    Affectsgenerated metrics using reaggregation

    With reaggregation enabled, after enough emit cycles, emit() could read counters that no longer matched the datapoints slice and panic with an index-out-of-range error. Resetting aggDataPoints in init() prevents this mismatch.

    - `cmd/mdatagen`: Reset aggDataPoints during metric init to avoid index out of range panic across emit cycles when reaggregation is enabled. (#14569)
    github.com/open-telemetry/opentelemetry-collector/releases/tag/v0.146.0
  • No-argument panic fixed in mdatagen
    Affectssetups that invoke mdatagen

    Running mdatagen without arguments previously caused an index-out-of-range panic; it now returns an argument error.

    - `cmd/mdatagen`: Fix panic when mdatagen is run without arguments. (#14506)
    github.com/open-telemetry/opentelemetry-collector/releases/tag/v0.146.0

Enhancements7

  • Exporter send-failed metrics gain failure attributes

    To use Telemetry level set to Detailed.

    - `all`: Add detailed failure attributes to exporter send_failed metrics at detailed telemetry level. (#13956)
      The `otelcol_exporter_send_failed_{spans,metric_points,log_records}` metrics now include
      failure attributes when telemetry level is Detailed: `error.type` (OpenTelemetry semantic convention
      describing the error class) and `error.permanent` (indicates if error is permanent/non-retryable).
      The `error.type` attribute captures gRPC status codes (e.g., "Unavailable", "ResourceExhausted"),
      standard Go context errors (e.g., "canceled", "deadline_exceeded"),
      and collector-specific errors (e.g., "shutdown").
      This enables better alerting and debugging by providing standardized error classification.
    github.com/open-telemetry/opentelemetry-collector/releases/tag/v0.146.0
  • Experimental ocb init subcommand for cmd/builder
    - `cmd/builder`: Introduce new experimental `init` subcommand (#14530)
      The new `init` subcommand initializes a new custom collector
    github.com/open-telemetry/opentelemetry-collector/releases/tag/v0.146.0
  • Telemetry provider module selection in cmd/builder

    To use A gomod entry in the telemetry module

    - `cmd/builder`: Add "telemetry" field to allow configuring telemetry providers (#14575)
      Most users should not need to use this, this field should only be set if you
    github.com/open-telemetry/opentelemetry-collector/releases/tag/v0.146.0
  • Deprecated-metric metadata in cmd/mdatagen now includes deprecation version and reason
    - `cmd/mdatagen`: Introduce additional metadata (the version since the deprecation started, and the deprecation reason) for deprecated metrics. (#14113)
    github.com/open-telemetry/opentelemetry-collector/releases/tag/v0.146.0
  • Optional relationships field added to the cmd/mdatagen entity schema
    - `cmd/mdatagen`: Add optional `relationships` field to entity schema in metadata.yaml (#14284)
    github.com/open-telemetry/opentelemetry-collector/releases/tag/v0.146.0
  • Configurable debug exporter output destinations

    To use use_internal_logger must be set to false to use output_paths

    - `exporter/debug`: Add `output_paths` configuration option to control output destination when `use_internal_logger` is false. (#10472)
      When `use_internal_logger` is set to `false`, the debug exporter now supports configuring the output destination via the `output_paths` option.
      This allows users to send debug exporter output to `stdout`, `stderr`, or a file path.
      The default value is `["stdout"]` to maintain backward compatibility.
    github.com/open-telemetry/opentelemetry-collector/releases/tag/v0.146.0
  • Experimental ToStringMapRaw function for confmap.Conf decoding
    - `pkg/confmap`: Add experimental `ToStringMapRaw` function to decode `confmap.Conf` into a string map without losing internal types (#14480)
      This method exposes the internal structure of a `confmap.Conf` which may change at any time without prior notice
    github.com/open-telemetry/opentelemetry-collector/releases/tag/v0.146.0
Other changes3

Summaries are produced by AI, so they can be wrong, and they are provided without warranty.