[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
OpenTelemetry.Exporter.OpenTelemetryProtocol (source)	1.20.0 → 1.20.1
OpenTelemetry.Extensions.Hosting (source)	1.20.0 → 1.20.1

---

Release Notes

open-telemetry/opentelemetry-dotnet (OpenTelemetry.Exporter.OpenTelemetryProtocol)

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.

---

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.