fix(deps): update opentelemetry (main) - #6504
Open
elastic-renovate-prod[bot] wants to merge 1 commit into
Open
Conversation
elastic-renovate-prod
Bot
force-pushed
the
renovate/main-opentelemetry
branch
from
May 29, 2026 14:59
c5f7f95 to
76a2c9c
Compare
elastic-renovate-prod
Bot
force-pushed
the
renovate/main-opentelemetry
branch
from
May 29, 2026 19:45
76a2c9c to
043a1eb
Compare
elastic-renovate-prod
Bot
force-pushed
the
renovate/main-opentelemetry
branch
from
May 30, 2026 06:44
043a1eb to
0fc75a8
Compare
elastic-renovate-prod
Bot
force-pushed
the
renovate/main-opentelemetry
branch
from
June 1, 2026 13:08
0fc75a8 to
f0a9d78
Compare
elastic-renovate-prod
Bot
force-pushed
the
renovate/main-opentelemetry
branch
from
June 1, 2026 13:09
f0a9d78 to
56bb8c4
Compare
elastic-renovate-prod
Bot
force-pushed
the
renovate/main-opentelemetry
branch
from
June 1, 2026 14:28
56bb8c4 to
70c0b62
Compare
elastic-renovate-prod
Bot
force-pushed
the
renovate/main-opentelemetry
branch
from
June 1, 2026 14:37
70c0b62 to
bd8ea82
Compare
elastic-renovate-prod
Bot
force-pushed
the
renovate/main-opentelemetry
branch
from
June 1, 2026 14:46
bd8ea82 to
6d80890
Compare
elastic-renovate-prod
Bot
force-pushed
the
renovate/main-opentelemetry
branch
from
July 23, 2026 16:47
48666d2 to
48c1bc1
Compare
elastic-renovate-prod
Bot
force-pushed
the
renovate/main-opentelemetry
branch
from
July 23, 2026 18:49
48c1bc1 to
3f52360
Compare
elastic-renovate-prod
Bot
force-pushed
the
renovate/main-opentelemetry
branch
from
July 24, 2026 11:46
3f52360 to
4a59f39
Compare
elastic-renovate-prod
Bot
force-pushed
the
renovate/main-opentelemetry
branch
from
July 24, 2026 19:34
4a59f39 to
c375302
Compare
elastic-renovate-prod
Bot
force-pushed
the
renovate/main-opentelemetry
branch
from
July 24, 2026 19:34
c375302 to
d0b38bb
Compare
Contributor
Author
ℹ️ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.59.0→v1.64.0v1.59.0→v1.64.0v1.59.0→v1.64.0v1.59.0→v1.64.0v1.59.0→v1.64.0v0.153.0→v0.158.0v1.59.0→v1.64.0v0.153.0→v0.158.0v1.59.0→v1.64.0v0.153.0→v0.158.0v1.59.0→v1.64.0v0.153.0→v0.158.0v1.59.0→v1.64.0v0.153.0→v0.158.0v1.59.0→v1.64.0v0.153.0→v0.158.0v0.153.0→v0.158.0v1.59.0→v1.64.0v0.153.0→v0.158.0v1.43.0→v1.44.0v0.68.0→v0.69.0v0.68.0→v0.69.0v0.68.0→v0.69.0v1.44.0→v1.45.0v1.43.0→v1.45.0v1.43.0→v1.45.0v1.43.0→v1.45.0v1.44.0→v1.45.0v1.43.0→v1.45.0v1.43.0→v1.45.0v1.44.0→v1.45.0v1.10.0→v1.11.0Warning
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 🚀
processor/queuebatch: Newqueuebatchprocessorto replace the legacybatchprocessor. (#15047, #13582, #12022, #11308, #8272, #6046)New implementation is based exporterhelper, uses same configuration as
sending_queue.💡 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, ortype: opaque_mapdirectly as a property type in theconfig:section ofmetadata.yaml.Each alias expands to the correct JSON Schema representation and Go type automatically.
Existing uses of standard JSON Schema types,
format:, andx-customType:remain supportedwithout 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-worldtoStr(hello-world).pkg/config/configtls: Fix goroutine and file descriptor leak whenclient_ca_file_reloadis enabled (#9221)Every call to
ServerConfig.LoadTLSConfigwithclient_ca_file_reloadenabled started afile 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 TLShandshakes are served, at most once per second, matching how
reload_intervalalreadyreloads 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 forotelcol_exporter_queue_batch_send_size_bytesandotelcol_processor_batch_batch_send_size_byteswith 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_bytestopped out at 6000 bytes so nearly allobservations fell into the
+Infoverflow bucket. The new boundaries are powers of two from 128 Bto
1677721(16 MiB), giving a meaningful distribution for real batch payload sizes (including smalltimeout-flushed batches) and keeping the two
metrics directly comparable on the same dashboards. Dashboards or alerts that hard-code specific
levalues for these histograms will need to be updated.
processor/batch: Replace histogram bucket boundaries forotelcol_processor_batch_batch_send_size_byteswith 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 meaningfuldistribution for real batch payload sizes (including small timeout-flushed batches) and keeping the
metric directly comparable with
otelcol_exporter_queue_batch_send_size_byteson the same dashboards. Dashboards or alerts thathard-code specific
levalues for this histogram will need to be updated.💡 Enhancements 💡
all: Bootstrapconfig.schema.yamlfor 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
schemagentool from opentelemetry-collector-contrib and hand-tuned to capturevalidation rules and references to shared library schemas (confighttp, configgrpc, configretry, exporterhelper,
etc.). A
.schemagen.yamlsettings file and agenerate-schemasMakefile target are added so the schemas canbe regenerated reproducibly.
pkg/service: Apply experimentalservice::telemetry::resource::detection/developmentresource detection to the Collector's internal telemetry resource. (#14311)This follows the OpenTelemetry configuration schema by treating
service::telemetry::resource::detection/development::detectorsas detector selection.Currently supported detector entries are
container,host,process, andservice.See the OpenTelemetry Configuration Go support table and search for
ExperimentalResourceDetectorfor current detector support:https://github.com/open-telemetry/opentelemetry-configuration/blob/main/language-support-status.md#go
Example:
pkg/service: Addservice.partialReloadfeature gate (Alpha) andservice.partialReloadReceiversfeature 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 thenormalverbosity 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
#0instead of#1.pkg/config/configgrpc: FixWaitForReadyoption not being applied to gRPC client connections. (#15615)pkg/featuregate: Fix panic when a--feature-gatesvalue 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. theprocessdetector'sprocess.command_args) (#15571)createResourcepassed the OTel SDK attribute value straight intopcommon.Value.FromRaw, whichonly accepts
[]anyfor slices, so any string, int, float, or bool slice resource attribute producedan
<Invalid value type>error and abortedservice.New. Slice-typed attributes are now convertedelement-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_limitedandmax_gc_interval_when_hard_limited(both default30s); set either to0to 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 gateconfighttp.framedSnappy(#15420)pkg/configoptional: Remove stabilized gateconfigoptional.AddEnabledField. (#15421)pkg/confmap: Remove stabilized featuregateconfmap.newExpandedValueSanitizer(#15418)pkg/exporterhelper: Remove stable gateexporter.PersistRequestContext. (#15424)pkg/otelcol: Remove stable gateotelcol.printInitialConfig(#15425)pkg/service: Remove stable featuregatetelemetry.UseLocalHostAsDefaultMetricsAddress(#15419)pkg/xpdata: Remove stable gatepdata.enableRefCounting. (#15426)processor/memory_limiter: Rename deprecated memory limiter metrics to include thememory_limiterprefix (e.g.otelcol_processor_memory_limiter_*) to clarify they are specific to this processor. (#11203)🚀 New components 🚀
cmd/schemagen: Move theschemagenCLI from opentelemetry-collector-contrib to this repository ascmd/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 toexercise 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: AddoverlayFilesupport to deep-merge hand-curated schema fragments into generated schemas. (#14543)Components can declare an
overlayFilein.schemagen.yamlpointing to a YAML filewhose 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/schemageninopen-telemetry/opentelemetry-collector-contrib#48917 and brought over with the tool
in this move.
cmd/schemagen: Add-pflag to specify a custom Go package pattern for the config struct. (#14543)The new
-pflag lets callers override the default.package pattern with an arbitraryGo package selector (e.g. a sub-package whose
Configtype schemagen should walk).Originally added to the contrib copy of
cmd/schemageninopen-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-pto target a package outside the current directory. (#15453)A new
-m component|packageflag is available as a manual override when auto-detection is not possible.v1.60.0🛑 Breaking changes 🛑
cmd/builder: The--skip-get-modulesflag will no longer regenerate yourgo.modfile. (#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, yourgo.modfile will truly be untouched byocbas the info log claims.💡 Enhancements 💡
pkg/config/configtls: Addinclude_insecure_cipher_suitesto configtls to enable insecure cipher suites. Insecure cipher suites are disabled by default for security. (#13829)pkg/confighttp: AddExposedHeadersfield toCORSConfigto allow setting theAccess-Control-Expose-Headersresponse 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 insending_queue::batchUnmarshal whensending_queue::sizeris set andsending_queue::batch::enabledis false. (#14687)When
sending_queue::sizerwas set andsending_queue::batch::enabled: falsecleared the batch Optional to None, the sizer-inheritance branch in
queuebatch.Config.Unmarshaldereferenced a nil Optional and crashed thecollector at startup. The branch now also requires
Batch.HasValue().open-telemetry/opentelemetry-go-contrib (go.opentelemetry.io/contrib/detectors/gcp)
v1.44.0: /v2.5.1/v0.69.0/v0.37.1/v0.24.0/v0.19.0/v0.16.1/v0.16.0Compare Source
Added
error.typeattribute tohttp.client.request.durationfor transport failures inotelhttp. (#8801)cardinality_limitsinPeriodicMetricReaderinotelconf. (#8885)Resourcemethod toSDKingo.opentelemetry.io/contrib/otelconf/xto expose the resolved SDK resource from declarative configuration. (#8913)go.opentelemetry.io/contrib/detectors/hetzner, a new resource detector for Hetzner Cloud servers, ported fromgithub.com/open-telemetry/opentelemetry-collector-contrib/processor/resourcedetectionprocessor/internal/hetzner. Detectscloud.provider,cloud.platform,cloud.region,cloud.availability_zone,host.id, andhost.name. (#8979)Changed
record.SetErrinstead of a plain attribute ingo.opentelemetry.io/contrib/bridges/otellogrus. (#8776)zap.Error) asrecord.SetErrinstead of a plain attribute ingo.opentelemetry.io/contrib/bridges/otelzap. (#8719)errorinterface fromslogrecords asrecord.SetErrinstead of plain attributes ingo.opentelemetry.io/contrib/bridges/otelslog. (#8774)go.opentelemetry.io/contrib/bridges/otellogras record errors (Record.SetErr) instead ofexception.messageattributes. (#8775)Fixed
go.opentelemetry.io/contrib/instrumentation/net/http/httptrace/otelhttptrace. (#8797)encodingconfiguration for OTLP HTTP exporters ingo.opentelemetry.io/contrib/otelconf. (#8772)go.opentelemetry.io/contrib/instrumentation/net/http/otelhttpandgo.opentelemetry.io/contrib/instrumentation/github.com/gorilla/mux/otelmux. (#6914)go.opentelemetry.io/contrib/instrumentation/net/http/otelhttpnow conforms to the OpenTelemetry HTTP semantic conventions for server span names. (#8871){method} {route}(e.g.GET /foo/{id}) when a route pattern is available, or{method}(e.g.GET) otherwise.Removed
WithSpanOptionsoption ingo.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc. (#8991)What's Changed
record.SetErrby @sonalgaud12 in #877893c7c8aby @renovate[bot] in #8786746e56fby @renovate[bot] in #87963e5c5a5by @renovate[bot] in #8807afd174aby @renovate[bot] in #8811afd174aby @renovate[bot] in #8816ec9c827by @renovate[bot] in #8824fac6e1cby @renovate[bot] in #8823e10c466by @renovate[bot] in #8849392afabby @renovate[bot] in #8853329d219by @renovate[bot] in #88618949caaby @renovate[bot] in #88757cedc36by @renovate[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.
This PR has been generated by Renovate Bot.