Update module github.com/open-telemetry/opentelemetry-collector-contrib/processor/deltatocumulativeprocessor to v0.156.0

[red-hat-konflux-kflux-prd-rh02]

ℹ️ Note

This PR body was truncated due to platform limits.

This PR contains the following updates:

Package	Change	Age	Confidence
github.com/open-telemetry/opentelemetry-collector-contrib/processor/deltatocumulativeprocessor	v0.150.0 → v0.156.0

---

Warning

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

---

Release Notes

open-telemetry/opentelemetry-collector-contrib (github.com/open-telemetry/opentelemetry-collector-contrib/processor/deltatocumulativeprocessor)

v0.156.0

Compare Source

🛑 Breaking changes 🛑

• pkg/fileconsumer: Move feature gate filelog.protobufCheckpointEncoding to beta and keep it enabled by default (#​49387)

• receiver/oracledb: Enhanced Oracle SQL query plan details with runtime execution statistics. (#​49329)
  This change requires the collector user to have access to V$SQL_PLAN_STATISTICS_ALL. Existing deployments that only grant access to V$SQL_PLAN
  may experience query plan collection failures until the appropriate privileges are granted.

  SQL query plan details are now retrieved from V$SQL_PLAN_STATISTICS_ALL instead of V$SQL_PLAN. Since V$SQL_PLAN_STATISTICS_ALL is a superset of V$SQL_PLAN,
  this change is backward compatible with respect to the emitted plan detail fields while enabling collection of additional runtime execution statistics,
  including OUTPUT_ROWS, LAST_OUTPUT_ROWS, LAST_ELAPSED_TIME, LAST_CR_BUFFER_GETS, LAST_CU_BUFFER_GETS, STARTS, and LAST_STARTS.

🚩 Deprecations 🚩

• connector/routing: Deprecate the request context in favor of otelcol.* OTTL paths. (#​44762)
  The routing connector request context and request["key"] condition syntax are deprecated in favor of
  otelcol.client.metadata["key"][0] for HTTP/client metadata and otelcol.grpc.metadata["key"][0] for gRPC metadata.
  These paths work in all signal contexts and are documented in the OTelCol OTTL context.
  A warning is logged when the request context is still configured.

• exporter/datadog: The exporter.datadogexporter.metricremappingdisabled feature gate no longer has any effect when the serializer exporter path is active (the default). Use exporter.datadogexporter.DisableAllMetricRemapping to disable metric remapping. (#​49320)
  See DataDog/datadog-agent#51232.

• receiver/aws_cloudwatch: rename to aws_cloudwatch with deprecated alias awscloudwatch (#​45339)

🚀 New components 🚀

• processor/dynamic_sampling: Add dynamic sampling processor for adaptive trace sampling with W3C TraceState rate encoding. (#​48898)

💡 Enhancements 💡

• cmd/opampsupervisor: Make the OpAMP Supervisor logger encoding configurable so it can emit console (plain-text) logs as well as JSON (#​47532)

• connector/routing: Add OTTL context inference support to routing connector. (#​38080)
  The routing connector now supports OTTL context inference, allowing users to write clearer routing conditions using
  context-qualified paths. Instead of relying on implicit context resolution, users can explicitly specify which
  context's attributes they want to access (e.g., resource.attributes["env"] or span.attributes["http.method"]).
  Unqualified paths like attributes["key"] continue to work and default to the resource context for backward compatibility.

• exporter/alibabacloud_logservice: Add security_token (STS) support alongside AK/SK; preserve ECS role/token-file fallback. (#​48624)
  When security_token is provided in the exporter configuration the SDK is
  configured to use static STS credentials via the provider. The existing
  ecs_ram_role and token_file_path behavior remains the higher-priority
  authentication method and is unchanged.

• exporter/clickhouse: Add experimental support for the profiles signal (#​49304)

• exporter/datadog: Emit otel.datadog_exporter.metrics.running.fargate{task_arn} for AWS ECS Fargate workloads so that each workload has its own metric. (#​49042)
  Host-based workloads continue to use otel.datadog_exporter.metrics.running{host} unchanged.
  otel.datadog_exporter.metrics.running will no longer be tagged with task_arn. Fargate workloads will only use otel.datadog_exporter.metrics.running.fargate{task_arn}.

• exporter/datadog: Fargate workloads now emit a dedicated otel.datadog_exporter.metrics.running.fargate metric tagged with task_arn instead of sharing otel.datadog_exporter.metrics.running with host-based workloads. (#​49320)
  Host-based workloads continue to emit otel.datadog_exporter.metrics.running{host} unchanged.
  See DataDog/datadog-agent#52203.

• exporter/elasticsearch: Support routing from data_stream attributes defined as scope attributes (#​49306)

• extension/azure_auth: Promote the Azure Authenticator extension to beta stability. (#​48521)

• extension/file_storage: Added max_size support to the filestorage extension to cap per-component database growth. (#​38620)

• extension/sigv4auth: Add automatic service detection for CloudWatch OTLP metrics endpoint (monitoring..amazonaws.com) (#​48738)

• pkg/translator/pprof: reduce allocations in sample conversion (#​49452)

• processor/transform: Add exemplar context support to the transform processor, allowing metric_statements to read and modify exemplar fields on metric datapoints. (#​49022)

• receiver/aws_lambda: Add support for AWS configuration overrides for static credentials (#​49163)

• receiver/faro: Emit per-payload counters for ingested Faro logs, measurements, exceptions, and events (#​48071)
  Adds otelcol_faro_log_ingested_total, otelcol_faro_measurement_ingested_total,
  otelcol_faro_exception_ingested_total, and otelcol_faro_event_ingested_total. Each
  counter is incremented by the number of entries in the corresponding
  payload section after the request body is parsed.

• receiver/mongodb: Add Query Sample collection to the MongoDB receiver, emitting a db.server.query_sample log event for each currently executing operation. (#​48573)
  Samples are collected via $currentOp, with idle connections and administrative commands
  filtered out. Each event includes obfuscated query text and operation metadata.
  The logs signal is at development stability; attribute names may change until OTel
  db.server.query_sample conventions stabilize. The metrics signal remains at beta.

• receiver/oracledb: Add service.name and service.namespace opt-in resource attributes and allow overriding any resource attribute via override_value. (#​47088)

• receiver/oracledb: Add workload analysis metrics related to scans, enqueue, LOB, parse, sort, cursor, and session activity (#​48808)
  Adds fourteen new opt-in metrics (disabled by default):

  • oracledb.call.count, oracledb.call.recursive.cpu.time
  • oracledb.cursor.cache.hits, oracledb.cursor.cache.size, oracledb.cursor.open
  • oracledb.db.time
  • oracledb.enqueue.operations
  • oracledb.lob.operations
  • oracledb.parse.cpu.time, oracledb.parse.elapsed.time
  • oracledb.scan.count, oracledb.scan.table.rows
  • oracledb.sort.operations, oracledb.sort.rows
    No new SQL queries are issued; the existing v$sysstat scrape already returns
    all required rows, so the receiver adds no additional load on the monitored
    Oracle instance.

• receiver/oracledb: Add buffer cache and Database Writer (DBWR) metrics (#​49061)

• receiver/oracledb: Add redo log metrics (#​49060)

• receiver/postgresql: Add default service.name and service.namespace resource attributes (#​47087)
  Both attributes default to enabled: false. When enabled, service.name
  defaults to unknown_service:postgresql and service.namespace defaults
  to an empty string. Additionally, override_value is enabled for all
  resource attributes, allowing users to set custom values via
  override_value in the collector configuration.

• receiver/postgresql: Adds blocking session and lock attributes to db.server.query_sample events for PostgreSQL blocking session detection. Blocking attributes are always emitted (empty string / 0 when not blocked). (#​49028)
  New attributes under postgresql.blocking.*: postgresql.blocking.pids, postgresql.blocking.start_time,
  postgresql.blocking.wait_duration, postgresql.blocking.lock.mode, postgresql.blocking.lock.type,
  postgresql.blocking.lock.relation, postgresql.blocking.transaction.start_time.
  postgresql.blocking.pids contains the full array of blocking PIDs from pg_blocking_pids() (e.g. {5121,5122}).
  postgresql.blocking.start_time uses pg_locks.waitstart (PostgreSQL 14+) to record when the lock wait began. waitstart is stable for the full duration of the wait — it is set once when the lock wait starts and is not affected by blockers joining or leaving.
  postgresql.blocking.transaction.start_time provides a UTC timestamp (RFC3339) from xact_start representing when the transaction started, predating the lock contention itself.
  Idle-in-transaction blocker sessions (holding locks without an active request) are captured via pg_blocking_pids subquery in the WHERE clause.
  All blocking attributes are always present on every db.server.query_sample event; empty string / 0 values indicate no active blocking.
  Requires PostgreSQL 14 or later.

• receiver/prometheus: Promote receiver.prometheusreceiver.IgnoreScopeInfoMetric feature gate to beta. (#​47312)
  The otel_scope_info metric is now ignored for scope attribute extraction by default.
  To temporarily restore the previous behavior, disable the feature gate with --feature-gates=-receiver.prometheusreceiver.IgnoreScopeInfoMetric.

• receiver/sqlserver: Add access methods and buffer pool metrics (#​49182)
  Adds the following metrics, all disabled by default:

  • sqlserver.access.scan.rate
  • sqlserver.extent.operation.rate
  • sqlserver.ghost_record.skipped.rate
  • sqlserver.page.allocation.rate
  • sqlserver.page.compression.rate
  • sqlserver.page.read_ahead.rate
  • sqlserver.scan_point.revalidation.rate
  • sqlserver.worktable.cache.hit_ratio

• receiver/syslog: Add support for RFC6587 Octet Counting framing with RFC3164 message format. (#​45216)

🧰 Bug fixes 🧰

• connector/routing: Fix duplicate routing table entry handling to correctly ignore duplicates instead of overwriting the original route (#​44762)
  Previously, when duplicate routing table entries were encountered, the warning message indicated that the duplicate
  would be ignored, but in fact the original entry was being overwritten by the duplicate.
  This fix ensures that duplicates are properly ignored and the original route's consumer is preserved.

• exporter/awsxray: Use local service name for Consumer local root segment names, falling back to resource service name when aws.local.service is absent. (#​43432)
  Consumer spans promoted to X-Ray Segments after #​42633 were named
  using the span (operation) name instead of the local service name.
  The fix mirrors the existing Server span naming behavior.

• exporter/datadog: Compress the metric sketches payload with gzip in the legacy metric API client, matching the metric series payload. Previously sketches were sent uncompressed, increasing egress for distribution/histogram metrics. (#​49313)

• exporter/datadog: Fix CPU core count fields (cpu_cores, cpu_logical_processors) missing from host metadata payloads for remote hosts in OTel gateway topologies. (#​49320)
  CPU data arrives via system.cpu.physical.count / system.cpu.logical.count metrics and was never
  forwarded to the host metadata reporter in the serializer exporter path.
  See DataDog/datadog-agent#51893.

• exporter/datadog: Fix host metadata collection no longer aborts the entire batch when one resource fails; errors are accumulated and processing continues for remaining resources (#​49153)
  See DataDog/datadog-agent#51893.

• exporter/datadog: Metrics from the Podman stats receiver now report the correct Datadog metric origin (opentelemetry_collector_podmanreceiver) instead of falling through to opentelemetry_collector_unknown. (#​49320)
  See DataDog/datadog-agent#52594.

• exporter/file: Fix path traversal vulnerability on Windows when using grouping file exporter (#​49194)

• exporter/opensearch: Preserve LogRecord EventName field in all log encoding modes. (#​49314)

• extension/datadog: Skip cloud metadata source provider probe when hostname is already set in config, avoiding spurious GCP metadata server requests on non-GCP hosts. (#​49241)

• pkg/translator/pprof: Wrong conversion of labels from pprof to OTLP profiles (#​49449)

• processor/cumulativetodelta: Align reset detection and dropping on histograms and exponential histograms (#​48278)
  Histograms and exponential histograms where there is a drop in total count or on any bucket counts are now treated as a reset and dropped.

• processor/cumulativetodelta: Fix non-deterministic order of valid metric types in error messages for invalid metric_types config values. (#​49120)

• processor/gen_ai_normalizer: Fix OpenInference message normalization for flattened indexed attributes (#​48421)
  Reconstruct gen_ai.input.messages and gen_ai.output.messages from
  OpenInference flattened indexed span attributes
  (llm.{input,output}_messages.N.message.*).

• processor/k8s_attributes: Fix cache key memory leak in k8sattributesprocessor when a Pod's IP is missing or cleared from the delete event (#​48986)
  When a Pod is deleted, if its IP address is missing or already cleared from the delete event status,
  the processor now looks up the cached pod by its UID to retrieve the stored IP and correctly queue
  all associated keys for deletion.

• processor/resource_detection: Fix Docker resource detection failing to start when optional resource attributes are disabled, including container attributes when the hostname does not match a Docker container name. (#​46275)

• processor/spanpruning: Fix non-deterministic depth of preserved outlier spans by grouping leaves and parents by tree depth, so same-named ancestors at different depths are no longer merged. (#​49323)

• receiver/aws_cloudwatch: Fix logs being skipped when AWS pagination returns an empty page (#​48577)

• receiver/github: Capture the datapoint timestamp per repository instead of once at scrape start, so per-repository metrics carry a timestamp close to when each repository was observed. (#​48497)

• receiver/prometheus: Prometheus API server config/targets stay in sync with Target Allocator changing it if both are enabled. (#​48040)
  Previously, the API server config and targets did not get the updates from the Target Allocator.

• receiver/tcp_log: Fix tcp input operator emitting partial log data after a connection read error when one_log_per_packet is enabled (#​49199)
  Previously, if a TCP connection was reset mid-read while one_log_per_packet
  was set to true, the partial buffer was still processed and emitted as a log
  entry. Now the read error causes the message to be discarded instead.

v0.155.0

Compare Source

🛑 Breaking changes 🛑

• all: Move cmd/schemagen to opentelemetry-collector as go.opentelemetry.io/collector/cmd/schemagen. (#​14543)
  The schemagen CLI now lives in the opentelemetry-collector repository. Existing make schemagen and
  make generate-schemas targets continue to work — they now invoke the tool via
  go run go.opentelemetry.io/collector/cmd/schemagen@latest. Override the new SCHEMAGEN_PKG variable
  to pin a specific release. Downstream users that previously imported
  github.com/open-telemetry/opentelemetry-collector-contrib/cmd/schemagen must update their import path
  to go.opentelemetry.io/collector/cmd/schemagen.

• exporter/signalfx: Stop calculating per-core cpu.* metrics disabled by default. (#​49247)
  The default transformations still create aggregate CPU metrics. However, per-core cpu.* metrics which are disabled by default aren't produced by the default transformations anymore.
  This change doesn't have any impact unless any of cpu.* metrics are explicitly enabled with the cpu attribute in signalfx exporter with configuration like this:

  exporters:
    signalfx:
      include_metrics:
        - metric_name: cpu.idle
          dimensions:
            cpu: ["*"]

  In that case, the same metrics can be restore by applying the transform processor the following way:

  receivers:
    hostmetrics:
      scrapers:
        cpu:
          metrics:
            system.cpu.time:
              enabled: true
              attributes: [cpu, state]
  processors:
    transform/cpu_idle_per_core:
      error_mode: ignore
      metric_statements:
        - context: metric
          statements:
            - copy_metric(name="cpu.idle") where metric.name == "system.cpu.time"
        - context: datapoint
          statements:
            - set(datapoint.value_double, 0.0) where metric.name == "cpu.idle" and datapoint.attributes["state"] != "idle"
        - context: metric
          statements:
            - aggregate_on_attributes("sum", ["cpu"]) where metric.name == "cpu.idle"
            - scale_metric(100.0) where metric.name == "cpu.idle"
        - context: datapoint
          statements:
            - set(datapoint.value_int, Int(datapoint.value_double)) where metric.name == "cpu.idle"
  service:
    pipelines:
      metrics:
        receivers: [hostmetrics]
        processors: [transform/cpu_idle_per_core]
        exporters: [signalfx]

• exporter/signalfx: Stop calculating cpu.utilization_per_core disabled by default. (#​49243)
  The exporter still creates the aggregate cpu.utilization metric by default. However, cpu.utilization_per_core which is disabled by default isn't produced by the default transformations anymore.
  This change doesn't have any impact unless cpu.utilization_per_core metric is explicitly enabled in signalfx exporter with configuration like this:

  exporters:
    signalfx:
      include_metrics:
        - metric_name: cpu.utilization_per_core

  In that case, the same metric can be restore by applying the transform processor the following way:

  receivers:
    hostmetrics:
      scrapers:
        cpu:
          metrics:
            system.cpu.utilization:
              enabled: true
              attributes: [cpu, state]
  processors:
    transform/cpu_utilization_per_core:
      error_mode: ignore
      metric_statements:
        - context: metric
          statements:
            - set(metric.name, "cpu.utilization_per_core") where metric.name == "system.cpu.utilization"
        - context: datapoint
          statements:
            - set(datapoint.value_double, 0.0) where metric.name == "cpu.utilization_per_core" and datapoint.attributes["state"] == "idle"
        - context: metric
          statements:
            - aggregate_on_attributes("sum", ["cpu"]) where metric.name == "cpu.utilization_per_core"
  service:
    pipelines:
      metrics:
        receivers: [hostmetrics]
        processors: [transform/cpu_utilization_per_core]
        exporters: [signalfx]

• pkg/fileconsumer: Remove stable gate filelog.decompressFingerprint (#​48980)

• processor/k8s_attributes: Remove deprecated gate k8sattr.labelsAnnotationsSingular.allow (#​48977)

• processor/tail_sampling: Remove stable gate processor.tailsamplingprocessor.disableinvertdecisions (#​48976)

• receiver/datadog: Enhance Datadog logs support (#​49102)
  Logs are now translated to the OpenTelemetry data model instead of being emitted as flat string
  attributes: the record timestamp/observed timestamp are set (converting Datadog epoch-milliseconds
  to nanoseconds), status maps to the severity number/text, hostname/service and known ddtags
  are promoted to resource attributes, and dd.trace_id/dd.span_id populate TraceID/SpanID for
  trace correlation (reconstructing full 128-bit trace ids from _dd.p.tid the same way spans do).
  A new logs::decode_json_message option (enabled by default) expands JSON-encoded log messages
  forwarded by the Datadog Agent, lifting their reserved fields and attributes into the log record.

• receiver/datadog: Enable the receiver.datadogreceiver.Enable128BitTraceID feature gate by default (#​49103)
  The gate is promoted from alpha to beta (on by default), so spans reconstruct full 128-bit trace ids
  from _dd.p.tid and emit OpenTelemetry-native trace ids that correlate with other OpenTelemetry
  services. Disable the gate to fall back to 64-bit (zero-padded) trace ids.

• receiver/mongodb: Minimum supported MongoDB version is now 4.4. (#​49248)
  MongoDB 4.0 reached end-of-life in April 2022 and is no longer supported by the Go MongoDB driver v2.7.0+,
  which raised the minimum required wire protocol version. Users still on MongoDB 4.0 must upgrade to at
  least MongoDB 4.4 before upgrading to this version of the receiver.

• receiver/oracledb: Set db.namespace to database name and add oracle.db.service attribute on query sample and top query events. (#​48996)
  On db.server.query_sample and db.server.top_query events, db.namespace
  now reports the database name instead of the Oracle service
  name. The service name moves to the new oracle.db.service attribute.

🚩 Deprecations 🚩

• connector/service_graph: Deprecate the legacy servicegraph connector latency metric names and millisecond latency unit feature gates, and mark the virtual node feature gate as stable. (#​49215)
• receiver/flink_metrics: Rename receiver type from flinkmetrics to flink_metrics (#​45339)
• receiver/splunk_enterprise: Rename receiver type from splunkenterprise to splunk_enterprise (#​45339)

🚀 New components 🚀

• processor/cardinality_guardian: Promote the cardinalityguardian processor to alpha stability and include it in the contrib distribution. (#​47368)
• receiver/active_directory_inv: Add Windows Active Directory Inventory receiver for collecting inventory data from Active Directory. (#​48733)

💡 Enhancements 💡

• cmd/opampsupervisor: Allow Supervisor to configure its managed OpAMP extension config to include Collector resource attributes (#​48536)

• connector/routing: Add connector.routing.defaultErrorModeIgnore feature gate to change default error_mode from propagate to ignore (#​48418)

• exporter/awsxray: Migrate http.status_code (v1.25.0) semantic convention to http.response.status_code (v1.40.0) (#​45058)

• exporter/awsxray: Migrate container.image.tag (v1.21.0) semantic convention to container.image.tags (v1.40.0) (#​45057)

• exporter/azure_blob: Add support for gzip and zstd compression to the Azure Blob Storage exporter. The compression config option is now supported and the appropriate file extension is added to blob names. (#​45338)
  This mirrors the compression support added to the Google Cloud Storage exporter in commit 6fd0eb6. Compression is applied to the marshaled data before upload (including append blocks). Tests and documentation updated.

• exporter/elasticsearch: Extract span events as separate ECS log documents in ECS mapping mode (#​49181)
  In ECS mapping mode, exception span events are routed to logs-apm.error-* and all other
  span events to logs-apm.app.<service>-*, with OTel exception attributes mapped to
  their correct nested ECS paths (error.exception.type, error.exception.message,
  error.stack_trace).

• exporter/file: Add feature gate for native file-level compression in file exporter (#​44077)
  A new alpha feature gate exporter.file.nativeCompression enables native file-level zstd compression.
  When enabled, the exporter produces standard .zst files that can be decompressed with zstd -d,
  unlike the legacy per-message compression format which requires custom tooling.

• exporter/google_cloud_storage: Add universe_domain config option to support Sovereign Google Cloud regions. Setting this field passes option.WithUniverseDomain to the underlying Google API client. (#​48924)

• exporter/google_cloud_storage: Add resource_attrs_to_gcs to partition objects by a resource attribute value. (#​49136)
  When resource_attrs_to_gcs.prefix is set, the value of the given resource attribute
  (read from the first resource of each batch) is inserted as a partition path segment
  between bucket.partition.prefix and the time-based bucket.partition.format, mirroring
  the awss3exporter resource_attrs_to_s3 behavior.

• exporter/googlecloudpubsub: Add universe_domain config option to support Sovereign Google Cloud regions. Setting this field passes option.WithUniverseDomain to the underlying Google API client. (#​48924)

• exporter/kafka: Add producer.max_broker_write_bytes config (#​47492)
  The maximum size of a single write to a broker was previously fixed at the underlying
  franz-go default of 100 MiB and could not be configured. As a result, setting
  producer.max_message_bytes above 100 MiB passed configuration validation but caused the
  collector to fail on startup with an unrecoverable error ("max broker write bytes ... is
  erroneously less than max record batch bytes ...").

  The new producer.max_broker_write_bytes setting (default 1048576, i.e. 100 MiB) exposes
  this limit. To send messages larger than 100 MiB, raise it so it is greater than or equal to
  max_message_bytes. Configuration is now validated up front: the collector reports a clear
  error if max_broker_write_bytes is below the 100 MiB minimum or smaller than
  max_message_bytes, rather than failing at runtime.

• exporter/load_balancing: Reduce CPU usage and memory allocations when routing traces by traceID (the default routing key) (#​48983)
  Routing decisions are unchanged. Spans are now regrouped per backend, so the exact
  ResourceSpans/ScopeSpans grouping of exported traces may differ from the input. If a downstream
  consumer is sensitive to this, a groupbyattrsprocessor on the receiving end can recompact the
  ResourceSpans.

• exporter/splunk_hec: Support exporting profiles (#​48598)

• extension/azure_encoding: Map schemaVersion and resourceType fields of Azure Storage Blob logs to azure.storage.schema_version and azure.resource.type. (#​48753)

• extension/azure_encoding: Support statusMessage on Administrative Activity Logs (#​48932)
  The properties.statusMessage field on Azure Administrative activity logs is now
  parsed. When it contains JSON (the common case for VM ScaleSet operations etc.),
  the structured object is stored under the azure.administrative.status_message
  attribute. Plain-string values are stored as-is.

• pkg/coreinternal: Migrate messaging.destination (v1.16.0) semantic convention to messaging.destination.name (v1.40.0) (#​45077)

• pkg/coreinternal: Migrate semantic conventions from v1.18.0 to v1.40.0 (#​45293)
  Introduced feature gates for the migration of two deprecated semantic conventions:

  • FaaS Execution (faas.execution): Added internal.coreinternal.goldendataset.EmitV1FaaSConventions to opt-in to the new faas.invocation_id attribute.
  • HTTP User Agent (http.user_agent): Added internal.coreinternal.goldendataset.EmitV1HTTPConventions to opt-in to the new user_agent.original attribute.

• pkg/coreinternal: Improved strptime compatibility for time parsing (#​43842)
  Time parsing interfaces (such as the OTTL Time function and the
  timestamp operator) accept strptime-style format strings. This
  PR makes several changes to the parsing logic to better match the
  behavior of strptime. (Most notably, leading zeros are now
  optional for numbers, whitespace is ignored before most elements,
  and more ISO 8601 timezone formats are accepted for %z.)

• pkg/faro: Migrate deployment.environment (v1.26.0) semantic convention to deployment.environment.name (v1.40.0) (#​45074)

• pkg/ottl: Add stringify_all editor that converts all non-string values in a map to their string representation (#​48044)

• pkg/ottl: Add support for dynamic keys in converters results. (#​48834)
  Converter results can now be indexed with dynamic keys expressions that evaluate to a string or integer.
  For example: Split(...)[Len(attributes["items"])] or Split(...)[attributes["index"]].
  Previously, only literal keys (e.g. [0] or ["index"]) were supported.

• pkg/translator/pprof: Add support for OTel Profiles to pprof conversion across all three message Sample value/timestamp combinations (#​48864)

• pkg/zipkin: Migrated semantic convention from v1.18.0 to v1.40.0 (#​45080)

• processor/coralogix: Add critical path trace annotations. (#​48824)
  New critical_path.enabled config computes and writes span attributes cgx.critical_path.is_on_path, cgx.critical_path.exclusive_duration_ns, and cgx.critical_path.inclusive_duration_ns.
  Feature expects complete traces, so groupbytrace should run before coralogixprocessor in the pipeline.
  Example:
  processors: coralogix: critical_path: enabled: true

• processor/geoip: Add error_mode configuration option to control how geolocation lookup errors are handled. (#​35069)
  The error_mode option supports propagate (default, preserves existing behavior),
  ignore (logs the error and continues), and silent (continues without logging).

• processor/log_dedup: Add metadata_keys and metadata_cardinality_limit options to support multi-tenant pipelines by aggregating logs into separate buckets per unique metadata combination and preserving request context for downstream extensions. (#​47521)

• processor/resource_detection: Add GCP Cloud Run Worker Pool detector to the resource detection processor (#​48931)

• processor/schema: Add support for the Schema v2 file formats (manifest/2.0 and resolved/2.0) defined by OTEP (#​48189)
  The processor now auto-detects the schema document format via the file_format
  field and dispatches to a v1.1 or v2 code path accordingly. When the schema URL
  serves a manifest/2.0, the processor follows resolved_registry_uri through
  the existing provider chain (so caching, retry, and storage all apply to both
  fetches) and constructs a single-hop translator from the resolved registry.
  Renames are extracted from deprecated.renamed_to entries in
  attribute_catalog and registry.{metrics,spans,events}. diff/2.0 and
  definition/2 are recognised but not yet supported.

• processor/spanpruning: Add duration outlier detection, attribute correlation, and outlier preservation to span aggregation (#​48984)
  Enabled with enable_outlier_analysis and configured via outlier_analysis.*. Detects slow spans within
  an aggregation group using IQR (default) or MAD, reports attribute values correlated with outliers, and can
  optionally preserve outliers as individual spans instead of aggregating them. Adds the
  processor_spanpruning_outliers_detected, processor_spanpruning_outliers_preserved, and
  processor_spanpruning_outliers_correlations_detected metrics. Behavior is unchanged when disabled.

• processor/transform: Improve merge_histogram_buckets with method="limit_buckets" to compact buckets closer to the configured limit. (#​49020)

• processor/transformprocessor/internal/logparsingfuncs: Add ParseLEEF function to parse Log Event Extended Format (LEEF) messages. (#​44908)

• processor/transformprocessor/internal/logparsingfuncs: Add ParseCLF function for parsing Common Log Format (CLF) HTTP access log entries. (#​48349)
  ParseCLF is available in log statements and returns a map with the parsed
  clf.remote_host, clf.rfc931, clf.auth_user, clf.timestamp, clf.request,
  clf.method, clf.request_uri, clf.protocol, clf.status, and clf.bytes
  fields. An optional format parameter selects between the strict "clf" format
  (default) and the NCSA "combined" format, which additionally parses
  clf.referer and clf.user_agent.

• receiver/aws_lambda: Introduce Custom Handler support for AWS Lambda Receiver. The custom handler allows the receiver to bind a signal-agnostic extension. (#​49160)

• receiver/awscloudwatch: Adds a new configuration option initial_lookback to the AWS CloudWatch Logs receiver for specifying how far back from the collector's startup time to begin collecting logs. (#​47754)

• receiver/azure_event_hub: Add the ability to use encoding extensions to the Azure Event Hub receiver. (#​48753)

• receiver/datadog: Support zstd-compressed request payloads (#​49101)
  Recent Datadog Agents (7.59+) zstd-compress HTTP payloads by default. The receiver now decompresses
  both gzip and zstd request bodies.

• receiver/datadog: Add feature gate to stop emitting deprecated rpc.service attribute (#​22095)
  The feature gate receiver.datadogreceiver.DontEmitDeprecatedRPCServiceAttr
  (disabled by default) allows users to opt out of the deprecated rpc.service
  attribute on gRPC spans. The service name is already captured in the span
  name (service/method) and rpc.method attribute.

• receiver/file_log: Improve polling performance when watching many files by indexing fingerprint matching. (#​27404)

• receiver/googlecloudmonitoring: Add universe_domain config option to support Sovereign Google Cloud regions. Setting this field passes option.WithUniverseDomain to the underlying Google API client. (#​48924)

• receiver/googlecloudpubsub: Add universe_domain config option to support Sovereign Google Cloud regions. Setting this field passes option.WithUniverseDomain to the underlying Google API client. (#​48924)

• receiver/host_metrics: Enable the Android platform in the process scraper. (#​47296)

• receiver/host_metrics: Add AIX-specific process scraper implementation. (#​47095)
  Implements AIX versions of the platform-specific process scraper hooks
  (CPU time/utilization recording, process name, executable, and command
  extraction), replacing the previous empty stubs that the "others"
  fallback provided.

• receiver/oracledb: Enhance SQL obfuscation to anonymize comments while preserving query structure (#​48508)

  • Query structure, formatting, and whitespace are now preserved during obfuscation for improved readability.

• receiver/oracledb: Add additional attributes to the Oracle query execution plan. (#​48965)
  Extend the execution plan with five additional attributes:

  • OBJECT_NAME: Name of the object referenced by the plan step
  • OBJECT_TYPE: Type of the referenced object (e.g., table, index)
  • FILTER_PREDICATES: Predicates applied as a filter during the step
  • PARTITION_START: Starting partition for partitioned access
  • PARTITION_STOP: Ending partition for partitioned access

• receiver/oracledb: Add oracledb.plan.first_load attribute to the db.server.top_query event (#​48998)

• receiver/oracledb: Add SQL comment extraction support. Users can now configure allowed_comment_keys to extract key-value pairs from leading SQL block comments and include them as the db.query.comment_tags telemetry attribute. (#​48338)

• receiver/prometheus: Add scrape_on_shutdown, discovery_reload_on_startup, and initial_scrape_offset configuration options to allow tuning startup and shutdown scrape behavior in serverless environments. (#​48979)

  • scrape_on_shutdown (default: false): Enables a final scrape before the receiver closes.
  • discovery_reload_on_startup (default: false): Enables discovering targets immediately on startup.
  • initial_scrape_offset (default: 0s): Adds a fixed delay before the initial scrape of targets.

• receiver/sqlserver: Add sqlserver.query.plan.creation_time attribute to the db.server.top_query event. (#​49018)

• receiver/sqlserver: Add service.name and service.namespace opt-in resource attributes and allow overriding any resource attribute via override_value. (#​46176)
  When service.name is enabled, the receiver sets it to unknown_service:microsoft.sql_server per OTel specification.
  When service.namespace is enabled, it defaults to an empty string until set via configuration.
  Each resource attribute now accepts an override_value under resource_attributes, letting users pin
  values such as service.name, service.namespace, or service.instance.id to uniquely identify
  database instances across environments.

🧰 Bug fixes 🧰

• cmd/opampsupervisor: Normalize merged service.telemetry.resource settings so mixed legacy inline attributes and declarative attributes entries do not produce invalid effective Collector configs (#​48365)

• connector/failover: Stop the connector's wrapped exporterhelper from imposing its default 5s timeout on the downstream pipeline when sending_queue is enabled. (#​48567)
  Previously, enabling sending_queue caused the connector to wrap itself in exporterhelper.NewLogs/Traces/Metrics, which silently installs a timeoutSender with the 5s default TimeoutConfig.Timeout. That deadline propagated through to downstream exporters via ctx.Deadline(), capping their configured timeouts (e.g., a downstream exporter configured with timeout: 30s would only see ~5s of budget at its pushLogsData). The connector now passes WithTimeout(TimeoutConfig{Timeout: 0}) explicitly, matching the pattern used by signalfxexporter and splunkhecexporter. A user-facing timeout config field on the connector may be added separately if there is demand for connector-level hang-protection.

• exporter/elasticsearch: Skip error.grouping_name when encoding ECS span events, as it is a scripted field in the logs-apm.error index template and cannot be indexed directly. (#​49216)

• exporter/load_balancing: Fix Kubernetes resolver initialization to allow exporter creation outside k8s cluster by deferring client creation to start time (#​42293)

• exporter/load_balancing: Fix a wait-group leak on the trace routing path that could cause Shutdown to hang when backend resolution fails partway through a batch (#​48983)

• extension/datadog: Fix tls.insecure_skip_verify being ignored (#​48992)

• extension/google_cloud_logentry_encoding: Accept short ALPN protocol tokens (e.g. h2, h3) in httpRequest.protocol that do not contain a /; previously any protocol string without a slash was rejected with an error, causing log entries from Google Cloud Load Balancers that switched to reporting h2 for HTTP/2 to be silently dropped. (#​45214)

• pkg/ottl: Fix replace_pattern and replace_all_patterns using a Function argument so each match is replaced only at its position, instead of everywhere the matched text appears. (#​48437)

• pkg/stanza: Fix stanza container operator logging errors at ERROR level when on_error is set to a quiet mode (#​42646)
  Previously, the container operator logged entry-level processing errors at
  ERROR level even when on_error was set to drop_quiet or send_quiet.
  These errors are now logged at DEBUG level in quiet modes, matching the
  documented behavior. Downstream delivery failures continue to propagate so
  the pipeline can react to them.

• pkg/translator/pprof: Fix the wrong timestamp conversion. (#​48813)

• processor/k8s_attributes: Prevent unbounded memory growth by cleaning up stale pod identifiers, including container.id entries left behind after container restarts (#​48398)

• processor/metrics_transform: Add required-field validation for combine action: return an error if new_name or aggregation_type is missing, preventing silent data loss and empty metric names. (#​48871)

• processor/redaction: Fix a panic in database attribute sanitization when traces are processed concurrently. (#​49048)

• processor/transform: Fix transform processor config unmarshaling to return an error for empty statement list items instead of panicking. (#​49245)

• receiver/azure_monitor: Fix discovery and collection of custom metric namespace definitions (e.g. azure.vm.linux.guestmetrics published by Azure Monitor Agent / MetricsExtension) (#​40989)
  The MetricDefinitions API only returns custom namespace metrics when the metricnamespace query parameter is explicitly set. Previously, metrics configured under receiver::metrics for a custom namespace were silently dropped because the API call used no filter and only returned the resource's default namespace. The receiver now makes an additional namespace-filtered call for each custom namespace in the metrics config that was not returned by the default call.

• receiver/datadog: Fix StartTimestamp exceeding Timestamp on delta-temporality data points when out-of-order or late-arriving submissions are received. (#​48449)
  The datadog receiver now guards StartTimestamp assignment to enforce the OTel data model
  invariant (StartTimestamp <= Timestamp) for delta-temporality metrics. Late-arriving or
  out-of-order data points no longer poison the stored timestamp for subsequent submissions.

• receiver/http_check: Stop emitting two httpcheck.tls.cert_remaining data points per scrape (#​47740)

• receiver/kafka_metrics: use kadm.Client.Lag and do not record negative values (#​48701)

• receiver/oracledb: Clamp negative DURATION_SEC and SESSION_DURATION_SEC values in the query sample to zero. (#​48901)
  Fix negative duration values in query sample metrics by clamping DURATION_SEC and SESSION_DURATION_SEC to zero minimum.

• receiver/purefa: Fix the receiver failing to start due to an invalid internal Prometheus scrape configuration. (#​48847)
  The receiver used a *discovery.StaticConfig pointer when building the Prometheus scrape
  configs. Only the value type discovery.StaticConfig is registered for YAML marshaling, so
  the prometheus receiver failed on startup with "cannot mar

✂ Note

PR body was truncated to here.

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • "every weekend"
• 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.

[red-hat-konflux-kflux-prd-rh02]

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

• 26 additional dependencies were updated

Details:

Package	Change
golang.org/x/mod	v0.35.0 -> v0.37.0
golang.org/x/net	v0.53.0 -> v0.56.0
github.com/knadh/koanf/v2	v2.3.4 -> v2.3.5
github.com/open-telemetry/opentelemetry-collector-contrib/internal/exp/metrics	v0.150.0 -> v0.156.0
github.com/open-telemetry/opentelemetry-collector-contrib/pkg/pdatautil	v0.150.0 -> v0.156.0
github.com/puzpuzpuz/xsync/v4	v4.4.0 -> v4.5.0
go.opentelemetry.io/collector/component	v1.56.0 -> v1.62.0
go.opentelemetry.io/collector/confmap	v1.56.0 -> v1.62.0
go.opentelemetry.io/collector/confmap/xconfmap	v0.150.0 -> v0.156.0
go.opentelemetry.io/collector/consumer	v1.56.0 -> v1.62.0
go.opentelemetry.io/collector/featuregate	v1.56.0 -> v1.62.0
go.opentelemetry.io/collector/internal/componentalias	v0.150.0 -> v0.156.0
go.opentelemetry.io/collector/pdata	v1.56.0 -> v1.62.0
go.opentelemetry.io/collector/pipeline	v1.56.0 -> v1.62.0
go.opentelemetry.io/collector/processor	v1.56.0 -> v1.62.0
go.opentelemetry.io/otel	v1.43.0 -> v1.44.0
go.opentelemetry.io/otel/metric	v1.43.0 -> v1.44.0
go.opentelemetry.io/otel/trace	v1.43.0 -> v1.44.0
go.uber.org/zap	v1.27.1 -> v1.28.0
golang.org/x/crypto	v0.50.0 -> v0.53.0
golang.org/x/sync	v0.20.0 -> v0.21.0
golang.org/x/sys	v0.43.0 -> v0.46.0
golang.org/x/term	v0.42.0 -> v0.44.0
golang.org/x/text	v0.36.0 -> v0.38.0
golang.org/x/tools	v0.44.0 -> v0.47.0
google.golang.org/grpc	v1.80.0 -> v1.82.0

[openshift-ci]

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]

[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 vickeybrown 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:

• OWNERS

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

[openshift-ci]

@red-hat-konflux-kflux-prd-rh02[bot]: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/ci-index-file-integrity-operator-bundle	ac3e144	link	true	/test ci-index-file-integrity-operator-bundle
ci/prow/e2e-aws	ac3e144	link	true	/test e2e-aws
ci/prow/images	ac3e144	link	true	/test images

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.