fix(deps): update module go.opentelemetry.io/collector/pdata to v1.34.0 (main)

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
go.opentelemetry.io/collector/pdata	v1.30.0 -> v1.34.0

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

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

v1.34.0

🛑 Breaking changes 🛑

• service/telemetry: Mark "telemetry.disableAddressFieldForInternalTelemetry" as stable (#​13152)

💡 Enhancements 💡

• confighttp: Update the HTTP server span naming to use the HTTP method and route pattern instead of the path. (#​12468)
  The HTTP server span name will now be formatted as <http.request.method> <http.route>.
  If a route pattern is not available, it will fall back to <http.request.method>.

• service: Use configured loggers to log errors as soon as it is available (#​13081)

• service: Remove stabilized featuregate useOtelWithSDKConfigurationForInternalTelemetry (#​13152)

🧰 Bug fixes 🧰

• telemetry: Add generated resource attributes to the printed log messages. (#​13110)
  If service.name, service.version, or service.instance.id are not specified in the config, they will be generated automatically.
  This change ensures that these attributes are also included in the printed log messages.

• mdatagen: Fix generation when there are no events in the metadata. (#​13123)

• confmap: Do not panic on assigning nil maps to non-nil maps (#​13117)

• pdata: Fix event_name skipped when unmarshalling LogRecord from JSON (#​13127)

v1.33.0

🚩 Deprecations 🚩

• semconv: Deprecating the semconv package in favour of go.opentelemetry.io/otel/semconv (#​13012)

💡 Enhancements 💡

• exporter/debug: Display resource and scope in normal verbosity (#​10515)
• service: Add size metrics defined in Pipeline Component Telemetry RFC (#​13032)
  See Pipeline Component Telemetry RFC for more details:
  • otelcol.receiver.produced.size
  • otelcol.processor.consumed.size
  • otelcol.processor.produced.size
  • otelcol.connector.consumed.size
  • otelcol.connector.produced.size
  • otelcol.exporter.consumed.size

v1.32.0

🛑 Breaking changes 🛑

• configauth: Removes deprecated configauth.Authentication and extensionauthtest.NewErrorClient (#​12992)
  The following have been removed:
  • configauth.Authentication use configauth.Config instead
  • extensionauthtest.NewErrorClient use extensionauthtest.NewErr instead

💡 Enhancements 💡

• service: Replace go.opentelemetry.io/collector/semconv usage with go.opentelemetry.io/otel/semconv (#​12991)
• confmap: Update the behavior of the confmap.enableMergeAppendOption feature gate to merge only component lists. (#​12926)
• service: Add item count metrics defined in Pipeline Component Telemetry RFC (#​12812)
  See Pipeline Component Telemetry RFC for more details:
  • otelcol.receiver.produced.items
  • otelcol.processor.consumed.items
  • otelcol.processor.produced.items
  • otelcol.connector.consumed.items
  • otelcol.connector.produced.items
  • otelcol.exporter.consumed.items
• tls: Add trusted platform module (TPM) support to TLS authentication. (#​12801)
  Now the TLS allows the use of TPM for loading private keys (e.g. in TSS2 format).

🧰 Bug fixes 🧰

• exporterhelper: Add validation error for batch config if min_size is greater than queue_size. (#​12948)

• telemetry: Allocate less memory per component when OTLP exporting of logs is disabled (#​13014)

• confmap: Use reflect.DeepEqual to avoid panic when confmap.enableMergeAppendOption feature gate is enabled. (#​12932)

• internal telemetry: Add resource attributes from telemetry.resource to the logger (#​12582)
  Resource attributes from telemetry.resource were not added to the internal
  console logs.

  Now, they are added to the logger as part of the "resource" field.

• confighttp and configcompression: Fix handling of snappy content-encoding in a backwards-compatible way (#​10584, #​12825)
  The collector used the Snappy compression type of "framed" to handle the HTTP
  content-encoding "snappy". However, this encoding is typically used to indicate
  the "block" compression variant of "snappy". This change allows the collector to:

  • When receiving a request with encoding 'snappy', the server endpoints will peek
    at the first bytes of the payload to determine if it is "framed" or "block" snappy,
    and will decompress accordingly. This is a backwards-compatible change.
    If the feature-gate "confighttp.framedSnappy" is enabled, you'll see new behavior for both client and server:
  • Client compression type "snappy" will now compress to the "block" variant of snappy
    instead of "framed". Client compression type "x-snappy-framed" will now compress to the "framed" variant of snappy.
  • Servers will accept both "snappy" and "x-snappy-framed" as valid content-encodings.

• tlsconfig: Disable TPM tests on MacOS/Darwin (#​12964)

v1.31.0

🛑 Breaking changes 🛑

• service: Lowercase values for 'otelcol.component.kind' attributes. (#​12865)

• service: Restrict the telemetry.newPipelineTelemetry feature gate to metrics. (#​12856, #​12933)
  The "off" state of this feature gate introduced a regression, where the Collector's internal logs were missing component attributes. See issue #​12870 for more details on this bug.

  On the other hand, the "on" state introduced an issue with the Collector's default internal metrics, because the Prometheus exporter does not currently support instrumentation scope attributes.

  To solve both of these issues, this change turns on the new scope attributes for logs and traces by default regardless of the feature gate.
  However, the new scope attributes for metrics stay locked behind the feature gate, and will remain off by default until the Prometheus exporter is updated to support scope attributes.

  Please understand that enabling the telemetry.newPipelineTelemetry feature gate may break the export of Collector metrics through, depending on your configuration.
  Having a batch processor in multiple pipelines is a known trigger for this.

  This comes with a breaking change, where internal logs exported through OTLP will now use instrumentation scope attributes to identify the source component instead of log attributes.
  This does not affect the Collector's stderr output. See the changelog for v0.123.0 for a more detailed description of the gate's effects.

💡 Enhancements 💡

• mdatagen: Add support for attributes for telemetry configuration in metadata. (#​12919)
• configmiddleware: Add extensionmiddleware interface. (#​12603, #​9591)
• configgrpc: Add gRPC middleware support. (#​12603, #​9591)
• confighttp: Add HTTP middleware support. (#​12603, #​9591, #​7441)
• configmiddleware: Add configmiddleware struct. (#​12603, #​9591)

🧰 Bug fixes 🧰

• exporterhelper: Do not ignore the num_consumers setting when batching is enabled. (#​12244)
• exporterhelper: Reject elements larger than the queue capacity (#​12847)
• mdatagen: Add time and plog package imports (#​12907)
• confmap: Maintain nil values when marshaling or unmarshaling nil slices (#​11882)
  Previously, nil slices were converted to empty lists, which are semantically different
  than a nil slice. This change makes this conversion more consistent when encoding
  or decoding config, and these values are now maintained.

---

Configuration

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

🚦 Automerge: Enabled.

♻ 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 was generated by Mend Renovate. View the repository job log.

[renovate]

ℹ Artifact update notice

File name: 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):

• 1 additional dependency was updated

Details:

Package	Change
google.golang.org/grpc	v1.72.1 -> v1.72.2