fix(deps): update module go.opentelemetry.io/collector/consumer/consumertest to v0.127.0 - autoclosed

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
go.opentelemetry.io/collector/consumer/consumertest	v0.115.0 -> v0.127.0

---

Release Notes

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

v0.127.0

Compare Source

🚩 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

v0.126.0

Compare Source

🛑 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)

v0.125.0

Compare Source

🛑 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.

v0.124.0

Compare Source

💡 Enhancements 💡

• exporterhelper: Add support for bytes-based batching for profiles in the exporterhelper package. (#​3262)
• otelcol: Enhance config validation using command to capture all validation errors that prevents the collector from starting. (#​8721)
• exporterhelper: Link batcher context to all batched request's span contexts. (#​12212, #​8122)

🧰 Bug fixes 🧰

• confighttp: Ensure http authentication server failures are handled by the provided error handler (#​12666)

v0.123.0

Compare Source

❗ Known Issues ❗

• This version increases memory usage by ~0.5 MB per component in the pipelines because a separate Zap Core logger is
  initialized for each component. The issue is partially fixed in v0.126.0 for users who write logs to stdout, but do
  not export logs via OThttps://github.com/open-telemetry/opentelemetry-collector/issues/13014es/13014 for more details.

🛑 Breaking changes 🛑

• service/telemetry: Mark telemetry.disableAddressFieldForInternalTelemetry as beta, usage of deprecated service::telemetry::address are ignored (#​25115)
  To restore the previous behavior disable telemetry.disableAddressFieldForInternalTelemetry feature gate.
• exporterbatch: Remove deprecated fields min_size_items and max_size_items from batch config. (#​12684)

🚩 Deprecations 🚩

• otlpexporter: Mark BatcherConfig as deprecated, use sending_queue::batch instead (#​12726)
• exporterhelper: Deprecate blocking in favor of block_on_overflow. (#​12710)
• exporterhelper: Deprecate configuring exporter batching separately. Use sending_queue::batch instead. (#​12772)
  Moving the batching configuration to sending_queue::batch requires setting sending_queue::sizer to items
  which means that sending_queue::queue_size needs to be also increased by the average batch size number (roughly
  x5000 for the default batching configuration).
  See https://github.com/open-telemetry/opentelemetry-collector/tree/main/exporter/exporterhelper#configuration

💡 Enhancements 💡

• exporterhelper: Add support to configure batching in the sending queue. (#​12746)

• exporterhelper: Add support for wait_for_result, remove disabled_queue (#​12742)
  This has a side effect for users of the experimental BatchConfig with the queue disabled, since not this is | uses only NumCPU() consumers.

• exporterhelper: Allow exporter memory queue to use different type of sizers. (#​12708)

• service: Add "telemetry.newPipelineTelemetry" feature gate to inject component-identifying attributes in internal telemetry (#​12217)
  With the feature gate enabled, all internal telemetry (metrics/traces/logs) will include some of
  the following instrumentation scope attributes:

  • otelcol.component.kind
  • otelcol.component.id
  • otelcol.pipeline.id
  • otelcol.signal
  • otelcol.signal.output

  These attributes are defined in the Pipeline Component Telemetry RFC,
  and identify the component instance from which the telemetry originates.
  They are added automatically without changes to component code.

  These attributes were already included in internal logs as regular log attributes, starting from
  v0.120.0. For consistency with other signals, they have been switched to scope attributes (with
  the exception of logs emitted to standard output), and are now enabled by the feature gate.

  Please make sure that the exporter / backend endpoint you use has support for instrumentation
  scope attributes before using this feature. If the internal telemetry is exported to another
  Collector, a transform processor could be used to turn them into other kinds of attributes if
  necessary.

• exporterhelper: Enable support to do batching using bytes sizer (#​12751)

• service: Add config key to set metric views used for internal telemetry (#​10769)
  The service::telemetry::metrics::views config key can now be used to explicitly set the list of
  metric views used for internal telemetry, mirroring meter_provider::views in the SDK config.
  This can be used to disable specific internal metrics, among other uses.

  This key will cause an error if used alongside other features which would normally implicitly create views, such as:

  • not setting service::telemetry::metrics::level to detailed;
  • enabling the telemetry.disableHighCardinalityMetrics feature flag.

🧰 Bug fixes 🧰

• exporterhelper: Fix order of starting between queue and batch. (#​12705)

v0.122.1

Compare Source

🧰 Bug fixes 🧰

• confmap: Ensure slices with defaults containing struct values are correctly set. (#​12661)
  This reverts the changes madehttps://github.com/open-telemetry/opentelemetry-collector/pull/118821882.

v0.122.0

Compare Source

🛑 Breaking changes 🛑

• service: Batch processor telemetry is no longer emitted at "basic" verbosity level (#​7890)
  According to the guidelines, basic-level telemetry should be reserved for core Collector APIs.
  Components such as the batch processor should emit telemetry starting from the "normal" level
  (which is also the default level).

  Migration: If your Collector telemetry was set to level: basic and you want to keep seeing
  batch processor-related metrics, consider switching to level: normal instead.

💡 Enhancements 💡

• service: Add service.AllowNoPipelines feature gate to allow starting the Collector without pipelines. (#​12613)
  This can be used to start with only extensions.

• mdatagen: Delete generated_status.go if the component type doesn't require it. (#​12346)

• componenttest: Improve config struct mapstructure field tag checks (#​12590)
  remain tags and omitempty tags without a custom field name will now pass validation.

• service: include component id/type in start error (#​10426)

• mdatagen: Add deprecation date and migration guide fields as part of component metadata (#​12359)

• confmap: Introduce a new feature flag to allow for merging lists instead of discarding the existing ones. (#​8394, #​8754, #​10370)
  You can enable this option via the command line by running following command:
  otelcol --config=main.yaml --config=extra_config.yaml --feature-gates=-confmap.enableMergeAppendOption

• zpagesextension: Add expvar handler to zpages extension. (#​11081)

🧰 Bug fixes 🧰

• 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.

• service: do not attempt to register process metrics if they are disabled (#​12098)

v0.121.0

Compare Source

🛑 Breaking changes 🛑

• confighttp: Make the client config options max_idle_conns, max_idle_conns_per_host, max_conns_per_host, and idle_conn_timeout integers (#​9478)
  All four options can be set to 0 where they were previously set to null

🚩 Deprecations 🚩

• exporterhelper: Deprecate min_size_items and max_size_items in favor of min_size and max_size. (#​12486)

💡 Enhancements 💡

• mdatagen: Add converter and provider module classes (#​12467)

• pipeline: output pipeline name with signal as signal[/name] format in logs. (#​12410)

• memorylimiter: Add support to configure min GC intervals for soft and hard limits. (#​12450)

• otlpexporter: Update the stability level for logs, it has been as stable as traces and metrics for some time. (#​12423)

• service: Create a new subcommand to dump the initial configuration after resolving/merging. (#​11479)
  To use the print-initial-config subcommand, invoke the Collector with the subcommand and corresponding feature gate: otelcol print-initial-config --feature-gates=otelcol.printInitialConfig --config=config.yaml.
  Note that the feature gate enabling this flag is currently in alpha stability, and the subcommand may
  be changed in the future.

• memorylimiterprocessor: Add support for profiles. (#​12453)

• otelcol: Converters are now available in the components command. (#​11900, #​12385)

• component: Mark module as stable (#​9376)

• confmap: Surface YAML parsing errors when they happen at the top-level. (#​12180)
  This adds context to some instances of the error "retrieved value (type=string) cannot be used as a Conf", which typically happens because of invalid YAML documents

• pprofile: Add LinkIndex attribute to the generated Sample type (#​12485)

• exporterhelper: Stabilize exporter.UsePullingBasedExporterQueueBatcher and remove old batch sender (#​12425)

• mdatagen: Update metadata schema with new fields without enforcing them (#​12359)

🧰 Bug fixes 🧰

• service: Fix crash at startup when converting from v0.2.0 to v0.3.0 (#​12438)
• service: fix bug in parsing service::telemetry configuration (#​12437)
• exporterhelper: Fix bug where the error logged when conversion of data fails is always nil (#​12510)
• mdatagen: Adds back missing import for filter when emitting resource attributes (#​12455)

v0.120.0

Compare Source

🛑 Breaking changes 🛑

• all: Added support for go1.24, bumped minimum version to 1.23 (#​12370)
• mdatagen: Removing deprecated generated funcs and a few test funcs as well. (#​12304)
• service: Align component logger attributes with those defined in RFC (#​12217)
  See Pipeline Component Telemetry RFC

💡 Enhancements 💡

• otlpreceiver: Update stability for logs (#​12335)
• exporterhelper: Implement sync disabled queue used when batching is enabled. (#​12245)
• exporterhelper: Enable the new pull-based batcher in exporterhelper (#​12291)
• exporterhelper: Update queue size after the element is done exported (#​12399)
  After this change the active queue size will include elements in the process of being exported.
• otelcol: Add featuregate command to display information about available features (#​11998)
  The featuregate command allows users to view detailed information about feature gates
  including their status, stage, and description.

🧰 Bug fixes 🧰

• memorylimiter: Logger no longer attributes to single signal, pipeline, or component. (#​12217)
• otlpreceiver: Logger no longer attributes to random signal when receiving multiple signals. (#​12217)
• exporterhelper: Fix undefined behavior access to request after send to next component. This causes random memory access. (#​12281)
• exporterhelper: Fix default batcher to correctly call all done callbacks exactly once (#​12247)
• otlpreceiver: Fix OTLP http receiver to correctly set Retry-After (#​12367)
• otlphttpexporter: Fix parsing logic for Retry-After in OTLP http protocol. (#​12366)
  The value of Retry-After field can be either an HTTP-date or delay-seconds and the current logic only parsed delay-seconds.
• cmd/builder: Ensure unique aliases for modules with same suffix (#​12201)

v0.119.0

Compare Source

🛑 Breaking changes 🛑

• exporterhelper: Rename exporter span signal specific attributes (e.g. "sent_spans" / "send_failed_span") to "items.sent" / "items.failed". (#​12165)

• cmd/mdatagen: Remove dead field telemetry::level (#​12144)

• exporterhelper: Change exporter ID to be a Span level attribute instead on each event. (#​12164)
  This does not have an impact on the level of information emitted, but on the structure of the Span.

• cmd/mdatagen: Remove level field from metrics definition (#​12145)
  This mechanism will be added back once a new views mechanism is implemented.

• service: Value for telemetry exporter otlp.protocol updated from grpc/protobuf to grpc. (#​12337)

• service: internal metrics exported over Prometheus may differ from previous versions. (#​11611)

  Users who do not customize the Prometheus reader should not be impacted. The change to update the internal telemetry to use otel-go config can cause unexpected behaviour
  for end users. This change is caused by the default values in config being different from what the Collector has used in previous versions. The
  following changes can occur when users configure their service::telemetry::metrics::readers:

  • the metric name will append a _total suffix if without_type_suffix is not configured. Set without_type_suffix to true to disable this.
  • units will be appended to metric name if without_units is not configured. Set without_units to true to disable this.
  • a target_info metric will be emitted if without_scope_info is not configured. Set without_scope_info to true to disable this.

💡 Enhancements 💡

• configtls: Allow users to mention their preferred curve types for ECDHE handshake (#​12174)
• service: remove custom code and instead use config package to instantiate meter provider. (#​11611)
• otelcol: Adds support for listing config providers in components command's output (#​11570)
• general: Reduce memory allocations when loading configuration and parsing component names (#​11964)

🧰 Bug fixes 🧰

• exporterhelper: Fix bug that the exporter with new batcher may have been marked as non mutation. (#​12239)
  Only affects users that manually turned on exporter.UsePullingBasedExporterQueueBatcher featuregate.

• service: Preserve URL normalization logic that was present before. (#​12254)

• confighttp: confighttp.ToServer now sets ErrorLog with a default logger backed by Zap (#​11820)

  This change ensures that the http.Server's ErrorLog is correctly set using Zap's logger at the error level, addressing the issue of error logs being printed using a different logger.

• exporterhelper: Fix context propagation for DisabledBatcher (#​12231)

• mdatagen: apply fieldalignment to generated code (#​12125)

• mdatagen: Fix bug where Histograms were marked as not supporting temporal aggregation (#​12168)

• exporterhelper: Fix MergeSplit issue that ignores the initial message size. (#​12257)

• service: Include validation errors from telemetry.Config when validating the service config (#​12100)
  Previously validation errors were only printed to the console

• service-telemetry: pass the missing async error channel into service telemetry settings (#​11417)

v0.118.0

Compare Source

💡 Enhancements 💡

• exporterhelper: Add blocking option to control queue behavior when full (#​12090)
• debugexporter: Add EventName to debug exporter for Logs. EventName was added as top-level field in the LogRecord from 1.5.0 of proto definition. (#​11966)
• confighttp: Added support for configuring compression levels. (#​10467)
  A new configuration option called CompressionParams has been added to confighttp. | This allows users to configure the compression levels for the confighttp client.
• exporterhelper: Change the memory queue implementation to not pre-allocate capacity objects. (#​12070)
  This change improves memory usage of the collector under low utilization and is a prerequisite for supporting different other size limitations (number of items, bytes).

🧰 Bug fixes 🧰

• mdatagen: apply fieldalignment to generated code (#​12121)
• otelcoltest: Set DefaultScheme to env in the test ConfigProvider to replicate the default provider used by the Collector. (#​12066)

v0.117.0

Compare Source

🛑 Breaking changes 🛑

• otelcol: Remove warnings when 0.0.0.0 is used (#​11713, #​8510)

🧰 Bug fixes 🧰

• internal/sharedcomponent: Fixed bug where sharedcomponent would use too much memory remembering all the previously reported statuses (#​11826)

v0.116.0

Compare Source

🛑 Breaking changes 🛑

• pdata/pprofile: Remove deprecated Profile.EndTime and Profile.SetEndTime methods. (#​11796)

💡 Enhancements 💡

• xconfighttp: Add WithOtelHTTPOptions to experimental module xconfighttp (#​11770)

🧰 Bug fixes 🧰

• exporterhelper: Fix memory leak at exporter shutdown (#​11401)
• sharedcomponent: Remove race-condition and cleanup locking (#​11819)

---

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

• 9 additional dependencies were updated
• The go directive was updated for compatibility reasons

Details:

Package	Change
go	1.22.0 -> 1.24.1
go.opentelemetry.io/collector/consumer	v1.21.0 -> v1.27.0
go.opentelemetry.io/collector/pdata	v1.21.0 -> v1.27.0
go.opentelemetry.io/collector/pdata/pprofile	v0.115.0 -> v0.121.0
golang.org/x/net	v0.31.0 -> v0.33.0
golang.org/x/sys	v0.27.0 -> v0.28.0
golang.org/x/text	v0.20.0 -> v0.21.0
google.golang.org/genproto/googleapis/rpc	v0.0.0-20240822170219-fc7c04adadcd -> v0.0.0-20241202173237-19429a94021a
google.golang.org/grpc	v1.67.1 -> v1.70.0
google.golang.org/protobuf	v1.35.2 -> v1.36.5

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: go.sum

Command failed: go get -d -t ./...
go: module go.opentelemetry.io/collector/consumer/[email protected] requires go >= 1.23.0; switching to go1.23.9
go: downloading go1.23.9 (linux/amd64)
go: download go1.23.9: golang.org/[email protected]: verifying module: checksum database disabled by GOSUMDB=off