Release v1.36.0/v0.58.0/v0.12.0

[dmathieu]

Overview

Closes #6786

Added

• Add exponential histogram support in go.opentelemetry.io/otel/exporters/prometheus. (exporters: prometheus: add exponential (native) histogram support #6421)
• The go.opentelemetry.io/otel/semconv/v1.31.0 package.
  The package contains semantic conventions from the v1.31.0 version of the OpenTelemetry Semantic Conventions.
  See the migration documentation for information on how to upgrade from go.opentelemetry.io/otel/semconv/v1.30.0. (Generate v1.31.0 semconv #6479)
• Add Recording, Scope, and Record types in go.opentelemetry.io/otel/log/logtest. (log/logtest: Change Recorder.Result #6507)
• Add WithHTTPClient option to configure the http.Client used by go.opentelemetry.io/otel/exporters/otlp/otlptrace/otlptracehttp. (otlptracehttp: Add WithHTTPClient option #6751)
• Add WithHTTPClient option to configure the http.Client used by go.opentelemetry.io/otel/exporters/otlp/otlpmetric/otlpmetrichttp. (otlpmetrichttp: Add WithHTTPClient option #6752)
• Add WithHTTPClient option to configure the http.Client used by go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploghttp. (otlploghttp: Add WithHTTPClient option #6688)
• Add ValuesGetter in go.opentelemetry.io/otel/propagation, a TextMapCarrier that supports retrieving multiple values for a single key. (propagation: extract of multiple header values #5973)
• Add Values method to HeaderCarrier to implement the new ValuesGetter interface in go.opentelemetry.io/otel/propagation. (propagation: extract of multiple header values #5973)
• Update Baggage in go.opentelemetry.io/otel/propagation to retrieve multiple values for a key when the carrier implements ValuesGetter. (propagation: extract of multiple header values #5973)
• Add AssertEqual function in go.opentelemetry.io/otel/log/logtest. (log/logtest: Add AssertEqual and remove AssertRecordEqual #6662)
• The go.opentelemetry.io/otel/semconv/v1.32.0 package.
  The package contains semantic conventions from the v1.32.0 version of the OpenTelemetry Semantic Conventions.
  See the migration documentation for information on how to upgrade from go.opentelemetry.io/otel/semconv/v1.31.0(Add semconv/v1.32.0 #6782)
• Add Transform option in go.opentelemetry.io/otel/log/logtest. (logtest: add Transform #6794)
• Add Desc option in go.opentelemetry.io/otel/log/logtest. (logtest: add Desc #6796)

Removed

• Drop support for [Go 1.22]. (Drop support for Go 1.22 #6381, Bump Go version for schema #6418)
• Remove Resource field from EnabledParameters in go.opentelemetry.io/otel/sdk/log. (sdk/log: remove EnabledParameters.Resource #6494)
• Remove RecordFactory type from go.opentelemetry.io/otel/log/logtest. (log/logtest: Remove RecordFactory #6492)
• Remove ScopeRecords, EmittedRecord, and RecordFactory types from go.opentelemetry.io/otel/log/logtest. (log/logtest: Change Recorder.Result #6507)
• Remove AssertRecordEqual function in go.opentelemetry.io/otel/log/logtest, use AssertEqual instead. (log/logtest: Add AssertEqual and remove AssertRecordEqual #6662)

Changed

• ⚠️ Update github.com/prometheus/client_golang to v1.21.1, which changes the NameValidationScheme to UTF8Validation.
  This allows metrics names to keep original delimiters (e.g. .), rather than replacing with underscores.
  This can be reverted by setting github.com/prometheus/common/model.NameValidationScheme to LegacyValidation in github.com/prometheus/common/model. (chore(deps): update github.com/prometheus/client_golang to v1.21.1 #6433)
• Initialize map with len(keys) in NewAllowKeysFilter and NewDenyKeysFilter to avoid unnecessary allocations in go.opentelemetry.io/otel/attribute. (attribute: preallocate map in NewAllowKeysFilter and NewDenyKeysFilter #6455)
• go.opentelemetry.io/otel/log/logtest is now a separate Go module. (log/logtest: new module #6465)
• go.opentelemetry.io/otel/sdk/log/logtest is now a separate Go module. (sdk/log/logtest: new module #6466)
• Recorder in go.opentelemetry.io/otel/log/logtest no longer separately stores records emitted by loggers with the same instrumentation scope. (log/logtest: Change Recorder.Result #6507)
• Improve performance of BatchProcessor in go.opentelemetry.io/otel/sdk/log by not exporting when exporter cannot accept more. (Optimize Logs SDK BatchProcessor #6569, sdk/log: remove unnecessary b.q.Len() call #6641)

Deprecated

• Deprecate support for model.LegacyValidation for go.opentelemetry.io/otel/exporters/prometheus. (Ignore deprecation warnings about NameValidationScheme #6449)

Fixes

• Stop percent encoding header environment variables in go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploggrpc and go.opentelemetry.io/otel/exporters/otlp/otlplog/otlploghttp. (Stop percent-encoding the header environment variables in otlplog exporters #6392)
• Ensure the noopSpan.tracerProvider method is not inlined in go.opentelemetry.io/otel/trace so the go.opentelemetry.io/auto instrumentation can instrument non-recording spans. (Do not inline noopSpan.tracerProvider #6456)
• Use a sync.Pool instead of allocating metricdata.ResourceMetrics in go.opentelemetry.io/otel/exporters/prometheus. (prometheus: use a sync.Pool instead of allocating metricdata.ResourceMetrics in Collect #6472)

[pellared]

@dmathieu, @dashpole, just to double-check.
Is there something we should address for Prometheus exporter or is it good to go?
Related:

• chore(deps): update github.com/prometheus/client_golang to v1.21.1 #6433
• Ignore deprecation warnings about NameValidationScheme #6449

CC @ywwg @ArthurSens

[dashpole]

@pellared i don't think we should log the warning. If a user is setting model.NameValidationScheme, they are already using a deprecated field. We should continue to support the legacy validation scheme until it is removed from the Prometheus library, or just keep it.

[dmathieu]

We already removed the warning from the changelog. So we should be good here.
I believe semconv 1.32.0 is the only blocked for this release.

[pellared]

@dashpole, what do you think of adding #5947 to the release? Do you think there would be issues if we merge it to in order to get some momentum? I am aware that the behavior is not in the spec yet, however it is an experimental exporter (both in the spec and the implementation).

[ArthurSens]

@dashpole, what do you think of adding #5947 to the release? Do you think there would be issues if we merge it to in order to get some momentum? I am aware that the behavior is not in the spec yet, however it is an experimental exporter (both in the spec and the implementation).

Could we test the interaction with Prometheus receiver before making this decision? The PR you mention only adds new labels, but doesn't remove otel_scope_info, right? I suspect that all the otel_scope_[attributes] labels will become metric attributes, instead of scope attributes 😬

[pellared]

Could we test the interaction with Prometheus receiver before making this decision?

@ArthurSens, sure.

The PR you mention only adds new labels, but doesn't remove otel_scope_info, right?

Correct.

I suspect that all the otel_scope_[attributes] labels will become metric attributes, instead of scope attributes

I am pretty sure you are correct! However, TBH I have never seen scope attributes being used 😅

[dmathieu]

This required testing makes me think we shouldn't include that PR into the release.

[pellared]

Please update the PR description with new changelog entries 😉