Bump go.opentelemetry.io/otel from 1.31.0 to 1.32.0

[dependabot]

Bumps go.opentelemetry.io/otel from 1.31.0 to 1.32.0.

Changelog

Sourced from go.opentelemetry.io/otel's changelog.

[1.32.0/0.54.0/0.8.0/0.0.11] 2024-11-08

Added

• Add go.opentelemetry.io/otel/sdk/metric/exemplar.AlwaysOffFilter, which can be used to disable exemplar recording. (#5850)
• Add go.opentelemetry.io/otel/sdk/metric.WithExemplarFilter, which can be used to configure the exemplar filter used by the metrics SDK. (#5850)
• Add ExemplarReservoirProviderSelector and DefaultExemplarReservoirProviderSelector to go.opentelemetry.io/otel/sdk/metric, which defines the exemplar reservoir to use based on the aggregation of the metric. (#5861)
• Add ExemplarReservoirProviderSelector to go.opentelemetry.io/otel/sdk/metric.Stream to allow using views to configure the exemplar reservoir to use for a metric. (#5861)
• Add ReservoirProvider, HistogramReservoirProvider and FixedSizeReservoirProvider to go.opentelemetry.io/otel/sdk/metric/exemplar to make it convenient to use providers of Reservoirs. (#5861)
• The go.opentelemetry.io/otel/semconv/v1.27.0 package. The package contains semantic conventions from the v1.27.0 version of the OpenTelemetry Semantic Conventions. (#5894)
• Add Attributes attribute.Set field to Scope in go.opentelemetry.io/otel/sdk/instrumentation. (#5903)
• Add Attributes attribute.Set field to ScopeRecords in go.opentelemetry.io/otel/log/logtest. (#5927)
• go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc adds instrumentation scope attributes. (#5934)
• go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp adds instrumentation scope attributes. (#5934)
• go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetricgrpc adds instrumentation scope attributes. (#5935)
• go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp adds instrumentation scope attributes. (#5935)
• go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploggrpc adds instrumentation scope attributes. (#5933)
• go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploghttp adds instrumentation scope attributes. (#5933)
• go.opentelemetry.io/otel/exporters/prometheus adds instrumentation scope attributes in otel_scope_info metric as labels. (#5932)

Changed

• Support scope attributes and make them as identifying for Tracer in go.opentelemetry.io/otel and go.opentelemetry.io/otel/sdk/trace. (#5924)
• Support scope attributes and make them as identifying for Meter in go.opentelemetry.io/otel and go.opentelemetry.io/otel/sdk/metric. (#5926)
• Support scope attributes and make them as identifying for Logger in go.opentelemetry.io/otel and go.opentelemetry.io/otel/sdk/log. (#5925)
• Make schema URL and scope attributes as identifying for Tracer in go.opentelemetry.io/otel/bridge/opentracing. (#5931)
• Clear unneeded slice elements to allow GC to collect the objects in go.opentelemetry.io/otel/sdk/metric and go.opentelemetry.io/otel/sdk/trace. (#5804)

Fixed

• Global MeterProvider registration unwraps global instrument Observers, the undocumented Unwrap() methods are now private. (#5881)
• go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetricgrpc now keeps the metadata already present in the context when WithHeaders is used. (#5892)
• go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploggrpc now keeps the metadata already present in the context when WithHeaders is used. (#5911)
• go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc now keeps the metadata already present in the context when WithHeaders is used. (#5915)
• Fix go.opentelemetry.io/otel/exporters/prometheus trying to add exemplars to Gauge metrics, which is unsupported. (#5912)
• Fix WithEndpointURL to always use a secure connection when an https URL is passed in go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetricgrpc. (#5944)
• Fix WithEndpointURL to always use a secure connection when an https URL is passed in go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp. (#5944)
• Fix WithEndpointURL to always use a secure connection when an https URL is passed in go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracegrpc. (#5944)
• Fix WithEndpointURL to always use a secure connection when an https URL is passed in go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp. (#5944)
• Fix incorrect metrics generated from callbacks when multiple readers are used in go.opentelemetry.io/otel/sdk/metric. (#5900)

Removed

• Remove all examples under go.opentelemetry.io/otel/example as they are moved to Contrib repository. (#5930)

Commits

• 7cfbd86 Release v1.32.0/v0.54.0/v0.8.0/v0.0.11 (#5960)
• 2be617e fix(deps): update github.com/opentracing-contrib/go-grpc/test digest to 51a56...
• 6db18df fix(deps): update module github.com/opentracing-contrib/go-grpc to v0.1.0 (#5...
• ef12bf8 chore(deps): update golang.org/x (#5957)
• 85eb76f Allow GC to collect unneeded slice elements (#5804)
• 1492efa Fix incorrect metrics getting generated from multiple readers (#5900)
• d2b0663 fix(deps): update module go.opentelemetry.io/build-tools/multimod to v0.15.0 ...
• 394cbd2 chore(deps): update lycheeverse/lychee-action action to v2.1.0 (#5950)
• 37b2537 fix(deps): update github.com/opentracing-contrib/go-grpc digest to e3cbcab (#...
• 7f68356 fix(deps): update module go.opentelemetry.io/build-tools/semconvgen to v0.15....
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[cit-pr-commenter]

Regression Detector

Regression Detector Results

Metrics dashboard
Target profiles
Run ID: 26a9678f-82de-4445-8375-a0744c86d4cb

Baseline: 958c609
Comparison: 0fea19b
Diff

Optimization Goals: ✅ No significant changes detected

Fine details of change detection per experiment

perf	experiment	goal	Δ mean %	Δ mean % CI	trials	links
➖	basic_py_check	% cpu utilization	+3.20	[-0.71, +7.11]	1	Logs
➖	pycheck_lots_of_tags	% cpu utilization	+1.31	[-2.14, +4.77]	1	Logs
➖	quality_gate_idle_all_features	memory utilization	+0.90	[+0.80, +1.00]	1	Logs bounds checks dashboard
➖	uds_dogstatsd_to_api_cpu	% cpu utilization	+0.72	[-0.01, +1.46]	1	Logs
➖	tcp_dd_logs_filter_exclude	ingress throughput	+0.00	[-0.01, +0.01]	1	Logs
➖	uds_dogstatsd_to_api	ingress throughput	-0.01	[-0.10, +0.09]	1	Logs
➖	file_to_blackhole_500ms_latency	egress throughput	-0.02	[-0.26, +0.23]	1	Logs
➖	file_tree	memory utilization	-0.03	[-0.17, +0.10]	1	Logs
➖	file_to_blackhole_1000ms_latency	egress throughput	-0.04	[-0.53, +0.46]	1	Logs
➖	quality_gate_idle	memory utilization	-0.05	[-0.10, -0.00]	1	Logs bounds checks dashboard
➖	file_to_blackhole_0ms_latency	egress throughput	-0.06	[-0.53, +0.42]	1	Logs
➖	file_to_blackhole_100ms_latency	egress throughput	-0.06	[-0.39, +0.26]	1	Logs
➖	file_to_blackhole_300ms_latency	egress throughput	-0.12	[-0.32, +0.07]	1	Logs
➖	tcp_syslog_to_blackhole	ingress throughput	-0.35	[-0.40, -0.30]	1	Logs
➖	otel_to_otel_logs	ingress throughput	-1.25	[-1.91, -0.59]	1	Logs

Bounds Checks: ❌ Failed

perf	experiment	bounds_check_name	replicates_passed	links
❌	quality_gate_idle	memory_usage	7/10	bounds checks dashboard
❌	file_to_blackhole_0ms_latency	lost_bytes	8/10
❌	quality_gate_idle_all_features	memory_usage	9/10	bounds checks dashboard
✅	file_to_blackhole_0ms_latency	memory_usage	10/10
✅	file_to_blackhole_1000ms_latency	memory_usage	10/10
✅	file_to_blackhole_100ms_latency	lost_bytes	10/10
✅	file_to_blackhole_100ms_latency	memory_usage	10/10
✅	file_to_blackhole_300ms_latency	memory_usage	10/10
✅	file_to_blackhole_500ms_latency	memory_usage	10/10

Explanation

Confidence level: 90.00%
Effect size tolerance: |Δ mean %| ≥ 5.00%

Performance changes are noted in the perf column of each table:

• ✅ = significantly better comparison variant performance
• ❌ = significantly worse comparison variant performance
• ➖ = no significant change in performance

A regression test is an A/B test of target performance in a repeatable rig, where "performance" is measured as "comparison variant minus baseline variant" for an optimization goal (e.g., ingress throughput). Due to intrinsic variability in measuring that goal, we can only estimate its mean value for each experiment; we report uncertainty in that value as a 90.00% confidence interval denoted "Δ mean % CI".

For each experiment, we decide whether a change in performance is a "regression" -- a change worth investigating further -- if all of the following criteria are true:

1. Its estimated |Δ mean %| ≥ 5.00%, indicating the change is big enough to merit a closer look.

2. Its 90.00% confidence interval "Δ mean % CI" does not contain zero, indicating that if our statistical model is accurate, there is at least a 90.00% chance there is a difference in performance between baseline and comparison variants.

3. Its configuration does not mark it "erratic".

[dependabot]

Looks like go.opentelemetry.io/otel is up-to-date now, so this is no longer needed.