OpenTelemetryv0.145.0
Email is sent weekly only when there are changes to check; critical security advisories are sent immediately.
Important fixes5
OTLP gRPC exporter default balancer fixed to
round_robinAffectssetups using theexporter/otlp_grpcOTLP exporter with its default balancer(Inferred)With the default balancer, behavior could fall back to
pick_first; with the passthrough resolver scheme,round_robindid not take effect.- `exporter/otlp_grpc`: Fix the OTLP exporter balancer to use round_robin by default, as intended. (#14090)
github.com/open-telemetry/opentelemetry-collector/releases/tag/v0.145.0Exporter batch sizer defaults restored
Affectsexporter configurations usingsending_queuebatching(Inferred)When configuration was wrapped in
Optional, itsUnmarshalmethod could be skipped, leaving batchmin_sizeandmax_sizein the wrong units. Wrapper types can now usexconfmap.WithForceUnmarshalerto call the innerUnmarshal; top-levelUnmarshalcalls onconfmap.Confstill skip top-level methods by default.- `pkg/config/configoptional`: Fix `Unmarshal` methods not being called when config is wrapped inside `Optional` (#14500) This bug notably manifested in the fact that the `sending_queue::batch::sizer` config for exporters stopped defaulting to `sending_queue::sizer`, which sometimes caused the wrong units to be used As part of the fix, `xconfmap` exposes a new `xconfmap.WithForceUnmarshaler` option, to be used in the `Unmarshal` methods The default behavior remains that calling `conf.Unmarshal` on the `confmap.Conf` passed as argument to an `Unmarshal` method will skip any top-level `Unmarshal` methods to avoid infinite recursion in standard use cases. - `pkg/config/configoptional`: Fix `Unmarshal` methods not being called when config is wrapped inside `Optional` (#14500) This bug notably manifested in the fact that the `sending_queue::batch::sizer` config for exporters stopped defaulting to `sending_queue::sizer`, which sometimes caused the wrong units to be used when configuring `sending_queue::batch::min_size` and `max_size`.
github.com/open-telemetry/opentelemetry-collector/releases/tag/v0.145.0Optional-wrapped config unmarshalling and exporter batch sizer default fixed
Affectsexporter configuration wrapped inOptional, especially configurations usingsending_queue::batch::sizer,sending_queue::batch::min_sizeorsending_queue::batch::max_sizeThe
sending_queue::batch::sizersetting could stop defaulting tosending_queue::sizer, causingsending_queue::batch::min_sizeandmax_sizeto use the wrong units. That default is restored.- `pkg/config/configoptional`: Fix `Unmarshal` methods not being called when config is wrapped inside `Optional` (#14500) This bug notably manifested in the fact that the `sending_queue::batch::sizer` config for exporters stopped defaulting to `sending_queue::sizer`, which sometimes caused the wrong units to be used when configuring `sending_queue::batch::min_size` and `max_size`.
github.com/open-telemetry/opentelemetry-collector/releases/tag/v0.145.0Interpolated string decoding fixed in
pkg/confmapstruct collectionsAffectsconfigurations with interpolated values in string fields within collections of structsBefore the fix, a value that parsed as a non-string, such as an environment-supplied
1234, could make decoding fail. Withconfmap.newExpandedValueSanitizerenabled, per-field decoding avoids that failure.- `pkg/confmap`: Fix an issue where configs could fail to decode when using interpolated values in string fields. (#14413) For example, a header can be set via an environment variable to a string that is parseable as a number, e.g. `1234`
github.com/open-telemetry/opentelemetry-collector/releases/tag/v0.145.0Unsupported-OS process-metrics startup error fixed in
pkg/serviceAffectscustom-compiled collectors on unsupported operating systems with process metrics enabledThese collectors previously failed to start with
failed to register process metrics: not implemented yet; they now start without that error.- `pkg/service`: Don't error on startup when process metrics are enabled on unsupported OSes (e.g. AIX) (#14307)
github.com/open-telemetry/opentelemetry-collector/releases/tag/v0.145.0
Enhancements2
Forced inner unmarshaling for wrapper types
To use Wrapper types'
Unmarshalmethods must usexconfmap.WithForceUnmarshalerto ensure the inner type'sUnmarshalmethod is called.As part of the fix, `xconfmap` exposes a new `xconfmap.WithForceUnmarshaler` option, to be used in the `Unmarshal` methods of wrapper types like `configoptional.Optional` to make sure the `Unmarshal` method of the inner type is called. The default behavior remains that calling `conf.Unmarshal` on the `confmap.Conf` passed as argument to an `Unmarshal` method will skip any top-level `Unmarshal` methods to avoid infinite recursion in standard use cases. As part of the fix, `xconfmap` exposes a new `xconfmap.WithForceUnmarshaler` option, to be used in the `Unmarshal` methods of wrapper types like `configoptional.Optional` to make sure the `Unmarshal` method of the inner type is called. The default behavior remains that calling `conf.Unmarshal` on the `confmap.Conf` passed as argument to an `Unmarshal` method will skip any top-level `Unmarshal` methods to avoid infinite recursion in standard use cases.
github.com/open-telemetry/opentelemetry-collector/releases/tag/v0.145.0AddProfilesScraperhelper added topkg/xscraperhelper- `pkg/xscraperhelper`: Add AddProfilesScraper similar to scraperhelper.AddMetricsScraper (#14427)
github.com/open-telemetry/opentelemetry-collector/releases/tag/v0.145.0
Other changes2
Scraper IDs added to
pkg/scraperhelpererror logs- `pkg/scraperhelper`: ScraperID has been added to the logs for metrics, logs, and profiles (#14461)
github.com/open-telemetry/opentelemetry-collector/releases/tag/v0.145.0pkg/config/configgrpcadds client info before server authentication- `pkg/config/configgrpc`: add client info to context before server authentication (#12836)
github.com/open-telemetry/opentelemetry-collector/releases/tag/v0.145.0
Summaries are produced by AI, so they can be wrong, and they are provided without warranty.