Bump github.com/open-telemetry/opentelemetry-collector-contrib/processor/transformprocessor from 0.141.0 to 0.150.0

[dependabot]

Bumps github.com/open-telemetry/opentelemetry-collector-contrib/processor/transformprocessor from 0.141.0 to 0.150.0.

Release notes

Sourced from github.com/open-telemetry/opentelemetry-collector-contrib/processor/transformprocessor's releases.

v0.150.0

The OpenTelemetry Collector Contrib contains everything in the opentelemetry-collector release, be sure to check the release notes there as well.

Unmaintained Components

These components are marked as Unmaintained and will eventually be removed from our community distributions. If you depend on these components we need your help to support them.

• exporter/alibabacloudlogserviceexporter

End User Changelog

🛑 Breaking changes 🛑

• pkg/ottl: Return errors when OTTL context accessors receive values of the wrong type (part 2) (#40198) Setters in OTTL contexts now validate that values are of the expected type and return descriptive errors when type mismatches occur. This is the continuation of work done in #43505, addressing remaining contexts: datapoint, profile, profilesample, resource, span, and spanevent.

  Changes include:

  • Slice setters (explicit_bounds, bucket_counts, positive.bucket_counts, negative.bucket_counts) now use SetCommonTypedSliceValues/SetCommonIntSliceValues for better type handling.
  • SetMap now returns an error for invalid value types instead of silently ignoring them.

  Note: Users may see new errors from OTTL statements that were previously silently failing due to type mismatches. These errors indicate pre-existing issues in OTTL configurations that were not being applied as expected.

• processor/resourcedetection: Remove feature gate processor.resourcedetection.propagateerrors (#45853)

• processor/transform: Remove the processor.transform.ConvertBetweenSumAndGaugeMetricContext feature gate. (#47358) This feature gate has been stable for over a year and is no longer used in any code paths.

• receiver/k8s_cluster: Kubernetes resource labels in entity events are now prefixed per OTel semantic conventions. (#47491) Labels on Kubernetes resources emitted as entity event attributes are now prefixed with k8s.<resource>.label. to align with OTel semantic conventions (e.g. k8s.pod.label.<key>, k8s.node.label.<key>, k8s.deployment.label.<key>, etc.). Previously, label keys were emitted verbatim without any prefix. Users consuming entity event attributes by label key will need to update their configurations.

• receiver/kubeletstats: Disable deprecated resource attributes by default (#47184) The following resource attributes are deprecated and will now be disabled by default: aws.volume.id, fs.type, gce.pd.name, glusterfs.endpoints.name, glusterfs.path, and partition. All of these attributes will be removed in a future release.

🚩 Deprecations 🚩

• receiver/http_check: Rename httpcheck receiver to http_check with deprecated alias httpcheck (#45339)
• receiver/named_pipe: Rename namedpipe receiver to named_pipe with deprecated alias namedpipe. (#45339)
• receiver/tcp_log: Rename tcplog receiver to tcp_log with deprecated alias tcplog (#45339)
• receiver/tls_check: Rename tlscheck receiver to tls_check with deprecated alias tlscheck (#45339)

... (truncated)

Changelog

Sourced from github.com/open-telemetry/opentelemetry-collector-contrib/processor/transformprocessor's changelog.

v0.150.0

🛑 Breaking changes 🛑

• pkg/ottl: Return errors when OTTL context accessors receive values of the wrong type (part 2) (#40198) Setters in OTTL contexts now validate that values are of the expected type and return descriptive errors when type mismatches occur. This is the continuation of work done in #43505, addressing remaining contexts: datapoint, profile, profilesample, resource, span, and spanevent.

  Changes include:

  • Slice setters (explicit_bounds, bucket_counts, positive.bucket_counts, negative.bucket_counts) now use SetCommonTypedSliceValues/SetCommonIntSliceValues for better type handling.
  • SetMap now returns an error for invalid value types instead of silently ignoring them.

  Note: Users may see new errors from OTTL statements that were previously silently failing due to type mismatches. These errors indicate pre-existing issues in OTTL configurations that were not being applied as expected.

💡 Enhancements 💡

• receiver/active_directory_ds: Enables dynamic metric reaggregation in the Active Directory Domain Services receiver. This does not break existing configuration files. (#46346)

v0.149.0

🛑 Breaking changes 🛑

• pkg/stanza: Change signature of adapter.NewFactory to accept xreceiver.FactoryOptions (#45339) While the change is technically breaking, the existing calls to adapter.NewFactory will continue to work.

💡 Enhancements 💡

• pkg/expohisto: Move Go exponential histogram data structure into collector-contrib repository (#46646)

• receiver/docker_stats: Add TLS configuration support for connecting to the Docker daemon over HTTPS with client and server certificates. (#33557) A new optional tls configuration block is available in docker_stats receiver config (and the shared internal/docker package). When omitted the connection remains insecure (plain HTTP or Unix socket), preserving existing behavior. When provided it supports the standard configtls.ClientConfig fields: ca_file, cert_file, key_file, insecure_skip_verify, min_version, and max_version. A warning is now emitted when a plain tcp:// or http:// endpoint is used without TLS, reflecting Docker's deprecation of unauthenticated TCP connections since Docker v26.0 (see https://docs.docker.com/engine/deprecated/#unauthenticated-tcp-connections).

• receiver/docker_stats: Add "stream_stats" config option to maintain a persistent Docker stats stream per container instead of opening a new connection on every scrape cycle. (#46493) When stream_stats: true is set, each container maintains a persistent open Docker stats stream instead of opening and closing a new connection on every scrape cycle. The scraper reads from the cached latest value, which reduces connection overhead.

... (truncated)

Commits

• 5358b47 [chore] Prepare release 0.150.0 (#47589)
• b1f301c [exporter/datadog] Remove stable feature gates and migrate remaining to metad...
• ca4224f chore:fix updatebookmark window link (#47577)
• 52a38c3 [chore] Update core dependencies (#47579)
• 3018f9f [chore] Bump load test memory limits (#47567)
• f431af5 [chore] bump semconv import to 1.40.0 (#47510)
• 106e2a3 chore move feature gates for metadata… (#47336)
• c19f0ed [receiver/vcenter] Fix nil pointer dereference in recordVMStats (#47005)
• 1777163 [receiver/windowseventlog] rename to windows_event_log with deprecated alia...
• 780c85b [chore]: (processor/transformprocessor) finish migrating feature gate to meta...
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[aphralG]

closed by #1557

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.