Skip to content

chore(deps): update logging and telemetry backends - #1724

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/logging-and-telemetry-backends
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/logging-and-telemetry-backends

Conversation

@renovate

@renovate renovate Bot commented Oct 13, 2026 •

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
Microsoft.ApplicationInsights (source) 3.1.2 → 3.2.0 age confidence
Mindscape.Raygun4Net.NetCore (source) 11.2.6 → 11.2.7 age confidence
NLog (source) 6.2.1 → 6.2.2 age confidence
OpenTelemetry.Api (source) 1.19.1 → 1.20.0 age confidence

Release Notes

Microsoft/ApplicationInsights-dotnet (Microsoft.ApplicationInsights)

v3.2.0

MindscapeHQ/raygun4net (Mindscape.Raygun4Net.NetCore)

v11.2.7

  • Feature: Opt-in request IP address masking (IsRequestIpAddressMasked)
    • Masks IPv4 and IPv4-mapped IPv6 addresses to the embedded IPv4 /24, and native IPv6 addresses to /48 (ports retained)
    • Excludes known client-IP forwarding headers and server variables from request metadata while masking is enabled
    • Supported on AspNetCore, MVC/Net4, and WebApi providers; disabled by default
    • Classic Net4/WebApi IP extraction now accepts IPv6 (including bracketed forms) from X-Forwarded-For / REMOTE_ADDR
    • XFF/REMOTE_ADDR acceptance requires canonical four-octet IPv4 values and strict port validation; masking still best-effort redacts the host when a port suffix is malformed
    • AspNetCore: unmasked IPv6+port keeps the historical addr:port shape; masked IPv6+port uses unambiguous [addr]:port
    • See: #​583
  • Fix: #​584 - SendInBackground could block indefinitely while collecting disk space on Windows when a mapped network drive was unavailable
    • Mindscape.Raygun4Net.NetCore.Common: disk-space collection checks the drive type before readiness, so drives that are not reported (e.g. network drives, non-root mounts) are no longer probed
    • Mindscape.Raygun4Net.NetCore.Common: disk space is collected on a background thread with a 5 second limit. If it runs out, the report is sent (or stored offline) with an empty DiskSpaceFree and DiskSpaceFreeStatus set to "TimedOut", instead of stale values
    • Mindscape.Raygun4Net.NetCore.Common: if the disk check fails, the report has an empty DiskSpaceFree and DiskSpaceFreeStatus set to "Error"
    • Mindscape.Raygun4Net.NetCore.Common: reports that arrive while another report is collecting disk space wait for the fresh values instead of skipping them, for up to twice the disk limit. Machine details (OS, CPU, memory) are cached separately, and only the first report of the process waits for them
    • See: #​586
    • See: #​585
  • Feature: IsDiskSpaceFreeIgnored setting turns off disk space collection
    • Reports sent while it is on have an empty DiskSpaceFree and DiskSpaceFreeStatus set to "Ignored"
    • Those reports never wait for a disk check running for another client, so an unresponsive disk cannot delay them
    • Applies to the modern .NET packages only. The .NET Framework packages (Mindscape.Raygun4Net, .Mvc, .WebApi, .Azure.WebJob) still collect disk space without a time limit and have no opt-out
    • See: #​585
NLog/NLog (NLog)

v6.2.2

Improvements

open-telemetry/opentelemetry-dotnet (OpenTelemetry.Api)

v1.20.0

