Skip to content

fix(deps): update opentelemetry (9.4) - #6523

Open
elastic-renovate-prod[bot] wants to merge 1 commit into
9.4from
renovate/9.4-opentelemetry
Open

fix(deps): update opentelemetry (9.4)#6523
elastic-renovate-prod[bot] wants to merge 1 commit into
9.4from
renovate/9.4-opentelemetry

Conversation

@elastic-renovate-prod

@elastic-renovate-prod elastic-renovate-prod Bot commented May 29, 2026

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/client v1.59.0v1.64.0 age confidence
go.opentelemetry.io/collector/component v1.59.0v1.64.0 age confidence
go.opentelemetry.io/collector/config/configoptional v1.59.0v1.64.0 age confidence
go.opentelemetry.io/collector/config/configretry v1.59.0v1.64.0 age confidence
go.opentelemetry.io/collector/confmap v1.59.0v1.64.0 age confidence
go.opentelemetry.io/collector/confmap/xconfmap v0.153.0v0.158.0 age confidence
go.opentelemetry.io/collector/consumer v1.59.0v1.64.0 age confidence
go.opentelemetry.io/collector/consumer/consumererror v0.153.0v0.158.0 age confidence
go.opentelemetry.io/collector/exporter v1.59.0v1.64.0 age confidence
go.opentelemetry.io/collector/exporter/exporterhelper v0.153.0v0.158.0 age confidence
go.opentelemetry.io/collector/extension v1.59.0v1.64.0 age confidence
go.opentelemetry.io/collector/extension/xextension v0.153.0v0.158.0 age confidence
go.opentelemetry.io/collector/featuregate v1.59.0v1.64.0 age confidence
go.opentelemetry.io/collector/internal/componentalias v0.153.0v0.158.0 age confidence
go.opentelemetry.io/collector/pdata v1.59.0v1.64.0 age confidence
go.opentelemetry.io/collector/pdata/pprofile v0.153.0v0.158.0 age confidence
go.opentelemetry.io/collector/pdata/xpdata v0.153.0v0.158.0 age confidence
go.opentelemetry.io/collector/pipeline v1.59.0v1.64.0 age confidence
go.opentelemetry.io/collector/pipeline/xpipeline v0.153.0v0.158.0 age confidence
go.opentelemetry.io/contrib/detectors/gcp v1.43.0v1.45.0 age confidence
go.opentelemetry.io/contrib/instrumentation/github.com/aws/aws-sdk-go-v2/otelaws v0.68.0v0.70.0 age confidence
go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc v0.68.0v0.70.0 age confidence
go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp v0.68.0v0.70.0 age confidence
go.opentelemetry.io/otel v1.44.0v1.45.0 age confidence
go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetricgrpc v1.43.0v1.45.0 age confidence
go.opentelemetry.io/otel/exporters/otlp/otlptrace v1.43.0v1.45.0 age confidence
go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc v1.43.0v1.45.0 age confidence
go.opentelemetry.io/otel/metric v1.44.0v1.45.0 age confidence
go.opentelemetry.io/otel/sdk v1.43.0v1.45.0 age confidence
go.opentelemetry.io/otel/sdk/metric v1.43.0v1.45.0 age confidence
go.opentelemetry.io/otel/trace v1.44.0v1.45.0 age confidence
go.opentelemetry.io/proto/otlp v1.10.0v1.11.0 age confidence

Warning

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


Release Notes

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

v1.64.0

