chore(deps): bump module go.opentelemetry.io/collector go.opentelemetry.io/collector from v0.130.1 to v0.134.0

[Astitva-sumo]

This PR contains the following updates:

Package	Type	Update	Change
go.opentelemetry.io/collector	indirect	minor	v0.130.1 -> v0.134.0

---

Release Notes

open-telemetry/opentelemetry-collector (go.opentelemetry.io/collector)

v0.134.0

Compare Source

💡 Enhancements 💡

• pdata: Add custom grpc/encoding that replaces proto and calls into the custom marshal/unmarshal logic in pdata. (#​13631)
  This change should not affect other gRPC calls since it fallbacks to the default grpc/proto encoding if requests are not pdata/otlp requests.
• pdata: Avoid copying the pcommon.Map when same origin (#​13731)
  This is a very large improvement if using OTTL with map functions since it will avoid a map copy.
• exporterhelper: Respect num_consumers when batching and partitioning are enabled. (#​13607)

🧰 Bug fixes 🧰

• pdata: Correctly parse OTLP payloads containing non-packed repeated primitive fields (#​13727, #​13730)
  This bug prevented the Collector from ingesting most Histogram, ExponentialHistogram,
  and Profile payloads.

v0.133.0

Compare Source

🛑 Breaking changes 🛑

• all: Increase minimum Go version to 1.24 (#​13627)

💡 Enhancements 💡

• otlphttpexporter: Add profiles_endpoint configuration option to allow custom endpoint for profiles data export (#​13504)
  The profiles_endpoint configuration follows the same pattern as traces_endpoint, metrics_endpoint, and logs_endpoint.
  When specified, profiles data will be sent to the custom URL instead of the default {endpoint}/v1development/profiles.

• pdata: Add support for local memory pooling for data objects. (#​13678)
  This is still an early experimental (alpha) feature. Do not recommended to be used production. To enable use "--featuregate=+pdata.useProtoPooling"

• pdata: Optimize CopyTo messages to avoid any copy when same source and destination (#​13680)

• receiverhelper: New feature flag to make receiverhelper distinguish internal vs. downstream errors using new otelcol_receiver_failed_x and otelcol_receiver_requests metrics (#​12207, #​12802)
  This is a breaking change for the semantics of the otelcol_receiver_refused_metric_points, otelcol_receiver_refused_log_records and otelcol_receiver_refused_spans metrics.
  These new metrics and semantics are enabled through the receiverhelper.newReceiverMetrics feature gate.

• debugexporter: Add support for entity references in debug exporter output (#​13324)

• pdata: Fix unnecessary allocation of a new state when adding new values to pcommon.Map (#​13634)

• service: Implement refcounting for pipeline data owned memory. (#​13631)
  This feature is protected by --featuregate=+pdata.useProtoPooling.

• service: Add a debug-level log message when a consumer returns an error. (#​13357)

• xpdata: Optimize xpdata/context for persistent queue when only one value for key (#​13636)

• otlpreceiver: Log the listening addresses of the receiver, rather than the configured endpoints. (#​13654)

• pdata: Use the newly added proto marshaler/unmarshaler for the official proto Marshaler/Unmarshaler (#​13637)
  If any problems observed with this consider to disable the featuregate --feature-gates=-pdata.useCustomProtoEncoding

• configtls: Enable X25519MLKEM768 as per draft-ietf-tls-ecdhe-mlkem (#​13670)

🧰 Bug fixes 🧰

• exporterhelper: Prevent uncontrolled goroutines in batcher due to a incorrect worker pool behaviour. (#​13689)
• service: Ensure the insecure configuration is accounted for when normalizing the endpoint. (#​13691)
• configoptional: Allow validating nested types (#​13579)
  configoptional.Optional now implements xconfmap.Validator
• batchprocessor: Fix UB in batch processor when trying to read bytes size after adding request to pipeline (#​13698)
  This bug only happens id detailed metrics are enabled and also an async (sending queue enabled) exporter that mutates data is configure.

v0.132.0

Compare Source

🛑 Breaking changes 🛑

• componentstatus: Change the signature of the componentstatus.NewEvent to accept multiple options. (#​13210)
  Changes the signature of the component.NewEvent to accept multiple EventBuilderOption,
  like the new WithAttributes constructor.

🚩 Deprecations 🚩

• service: move service.noopTraceProvider feature gate to deprecated stage (#​13492)
  The functionality of the feature gate is available via configuration with the following telemetry settings:
  service:
  telemetry:
  traces:
  level: none

• mdatagen: Remove the deletion of generated_component_telemetry_test.go. (#​12067)
  This file used to be generated by mdatagen. Starting with 0.122.0, the code deletes that file.
  It is no longer necessary to delete the file, as code has had time to upgrade to mdatagen and delete the file.

• service: The telemetry.disableHighCardinalityMetrics feature gate is deprecated (#​13537)
  The feature gate is now deprecated since metric views can be configured.
  The feature gate will be removed in v0.134.0.

  The metric attributes removed by this feature gate are no longer emitted
  by the Collector by default, but if needed, you can achieve the same
  functionality by configuring the following metric views:

  service:
    telemetry:
      metrics:
        level: detailed
        views:
          - selector:
              meter_name: "go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc"
            stream:
              attribute_keys:
                excluded: ["net.sock.peer.addr", "net.sock.peer.port", "net.sock.peer.name"]
          - selector:
              meter_name: "go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp"
            stream:
              attribute_keys:
                excluded: ["net.host.name", "net.host.port"]

  Note that this requires setting service::telemetry::metrics::level: detailed.
  If you have a strong use case for using views in combination with a different
  level, please show your intehttps://github.com/open-telemetry/opentelemetry-collector/issues/10769issues/10769.

💡 Enhancements 💡

• pdata: Generate Logs/Traces/Metrics/Profiles and p[log|trace|metric|profile]ExportResponse with pdatagen. (#​13597)
  This change brings consistency on how these structs are written and remove JSON marshaling/unmarshaling hand written logic.
• confighttp: Add option to configure ForceAttemptHTTP2 to support HTTP/1 specific transport settings. (#​13426)
• pdata: Avoid unnecessary buffer copy when JSON marshal fails. (#​13598)
• cmd/mdatagen: Use a custom host implementation for lifecycle tests (#​13589)
  Use a custom noop host implementation that implements all non-deprecated, publicly-accessible interfaces implemented by the Collector service.
• processorhelper: Add processor internal duration metric. (#​13231)
• pdata: Improve RemoveIf for slices to not reference anymore the removed memory (#​13522)

🧰 Bug fixes 🧰

• pdata: Fix null pointer access when copying into a slice with larger cap but smaller len. (#​13523)

• confighttp: Fix middleware configuration field name from "middleware" to "middlewares" for consistency with configgrpc (#​13444)

• memorylimiterextension, memorylimiterprocessor: Memory limiter extension and processor shutdown don't throw an error if the component was not started first. (#​9687)
  The components would throw an error if they were shut down before being started.
  With this change, they will no longer return an error, conforming to the lifecycle of components expected.

• confighttp: Reuse zstd Reader objects (#​11824)

v0.131.0

Compare Source

🛑 Breaking changes 🛑

• confighttp: Move confighttp.framedSnappy feature gate to beta. (#​10584)

💡 Enhancements 💡

• exporter/debug: Move to alpha stability except profiles (#​13487)

• exporterhelper: Enable exporter.PersistRequestContext feature gate by default. (#​13437)
  Request context is now preserved by default when using persistent queues.
  Note that Auth extensions context is not propagated through the persistent queue.

• pdata: Use pdatagen to generate marshalJSON without using gogo proto jsonpb. (#​13450)

• otlpreceiver: Remove usage of gogo proto which uses reflect.Value.MethodByName. Removes one source of disabling DCE. (#​12747)

• exporterhelper: Fix metrics split logic to consider metrics description into the size. (#​13418)

• service: New pipeline instrumentation now differentiates internal failures from downstream errors (#​13234)
  With the telemetry.newPipelineTelemetry feature gate enabled, the "received" and "produced"
  metrics related to a component now distinguish between two types of errors:

  • "outcome = failure" indicates that the component returned an internal error;
  • "outcome = refused" indicates that the component successfully emitted data, but returned an
    error coming from a downstream component processing that data.

• pdata: Remove usage of text/template from pdata, improves DCE. (#​12747)

• architecture: New Tier 3 platform riscv64 allowing the collector to be built and distributed for this platform. (#​13462)

🧰 Bug fixes 🧰

• exporterhelper: Prevents the exporter for being stuck when telemetry data is bigger than batch.max_size (#​12893)
• mdatagen: Fix import paths for mdatagen component (#​13069)
• otlpreceiver: Error handler correctly fallbacks to content type (#​13414)
• pdata/pprofiles: Fix profiles JSON unmarshal logic for originalPayload. The bytes have to be base64 encoded. (#​13483)
• xpdata: Fix unmarshaling JSON for entities, add e2e tests to avoid this in the future. (#​13480)
• service: Downgrade dependency of prometheus exporter in OTel Go SDK (#​13429)
  This fixes the bug where collector's internal metrics are emitted with an unexpected suffix in their names when users configure the service::telemetry::metrics::readers with Prometheus
• service: Revert Default internal metrics config now enables otel_scope_ labels (#​12939, #​13344)
  Reverting change temporarily due to prometheus exporter downgrade. This unfortunately re-introduces the bug that instrumentation scope attributes cause errors in Prometheus exporter. http://github.com/open-telemetry/opentelemetry-collector/issues/129392939 for details.
• builder: Remove undocumented handling of DIST_* environment variables replacements (#​13335)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.

[Astitva-sumo]

ℹ Artifact update notice

File name: pkg/extension/opampextension/go.mod

In order to perform the update(s) described in the table above, Renovate ran the go get command, which resulted in the following additional change(s):

• 8 additional dependencies were updated

Details:

Package	Change
cel.dev/expr	v0.23.0 -> v0.24.0
github.com/GoogleCloudPlatform/opentelemetry-operations-go/detectors/gcp	v1.27.0 -> v1.29.0
github.com/cncf/xds/go	v0.0.0-20250326154945-ae57f3c0d45f -> v0.0.0-20250501225837-2ac532fd4443
github.com/go-jose/go-jose/v4	v4.0.5 -> v4.1.1
google.golang.org/genproto/googleapis/api	v0.0.0-20250603155806-513f23925822 -> v0.0.0-20250707201910-8d1bb00bc6a7
google.golang.org/genproto/googleapis/rpc	v0.0.0-20250603155806-513f23925822 -> v0.0.0-20250707201910-8d1bb00bc6a7
google.golang.org/grpc	v1.73.0 -> v1.75.0
google.golang.org/protobuf	v1.36.6 -> v1.36.8