Skip to content

chore(deps): update module go.opentelemetry.io/collector/pdata to v1.59.0#973

Open
red-hat-konflux-kflux-prd-rh02[bot] wants to merge 1 commit into
release-1.3from
konflux/mintmaker/release-1.3/go.opentelemetry.io-collector-pdata-1.x
Open

chore(deps): update module go.opentelemetry.io/collector/pdata to v1.59.0#973
red-hat-konflux-kflux-prd-rh02[bot] wants to merge 1 commit into
release-1.3from
konflux/mintmaker/release-1.3/go.opentelemetry.io-collector-pdata-1.x

Conversation

@red-hat-konflux-kflux-prd-rh02
Copy link
Copy Markdown
Contributor

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package Change Age Confidence
go.opentelemetry.io/collector/pdata v1.12.0v1.59.0 age confidence

Warning

Some dependencies could not be looked up. Check the warning logs for more information.


Release Notes

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

v1.59.0

🛑 Breaking changes 🛑
  • pkg/configoptional: Stabilize feature gate configoptional.AddEnabledField (#​15333)
  • pkg/confmap: Stabilize confmap.newExpandedValueSanitizer feature gate (#​15339)
  • pkg/exporterhelper: mark exporter.PersistRequestContext as stable (#​15330)
  • pkg/otelcol: Stabilize otelcol.printInitialConfig gate (#​15340)
  • pkg/pdata: Remove pdata.useCustomProtoEncoding feature gate (#​15332)
  • pkg/service: Stabilize telemetry.UseLocalHostAsDefaultMetricsAddress gate (#​15342)
  • pkg/xpdata: Stabilize pdata.enableRefCounting feature gate (#​15331)
🧰 Bug fixes 🧰
  • pkg/config/configgrpc: Fix memory corruption and fatal error in Snappy (#​15237, #​15320)

v1.58.0

💡 Enhancements 💡
  • pkg/exporterhelper: Add otelcol_exporter_in_flight_requests metric to track the number of export requests currently in-flight per exporter. (#​15009)
    This UpDownCounter increments in startOp and decrements in endOp, allowing operators to monitor
    concurrent export activity and detect when an exporter is saturating its worker pool.
🧰 Bug fixes 🧰
  • pkg/confighttp: Close the original request body after reading block-format Content-Encoding: snappy requests. (#​15262)

  • pkg/confighttp: Recover from panics in decompression libraries, return HTTP 400 instead of 500. (#​13228)

  • pkg/confighttp: Enforce max_request_body_size on Content-Encoding: snappy requests before the decoded buffer is allocated. (#​15252)

  • pkg/otelcol: Stop emitting verbose gRPC transport messages at WARN during normal client disconnect. (#​5169)
    grpc-go gates chatty per-RPC notices (e.g. "HandleStreams failed to read frame:
    connection reset by peer") behind LoggerV2.V(2). zapgrpc.Logger.V conflates
    grpclog verbosity with zap severity, so V(2) returns true whenever WARN is
    enabled and these messages emit at WARN. Wrap the installed grpclog.LoggerV2
    with a corrected V() that compares against a fixed verbosity threshold,
    matching grpclog's intended semantics. See uber-go/zap#1544.

  • pkg/pdata: pcommon.Value.AsString no longer HTML-escapes <, >, and & inside ValueTypeMap and ValueTypeSlice values, matching the behavior already used for ValueTypeStr. (#​14662)

  • pkg/service: Fix Prometheus config defaults mismatch when host is explicitly set in telemetry configuration. (#​13867)
    When users explicitly configured the telemetry metrics section (e.g. to change the host),
    the Prometheus exporter boolean fields (WithoutScopeInfo, WithoutUnits, WithoutTypeSuffix)
    defaulted to nil/false instead of true, causing metric name format changes compared to the
    implicit default configuration. This fix applies the correct defaults during config unmarshaling.

  • pkg/service: Return noop tracer provider when no trace processors are defined (#​15135)

v1.57.0

🛑 Breaking changes 🛑
  • cmd/builder: In the generated Collector source, the replace statements in the Go module will now use relative paths by default. (#​15097)
    We expect that this will not break existing use-cases where the generated collector is only used in an interim manner for builds. It enables the possibility of tracking the generated Collector code as a longer living artifact, allowing it to be run on any machine (whereas absolute paths will be different depending on the machine the Collector source is generated on.) We have added dist::use_absolute_replace_paths to go back to the absolute path behaviour in the case where there is an unforeseen use-case that requires absolute paths.

  • pkg/confighttp: Stabilize framedSnappy feature gate. (#​15096)

💡 Enhancements 💡
  • all: Add declarative schema support for service telemetry resource configuration. (#​14411)
    The service::telemetry::resource configuration now accepts the declarative schema with explicit name/value pairs:

    service:
      telemetry:
        resource:
          schema_url: https://opentelemetry.io/schemas/1.38.0
          attributes:
            - name: service.name
              value: my-collector
            - name: host.name
              value: collector-host

    The legacy inline attribute map format is still supported for backward compatibility:

    service:
      telemetry:
        resource:
          service.name: my-collector
          host.name: collector-host

    Note: resource.detectors is accepted for forward compatibility but is not yet applied by the collector.

  • exporter/otlp_grpc: Added the server.address and url.path attributes to metrics generated by the otlp exporter. (#​14998)

  • exporter/otlp_http: Added the server.address and url.path attributes to metrics generated by the otlp_http exporter. (#​14998)

  • pkg/config/configgrpc: Add UserAgent field to ClientConfig to allow overriding the default gRPC user-agent string. (#​14686)
    The otlp gRPC exporter was unconditionally setting the User-Agent via
    grpc.WithUserAgent() at dial time, which takes precedence over per-call
    metadata, causing any user-configured User-Agent to be silently discarded.
    A dedicated UserAgent field has been added to ClientConfig which, when
    set, is used in the dial option directly instead of the default BuildInfo-derived string.

  • pkg/config/configgrpc: Accept gRPC resolver scheme URIs in client endpoint (e.g. passthrough:///host:port) to allow control over name resolution (#​14990)
    After the migration to grpc.NewClient, some gRPC client components such as the OTLP
    exporter experienced connection issues in dual-stack DNS environments. This can now be
    fixed by using the passthrough:/// gRPC resolver scheme in the endpoint field.

  • pkg/config/confignet: Add support for Windows Named Pipe (npipe) transport (#​15085)

  • pkg/service: Emit a warning when using the old v0.2.0 declarative config format (#​15088)

🧰 Bug fixes 🧰
  • pkg/otelcol: Print components exactly once in the otelcol components command (#​14682)
    This resolves an issue where aliased components were skipped.

  • pkg/otelcol: Synchronize Collector Run and Shutdown lifecycles so that Shutdown blocks until Run completes all cleanup. (#​4947)
    Shutdown now blocks until Run finishes cleanup, matching http.Server semantics.
    If Shutdown is called before Run, the next Run call returns nil after cleaning up
    the config provider.

  • pkg/pdata: Use spec-compliant string representation for NaN, Infinity, and -Infinity in Value.AsString(). (#​14487)

  • pkg/pprofile: Fix data corruption of resource and scope attributes after marshal-unmarshal-merge round-trip. (#​15084)

  • pkg/service: Non-string resource attributes in telemetry configuration now return an error instead of panicking (#​15171)

  • pkg/xscraperhelper: fix the merge of profiles in the profiling scraper helpers (#​14790)

  • receiver/otlp: Fix profiles receiver reporting its samples as spans (#​15089)

v1.56.0

💡 Enhancements 💡
🧰 Bug fixes 🧰
  • exporter/debug: Guard from out of bounds profiles dictionary indices (#​14803)

  • pdata/pprofile: create a copy when the input is marked as read-only (#​15080)

  • pkg/otelcol: Fix missing default values in unredacted print-config command by introducing confmap.WithUnredacted MarshalOption. (#​14750)
    Resolves an issue where the unredacted mode output omitted all default-valued options. By introducing a new MarshalOption to disable redaction directly at the confmap encoding level, the unredacted mode now preserves all component defaults natively without requiring post-processing.

  • pkg/service: Headers on the internal telemetry OTLP exporter are now redacted when the configuration is marshaled (#​14756)

v1.55.0

🛑 Breaking changes 🛑
  • pkg/service: Remove service_name, service_instance_id, and service_version as constant labels on every internal metric datapoint. These attributes are already present in target_info and were being duplicated on each series for OpenCensus backwards compatibility. (#​14811)
    Previously, the collector stamped every internal metric series (e.g. otelcol_process_runtime_heap_alloc_bytes)
    with service_name, service_instance_id, and service_version labels to match the old OpenCensus behavior.
    These attributes are now only present in the target_info metric, which is the correct Prometheus/OTel convention.
    Users who filter or group by these labels on individual metrics will need to update their queries to use
    target_info joins instead.
💡 Enhancements 💡
  • all: Move aix/ppc64 to tier 3 support (#​13380)

  • all: Upgrade the profiles stability status to alpha (#​14817)
    The following components have their profiles status upgraded from development to alpha:

    • pdata/pprofile
    • connector/forward
    • exporter/debug
    • receiver/nop
    • exporter/nop
    • exporter/otlp_grpc
    • exporter/otlp_http
  • cmd/mdatagen: Add semconv reference for attributes (#​13297)

🧰 Bug fixes 🧰
  • cmd/mdatagen: Fix entity code generation so extra_attributes are emitted as resource attributes instead of entity descriptive attributes. (#​14778)

v1.54.0

❗ Known Issues ❗
  • service: The collector's internal Prometheus metrics endpoint (:8888) now emits OTel service labels with underscore
    names (service_name, service_instance_id, service_version) instead of dot-notation names (service.name,
    service.instance.id, service.version). Users scraping this endpoint with the Prometheus receiver will see these renamed
    labels in resource and datapoint attributes. As a workaround, add the following metric_relabel_configs to your scrape
    config in prometheus receiver:
    metric_relabel_configs:
      - source_labels: [service_name]
        target_label: service.name
      - source_labels: [service_instance_id]
        target_label: service.instance.id
      - source_labels: [service_version]
        target_label: service.version
      - regex: service_name|service_instance_id|service_version
        action: labeldrop
    See #​14814 for details and updates.
🛑 Breaking changes 🛑
  • all: Change metric units to be singular to match OTel specification, e.g. {requests} -> {request} (#​14753)
💡 Enhancements 💡
  • cmd/mdatagen: Add deprecated_type field to allow specifying an alias for component types. (#​14718)
  • cmd/mdatagen: Generate entity-scoped MetricsBuilder API that enforces entity-metric associations at compile time (#​14659)
  • cmd/mdatagen: Skip generating reaggregation config options for metrics that have no aggregatable attributes. (#​14689)
  • pkg/service: The internal status reporter no longer drops repeated Ok and RecoverableError statuses (#​14282)
    Status events can now carry metadata and there's value in allowing them to be emitted despite the status value itself
    not changing.
🧰 Bug fixes 🧰
  • cmd/builder: Add .exe to output binary names when building for Windows targets. (#​12591)

  • exporter/debug: Add printing of metric metadata in detailed verbosity. (#​14667)

  • exporter/otlp_grpc: Prevent nil pointer panic when push methods are called before the OTLP exporter initializes its gRPC clients. (#​14663)
    When the sending queue and retry are disabled, calling ConsumeTraces,
    ConsumeMetrics, ConsumeLogs, or ConsumeProfiles before the OTLP exporter
    initializes its gRPC clients could cause a nil pointer dereference panic.
    The push methods now return an error instead of panicking.

  • exporter/otlp_http: Show the actual destination URL in error messages when request URL is modified by middleware. (#​14673)
    Unwraps the *url.Error returned by http.Client.Do() to prevent misleading error logs when a middleware extension dynamically updates the endpoint.

  • pdata/pprofile: Switch the dictionary of dictionary tables entries only once when merging profiles (#​14709)
    For dictionary table data, we used to switch their dictionaries when doing
    the switch for the data that uses them.
    However, when an entry is associated with multiple other data (several
    samples can use the same stack), we would have been switching the
    dictionaries of the entry multiple times.

    We now switch dictionaries for dictionary table data only once, before
    switching the resource profiles.

v1.53.0

💡 Enhancements 💡
  • exporter/debug: Output bucket counts for exponential histogram data points in normal verbosity. (#​10463)
  • pkg/exporterhelper: Add metadata_keys configuration to sending_queue.batch.partition to partition batches by client metadata (#​14139)
    The metadata_keys configuration option is now available in the sending_queue.batch.partition section for all exporters.
    When specified, batches are partitioned based on the values of the listed metadata keys, allowing separate batching per metadata partition. This feature
    is automatically configured when using exporterhelper.WithQueue().
🧰 Bug fixes 🧰
  • cmd/builder: Fix duplicate error output when CLI command execution fails in the builder tool. (#​14436)

  • cmd/mdatagen: Fix duplicate error output when CLI command execution fails in the mdatagen tool. (#​14436)

  • cmd/mdatagen: Fix semconv URL validation for metrics with underscores in their names (#​14583)
    Metrics like system.disk.io_time now correctly validate against semantic convention URLs containing underscores in the anchor tag.

  • extension/memory_limiter: Use ChainUnaryInterceptor instead of UnaryInterceptor to allow multiple interceptors. (#​14634)
    If multiple extensions that use the UnaryInterceptor are set the binary panics at start time.

  • extension/memory_limiter: Add support for streaming services. (#​14634)

  • pkg/config/configmiddleware: Add context.Context to HTTP middleware interface constructors. (#​14523)
    This is a breaking API change for components that implement or use extensionmiddleware.

  • pkg/confmap: Fix another issue where configs could fail to decode when using interpolated values in string fields. (#​14034)
    For example, a resource attribute can be set via an environment variable to a string that is parseable as a number, e.g. 1234.

    (A similar bug was fixed in a previous release: that one was triggered when the field was nested in a struct,
    whereas this one is triggered when the field internally has type "pointer to string" rather than "string".)

  • pkg/otelcol: The featuregate subcommand now rejects extra positional arguments instead of silently ignoring them. (#​14554)

  • pkg/queuebatch: Fix data race in partition_batcher where resetTimer() was called outside mutex, causing concurrent timer.Reset() calls and unpredictable batch flush timing under load. (#​14491)

  • pkg/scraperhelper: Log scrapers now emit log-appropriate receiver telemetry (#​14654)
    Log scrapers previously emitted the same receiver telemetry as metric scrapers,
    such as the otelcol_receiver_accepted_metric_points metric (instead of otelcol_receiver_accepted_log_records),
    or spans named receiver/myreceiver/MetricsReceived (instead of receiver/myreceiver/LogsReceived).

    This did not affect scraper-specific spans and metrics.

  • processor/batch: Fixes a bug where the batch processor would not copy SchemaUrl metadata from resource and scope containers during partial batch splits. (#​12279, #​14620)

v1.52.0

v1.51.0

💡 Enhancements 💡
  • pkg/scraperhelper: ScraperID has been added to the logs for metrics, logs, and profiles (#​14461)
🧰 Bug fixes 🧰
  • exporter/otlp_grpc: Fix the OTLP exporter balancer to use round_robin by default, as intended. (#​14090)

  • pkg/config/configoptional: Fix Unmarshal methods not being called when config is wrapped inside Optional (#​14500)
    This bug notably manifested in the fact that the sending_queue::batch::sizer config for exporters
    stopped defaulting to sending_queue::sizer, which sometimes caused the wrong units to be used
    when configuring sending_queue::batch::min_size and max_size.

    As part of the fix, xconfmap exposes a new xconfmap.WithForceUnmarshaler option, to be used in the Unmarshal methods
    of wrapper types like configoptional.Optional to make sure the Unmarshal method of the inner type is called.

    The default behavior remains that calling conf.Unmarshal on the confmap.Conf passed as argument to an Unmarshal
    method will skip any top-level Unmarshal methods to avoid infinite recursion in standard use cases.

  • pkg/confmap: Fix an issue where configs could fail to decode when using interpolated values in string fields. (#​14413)
    For example, a header can be set via an environment variable to a string that is parseable as a number, e.g. 1234

  • pkg/service: Don't error on startup when process metrics are enabled on unsupported OSes (e.g. AIX) (#​14307)

v1.50.0

🛑 Breaking changes 🛑
  • pkg/exporterhelper: Change verbosity level for otelcol_exporter_queue_batch_send_size metric to detailed. (#​14278)
  • pkg/service: Remove deprecated telemetry.disableHighCardinalityMetrics feature gate. (#​14373)
  • pkg/service: Remove deprecated service.noopTracerProvider feature gate. (#​14374)
🚩 Deprecations 🚩
  • exporter/otlp_grpc: Rename otlp exporter to otlp_grpc exporter and add deprecated alias otlp. (#​14403)
  • exporter/otlp_http: Rename otlphttp exporter to otlp_http exporter and add deprecated alias otlphttp. (#​14396)
💡 Enhancements 💡
  • cmd/builder: Avoid duplicate CLI error logging in generated collector binaries by relying on cobra's error handling. (#​14317)

  • cmd/mdatagen: Add the ability to disable attributes at the metric level and re-aggregate data points based off of these new dimensions (#​10726)

  • cmd/mdatagen: Add optional display_name and description fields to metadata.yaml for human-readable component names (#​14114)
    The display_name field allows components to specify a human-readable name in metadata.yaml.
    When provided, this name is used as the title in generated README files.
    The description field allows components to include a brief description in generated README files.

  • cmd/mdatagen: Validate stability level for entities (#​14425)

  • pkg/xexporterhelper: Reenable batching for profiles (#​14313)

  • receiver/nop: add profiles signal support (#​14253)

🧰 Bug fixes 🧰
  • pkg/exporterhelper: Fix reference count bug in partition batcher (#​14444)

v1.49.0

💡 Enhancements 💡
  • all: Update semconv import to 1.38.0 (#​14305)
  • exporter/nop: Add profiles support to nop exporter (#​14331)
  • pkg/pdata: Optimize the size and pointer bytes for pdata structs (#​14339)
  • pkg/pdata: Avoid using interfaces/oneof like style for optional fields (#​14333)

v1.48.0

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

v1.47.0

🛑 Breaking changes 🛑
  • pkg/config/confighttp: Use configoptional.Optional for confighttp.ClientConfig.Cookies field (#​14021)
💡 Enhancements 💡
  • pkg/config/confighttp: Setting compression_algorithms to an empty list now disables automatic decompression, ignoring Content-Encoding (#​14131)
  • pkg/service: Update semantic conventions from internal telemetry to v1.37.0 (#​14232)
  • pkg/xscraper: Implement xscraper for Profiles. (#​13915)
🧰 Bug fixes 🧰
  • pkg/config/configoptional: Ensure that configoptional.None values resulting from unmarshaling are equivalent to configoptional.Optional zero value. (#​14218)

v1.46.0

💡 Enhancements 💡
  • cmd/mdatagen: metadata.yaml now supports an optional entities section to organize resource attributes into logical entities with identity and description attributes (#​14051)
    When entities are defined, mdatagen generates AssociateWith{EntityType}() methods on ResourceBuilder
    that associate resources with entity types using the entity refs API. The entities section is backward
    compatible - existing metadata.yaml files without entities continue to work as before.

  • cmd/mdatagen: Add semconv reference for metrics (#​13920)

  • connector/forward: Add support for Profiles to Profiles (#​14092)

  • exporter/debug: Disable sending queue by default (#​14138)
    The recently added sending queue configuration in Debug exporter was enabled by default and had a problematic default size of 1.
    This change disables the sending queue by default.
    Users can enable and configure the sending queue if needed.

  • pkg/config/configoptional: Mark configoptional.AddEnabledField as beta (#​14021)

  • pkg/otelcol: This feature has been improved and tested; secure-by-default redacts configopaque values (#​12369)

🧰 Bug fixes 🧰
  • all: Ensure service service.instance.id is the same for all the signals when it is autogenerated. (#​14140)

v1.45.0

🛑 Breaking changes 🛑
  • cmd/mdatagen: Make stability.level a required field for metrics (#​14070)

  • cmd/mdatagen: Replace optional field with requirement_level field for attributes in metadata schema (#​13913)
    The optional boolean field for attributes has been replaced with a requirement_level field that accepts enum values: required, conditionally_required, recommended, or opt_in.

    • required: attribute is always included and cannot be excluded
    • conditionally_required: attribute is included by default when certain conditions are met (replaces optional: true)
    • recommended: attribute is included by default but can be disabled via configuration (replaces optional: false)
    • opt_in: attribute is not included unless explicitly enabled in user config
      When requirement_level is not specified, it defaults to recommended.
  • pdata/pprofile: Remove deprecated PutAttribute helper method (#​14082)

  • pdata/pprofile: Remove deprecated PutLocation helper method (#​14082)

💡 Enhancements 💡
  • all: Add FIPS and non-FIPS implementations for allowed TLS curves (#​13990)
  • cmd/builder: Set CGO_ENABLED=0 by default, add the cgo_enabled configuration to enable it. (#​10028)
  • pkg/config/configgrpc: Errors of type status.Status returned from an Authenticator extension are being propagated as is to the upstream client. (#​14005)
  • pkg/config/configoptional: Adds new configoptional.AddEnabledField feature gate that allows users to explicitly disable a configoptional.Optional through a new enabled field. (#​14021)
  • pkg/exporterhelper: Replace usage of gogo proto for persistent queue metadata (#​14079)
  • pkg/pdata: Remove usage of gogo proto and generate the structs with pdatagen (#​14078)
🧰 Bug fixes 🧰
  • exporter/debug: add queue configuration (#​14101)

v1.44.0

🛑 Breaking changes 🛑
  • all: Remove deprecated type TracesConfig (#​14036)

  • pkg/exporterhelper: Add default values for sending_queue::batch configuration. (#​13766)
    Setting sending_queue::batch to an empty value now results in the same setup as the default batch processor configuration.

  • all: Add unified print-config command with mode support (redacted, unredacted), json support (unstable), and validation support. (#​11775)
    This replaces the print-initial-config command. See the service package README for more details. The original command name print-initial-config remains an alias, to be retired with the feature flag.

💡 Enhancements 💡
  • all: Add keep_alives_enabled option to ServerConfig to control HTTP keep-alives for all components that create an HTTP server. (#​13783)
  • pkg/otelcol: Avoid unnecessary mutex in collector logs, replace by atomic pointer (#​14008)
  • cmd/mdatagen: Add lint/ordering validation for metadata.yaml (#​13781)
  • pdata/xpdata: Refactor JSON marshaling and unmarshaling to use pcommon.Value instead of AnyValue. (#​13837)
  • pkg/exporterhelper: Expose MergeCtx in exporterhelper's queue batch settings` (#​13742)
🧰 Bug fixes 🧰
  • all: Fix zstd decoder data corruption due to decoder pooling for all components that create an HTTP server. (#​13954)
  • pkg/otelcol: Remove UB when taking internal logs and move them to the final zapcore.Core (#​14009)
    This can happen because of a race on accessing logsTaken.
  • pkg/confmap: Fix a potential race condition in confmap by closing the providers first. (#​14018)

v1.43.0

💡 Enhancements 💡
  • cmd/mdatagen: Improve validation for resource attribute enabled field in metadata files (#​12722)
    Resource attributes now require an explicit enabled field in metadata.yaml files, while regular attributes
    are prohibited from having this field. This improves validation and prevents configuration errors.

  • all: Changelog entries will now have their component field checked against a list of valid components. (#​13924)
    This will ensure a more standardized changelog format which makes it easier to parse.

  • pkg/pdata: Mark featuregate pdata.useCustomProtoEncoding as stable (#​13883)

v1.42.0

💡 Enhancements 💡
  • xpdata: Add Serialization and Deserialization of AnyValue (#​12826)
  • debugexporter: add support for batching (#​13791)
    The default queue size is 1
  • configtls: Add early validation for TLS server configurations to fail fast when certificates are missing instead of failing at runtime. (#​13130, #​13245)
  • mdatagen: Expose stability level in generated metric documentation (#​13748)
  • internal/tools: Add support for modernize in Makefile (#​13796)
🧰 Bug fixes 🧰
  • otelcol: Fix a potential deadlock during collector shutdown. (#​13740)
  • otlpexporter: fix the validation of unix socket endpoints (#​13826)

v1.41.0

💡 Enhancements 💡
  • exporterhelper: Add new exporter_queue_batch_send_size and exporter_queue_batch_send_size_bytes metrics, showing the size of telemetry batches from the exporter. (#​12894)

v1.40.0

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

v1.39.0

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

v1.38.0

🛑 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 interest in
    #​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)

v1.37.0

🛑 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](https://redirect.github.com/open-telem

Configuration

📅 Schedule: Branch creation - "every weekend" (UTC), 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

To execute skipped test pipelines write comment /ok-to-test.


Documentation

Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.

…59.0

Signed-off-by: red-hat-konflux-kflux-prd-rh02 <190377777+red-hat-konflux-kflux-prd-rh02[bot]@users.noreply.github.com>
@red-hat-konflux-kflux-prd-rh02 red-hat-konflux-kflux-prd-rh02 Bot added docs-approved Signifies that Docs has signed off on this PR ok-to-test Indicates a non-member PR verified by an org member that is safe to test. px-approved Signifies that Product Support has signed off on this PR qe-approved Signifies that QE has signed off on this PR labels May 30, 2026
@red-hat-konflux-kflux-prd-rh02
Copy link
Copy Markdown
Contributor Author

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

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

Details:

Package Change
go 1.22.0 -> 1.25.0
github.com/go-logr/logr v1.4.2 -> v1.4.3
github.com/stretchr/testify v1.9.0 -> v1.11.1
golang.org/x/mod v0.21.0 -> v0.35.0
golang.org/x/net v0.28.0 -> v0.55.0
github.com/google/go-cmp v0.6.0 -> v0.7.0
github.com/modern-go/reflect2 v1.0.2 -> v1.0.3-0.20250322232337-35a7c28c31ee
go.opentelemetry.io/otel v1.28.0 -> v1.43.0
go.opentelemetry.io/otel/metric v1.28.0 -> v1.43.0
go.opentelemetry.io/otel/trace v1.28.0 -> v1.43.0
golang.org/x/crypto v0.26.0 -> v0.51.0
golang.org/x/oauth2 v0.22.0 -> v0.36.0
golang.org/x/sync v0.8.0 -> v0.20.0
golang.org/x/sys v0.24.0 -> v0.45.0
golang.org/x/term v0.23.0 -> v0.43.0
golang.org/x/text v0.17.0 -> v0.37.0
golang.org/x/tools v0.24.0 -> v0.44.0
google.golang.org/genproto/googleapis/rpc v0.0.0-20240708141625-4ad9e859172b -> v0.0.0-20260226221140-a57be14db171
google.golang.org/grpc v1.65.0 -> v1.81.1
google.golang.org/protobuf v1.34.2 -> v1.36.11

@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 30, 2026

Hi @red-hat-konflux-kflux-prd-rh02[bot]. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@openshift-ci openshift-ci Bot requested review from Vincent056 and yuumasato May 30, 2026 08:23
@openshift-ci
Copy link
Copy Markdown
Contributor

openshift-ci Bot commented May 30, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: red-hat-konflux-kflux-prd-rh02[bot]
Once this PR has been reviewed and has the lgtm label, please assign rhmdnd for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@red-hat-konflux-kflux-prd-rh02 red-hat-konflux-kflux-prd-rh02 Bot changed the title chore(deps): update module go.opentelemetry.io/collector/pdata to v1.59.0 Update module go.opentelemetry.io/collector/pdata to v1.59.0 May 30, 2026
@red-hat-konflux-kflux-prd-rh02 red-hat-konflux-kflux-prd-rh02 Bot changed the title Update module go.opentelemetry.io/collector/pdata to v1.59.0 chore(deps): update module go.opentelemetry.io/collector/pdata to v1.59.0 May 30, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs-approved Signifies that Docs has signed off on this PR ok-to-test Indicates a non-member PR verified by an org member that is safe to test. px-approved Signifies that Product Support has signed off on this PR qe-approved Signifies that QE has signed off on this PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants