[renovate]

This PR contains the following updates:

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

---

Release Notes

Microsoft/ApplicationInsights-dotnet (Microsoft.ApplicationInsights)

v3.2.0

• Update OpenTelemetry core packages to 1.19.1, instrumentation packages to 1.19.0, and Azure Monitor OpenTelemetry Exporter to 1.10.0.
• Breaking change: Reduce default HTTP client metric volume in ASP.NET Core and Worker Service on .NET 8+ while retaining request latency, count, and failure dimensions through http.client.request.duration. Other System.Net.Http metrics are now opt-in through OpenTelemetry AddView; 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.
• Fix #​3197: NullReferenceException when using TelemetryClient APIs when no connection string is provided.
• Fix #​3211: TelemetryClient.TrackDependency(DependencyTelemetry) and TelemetryClient.TrackRequest(RequestTelemetry) now default an unset Timestamp to DateTimeOffset.UtcNow (restoring 2.x behavior) instead of emitting 0001-01-01T00:00:00Z, which ingestion rejects.
• Fix #​3223: The WEB package's activity processors now write the tag keys the Azure Monitor exporter maps (enduser.pseudo.id, microsoft.session.id, microsoft.synthetic_source, microsoft.user.account_id), so user_Id, session_Id, operation_SyntheticSource and user_AccountId are populated again instead of the values landing in customDimensions as ai.user.id, session.id, ai.operation.syntheticSource and enduser.account. user_AccountId is also no longer skipped when the authenticated user cookie is present, and the unmapped session.isFirst custom dimension is no longer emitted.
• Fix StartOperation/StopOperation losing or misreporting telemetry fields. Stopping an operation now exports the fields set on its telemetry item using the same keys as TrackDependency/TrackRequest: dependency Type, Data, Target and ResultCode (previously wrong or empty for HTTP, SQL, Queue Message and custom types), request Url, Source and ResponseCode, Success, and custom Properties. The unmapped OperationName and messaging.destination tags no longer appear as custom dimensions.

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

• #​6303 XmlParser - Keep whitespace from character references in InnerText. (@​APX403)
• #​6292 CachedLayoutRendererWrapper - Support CachedUntil=HourChange and CachedUntil=DayChange. (@​dualfroz)
• #​6298 ObjectGraphScanner - Skip scanning Layout.Empty. (@​snakefoot)
• #​6297 Remove Microsoft.SourceLink.GitHub as part of NET8 SDK. (@​snakefoot)
• #​6296 FileTarget - Refactor RollingArchiveFileHandler to reduce complexity. (@​snakefoot)
• #​6295 NullTarget - LastMessage property lock SyncRoot. (@​snakefoot)
• #​6289 MemoryTarget - Introduced DumpInitialError with focused diagnostic context. (@​snakefoot)
• #​6287 MemoryTarget - Introduced DumpOnError with full diagnostic context. (@​snakefoot)
• #​6283 MemoryTarget - RingBuffer supporting non-blocking enumeration. (@​snakefoot)

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

v1.20.1

Release details: 1.20.1

• Breaking change HttpClient instances created directly by the OTLP
  exporter no longer follow HTTP redirects. A 3xx response is now treated as
  a failed export. See the OTLP exporter README to prevent an HttpClient
  created by IHttpClientFactory from following redirects.
• Breaking change The experimental OTLP disk retry storage is now separated
  per destination, derived from the exporter's Protocol, Endpoint and
  Headers. This prevents telemetry stored by one exporter being resent by
  another exporter to its own endpoint with its own headers. Telemetry stored on
  disk by earlier versions is not resent.
• Improved how values near a bucket boundary are assigned to exponential
  histogram buckets by using a pre-computed lookup table.
• Invalid OTEL_EXPORTER_OTLP_ENDPOINT (and signal-specific) and
  OTEL_EXPORTER_ZIPKIN_ENDPOINT values are no longer written to the
  exporter's diagnostic log.
• Hardened the experimental OTLP disk retry feature:
  • On non-Windows platforms the retry directory and blob files are now
    accessible to the current user only.
  • Only files named the way the exporter names its blobs are now retried,
    removed or renamed. This matters when the retry directory is shared with
    other files.
  • Blobs that are empty, larger than the maximum storage size, or (on .NET)
    symbolic links are no longer read, and subdirectories are no longer
    followed when calculating the size of the directory.
  • Fixed files never being cleaned up when the current culture uses a
    non-Gregorian calendar, and fixed expired leases being located and released
    incorrectly.
• Self-diagnostics log files, whether configured through OTEL_DIAGNOSTICS.json
  or SelfDiagnosticsOptions, are now always created as new files.
• Self-diagnostics messages written to SelfDiagnosticsOptions sinks are now
  truncated 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.
• On Linux and macOS, the self-diagnostics log directory and files can now only
  be accessed by their owner (0700/0600) instead of inheriting the process
  umask.
• OTLP exponential histogram bucket counts are now serialized using packed
  encoding, which reduces the size of the exported payload.
• Fixed a possible race condition on ARM64 when multiple threads record the
  first measurement with no tags, or the first overflow measurement, at the
  same time.
• Fixed the Prometheus exporters handing scrape responses to the server in a
  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.
• Fixed self-diagnostics preamble redaction of quoted or encoded PEM material
  and prefixed JWTs.
• Fixed TracerProvider.GetTracer caching a new tracer on every call that
  passes equal array-valued scope tags.
• Fixed informational HTTP client logs not being suppressed by default when the
  OTLP log exporter is registered using OpenTelemetryLoggerOptions.AddOtlpExporter.
• Fixed legacy self-diagnostics logging terminating the process when the log
  file is truncated or its volume runs out of space.
• Experimental (pre-release builds only): Fixed Logger.EmitLog ignoring
  instrumentation suppression, which could cause recursive exports or deadlocks.
• Fixed Prometheus HttpListener scrape requests that announce a request body
  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.
• Fixed delta double counters losing later measurements after a non-finite or
  large value, and idle metric points with a NaN value not being reclaimed.
• Fixed LogRecords being returned to the shared pool while still queued for
  export when an exporter stops enumerating a single-item or array
  Batch<LogRecord> early.
• Fixed a SuppressInstrumentationScope.Enter() reference count never being
  released when the Activity it was entered for is not recorded. This caused
  all later telemetry in that execution context to be suppressed.
• Fixed reading the body of a failed OTLP export response for the diagnostic
  log not being bounded by the export timeout, and the body never being logged
  on .NET Framework.
• Fixed OTLP attributes whose value is converted with ToString() (for example
  enums, Uri or StringValues) being dropped when the export buffer was
  resized while the attribute was being written. For metric data points, the
  attribute was also left out of every later export.
• Fixed pooled log records retaining completed log data until reused.
• Fixed inline OTLP certificate or private key material being included in
  diagnostic events and exceptions when supplied instead of a file path.
• Fixed slow metric recording when distinct wide tag values, such as long or
  Guid, share the same built-in hash code.
• Fixed early metric collections permanently omitting resource attributes from
  later OTLP exports, and target_info and resource constant labels from later
  Prometheus scrape responses, while the MeterProvider is being built.
• Fixed ObservableCounter and ObservableUpDownCounter overflow points
  reporting only the last observation instead of the sum of all observations
  for each collection.
• Fixed replaced log attributes being exported together with their original
  values when buffering or updating LogRecord.State.

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

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud