RATATOSK
← All releases

OpenTelemetryv0.147.0

Breaking changes 4Important fixes 3Enhancements 2Other changes 5

Get OpenTelemetry alerts

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

Breaking changes4

Log scrapers emit log-appropriate receiver telemetry

AffectsSetups that use log scrapers in pkg/scraperhelper(Inferred)

Previously, log scrapers emitted otelcol_receiver_accepted_metric_points and receiver/myreceiver/MetricsReceived instead of otelcol_receiver_accepted_log_records and receiver/myreceiver/LogsReceived. Scraper-specific spans and metrics are unaffected.

Show release-note lines
- `pkg/scraperhelper`: Log scrapers now emit log-appropriate receiver telemetry (#14654)
  Log scrapers previously emitted the same receiver telemetry as metric scrapers,
  such as the otelcol_receiver_accepted_metric_points metric (instead of otelcol_receiver_accepted_log_records),
  or spans named receiver/myreceiver/MetricsReceived (instead of receiver/myreceiver/LogsReceived).
  This did not affect scraper-specific spans and metrics.
github.com/open-telemetry/opentelemetry-collector/releases/tag/v0.147.0

Streaming support added to the memory_limiter extension

Affectssetups using the memory_limiter extension with gRPC streaming services(Inferred)

Streaming requests receive RESOURCE_EXHAUSTED when MustRefuse() is true.

Show release-note lines
- `extension/memory_limiter`: Add support for streaming services. (#14634)
github.com/open-telemetry/opentelemetry-collector/releases/tag/v0.147.0

featuregate rejects extra positional arguments

Affectsthe featuregate subcommand(Inferred)

Previously, invocations with more than one positional argument succeeded and silently ignored the extras; they now return an error.

Show release-note lines
- `pkg/otelcol`: The featuregate subcommand now rejects extra positional arguments instead of silently ignoring them. (#14554)
github.com/open-telemetry/opentelemetry-collector/releases/tag/v0.147.0

gRPC middleware constructors now accept context.Context

AffectsgRPC middleware implementations and constructors in pkg/config/configmiddleware or pkg/extensionmiddleware

Option functions can retrieve options through a remote call, such as reading TLS configuration from a sidecar.

Evidence“Interfaces like GRPCClient/GRPCServer for the option function should accept context as first param. This is important if to retrieve some option a remote call is needed, for example read TLS config from a sidecar.” open-telemetry/opentelemetry-collector/issues/14523 ↗
Show release-note lines
- `pkg/config/configmiddleware`: Add context.Context to gRPC middleware interface constructors. (#14523)
- `pkg/extensionmiddleware`: Add context.Context to gRPC middleware interface constructors. (#14523)
  This is a breaking API change for components that implement or use extensionmiddleware.
- `pkg/config/configmiddleware`: Add context.Context to HTTP middleware interface constructors. (#14523)
  This is a breaking API change for components that implement or use extensionmiddleware.
github.com/open-telemetry/opentelemetry-collector/releases/tag/v0.147.0

Important fixes3

  • processor/batch SchemaUrl copying fixed
    Affectssetups using processor/batch(Inferred)

    During partial batch splits, processor/batch did not copy SchemaUrl metadata from resource and scope containers. It now copies that metadata during partial batch splits.

    - `processor/batch`: Fixes a bug where the batch processor would not copy `SchemaUrl` metadata from resource and scope containers during partial batch splits. (#12279, #14620)
    github.com/open-telemetry/opentelemetry-collector/releases/tag/v0.147.0
  • Memory limiter chains unary interceptors
    Affectssetups using the memory_limiter extension with multiple extensions that use UnaryInterceptor(Inferred)

    When multiple extensions using UnaryInterceptor were configured, gRPC's single-interceptor limit caused the binary to panic at startup; the memory_limiter extension now chains their unary interceptors.

    - `extension/memory_limiter`: Use ChainUnaryInterceptor instead of UnaryInterceptor to allow multiple interceptors. (#14634)
      If multiple extensions that use the UnaryInterceptor are set the binary panics at start time.
    github.com/open-telemetry/opentelemetry-collector/releases/tag/v0.147.0
  • Config decoding fixed for interpolated pointer-to-string fields
    Affectsconfigurations with interpolated values in fields internally typed as pointer to string

    Before this fix, an interpolated environment-variable value such as 1234 was treated as an integer and failed string validation, so configuration decoding failed.

    - `pkg/confmap`: Fix another issue where configs could fail to decode when using interpolated values in string fields. (#14034)
      For example, a resource attribute can be set via an environment variable to a string that is parseable as a number, e.g. `1234`.
      (A similar bug was fixed in a previous release: that one was triggered when the field was nested in a struct,
      whereas this one is triggered when the field internally has type "pointer to string" rather than "string".)
    github.com/open-telemetry/opentelemetry-collector/releases/tag/v0.147.0

Enhancements2

  • Metadata-based exporter batch partitioning

    To use Specify metadata_keys in sending_queue.batch.partition; exporterhelper.WithQueue() configures the partitioner and merge function automatically.

    - `pkg/exporterhelper`: Add `metadata_keys` configuration to `sending_queue.batch.partition` to partition batches by client metadata (#14139)
      The `metadata_keys` configuration option is now available in the `sending_queue.batch.partition` section for all exporters.
      When specified, batches are partitioned based on the values of the listed metadata keys, allowing separate batching per metadata partition. This feature
      is automatically configured when using `exporterhelper.WithQueue()`.
    - `pkg/exporterhelper`: Add `metadata_keys` configuration to `sending_queue.batch.partition` to partition batches by client metadata (#14139)
      The `metadata_keys` configuration option is now available in the `sending_queue.batch.partition` section for all exporters.
      When specified, batches are partitioned based on the values of the listed metadata keys, allowing separate batching per metadata partition. This feature
      is automatically configured when using `exporterhelper.WithQueue()`.
    github.com/open-telemetry/opentelemetry-collector/releases/tag/v0.147.0
  • Semantic-convention URLs with underscore anchors validated by cmd/mdatagen
    - `cmd/mdatagen`: Fix semconv URL validation for metrics with underscores in their names (#14583)
      Metrics like `system.disk.io_time` now correctly validate against semantic convention URLs containing underscores in the anchor tag.
    github.com/open-telemetry/opentelemetry-collector/releases/tag/v0.147.0
Other changes5

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