github open-telemetry/opentelemetry-collector v0.102.0
v1.9.0/v0.102.0

latest releases: config/configretry/v1.11.0, pdata/v1.11.0, featuregate/v1.11.0...
29 days ago

Images and binaries here: https://github.com/open-telemetry/opentelemetry-collector-releases/releases/tag/v0.102.0

This release addresses GHSA-c74f-6mfw-mm4v for confighttp. Use v0.102.1 instead to get the fix on configgrpc as well.

End User Changelog

🛑 Breaking changes 🛑

  • envprovider: Restricts Environment Variable names. Environment variable names must now be ASCII only and start with a letter or an underscore, and can only contain underscores, letters, or numbers. (#9531)
  • confighttp: Apply MaxRequestBodySize to the result of a decompressed body (#10289)
    When using compressed payloads, the Collector would verify only the size of the compressed payload.
    This change applies the same restriction to the decompressed content. As a security measure, a limit of 20 MiB was added, which makes this a breaking change. This addresses CVE-2024-36129 (GHSA-c74f-6mfw-mm4v) on confighttp.
    For most clients, this shouldn't be a problem, but if you often have payloads that decompress to more than 20 MiB, you might want to either configure your
    client to send smaller batches (recommended), or increase the limit using the MaxRequestBodySize option.

💡 Enhancements 💡

  • mdatagen: auto-generate utilities to test component telemetry (#19783)
  • mdatagen: support setting an AttributeSet for async instruments (#9674)
  • mdatagen: support using telemetry level in telemetry builder (#10234)
    This allows components to set the minimum level needed for them to produce telemetry. By default, this is set to configtelemetry.LevelBasic. If the telemetry level is below that minimum level, then the noop meter is used for metrics.
  • mdatagen: add support for bucket boundaries for histograms (#10218)
  • releases: add documentation in how to verify the image signatures using cosign (#9610)

🧰 Bug fixes 🧰

  • batchprocessor: ensure attributes are set on cardinality metadata metric (#9674)
  • batchprocessor: Fixing processor_batch_metadata_cardinality which was broken in v0.101.0 (#10231)
  • batchprocessor: respect telemetry level for all metrics (#10234)
  • exporterhelper: Fix potential deadlocks in BatcherSender shutdown (#10255)

Go API Changelog

🛑 Breaking changes 🛑

  • otelcol: Remove deprecated ConfigProvider field from CollectorSettings (#10281)
  • exporterhelper: remove deprecated RequestMarshaler & RequestUnmarshaler types (#10283)
  • service: remove deprecated Telemetry struct and New func (#10285)
  • configtls: remove deprecated LoadTLSConfigContext funcs (#10283)

🚩 Deprecations 🚩

  • component: Deprecate component.UnmarshalConfig, use (*confmap.Conf).Unmarshal(&intoCfg) instead. (#7102)
  • service/telemetry: Deprecate telemetry.New in favor of telemetry.NewFactory (#4970)

💡 Enhancements 💡

  • confmap: Allow setting a default Provider on a Resolver to use when ${} syntax is used without a scheme (#10182)
  • pdata: Introduce string and int64 slices to pcommon (#10148)
  • pdata: Introduce generated experimental pdata for profiling signal. (#10195)
  • confmap: Remove top level condition when considering struct as Unmarshalers (#7101)

🧰 Bug fixes 🧰

  • otelcol: Update validate command to use the new configuration options (#10203)

Don't miss a new opentelemetry-collector release

NewReleases is sending notifications on new releases.