chore(deps): bump OpenTelemetry SDK to v1.44.0 / v0.20.0#517
Open
nickytd wants to merge 1 commit into
Open
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
Upgrades the OpenTelemetry Go SDK family: - go.opentelemetry.io/otel v1.43.0 -> v1.44.0 - go.opentelemetry.io/otel/sdk v1.43.0 -> v1.44.0 - go.opentelemetry.io/otel/sdk/metric v1.43.0 -> v1.44.0 - go.opentelemetry.io/otel/trace v1.43.0 -> v1.44.0 - go.opentelemetry.io/otel/log v0.19.0 -> v0.20.0 - go.opentelemetry.io/otel/sdk/log v0.19.0 -> v0.20.0 - go.opentelemetry.io/otel/sdk/log/logtest v0.19.0 -> v0.20.0 - go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploggrpc v0.19.0 -> v0.20.0 - go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploghttp v0.19.0 -> v0.20.0 - go.opentelemetry.io/otel/exporters/prometheus v0.65.0 -> v0.66.0 Notable upstream fixes pulled in: - otlploghttp/otlpmetrichttp: replay gzipped request body on redirect, fixing a pooled-gzip-writer leak under sustained load behind a redirecting proxy. - semconv: clear cached/pooled slices to enable GC. - prometheus exporter: fix concurrent Collect data race when WithResourceAsConstantLabels is used. - All OTLP exporters gain WithMaxRequestSize (default 64 MiB). Heads-up (not triggered by current usage, but worth noting): sdk/metric now applies a default cardinality limit of 2000. Use WithCardinalityLimit(0) on the meter provider to restore unlimited cardinality if needed.
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.
How to categorize this PR?
/kind cleanup
/area logging
/area open-source
What this PR does / why we need it:
Bumps the OpenTelemetry Go SDK family from
v1.43.0/v0.19.0tov1.44.0/v0.20.0(single upstream releasev1.44.0/v0.66.0/v0.20.0, published 2026-05-27).Modules upgraded:
go.opentelemetry.io/otelgo.opentelemetry.io/otel/sdkgo.opentelemetry.io/otel/sdk/metricgo.opentelemetry.io/otel/tracego.opentelemetry.io/otel/loggo.opentelemetry.io/otel/sdk/loggo.opentelemetry.io/otel/sdk/log/logtestgo.opentelemetry.io/otel/exporters/otlp/otlplog/otlploggrpcgo.opentelemetry.io/otel/exporters/otlp/otlplog/otlploghttpgo.opentelemetry.io/otel/exporters/prometheusThe bump is API-compatible — only
go.modandgo.sumchange.Notable upstream fixes pulled in (full changelog):
otlploghttpandotlpmetrichttpnow correctly replay gzipped request bodies on HTTP redirects. The previous behavior could leak pooled gzip writer buffers per redirected request under sustained load behind a redirecting proxy/ingress. This plugin enables gzip by default, so the fix directly applies.semconv— pooled slices and cached objects are now cleared after release so they can be garbage collected.Collectdata race whenWithResourceAsConstantLabelsis configured (not triggered by current usage, but a relevant hardening since we use the Prometheus exporter for OTLP metrics passthrough).WithMaxRequestSizeoption, defaulted to 64 MiB. Oversized requests are non-retryable.GHSA-995v-fvrw-c78m(schema file descriptor leak) andGHSA-5wrp-cwcj-q835(baggage extraction log flooding).Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Heads-up — not triggered by current usage, but worth knowing for future work:
sdk/metricin v1.44.0 applies a default cardinality limit of 2000 per instrument (previously unlimited). Attribute sets beyond the limit are folded into a synthetic set taggedotel.metric.overflow=true. If we ever produce per-shoot/per-namespace label combinations exceeding 2000 on a single meter, setWithCardinalityLimit(0)on the meter provider inpkg/client/otlp/metrics_setup.goto restore the old behavior.attribute.Value.Emit()is deprecated in favor ofValue.String(). We don't currently call it.Verified locally:
passes clean. No source changes were necessary.
Release note: