Repository navigation
Bump OpenTelemetry and OpenTelemetry.Exporter.InMemory - #139
Merged
Merged
Conversation
Bumps OpenTelemetry from 1.20.1 to 1.21.0 Bumps OpenTelemetry.Exporter.InMemory from 1.20.1 to 1.21.0 --- updated-dependencies: - dependency-name: OpenTelemetry dependency-version: 1.21.0 dependency-type: direct:production update-type: version-update:semver-minor - dependency-name: OpenTelemetry.Exporter.InMemory dependency-version: 1.21.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/nuget/src/multi-3514cdffb6
branch
from
November 12, 2026 03:59
a3a437f to
146ca2b
Compare
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.
Updated OpenTelemetry from 1.20.1 to 1.21.0.
Release notes
Sourced from OpenTelemetry's releases.
1.21.0
For highlights and announcements pertaining to this release see: Release Notes > 1.21.0.
The following changes are from the previous release 1.21.0-rc.2.
NuGet: OpenTelemetry v1.21.0
OpenTelemetryLoggerOptionsis now bound from theLogging:OpenTelemetryconfiguration section using the configuration binding source generator instead
of reflection, making it fully trim and Native AOT compatible. An empty value
for a boolean option is now ignored on all target frameworks rather than
throwing on some, depending on the version of
Microsoft.Extensions.Configuration.Binderin use.(#8100)
Fixed the self-diagnostics environment snapshot leaving a dangling comma in a
redacted
OTEL_RESOURCE_ATTRIBUTESvalue when it contained empty entries.(#8104)
See CHANGELOG for details.
NuGet: OpenTelemetry.Api v1.21.0
System.Diagnostics.DiagnosticSourcedependency to11.0.0for all target frameworks.
(#8066)
See CHANGELOG for details.
NuGet: OpenTelemetry.Api.ProviderBuilderExtensions v1.21.0
No notable changes.
See CHANGELOG for details.
NuGet: OpenTelemetry.Exporter.Console v1.21.0
No notable changes.
See CHANGELOG for details.
NuGet: OpenTelemetry.Exporter.InMemory v1.21.0
No notable changes.
See CHANGELOG for details.
NuGet: OpenTelemetry.Exporter.OpenTelemetryProtocol v1.21.0
... (truncated)
1.21.0-rc.2
The following changes are from the previous release 1.21.0-rc.1.
NuGet: OpenTelemetry v1.21.0-rc.2
Fixed an exception when downscaling empty exponential histogram buckets after
a reset.
(#8064)
Fixed tracing callbacks continuing after provider shutdown or disposal on older
target frameworks.
(#8065)
Fixed initialization failures when environment variable access is denied.
Configuration reloads retain the last successful values when access is denied.
(#8070)
Fixed a source, meter or legacy activity name with a trailing line feed
matching a wildcard pattern which does not end in a wildcard.
(#8074)
Fixed
OTEL_RESOURCE_ATTRIBUTESvalues being decoded as form data, whichchanged a
+to a space. Values are now only percent-decoded, as defined bythe Resource SDK specification.
(#8074)
Updated the schema URL of resources created by the SDK to use OpenTelemetry
Semantic Conventions version
1.45.0.(#8079)
Added support for batching the metric points exported by
PeriodicExportingMetricReader. When a maximum export batch size is set,using the new constructor overload or
PeriodicExportingMetricReaderOptions.MaxExportBatchSize, the metricpoints of each collection are split into batches of at most that many
metric points, even if that splits up the metric points of a single
metric. The batches are exported serially with the export timeout
applying to each export. It can also be configured with the
OTEL_METRIC_EXPORT_MAX_BATCH_SIZEenvironment variable.(#8053)
Fixed
PeriodicExportingMetricReaderexporting a collection which was stillin progress when
Shutdown()timed out to its exporter after the exporterhad been shut down.
(#8053)
Fixed
PeriodicExportingMetricReadernot making its final collection whenShutdown()was called before its background task had started running onplatforms where threading is not available, such as browsers.
(#8053)
... (truncated)
1.21.0-rc.1
The following changes are from the previous release 1.20.1.
NuGet: OpenTelemetry v1.21.0-rc.1
Fixed a race in the self-diagnostics sink dispatcher where disposing it
while its pump thread was exiting could throw
ArgumentNullExceptionon.NET Framework.
(#7983)
SelfDiagnosticsOptionsis now automatically bound from theOpenTelemetry:SelfDiagnosticsconfiguration section, when present.(#8008)
Fixed a race where collecting a metric with delta temporality concurrently
with the creation of a new
MetricPointcould reclaim theMetricPointwhile it was being created, losing the measurement.
(#8019)
Fixed a race where collecting a metric with delta temporality could export
the same series twice in a single collection.
(#8019)
Fixed wildcard matching timeouts that could prevent configured source, meter,
legacy activity, or metric view patterns from matching.
(#8014)
The timeout passed to
MetricReader.Collect()(for example byMeterProvider.ForceFlush()), theExportTimeoutMillisecondsofPeriodicExportingMetricReaderand theExporterTimeoutMillisecondsofBatchExportProcessor<T>are now made available to the exporter instead ofbeing ignored once the export has started, so that the OTLP exporter can
cancel an export which runs past the timeout. The
ExportTimeoutMillisecondsof
PeriodicExportingMetricReadernow also limits exports which are notstarted by the reader itself, such as those of
MeterProvider.ForceFlush().(#7996)
Fixed a race where collecting a cumulative metric concurrently with the
creation of a new
MetricPointcould export aMetricPointthat was not yetfully initialized, could case a
NullReferenceExceptionwhen enumeratingTags.(#8018)
Breaking Change Dropped support for
net8.0andnet9.0.(#6899)
Add support for .NET 11.0.
(#6899)
Added support for enabling
ActivitySources from configuration using theMicrosoft.Extensions.Diagnosticstracing APIs introduced in .NET 11 (forexample,
services.AddTracing(b => b.AddConfiguration(section))).... (truncated)
1.21.0-beta.1
The following changes are from the previous release 1.20.1-beta.1.
NuGet: OpenTelemetry.Exporter.Prometheus.AspNetCore v1.21.0-beta.1
Fixed OpenMetrics scrape responses containing a
# UNITline whose unit isnot an underscore-separated suffix of the metric family name (for example
auth.failedloginswith the unitlogins), which caused scrapers such asPrometheus to reject the whole response. The
# UNITline is now omittedfor such metrics; exported metric names are unchanged.
(#7993)
Fixed scrapes that negotiate different response formats within the
ScrapeResponseCacheDurationMillisecondswindow each triggering their ownmetrics collection. A collection now also writes the response for other
formats whose scrapes arrived alongside a previous collection, so scrapes
that keep arriving together are served from the cache. Fresh cached responses
remain available while another format is serialized, even if that
serialization fails.
(#7994)
Fixed array- and map-valued attributes being serialized as the .NET type
name (e.g.
System.Byte[],System.Int32[]) instead of being JSON-encodedas per the specification.
byte[]-valued attributes are nowBase64-encoded, and other array- and map-valued attributes are now
JSON-encoded.
(#7694)
Fixed arrays of string-valued key/value pairs being
serialized as JSON arrays of strings instead of JSON objects.
(#7694)
Fixed scrape clients which stop reading their response delaying other
scrapes until
ScrapeResponseTimeoutMillisecondselapses.(#8041)
Breaking Change Dropped support for
net8.0andnet9.0.(#6899)
Add support for .NET 11.0.
(#6899)
Fixed a scrape response containing the same series (metric name and labels)
more than once, which causes Prometheus to reject the whole response, such as
when metric or tag names are the same once escaped, tag names become the same
when UTF-8 encoded, or the scope information is disabled. Duplicate series are
now dropped, and a warning event is written.
A metric which has the name of a sample that is generated for another one
(for example
_sumof a histogram) is now dropped, and a warning event iswritten.
(#8076)
... (truncated)
Commits viewable in compare view.
Updated OpenTelemetry.Exporter.InMemory from 1.20.1 to 1.21.0.
Release notes
Sourced from OpenTelemetry.Exporter.InMemory's releases.
1.21.0
For highlights and announcements pertaining to this release see: Release Notes > 1.21.0.
The following changes are from the previous release 1.21.0-rc.2.
NuGet: OpenTelemetry v1.21.0
OpenTelemetryLoggerOptionsis now bound from theLogging:OpenTelemetryconfiguration section using the configuration binding source generator instead
of reflection, making it fully trim and Native AOT compatible. An empty value
for a boolean option is now ignored on all target frameworks rather than
throwing on some, depending on the version of
Microsoft.Extensions.Configuration.Binderin use.(#8100)
Fixed the self-diagnostics environment snapshot leaving a dangling comma in a
redacted
OTEL_RESOURCE_ATTRIBUTESvalue when it contained empty entries.(#8104)
See CHANGELOG for details.
NuGet: OpenTelemetry.Api v1.21.0
System.Diagnostics.DiagnosticSourcedependency to11.0.0for all target frameworks.
(#8066)
See CHANGELOG for details.
NuGet: OpenTelemetry.Api.ProviderBuilderExtensions v1.21.0
No notable changes.
See CHANGELOG for details.
NuGet: OpenTelemetry.Exporter.Console v1.21.0
No notable changes.
See CHANGELOG for details.
NuGet: OpenTelemetry.Exporter.InMemory v1.21.0
No notable changes.
See CHANGELOG for details.
NuGet: OpenTelemetry.Exporter.OpenTelemetryProtocol v1.21.0
... (truncated)
1.21.0-rc.2
The following changes are from the previous release 1.21.0-rc.1.
NuGet: OpenTelemetry v1.21.0-rc.2
Fixed an exception when downscaling empty exponential histogram buckets after
a reset.
(#8064)
Fixed tracing callbacks continuing after provider shutdown or disposal on older
target frameworks.
(#8065)
Fixed initialization failures when environment variable access is denied.
Configuration reloads retain the last successful values when access is denied.
(#8070)
Fixed a source, meter or legacy activity name with a trailing line feed
matching a wildcard pattern which does not end in a wildcard.
(#8074)
Fixed
OTEL_RESOURCE_ATTRIBUTESvalues being decoded as form data, whichchanged a
+to a space. Values are now only percent-decoded, as defined bythe Resource SDK specification.
(#8074)
Updated the schema URL of resources created by the SDK to use OpenTelemetry
Semantic Conventions version
1.45.0.(#8079)
Added support for batching the metric points exported by
PeriodicExportingMetricReader. When a maximum export batch size is set,using the new constructor overload or
PeriodicExportingMetricReaderOptions.MaxExportBatchSize, the metricpoints of each collection are split into batches of at most that many
metric points, even if that splits up the metric points of a single
metric. The batches are exported serially with the export timeout
applying to each export. It can also be configured with the
OTEL_METRIC_EXPORT_MAX_BATCH_SIZEenvironment variable.(#8053)
Fixed
PeriodicExportingMetricReaderexporting a collection which was stillin progress when
Shutdown()timed out to its exporter after the exporterhad been shut down.
(#8053)
Fixed
PeriodicExportingMetricReadernot making its final collection whenShutdown()was called before its background task had started running onplatforms where threading is not available, such as browsers.
(#8053)
... (truncated)
1.21.0-rc.1
The following changes are from the previous release 1.20.1.
NuGet: OpenTelemetry v1.21.0-rc.1
Fixed a race in the self-diagnostics sink dispatcher where disposing it
while its pump thread was exiting could throw
ArgumentNullExceptionon.NET Framework.
(#7983)
SelfDiagnosticsOptionsis now automatically bound from theOpenTelemetry:SelfDiagnosticsconfiguration section, when present.(#8008)
Fixed a race where collecting a metric with delta temporality concurrently
with the creation of a new
MetricPointcould reclaim theMetricPointwhile it was being created, losing the measurement.
(#8019)
Fixed a race where collecting a metric with delta temporality could export
the same series twice in a single collection.
(#8019)
Fixed wildcard matching timeouts that could prevent configured source, meter,
legacy activity, or metric view patterns from matching.
(#8014)
The timeout passed to
MetricReader.Collect()(for example byMeterProvider.ForceFlush()), theExportTimeoutMillisecondsofPeriodicExportingMetricReaderand theExporterTimeoutMillisecondsofBatchExportProcessor<T>are now made available to the exporter instead ofbeing ignored once the export has started, so that the OTLP exporter can
cancel an export which runs past the timeout. The
ExportTimeoutMillisecondsof
PeriodicExportingMetricReadernow also limits exports which are notstarted by the reader itself, such as those of
MeterProvider.ForceFlush().(#7996)
Fixed a race where collecting a cumulative metric concurrently with the
creation of a new
MetricPointcould export aMetricPointthat was not yetfully initialized, could case a
NullReferenceExceptionwhen enumeratingTags.(#8018)
Breaking Change Dropped support for
net8.0andnet9.0.(#6899)
Add support for .NET 11.0.
(#6899)
Added support for enabling
ActivitySources from configuration using theMicrosoft.Extensions.Diagnosticstracing APIs introduced in .NET 11 (forexample,
services.AddTracing(b => b.AddConfiguration(section))).... (truncated)
1.21.0-beta.1
The following changes are from the previous release 1.20.1-beta.1.
NuGet: OpenTelemetry.Exporter.Prometheus.AspNetCore v1.21.0-beta.1
Fixed OpenMetrics scrape responses containing a
# UNITline whose unit isnot an underscore-separated suffix of the metric family name (for example
auth.failedloginswith the unitlogins), which caused scrapers such asPrometheus to reject the whole response. The
# UNITline is now omittedfor such metrics; exported metric names are unchanged.
(#7993)
Fixed scrapes that negotiate different response formats within the
ScrapeResponseCacheDurationMillisecondswindow each triggering their ownmetrics collection. A collection now also writes the response for other
formats whose scrapes arrived alongside a previous collection, so scrapes
that keep arriving together are served from the cache. Fresh cached responses
remain available while another format is serialized, even if that
serialization fails.
(#7994)
Fixed array- and map-valued attributes being serialized as the .NET type
name (e.g.
System.Byte[],System.Int32[]) instead of being JSON-encodedas per the specification.
byte[]-valued attributes are nowBase64-encoded, and other array- and map-valued attributes are now
JSON-encoded.
(#7694)
Fixed arrays of string-valued key/value pairs being
serialized as JSON arrays of strings instead of JSON objects.
(#7694)
Fixed scrape clients which stop reading their response delaying other
scrapes until
ScrapeResponseTimeoutMillisecondselapses.(#8041)
Breaking Change Dropped support for
net8.0andnet9.0.(#6899)
Add support for .NET 11.0.
(#6899)
Fixed a scrape response containing the same series (metric name and labels)
more than once, which causes Prometheus to reject the whole response, such as
when metric or tag names are the same once escaped, tag names become the same
when UTF-8 encoded, or the scope information is disabled. Duplicate series are
now dropped, and a warning event is written.
A metric which has the name of a sample that is generated for another one
(for example
_sumof a histogram) is now dropped, and a warning event iswritten.
(#8076)
... (truncated)
Commits viewable in compare view.