Skip to content

v1.48.0/v0.142.0

Latest
Latest

Choose a tag to compare

View all tags
@github-actions github-actions released this 15 Dec 20:48
· 17 commits to main since this release
v0.142.0
This tag was signed with the committer’s verified signature. The key has expired.
atoulme Antoine Toulme
GPG key ID: 63199BF2E58EE4AE
Expired
Verified
Learn about vigilant mode.
b579eb1
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

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

End User Changelog

💡 Enhancements 💡

  • exporter/debug: Add logging of dropped attributes, events, and links counts in detailed verbosity (#14202)

  • extension/memory_limiter: The memorylimiter extension can be used as an HTTP/GRPC middleware. (#14081)

  • pkg/config/configgrpc: Statically validate gRPC endpoint (#10451)
    This validation was already done in the OTLP exporter. It will now be applied to any gRPC client.

  • pkg/service: Add support to disabling adding resource attributes as zap fields in internal logging (#13869)
    Note that this does not affect logs exported through OTLP.

API Changelog

🛑 Breaking changes 🛑

  • pdata/xpdata: Rename Entity.IDAttributes() to Entity.IdentifyingAttributes() and Entity.DescriptionAttributes() to Entity.DescriptiveAttributes() to align with OpenTelemetry specification terminology for attributes. (#14275)
  • pkg/exporterhelper: Use configoptional.Optional for the exporterhelper.QueueBatchConfig (#14155)
    It's recommended to change the field type in your component configuration to be configoptional.Optional[exporterhelper.QueueBatchConfig] to keep the enabled subfield. Use configoptional.Some(exporterhelper.NewDefaultQueueConfig()) to enable by default. Use configoptional.Default(exporterhelper.NewDefaultQueueConfig()) to disable by default.

🚩 Deprecations 🚩

  • pkg/service: Deprecate Settings.LoggingOptions and telemetry.LoggerSettings.ZapOptions, add telemetry.LoggerSettings.BuildZapLogger (#14002)
    BuildZapLogger provides a more flexible way to build the Zap logger,
    since the function will have access to the zap.Config. This is used
    in otelcol to install a Windows Event Log output when the zap config
    does not specify any file output.

💡 Enhancements 💡

  • pdata/pprofile: add ProfileCount() (#14239)

🧰 Bug fixes 🧰

  • pkg/confmap: Ensure that embedded structs are not overwritten after Unmarshal is called (#14213)
    This allows embedding structs which implement Unmarshal and contain a configopaque.String.
Assets 2
Loading