Release details: 1.20.0

  • Breaking change byte[] attributes longer than the configured attribute value
    length limit (for example OTEL_ATTRIBUTE_VALUE_LENGTH_LIMIT) are now truncated
    to that many bytes instead of being exported in full.
  • Breaking change OTEL_EVENT_ATTRIBUTE_COUNT_LIMIT and OTEL_LINK_ATTRIBUTE_COUNT_LIMIT
    now fall back to OTEL_ATTRIBUTE_COUNT_LIMIT (then the default of 128) when
    not set, instead of falling back to OTEL_SPAN_ATTRIBUTE_COUNT_LIMIT.
  • Breaking change Instrumentation scope attributes exported from ActivitySource.Tags
    are now limited by OTEL_ATTRIBUTE_COUNT_LIMIT instead of
    OTEL_SPAN_ATTRIBUTE_COUNT_LIMIT. Only applications that set
    OTEL_SPAN_ATTRIBUTE_COUNT_LIMIT to a different value from OTEL_ATTRIBUTE_COUNT_LIMIT
    are affected.
  • Breaking change (pre-release only versions): LoggerProvider's protected
    TryCreateLogger(string? name, out Logger? logger) extensibility method has
    been replaced by TryCreateLogger(LoggerOptions options, out Logger? logger).
  • Added OpenTelemetryLoggerOptions.Version and
    OpenTelemetryLoggerOptions.SchemaUrl options to set an instrumentation
    library version and schema URL applied to logs emitted via the
    Microsoft.Extensions.Logging ILogger integration.
  • Added Logger.SchemaUrl and a LoggerProvider.GetLogger overload accepting
    a schema URL parameter using the new LoggerOptions type.
  • ConsoleLogRecordExporter now writes an Instrumentation scope (Logger) section
    (Name, Version, and Schema URL) for each exported LogRecord.
  • The OTLP log exporter now exports schema_url on ScopeLogs. Log records
    emitted from a Logger with a schema URL set now populate ScopeLogs.schema_url
    in exported OTLP requests.
  • Custom TLS certificate options (custom CA trust and mTLS) and the experimental
    disk retry feature are explicitly marked as not supported on browser-based
    platforms (e.g. Blazor).
  • Suppressed informational HTTP client logs from OTLP exporters by default.
  • Added improved self-diagnostics logging to improve the support experience.
  • Self-diagnostic features are explicitly disabled on browser-based platforms
    (e.g. Blazor) and are now non-functional.
  • Added TracerProviderBuilder.ConfigureSampler intended for library authors
    who need to influence sampling without overriding a sampler the application
    has configured.
  • Fixed SuppressInstrumentationScope reference counts leaking between
    inherited asynchronous execution contexts.
  • Fixed ResourceBuilder.CreateDefault ignoring OTEL_RESOURCE_ATTRIBUTES and
    OTEL_SERVICE_NAME environment variables when the host IConfiguration does
    not contain those settings.
  • Fixed a race that could incorrectly route a concurrent metric measurement to
    the overflow point when its tag set was published as the cardinality limit was
    reached.
  • Fixed LogRecord.CategoryName resetting the current Logger's Version to
    null when set to a new value.
  • Bounded the internal cache of Logger scopes keyed by instrumentation to
    avoid unbounded growth.
  • Fixed the MeterProvider and its IServiceProvider being kept alive after the
    host is disposed when using Microsoft.Extensions.Diagnostics versions prior
    to .NET 9.0.
  • Fixed a race condition between recording a measurement and collecting a
    histogram with delta temporality that could cause an empty data point to be exported.
  • Improved metric collection performance after metric streams are removed by
    compacting metric storage during collection.
  • Optimize performance of BaggagePropagator.Inject on .NET Framework using
    lookup tables.
  • Avoid closure allocations when serializing cached metric metadata.
  • Avoid logging malformed HTTP request headers in the exporter's diagnostic log.
  • Avoid buffering the whole compressed request body in memory before sending it
    on .NET Framework when using HTTP/protobuf with gzip compression.
  • Fixed log records being dropped when using OtlpExportProtocol.HttpProtobuf
    with IHttpClientFactory integration if the first export of logs happens while
    the IServiceProvider is being disposed. The exporter now falls back to the
    default HttpClient instead of failing the export.
  • Dozens of other minor performance improvements.

Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@codecov

codecov Bot commented Oct 13, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 99.11%. Comparing base (39466de) to head (406f609).

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.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@renovate
renovate Bot force-pushed the renovate/logging-and-telemetry-backends branch from 406f609 to ee3ae3c Compare October 18, 2026 14:28
@renovate renovate Bot changed the title chore(deps): update dependency microsoft.applicationinsights to 3.2.0 chore(deps): update logging and telemetry backends Oct 18, 2026
@renovate
renovate Bot force-pushed the renovate/logging-and-telemetry-backends branch from ee3ae3c to dabd17c Compare October 18, 2026 18:31
@renovate
renovate Bot force-pushed the renovate/logging-and-telemetry-backends branch from dabd17c to 8ad1e28 Compare October 23, 2026 04:11
@sonarqubecloud

Copy link
Copy Markdown

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants