Repository navigation
chore(deps): update logging and telemetry backends - #1724
Open
renovate[bot] wants to merge 1 commit into
Open
renovate[bot] wants to merge 1 commit into
renovate[bot] wants to merge 1 commit into
Conversation
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1724 +/- ##
==========================================
+ Coverage 99.08% 99.11% +0.02%
==========================================
Files 134 134
Lines 7108 7108
Branches 1114 1114
==========================================
+ Hits 7043 7045 +2
+ Misses 65 63 -2 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
renovate
Bot
force-pushed
the
renovate/logging-and-telemetry-backends
branch
from
October 18, 2026 14:28
406f609 to
ee3ae3c
Compare
renovate
Bot
force-pushed
the
renovate/logging-and-telemetry-backends
branch
from
October 18, 2026 18:31
ee3ae3c to
dabd17c
Compare
renovate
Bot
force-pushed
the
renovate/logging-and-telemetry-backends
branch
from
October 23, 2026 04:11
dabd17c to
8ad1e28
Compare
|
This branch has not been deployed
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:
3.1.2→3.2.011.2.6→11.2.76.2.1→6.2.21.19.1→1.20.0Release Notes
Microsoft/ApplicationInsights-dotnet (Microsoft.ApplicationInsights)
v3.2.0http.client.request.duration. OtherSystem.Net.Httpmetrics are now opt-in through OpenTelemetryAddView; dashboards and alerts using them must explicitly enable collection. HTTP dependency tracing and server metrics are unchanged. No new public API is introduced. Addresses the HTTP metric-volume concern in #3192.NullReferenceExceptionwhen using TelemetryClient APIs when no connection string is provided.TelemetryClient.TrackDependency(DependencyTelemetry)andTelemetryClient.TrackRequest(RequestTelemetry)now default an unsetTimestamptoDateTimeOffset.UtcNow(restoring 2.x behavior) instead of emitting0001-01-01T00:00:00Z, which ingestion rejects.enduser.pseudo.id,microsoft.session.id,microsoft.synthetic_source,microsoft.user.account_id), souser_Id,session_Id,operation_SyntheticSourceanduser_AccountIdare populated again instead of the values landing incustomDimensionsasai.user.id,session.id,ai.operation.syntheticSourceandenduser.account.user_AccountIdis also no longer skipped when the authenticated user cookie is present, and the unmappedsession.isFirstcustom dimension is no longer emitted.StartOperation/StopOperationlosing or misreporting telemetry fields. Stopping an operation now exports the fields set on its telemetry item using the same keys asTrackDependency/TrackRequest: dependencyType,Data,TargetandResultCode(previously wrong or empty for HTTP, SQL,Queue Messageand custom types), requestUrl,SourceandResponseCode,Success, and customProperties. The unmappedOperationNameandmessaging.destinationtags no longer appear as custom dimensions.MindscapeHQ/raygun4net (Mindscape.Raygun4Net.NetCore)
v11.2.7IsRequestIpAddressMasked)/24, and native IPv6 addresses to/48(ports retained)addr:portshape; masked IPv6+port uses unambiguous[addr]:portSendInBackgroundcould block indefinitely while collecting disk space on Windows when a mapped network drive was unavailableDiskSpaceFreeandDiskSpaceFreeStatusset to"TimedOut", instead of stale valuesDiskSpaceFreeandDiskSpaceFreeStatusset to"Error"IsDiskSpaceFreeIgnoredsetting turns off disk space collectionDiskSpaceFreeandDiskSpaceFreeStatusset to"Ignored"Mindscape.Raygun4Net,.Mvc,.WebApi,.Azure.WebJob) still collect disk space without a time limit and have no opt-outNLog/NLog (NLog)
v6.2.2Improvements
open-telemetry/opentelemetry-dotnet (OpenTelemetry.Api)
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.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.