Repository navigation
Update opentelemetry-dotnet monorepo to 1.21.0 - #6074
Open
dependencyupdates[bot] wants to merge 1 commit into
Open
dependencyupdates[bot] wants to merge 1 commit into
dependencyupdates[bot] wants to merge 1 commit into
Conversation
dependencyupdates
Bot
force-pushed
the
renovate/opentelemetry-dotnet-monorepo
branch
from
November 3, 2026 08:01
f980eb3 to
b48e61e
Compare
dependencyupdates
Bot
force-pushed
the
renovate/opentelemetry-dotnet-monorepo
branch
from
November 11, 2026 13:56
b48e61e to
c79c232
Compare
dependencyupdates
Bot
force-pushed
the
renovate/opentelemetry-dotnet-monorepo
branch
from
November 13, 2026 00:18
c79c232 to
930e24c
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.
This PR contains the following updates:
1.18.0→1.21.01.17.0→1.21.01.18.0→1.21.01.17.0→1.21.01.18.0→1.21.0Release Notes
open-telemetry/opentelemetry-dotnet (OpenTelemetry.Exporter.Console)
v1.21.0Release details: 1.21.0
net8.0andnet9.0. The supported.NET targets are now
net10.0,net11.0,net462andnetstandard2.0.ActivitySources fromconfiguration using the
Microsoft.Extensions.Diagnosticstracing APIs(for example,
services.AddTracing(b => b.AddConfiguration(section))).Activities from sources enabled this way are processed by the OpenTelemetry
TracerProviderregistered throughAddOpenTelemetry().WithTracing().This is not supported when targeting
net10.0.OTLP exporter with the experimental disk retry feature enabled now throws an
UnauthorizedAccessExceptionif the retry directory could be changed byanother user. The retry directory must be owned by the current user and must
not be writable by its group or by other users, and each directory and
symbolic link in its path must be owned by the current user or by root and
must not be writable by its group or by other users unless it has the sticky
bit set (such as
/tmp). These checks can be disabled by settingOTEL_DOTNET_EXPERIMENTAL_OTLP_DISK_RETRY_CHECK_PERMISSIONStofalse.OTEL_DIAGNOSTICS.jsonnow writes rollingotel-dotnet-*.logfiles in the standard entry format instead of a circular{executable}.{pid}.logfile.FileSizeis split evenly across two retainedfiles,
FormatMessageis now ignored, and writes are asynchronous and maydrop entries when the bounded queue fills. Sinks configured through
providers, including those enabled through environment variables, override
the JSON configuration with a warning event. The preamble of each file now
includes configuration warnings and a redacted environment snapshot.
Activity.StatusDescriptionor the
otel.status_descriptiontag) exported by the OTLP exporter is nowtruncated to the configured span attribute value length limit (for example
OTEL_SPAN_ATTRIBUTE_VALUE_LENGTH_LIMIT) instead of being exported in full.EnvironmentVariableCarrierAPIs previously covered byOTEL1005are nowstable. Carrier snapshots now preserve environment variable names, preventing
extraction from non-normalized aliases and collisions with normalized names,
and follow the platform's case-sensitivity rules.
PeriodicExportingMetricReader. SetPeriodicExportingMetricReaderOptions.MaxExportBatchSize(or theOTEL_METRIC_EXPORT_MAX_BATCH_SIZEenvironment variable) to split the metricpoints of each collection into batches of at most that many metric points.
Sampler.Shutdownand the overridableSampler.OnShutdownso samplerscan release resources.
TracerProvidernow callsShutdownon its samplerwhen it is shut down or disposed, and
ParentBasedSamplerandAlwaysRecordSamplercallShutdownon the samplers they delegate to.SelfDiagnosticsOptionsis now automatically bound from theOpenTelemetry:SelfDiagnosticsconfiguration section, when present.OpenTelemetryLoggerOptionsis now bound from theLogging:OpenTelemetryconfiguration section using the configuration binding source generator
instead of reflection, making it fully trim and Native AOT compatible.
IHostedLifecycleService.StartingAsyncinstead ofIHostedService.StartAsyncso that telemetry emitted by other hosted services during
StartingAsynciscaptured.
environment resource detector to use OpenTelemetry Semantic Conventions
version
1.45.0.System.Diagnostics.DiagnosticSourcedependency to11.0.0forall target frameworks.
Acceptheader negotiation in the Prometheusexporters.
IUtf8SpanFormattable(.NET 10+) are nowformatted directly into the OTLP export buffer instead of through
ToString().MetricReader.Collect()(for example byMeterProvider.ForceFlush()), theExportTimeoutMillisecondsofPeriodicExportingMetricReaderand theExporterTimeoutMillisecondsofBatchExportProcessor<T>are now made available to the exporter. The OTLPexporter now cancels an export when the shorter of these timeouts and
OtlpExporterOptions.TimeoutMillisecondselapses, counting the time taken toserialize the telemetry, and fixed in-memory retries exceeding the export
timeout when a retried request stalls.
byte[]-valued tags and attributes, array-valued tags containingNaNor infinite values, nested arrays and maps, and arrays of string-valued
key/value pairs being exported incorrectly by the Console, OTLP, Zipkin and
Prometheus exporters. They are now exported as specified (for example
byte[]values are Base64-encoded and arrays and maps are JSON-encodedinstead of being written as a .NET type name).
# UNITline whose unitis not an underscore-separated suffix of the metric family name, which
caused Prometheus to reject the whole response. The line is now omitted.
metric named like a sample generated for another metric, which caused
Prometheus to reject the whole response. Such series and metrics are now
dropped and a warning event is written.
different response format within the
ScrapeResponseCacheDurationMillisecondswindow.until
ScrapeResponseTimeoutMillisecondselapses.a new
MetricPointcould lose the measurement or export the same seriestwice in a single collection.
creation of a new
MetricPointcould export aMetricPointthat was not yetfully initialized, causing a
NullReferenceExceptionwhen enumeratingTags.a reset.
legacy activity, or metric view patterns from matching, and a name with a
trailing line feed matching a wildcard pattern which does not end in a
wildcard.
OTEL_RESOURCE_ATTRIBUTESvalues being decoded as form data, whichchanged a
+to a space. Values are now only percent-decoded.exporters and host resource detection when environment variable access is
denied.
older target frameworks.
PeriodicExportingMetricReaderexporting a collection which was stillin progress after its exporter had been shut down, and not making its final
collection when
Shutdown()was called before its background task hadstarted running on platforms where threading is not available.
OTEL_EXPORTER_OTLP_HEADERS(and theHeadersoption) being decodedbefore it was split into headers, so that a percent-encoded
,in a valuestarted a new header and encoded leading or trailing whitespace was removed.
oversized lengths, fields with an unexpected wire type, repeated fields and
unpadded Base64
grpc-status-details-bintrailers, and it is now ignored whenthe status code in the details contradicts the
grpc-statusof the response.reuse after buffer allocation failures.
ending in half of a surrogate pair. The truncated value now ends before the
pair instead.
OutOfMemoryExceptionthrown while converting an attribute value to astring is no longer swallowed and the attribute dropped; it now propagates.
its pump thread was exiting could throw
ArgumentNullExceptionon .NETFramework.
OTEL_RESOURCE_ATTRIBUTESvalue in theself-diagnostics environment snapshot when it contained empty entries.
v1.20.1Release details: 1.20.1
HttpClientinstances created directly by the OTLPexporter no longer follow HTTP redirects. A
3xxresponse is now treated asa failed export. See the OTLP exporter README to prevent an
HttpClientcreated by
IHttpClientFactoryfrom following redirects.per destination, derived from the exporter's
Protocol,EndpointandHeaders. This prevents telemetry stored by one exporter being resent byanother exporter to its own endpoint with its own headers. Telemetry stored on
disk by earlier versions is not resent.
histogram buckets by using a pre-computed lookup table.
OTEL_EXPORTER_OTLP_ENDPOINT(and signal-specific) andOTEL_EXPORTER_ZIPKIN_ENDPOINTvalues are no longer written to theexporter's diagnostic log.
accessible to the current user only.
removed or renamed. This matters when the retry directory is shared with
other files.
symbolic links are no longer read, and subdirectories are no longer
followed when calculating the size of the directory.
non-Gregorian calendar, and fixed expired leases being located and released
incorrectly.
OTEL_DIAGNOSTICS.jsonor
SelfDiagnosticsOptions, are now always created as new files.SelfDiagnosticsOptionssinks are nowtruncated to 16,384 characters. Only the first 4 KiB of the body of an
unsuccessful OTLP export response is now read and written to the exporter's
diagnostic log.
be accessed by their owner (
0700/0600) instead of inheriting the processumask.
encoding, which reduces the size of the exported payload.
first measurement with no tags, or the first overflow measurement, at the
same time.
single write. For each client that did not read the response, the server held
a full copy of it until the request completed or timed out (for HttpListener,
only on Linux and macOS). Responses are now written in bounded slices.
and prefixed JWTs.
TracerProvider.GetTracercaching a new tracer on every call thatpasses equal array-valued scope tags.
OTLP log exporter is registered using
OpenTelemetryLoggerOptions.AddOtlpExporter.file is truncated or its volume runs out of space.
Logger.EmitLogignoringinstrumentation suppression, which could cause recursive exports or deadlocks.
holding a thread pool thread on Linux and macOS for as long as the client
kept sending the body slowly after the response was sent. The connection is
now closed after responding to a request with a body.
large value, and idle metric points with a
NaNvalue not being reclaimed.LogRecords being returned to the shared pool while still queued forexport when an exporter stops enumerating a single-item or array
Batch<LogRecord>early.SuppressInstrumentationScope.Enter()reference count never beingreleased when the
Activityit was entered for is not recorded. This causedall later telemetry in that execution context to be suppressed.
log not being bounded by the export timeout, and the body never being logged
on .NET Framework.
ToString()(for exampleenums,
UriorStringValues) being dropped when the export buffer wasresized while the attribute was being written. For metric data points, the
attribute was also left out of every later export.
diagnostic events and exceptions when supplied instead of a file path.
longorGuid, share the same built-in hash code.later OTLP exports, and
target_infoand resource constant labels from laterPrometheus scrape responses, while the
MeterProvideris being built.ObservableCounterandObservableUpDownCounteroverflow pointsreporting only the last observation instead of the sum of all observations
for each collection.
values when buffering or updating
LogRecord.State.v1.20.0Release details: 1.20.0
byte[]attributes longer than the configured attribute valuelength limit (for example
OTEL_ATTRIBUTE_VALUE_LENGTH_LIMIT) are now truncatedto that many bytes instead of being exported in full.
OTEL_EVENT_ATTRIBUTE_COUNT_LIMITandOTEL_LINK_ATTRIBUTE_COUNT_LIMITnow fall back to
OTEL_ATTRIBUTE_COUNT_LIMIT(then the default of 128) whennot set, instead of falling back to
OTEL_SPAN_ATTRIBUTE_COUNT_LIMIT.ActivitySource.Tagsare now limited by
OTEL_ATTRIBUTE_COUNT_LIMITinstead ofOTEL_SPAN_ATTRIBUTE_COUNT_LIMIT. Only applications that setOTEL_SPAN_ATTRIBUTE_COUNT_LIMITto a different value fromOTEL_ATTRIBUTE_COUNT_LIMITare affected.
LoggerProvider's protectedTryCreateLogger(string? name, out Logger? logger)extensibility method hasbeen replaced by
TryCreateLogger(LoggerOptions options, out Logger? logger).OpenTelemetryLoggerOptions.VersionandOpenTelemetryLoggerOptions.SchemaUrloptions to set an instrumentationlibrary version and schema URL applied to logs emitted via the
Microsoft.Extensions.LoggingILoggerintegration.Logger.SchemaUrland aLoggerProvider.GetLoggeroverload acceptinga schema URL parameter using the new
LoggerOptionstype.ConsoleLogRecordExporternow writes anInstrumentation scope (Logger)section(Name, Version, and Schema URL) for each exported
LogRecord.schema_urlonScopeLogs. Log recordsemitted from a
Loggerwith a schema URL set now populateScopeLogs.schema_urlin exported OTLP requests.
disk retry feature are explicitly marked as not supported on browser-based
platforms (e.g. Blazor).
(e.g. Blazor) and are now non-functional.
TracerProviderBuilder.ConfigureSamplerintended for library authorswho need to influence sampling without overriding a sampler the application
has configured.
SuppressInstrumentationScopereference counts leaking betweeninherited asynchronous execution contexts.
ResourceBuilder.CreateDefaultignoringOTEL_RESOURCE_ATTRIBUTESandOTEL_SERVICE_NAMEenvironment variables when the hostIConfigurationdoesnot contain those settings.
the overflow point when its tag set was published as the cardinality limit was
reached.
LogRecord.CategoryNameresetting the currentLogger'sVersiontonullwhen set to a new value.Loggerscopes keyed by instrumentation toavoid unbounded growth.
MeterProviderand itsIServiceProviderbeing kept alive after thehost is disposed when using
Microsoft.Extensions.Diagnosticsversions priorto .NET 9.0.
histogram with delta temporality that could cause an empty data point to be exported.
compacting metric storage during collection.
BaggagePropagator.Injecton .NET Framework usinglookup tables.
on .NET Framework when using HTTP/protobuf with gzip compression.
OtlpExportProtocol.HttpProtobufwith
IHttpClientFactoryintegration if the first export of logs happens whilethe
IServiceProvideris being disposed. The exporter now falls back to thedefault
HttpClientinstead of failing the export.v1.19.1Release details: 1.19.1
NotSupportedExceptionthrown when building aTracerProviderorMeterProviderwith a large number of wildcard source/meter patterns onnet8.0, and a relatedOutOfMemoryExceptionthat could occur when manysuch providers were built over the lifetime of a process.
v1.19.0Release details: 1.19.0
Resourceinstances.AlwaysRecordSampler.AddOpenTelemetryextension method forIHostApplicationBuilder. Itregisters the OpenTelemetry SDK services and additionally seeds
service.namefrom
IHostEnvironment.ApplicationNameanddeployment.environment.namefromIHostEnvironment.EnvironmentNameas low-priority resource defaults. It alsoregisters the host's live configuration into DI so that extensions receiving
only
IServiceCollectioncan contribute configuration sources during setup.shapes (
IEnumerable<KeyValuePair<string, string?>>andIDictionary). Theseattributes will be serialized as JSON objects or
kvlist, as appropriate.be dropped.
environments to avoid stalled export requests when async HTTP handlers are used.
OTEL_EXPORTER_OTLP_CERTIFICATE) forPEM-encoded certificates that only contain a public key.
CircularBufferBucketsso the first delta histogram insertion after areset does not result in an unnecessary scale reduction.
initialized provider state.
tracestateheader whose member value trimmed toan empty value that previously threw an
IndexOutOfRangeExceptioninternallyand could silently truncate the tracestate.
the configured request size.
at runtime.
paramsoverload.SpanAttributesfrom an array.Configuration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about these updates again.
This PR has been generated by Renovate Bot.
Commands to ignore dependencies
You can trigger dependency actions by commenting on this PR:
@particularbot ignore this major version@particularbot ignore this minor version@particularbot ignore this dependency