🚀 New components 🚀
💡 Enhancements 💡
  • cmd/mdatagen: Add first-class extended type aliases (int64, duration, opaque_string, id, opaque_map, etc.) to config schemas in metadata.yaml (#​15513)
    Authors can now write type: int64, type: duration, type: opaque_string, type: id, or
    type: opaque_map directly as a property type in the config: section of metadata.yaml.
    Each alias expands to the correct JSON Schema representation and Go type automatically.
    Existing uses of standard JSON Schema types, format:, and x-customType: remain supported
    without migration.

  • extension/memory_limiter: Promote the memory limiter extension to beta stability. (#​14533)

🧰 Bug fixes 🧰
  • cmd/mdatagen: Removes the extra line in the documentation.md around description (#​15664)

  • cmd/mdatagen: Auto-enable v1 metrics when legacy metric is enabled and v1 feature gate is on (#​15650)
    When the v1 feature gate is enabled and a legacy metric is enabled, the corresponding
    v1 metric is now programmatically enabled so users don't need to add the v1 metric
    to their config.

  • cmd/mdatagen: Fix incorrect collision warning for versioned metrics with different emitted names (#​15648)
    Same name collision detection (type/attribute checks) was being used for versioned metrics
    with different names. This caused the legacy metric to be disabled which was incorrect and also
    a warning msg was being incorrectly logged that stated the metrics had the same name when in
    fact they had different names.

  • cmd/mdatagen: Versioned metrics don't handle renamed attributes with same type (#​15595)
    Versioned metrics need to support emitting legacy and latest attributes when the metric name is the same but the
    attributes names differ. This was not working when the attributes name changed but the type remained the same.
    Here we add support to versioned metrics with renamed attributes where those attributes have the same type.

  • exporter/debug: Fix profile sample attribute formatting for non-string values (#​15647)
    Previously, non-string values produced malformed output such as %!s(int64=42).
    Profile sample attributes now use the debug exporter's typed attribute format, such as Int(42).
    This will also change strings from hello-world to Str(hello-world).

  • pkg/config/configtls: Fix goroutine and file descriptor leak when client_ca_file_reload is enabled (#​9221)
    Every call to ServerConfig.LoadTLSConfig with client_ca_file_reload enabled started a
    file watcher goroutine that could never be stopped, since the reloader was not reachable
    from the returned *tls.Config. The client CA file is now checked for changes while TLS
    handshakes are served, at most once per second, matching how reload_interval already
    reloads the server certificate. No background goroutine is started, so nothing is left
    behind when a server is torn down and recreated.

v1.63.0

🛑 Breaking changes 🛑
  • pkg/exporterhelper: Replace histogram bucket boundaries for otelcol_exporter_queue_batch_send_size_bytes and otelcol_processor_batch_batch_send_size_bytes with a power-of-2 byte-scale set spanning 128 B to 16 MiB. (#​15535)
    The previous boundaries included many small sub-kilobyte buckets that were not useful for byte-scale
    payloads, and otelcol_exporter_queue_batch_send_size_bytes topped out at 6000 bytes so nearly all
    observations fell into the +Inf overflow bucket. The new boundaries are powers of two from 128 B
    to 1677721 (16 MiB), giving a meaningful distribution for real batch payload sizes (including small
    timeout-flushed batches) and keeping the two
    metrics directly comparable on the same dashboards. Dashboards or alerts that hard-code specific le
    values for these histograms will need to be updated.

  • processor/batch: Replace histogram bucket boundaries for otelcol_processor_batch_batch_send_size_bytes with a power-of-2 byte-scale set spanning 128 B to 16 MiB. (#​15535)
    The previous boundaries included many small sub-kilobyte buckets that were not useful for byte-scale
    payloads. The new boundaries are powers of two from 128 B to 1677721 (16 MiB), giving a meaningful
    distribution for real batch payload sizes (including small timeout-flushed batches) and keeping the
    metric directly comparable with
    otelcol_exporter_queue_batch_send_size_bytes on the same dashboards. Dashboards or alerts that
    hard-code specific le values for this histogram will need to be updated.

💡 Enhancements 💡
  • all: Bootstrap config.schema.yaml for core components (debug/otlp/otlphttp exporters, otlp receiver, batch/memory_limiter processors, memory_limiter/zpages extensions). Implements Phase 1 of the component configuration schema roadmap RFC. (#​14543)
    Schemas are generated using the schemagen tool from opentelemetry-collector-contrib and hand-tuned to capture
    validation rules and references to shared library schemas (confighttp, configgrpc, configretry, exporterhelper,
    etc.). A .schemagen.yaml settings file and a generate-schemas Makefile target are added so the schemas can
    be regenerated reproducibly.

  • pkg/service: Apply experimental service::telemetry::resource::detection/development resource detection to the Collector's internal telemetry resource. (#​14311)
    This follows the OpenTelemetry configuration schema by treating
    service::telemetry::resource::detection/development::detectors as detector selection.
    Currently supported detector entries are container, host, process, and service.
    See the OpenTelemetry Configuration Go support table and search for
    ExperimentalResourceDetector for current detector support:
    https://github.com/open-telemetry/opentelemetry-configuration/blob/main/language-support-status.md#go

    Example:

    service:
      telemetry:
        resource:
          attributes:
            - name: foo
              value: bar
          detection/development:
            detectors:
              - host: {}
  • pkg/service: Add service.partialReload feature gate (Alpha) and service.partialReloadReceivers feature gate (Beta) that together restart only receivers on config reload when non-receiver config sections are unchanged, avoiding unnecessary disruption to processors, exporters, and extensions. Enable with --feature-gates=service.partialReload. (#​5966)

🧰 Bug fixes 🧰
  • exporter/debug: Fix the scope index printed by the normal verbosity marshaler; each scope was labelled with its parent resource's index instead of its own position (#​15541)
    Affected all four signals (logs, traces, metrics, profiles) — e.g. the second scope under a resource printed #0 instead of #1.

  • pkg/config/configgrpc: Fix WaitForReady option not being applied to gRPC client connections. (#​15615)

  • pkg/featuregate: Fix panic when a --feature-gates value contains an empty comma-separated element (e.g. --feature-gates=alpha,) (#​15536)
    An empty identifier now produces a returned error instead of an index-out-of-range panic during flag parsing.

  • pkg/service: Fix collector startup panic when a resource detector emits a slice-valued attribute (e.g. the process detector's process.command_args) (#​15571)
    createResource passed the OTel SDK attribute value straight into pcommon.Value.FromRaw, which
    only accepts []any for slices, so any string, int, float, or bool slice resource attribute produced
    an <Invalid value type> error and aborted service.New. Slice-typed attributes are now converted
    element-wise.

  • pkg/service: Record status events reported by extensions (#​15557)

v1.62.0

💡 Enhancements 💡
  • cmd/mdatagen: Add support for defining stability levels for resource attributes (#​15312)
  • cmd/mdatagen: Add semantic convention reference to resource attributes (#​15313)
  • processor/memory_limiter: Adding health events for the memorylimiter (#​14700)
    Publish health event from memorylimiter using componentstatus.ReportStatus
🧰 Bug fixes 🧰
  • cmd/mdatagen: Removes the extra line in the documentation.md between extended description and table (#​15458)

  • exporter/otlp_http: Treat errors parsing successful (2xx) HTTP response bodies as permanent errors to prevent retrying already-accepted data. (#​15386)
    When a server returns a 2xx status but the response body exceeds the 64kB read limit,
    the body is truncated and proto unmarshaling fails. Previously this was treated as a
    retryable error, causing duplicate data to be exported. Now it is marked as a permanent
    error so the retry logic will not re-send data that was already accepted by the server.

  • pkg/config/configretry: Always validate BackOffConfig fields regardless of the Enabled flag. (#​15437)

  • pkg/service: Ensure receivers always start after all other components (#​15495)
    There was previously a race condition where multiple receivers using a shared internal implementation,
    such as the OTLP receiver, could start sending telemetry into a pipeline before all its components had fully started.

  • processor/memory_limiter: Fix degenerate collector performance when exporter has problems causing permanent CPU-burning GC loop (#​4981)
    Forced GC runs now use exponential backoff when deemed ineffective
    (still above soft limit and less than 5% reclaimed) to avoid preventing
    recovery by overloading CPU with excessive GC runs. The cap on the
    backoff interval is exposed via max_gc_interval_when_soft_limited and
    max_gc_interval_when_hard_limited (both default 30s); set either to
    0 to disable backoff on that path.

  • provider/env: Fix empty env var default resolving to nil instead of empty string (#​14587)
    When using ${env:VAR:-} with an unset variable, the empty default now correctly
    resolves to an empty string instead of nil.

v1.61.0

🛑 Breaking changes 🛑
  • pkg/confighttp: Remove stabilized gate confighttp.framedSnappy (#​15420)
  • pkg/configoptional: Remove stabilized gate configoptional.AddEnabledField. (#​15421)
  • pkg/confmap: Remove stabilized featuregate confmap.newExpandedValueSanitizer (#​15418)
  • pkg/exporterhelper: Remove stable gate exporter.PersistRequestContext. (#​15424)
  • pkg/otelcol: Remove stable gate otelcol.printInitialConfig (#​15425)
  • pkg/service: Remove stable featuregate telemetry.UseLocalHostAsDefaultMetricsAddress (#​15419)
  • pkg/xpdata: Remove stable gate pdata.enableRefCounting. (#​15426)
  • processor/memory_limiter: Rename deprecated memory limiter metrics to include the memory_limiter prefix (e.g. otelcol_processor_memory_limiter_*) to clarify they are specific to this processor. (#​11203)
🚀 New components 🚀
  • cmd/schemagen: Move the schemagen CLI from opentelemetry-collector-contrib to this repository as cmd/schemagen. (#​14543)
    The tool's source is identical to the upstream contrib version
    (github.com/open-telemetry/opentelemetry-collector-contrib/cmd/schemagen) except for the module path and
    the test fixtures' namespace, which now reflect the collector module
    (go.opentelemetry.io/collector/cmd/schemagen). A contrib-only integration test that pointed at three
    contrib components is removed; contrib's existing make generate-schemas + git-diff CI continues to
    exercise the FactoryMaps feature against real-world components.
💡 Enhancements 💡
  • cmd/mdatagen: Add support for versioned metrics (#​15309)
    Allows metadata to specify versioned metrics for migrating to new semantic conventions.
    There are two scenarios catered for when the metric name stays the same during migration.
    When a metric name stays the same but its type differs, just the latest metric is
    emitted with the new type.
    When a metric name stays the same but its attributes differ, the latest version
    is emitted with combined attributes during the migration period.

  • cmd/schemagen: Add overlayFile support to deep-merge hand-curated schema fragments into generated schemas. (#​14543)
    Components can declare an overlayFile in .schemagen.yaml pointing to a YAML file
    whose keys are recursively merged into the auto-generated schema after generation.
    This allows injecting descriptions, constraints, or additional properties that cannot
    be derived from Go types.
    Originally added to the contrib copy of cmd/schemagen in
    open-telemetry/opentelemetry-collector-contrib#48917 and brought over with the tool
    in this move.

  • cmd/schemagen: Add -p flag to specify a custom Go package pattern for the config struct. (#​14543)
    The new -p flag lets callers override the default . package pattern with an arbitrary
    Go package selector (e.g. a sub-package whose Config type schemagen should walk).
    Originally added to the contrib copy of cmd/schemagen in
    open-telemetry/opentelemetry-collector-contrib#48966 and brought over with the tool
    in this move.

🧰 Bug fixes 🧰
  • cmd/mdatagen: Fix an issue when the last feature gate is removed, stale files are left. (#​15423)
  • cmd/mdatagen: Fix known acronyms at the end of generated Go identifiers to be all-caps, same as in any other position (#​15438)
  • cmd/schemagen: Fix mode detection when using -p to target a package outside the current directory. (#​15453)
    A new -m component|package flag is available as a manual override when auto-detection is not possible.

v1.60.0

🛑 Breaking changes 🛑
  • cmd/builder: The --skip-get-modules flag will no longer regenerate your go.mod file. (#​15390)
    This is mostly a bug fix, as it led to adverse behaviour that was unintended in the described flow in the README.
    Now when you run --skip-get-modules, your go.mod file will truly be untouched by ocb as the info log claims.
💡 Enhancements 💡
  • pkg/config/configtls: Add include_insecure_cipher_suites to configtls to enable insecure cipher suites. Insecure cipher suites are disabled by default for security. (#​13829)
  • pkg/confighttp: Add ExposedHeaders field to CORSConfig to allow setting the Access-Control-Expose-Headers response header. (#​15119)
🧰 Bug fixes 🧰
  • cmd/mdatagen: Removes the extra line in the README.md between status and description (#​15306)
  • pkg/exporterhelper: Fix nil-pointer panic in sending_queue::batch Unmarshal when sending_queue::sizer is set and sending_queue::batch::enabled is false. (#​14687)
    When sending_queue::sizer was set and sending_queue::batch::enabled: false
    cleared the batch Optional to None, the sizer-inheritance branch in
    queuebatch.Config.Unmarshal dereferenced a nil Optional and crashed the
    collector at startup. The branch now also requires Batch.HasValue().
open-telemetry/opentelemetry-go-contrib (go.opentelemetry.io/contrib/detectors/gcp)

v1.45.0: /v2.5.2/v0.70.0/v0.37.2/v0.25.0/v0.20.0/v0.16.2/v0.17.0

Compare Source

Overview

Added
  • Add go.opentelemetry.io/contrib/detectors/ibmcloud/vpc, a new resource detector for IBM Cloud VPC virtual server instances, ported from github.com/open-telemetry/opentelemetry-collector-contrib/processor/resourcedetectionprocessor/internal/ibmcloud/vpc. Detects cloud.provider, cloud.platform, cloud.region, cloud.availability_zone, cloud.account.id, cloud.resource_id, host.id, host.image.id, host.image.name, host.name, and host.type. (#​9011)
  • Add go.opentelemetry.io/contrib/detectors/k8sapi, a new resource detector that queries the Kubernetes API. Detects k8s.node.name and k8s.node.uid when K8S_NODE_NAME is set via the downward API, and k8s.cluster.uid derived from the kube-system namespace UID (works on any Kubernetes distribution). (#​9108)
  • Add new elasticbeanstalk resource detector for AWS Elastic Beanstalk, ported from processor/resourcedetectionprocessor/internal/aws/elasticbeanstalk in opentelemetry-collector-contrib. (#​8993)
  • The resource created by go.opentelemetry.io/contrib/otelconf now includes default SDK attributes. (#​8990)
  • Add support for the aws.ecs resource detector in go.opentelemetry.io/contrib/otelconf/x. (#​8915)
  • Add support for the aws.eks resource detector in go.opentelemetry.io/contrib/otelconf/x. (#​9138)
  • Add support for the azure.vm resource detector in go.opentelemetry.io/contrib/otelconf/x. (#​9074)
  • Add support for the gcp resource detector in go.opentelemetry.io/contrib/otelconf/x. (#​9137)
  • Add go.opentelemetry.io/contrib/detectors/azure/azureappservice, a new resource detector for Azure App Service. Detects cloud.*, service.name, azure.resource_group.name, azure.app_service.instance.id, and deployment.environment.name from the WEBSITE_* and REGION_NAME environment variables. (#​9289)
  • Add azurecontainerapps resource detector for Azure Container Apps. (#​8939)
  • Add go.opentelemetry.io/contrib/detectors/azure/azurefunctions, a new resource detector for Azure Functions. Detects cloud.*, service.name, azure.resource_group.name, faas.instance, and deployment.environment.name from the FUNCTIONS_*, WEBSITE_*, CONTAINER_NAME, and REGION_NAME environment variables. (#​9290)
  • Add NewResourceDetector along with the WithAttributeFilter and WithTagKeyFilter options in go.opentelemetry.io/contrib/detectors/azure/azurevm. WithAttributeFilter restricts the returned resource to the attributes the filter accepts. WithTagKeyFilter opts in to azure.tag.<name> attributes for the VM tags whose keys satisfy the provided predicate; no VM tags are emitted without it. (#​9162)
  • Add go.opentelemetry.io/contrib/detectors/vultr — a new resource detector for Vultr Cloud Compute instances, ported from processor/resourcedetectionprocessor/internal/vultr in opentelemetry-collector-contrib. Detects cloud.provider, cloud.platform, cloud.region, host.id, and host.name. (#​8995)
Changed
  • Upgrade go.opentelemetry.io/otel/semconv to v1.43.0, including updates across instrumentation and detector modules.
    See semantic-conventions v1.43.0 release for complete details. (#​9337)
  • Upgrade go.opentelemetry.io/otel/semconv to v1.42.0, including updates across instrumentation and detector modules.
    See semantic-conventions v1.42.0 release for complete details. (#​9196)
  • Use direct normalized-key lookups in Carrier.Get and Carrier.Keys in go.opentelemetry.io/contrib/propagators/envcar. (#​9112)
  • Update log bridge conversions to use attribute key-values instead of the removed log key-values in go.opentelemetry.io/contrib/bridges/otellogr, go.opentelemetry.io/contrib/bridges/otellogrus, go.opentelemetry.io/contrib/bridges/otelslog, and go.opentelemetry.io/contrib/bridges/otelzap. (#​9180)
  • The Version() function in go.opentelemetry.io/contrib/instrumentation/github.com/gorilla/mux/otelmux has been replaced by const Version. (#​9076)
  • Set error.type attribute instead of adding exception span events in go.opentelemetry.io/contrib/instrumentation/github.com/gin-gonic/gin/otelgin. (#​8977)
  • Prefer the gRPC dial target over the resolved peer IP for the server.address and server.port attributes in go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc. (#​8904)
  • The detector in go.opentelemetry.io/contrib/detectors/azure/azurevm now also detects cloud.account.id, cloud.availability_zone, azure.vm.name, azure.vm.size, azure.vm.scaleset.name, and azure.resource_group.name, and prefers osProfile.computerName for host.name (falling back to the VM name), reconciling it with the collector-contrib Azure resource detector. (#​9162)
Fixed
  • Fix Prometheus reader resource label filter configuration in go.opentelemetry.io/contrib/otelconf/v0.2.0. (#​9062)
  • Apply resource.detection/development.attributes.included and excluded filtering to resource detector attributes in go.opentelemetry.io/contrib/otelconf/x. (#​9131)
  • Honor the context configured with WithContext when constructing resources in go.opentelemetry.io/contrib/otelconf and go.opentelemetry.io/contrib/otelconf/x. (#​9160)
  • Handle nil response bodies from custom RoundTripper implementations in go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp without panicking. (#​9184)
  • Fix incorrect (overestimated) sum calculation for runtime histograms in go.opentelemetry.io/contrib/instrumentation/runtime. (#​9063)
  • Fix Severity.UnmarshalText round trip for positive FATAL offsets above the named range in go.opentelemetry.io/contrib/processors/minsev. (#​9197)
  • Reduce binary size by fetching ConfigMaps via rest.HTTPClientFor instead of the Kubernetes clientset in go.opentelemetry.io/contrib/detectors/aws/eks. (#​9284)
  • TextMapPropagator in go.opentelemetry.io/contrib/propagators/autoprop returns the no-op propagator for empty input, matching the behavior of none. An unknown OTEL_PROPAGATORS value still returns an error with a nil propagator so NewTextMapPropagator falls back to the default TraceContext and Baggage propagators instead of disabling propagation. (#​9163)
  • Preserve error-valued attributes nested in a group as grouped attributes instead of silently dropping them in go.opentelemetry.io/contrib/bridges/otelslog. (#​9238)
  • Fix a data race in go.opentelemetry.io/contrib/bridges/otelslog where concurrent Handle calls could corrupt each other's log attributes because kvBuffer.KeyValues returned a slice aliasing a shared buffer. (#​9229)
  • Avoid a panic in go.opentelemetry.io/contrib/bridges/otelzap when a malformed error field contains a nil or non-error value. (#​9068)
  • Use azure.container_app.instance.id instead of service.instance.id for the replica name detected by go.opentelemetry.io/contrib/detectors/azure/azurecontainerapps. (#​9208)
  • Preserve the underlying metadata errors returned with partial resources from go.opentelemetry.io/contrib/detectors/gcp. (#​9069)
  • Copy MultipartForm back to the request otelmux.Middleware was given after the wrapped handler returns, so net/http can find and remove the temp files ParseMultipartForm created on the context-derived request copy, when otelmux.Middleware wraps a handler directly, in go.opentelemetry.io/contrib/instrumentation/github.com/gorilla/mux/otelmux. This does not cover a handler panic, nor the common router.Use(...) integration, where gorilla/mux's own routing step makes an additional request copy the middleware cannot write back through; see gorilla/mux#777. (#​9361)
  • Report the b3 header from Fields() for the default B3Unspecified single-header injection encoding, matching what Inject writes, in go.opentelemetry.io/contrib/propagators/b3. (#​9273)
  • Fix go.opentelemetry.io/contrib/propagators/aws/xray producing deterministic trace and span IDs when the seed read from crypto/rand silently failed, by switching to math/rand/v2's concurrency-safe top-level generator. (#​9359)
  • Strip connection number suffix from connection ID in go.opentelemetry.io/contrib/instrumentation/go.mongodb.org/mongo-driver/v2/mongo/otelmongo to prevent unbounded metric cardinality. (#​9352)
  • Strip connection number suffix from connection ID in go.opentelemetry.io/contrib/instrumentation/go.mongodb.org/mongo-driver/mongo/otelmongo so the network.peer.address and net.peer.name span attributes reflect the actual host instead of the raw connection ID. (#​9352)
  • Record network.protocol.version (and network.protocol.name) from the response's negotiated protocol instead of the request's stamped Proto in go.opentelemetry.io/contrib/instrumentation/net/http/otelhttp, so an HTTP/1.1-shaped request that gets upgraded to HTTP/2 via ALPN is no longer misreported as HTTP/1.1 on the client span and request metrics. (#​9371)

What's Changed


Configuration

📅 Schedule: Branch creation - Between 01:00 AM and 01:59 AM, Monday through Friday ( * 1 * * 1-5 ) (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

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

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


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

This PR has been generated by Renovate Bot.

@elastic-renovate-prod
elastic-renovate-prod Bot requested a review from a team as a code owner May 29, 2026 14:44
@elastic-renovate-prod elastic-renovate-prod Bot added backport-skip dependencies Pull requests that update a dependency file renovate renovate-auto-approve Team:Security-Cloud Services Security Data Experience - Cloud Services team. labels May 29, 2026
@elastic-renovate-prod
elastic-renovate-prod Bot enabled auto-merge May 29, 2026 14:44
@elastic-renovate-prod
elastic-renovate-prod Bot force-pushed the renovate/9.4-opentelemetry branch from 67d7754 to 008605d Compare May 29, 2026 14:44
@elastic-renovate-prod
elastic-renovate-prod Bot force-pushed the renovate/9.4-opentelemetry branch from 008605d to 45595f6 Compare May 29, 2026 15:11
@elastic-renovate-prod elastic-renovate-prod Bot changed the title fix(deps): update opentelemetry (9.4) fix(deps): update opentelemetry to v1.44.0 (9.4) May 29, 2026
@elastic-renovate-prod
elastic-renovate-prod Bot force-pushed the renovate/9.4-opentelemetry branch from 45595f6 to 92f6e8b Compare May 29, 2026 19:48
@elastic-renovate-prod
elastic-renovate-prod Bot force-pushed the renovate/9.4-opentelemetry branch from 92f6e8b to 87d82cd Compare May 30, 2026 06:47
@elastic-renovate-prod elastic-renovate-prod Bot changed the title fix(deps): update opentelemetry to v1.44.0 (9.4) fix(deps): update opentelemetry (9.4) May 30, 2026
@elastic-renovate-prod
elastic-renovate-prod Bot force-pushed the renovate/9.4-opentelemetry branch from 87d82cd to 7089482 Compare June 1, 2026 13:18
@elastic-renovate-prod
elastic-renovate-prod Bot force-pushed the renovate/9.4-opentelemetry branch from 7089482 to 629d1c0 Compare June 1, 2026 15:50
@elastic-renovate-prod
elastic-renovate-prod Bot force-pushed the renovate/9.4-opentelemetry branch from 629d1c0 to 9ebb6b3 Compare June 1, 2026 15:51
@elastic-renovate-prod
elastic-renovate-prod Bot force-pushed the renovate/9.4-opentelemetry branch from 9ebb6b3 to bee7a2e Compare June 2, 2026 13:53
@elastic-renovate-prod
elastic-renovate-prod Bot force-pushed the renovate/9.4-opentelemetry branch from 7a50a0b to cfd450f Compare August 4, 2026 17:30
@mergify

mergify Bot commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b renovate/9.4-opentelemetry upstream/renovate/9.4-opentelemetry
git merge upstream/9.4
git push upstream renovate/9.4-opentelemetry

@elastic-renovate-prod
elastic-renovate-prod Bot force-pushed the renovate/9.4-opentelemetry branch from cfd450f to f2b6484 Compare August 4, 2026 19:05
@mergify

mergify Bot commented Aug 4, 2026

Copy link
Copy Markdown
Contributor

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b renovate/9.4-opentelemetry upstream/renovate/9.4-opentelemetry
git merge upstream/9.4
git push upstream renovate/9.4-opentelemetry

@elastic-renovate-prod
elastic-renovate-prod Bot force-pushed the renovate/9.4-opentelemetry branch from f2b6484 to 413f40e Compare August 5, 2026 03:14
@elastic-renovate-prod
elastic-renovate-prod Bot force-pushed the renovate/9.4-opentelemetry branch from 413f40e to 8c1563c Compare August 5, 2026 06:57
@elastic-renovate-prod
elastic-renovate-prod Bot force-pushed the renovate/9.4-opentelemetry branch from 8c1563c to 899f28c Compare August 5, 2026 22:58
@elastic-renovate-prod
elastic-renovate-prod Bot force-pushed the renovate/9.4-opentelemetry branch from 899f28c to 7ae0382 Compare August 6, 2026 03:01
@elastic-renovate-prod
elastic-renovate-prod Bot force-pushed the renovate/9.4-opentelemetry branch from 7ae0382 to 43533e3 Compare August 6, 2026 11:01
@elastic-renovate-prod
elastic-renovate-prod Bot force-pushed the renovate/9.4-opentelemetry branch from 43533e3 to f76b6d9 Compare August 6, 2026 19:03
@mergify

mergify Bot commented Aug 7, 2026

Copy link
Copy Markdown
Contributor

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b renovate/9.4-opentelemetry upstream/renovate/9.4-opentelemetry
git merge upstream/9.4
git push upstream renovate/9.4-opentelemetry

@elastic-renovate-prod
elastic-renovate-prod Bot force-pushed the renovate/9.4-opentelemetry branch from f76b6d9 to 084320c Compare August 7, 2026 03:01
@elastic-renovate-prod
elastic-renovate-prod Bot force-pushed the renovate/9.4-opentelemetry branch from 084320c to f60a526 Compare August 7, 2026 18:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport-skip dependencies Pull requests that update a dependency file renovate renovate-auto-approve Team:Security-Cloud Services Security Data Experience - Cloud Services team.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants