Update opentelemetry-dotnet monorepo to 1.17.0#67
Open
renovate[bot] wants to merge 1 commit into
Open
Conversation
renovate
Bot
force-pushed
the
renovate/opentelemetry-dotnet-monorepo
branch
from
July 16, 2026 17:42
ed5e5ad to
b41bad1
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.15.3→1.17.01.15.3→1.17.0Release Notes
open-telemetry/opentelemetry-dotnet (OpenTelemetry.Exporter.OpenTelemetryProtocol)
v1.17.0Release details: 1.17.0
when using the Console and OTLP exporters.
ExcludedTagKeysproperty toMetricStreamConfigurationto supportexcluding specific tag keys from metric streams.
tracestatekey validation to comply with the W3C Trace ContextLevel 2 grammar.
instead of using a vendored implementation.
repeatedly created and disposed.
TraceContextPropagatorto normalize emptytracestateheader valuesto
nullwhen extracting trace context.OtlpLogExportersoOtlpExporterOptions.ExportProcessorTypeandOtlpExporterOptions.BatchExportProcessorOptionsare respected whenLogRecordExportProcessorOptionsare not configured.when persistent storage retry is enabled and an export exceeds the configured
timeout.
and metrics.
v1.16.0Release details: 1.16.0
10 million values.
BaggagePropagatorto correctly follow Key and Value Encoding rules.TraceContextPropagatorto deduplicate duplicatetracestatekeys.ObservedTimestampwill now be exported for logs in the console exporter.NullReferenceExceptionwhen exporting OTLP logs if the scope key isnull.
storage retry.
OtlpLogExporterintegration withIHttpClientFactory.IHttpClientFactorywhen mTLS isenabled.
Retry-Afterresponse headers that specify a date instead of a delay.observed_time_unix_nanowill no longer always be identical totime_unix_nanowhen using the logs bridge API.
Nameagainst the instrument namesyntax.
OTEL_BSP_*andOTEL_BLRP_*environment variables.collection cycle.
ExemplarReservoirimplementations.LoggerProviderto fail toresolve when one of its dependencies depends on
ILoggerorILoggerFactory.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 was generated by Mend Renovate. View the repository job log.