Skip to content

Update opentelemetry-dotnet monorepo to 1.19.1 - #67

Open
renovate[bot] wants to merge 1 commit into
mainfrom
renovate/opentelemetry-dotnet-monorepo
Open

renovate[bot] wants to merge 1 commit into
mainfrom
renovate/opentelemetry-dotnet-monorepo

Conversation

@renovate

@renovate renovate Bot commented Jun 12, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Change Age Confidence
OpenTelemetry.Exporter.OpenTelemetryProtocol (source) 1.15.31.19.1 age confidence
OpenTelemetry.Extensions.Hosting (source) 1.15.31.19.1 age confidence

Release Notes

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

v1.19.1

Release details: 1.19.1

  • Fixed NotSupportedException thrown when building a TracerProvider or
    MeterProvider with a large number of wildcard source/meter patterns on
    net8.0, and a related OutOfMemoryException that could occur when many
    such providers were built over the lifetime of a process.

v1.19.0

Release details: 1.19.0

  • Added Schema URL to internally created Resource instances.
  • Added AlwaysRecordSampler.
  • Added an AddOpenTelemetry extension method for IHostApplicationBuilder. It
    registers the OpenTelemetry SDK services and additionally seeds service.name
    from IHostEnvironment.ApplicationName and deployment.environment.name from
    IHostEnvironment.EnvironmentName as low-priority resource defaults. It also
    registers the host's live configuration into DI so that extensions receiving
    only IServiceCollection can contribute configuration sources during setup.
  • Extended key/value list attribute handling to cover additional dictionary
    shapes (IEnumerable<KeyValuePair<string, string?>> and IDictionary). These
    attributes will be serialized as JSON objects or kvlist, as appropriate.
  • If an exception is thrown when serializing an attribute, the attribute will now
    be dropped.
  • Disable HttpClientFactory integration on browser WebAssembly (e.g. Blazor)
    environments to avoid stalled export requests when async HTTP handlers are used.
  • Fixed CA certificate loading (e.g. using OTEL_EXPORTER_OTLP_CERTIFICATE) for
    PEM-encoded certificates that only contain a public key.
  • Fixed CircularBufferBuckets so the first delta histogram insertion after a
    reset does not result in an unnecessary scale reduction.
  • Fixed lazy logger provider builds after a failure from reusing partially
    initialized provider state.
  • Fixed parsing of an inbound tracestate header whose member value trimmed to
    an empty value that previously threw an IndexOutOfRangeException internally
    and could silently truncate the tracestate.
  • Prevented oversized metric metadata from being cached when it cannot fit within
    the configured request size.
  • Reduced allocations when formatting self-diagnostics events with up to three parameters.
  • Improved wildcard source/meter name matching to avoid excessive matching time
    at runtime.
  • Reduced allocations when creating log record attributes from an array.
  • Reduced allocations when setting baggage through the params overload.
  • Reduced allocations when constructing SpanAttributes from an array.

v1.18.0

Release details: 1.18.0

  • Breaking change: The maximum size of a single OTLP export request is now
    64 MiB by default instead of 128 MiB to conform with the OpenTelemetry specification.
    Raise the value of the new OtlpExporterOptions.MaxRequestSizeBytes property
    to increase the capacity.
  • Added OtlpExporterOptions.MaxRequestSizeBytes to configure the maximum OTLP
    request size limit, as required by the OpenTelemetry specification. The default
    is the recommended 64 MiB. A batch whose serialized payload exceeds the limit
    is not sent and is dropped in its entirety. The maximum supported value is
    256 MiB.
  • Added OtlpExporterOptions.MaxResponseSizeBytes to configure the maximum size
    of a response the exporter will accept, as required by the OpenTelemetry
    specification. The default is the recommended 4 MiB. A response exceeding the
    limit is discarded and treated as a non-retryable failure.
  • Added the otel.sdk.processor.log.processed and otel.sdk.processor.span.processed
    SDK self-observability metrics.
  • Added support for serializing attribute values that are key/value lists in
    the OTLP, console and Zipkin exporters.
  • The OTLP exporter will now export the logger version, if it was specified.
  • Add new ITelemetryHostInitializer interface for applications that do not
    support hosted services, such as Blazor, to use to manually initialize the
    OpenTelemetry SDK as part of application startup.
  • BatchActivityExportProcessor and SimpleActivityExportProcessor no longer
    forward spans to the exporter once Shutdown has been called, and
    BatchActivityExportProcessor.Shutdown now waits for in-flight OnEnd calls
    to finish enqueueing before flushing.
  • Fixed self-diagnostics log lines being silently dropped when an event message
    was too long to fit in the internal buffer. Such content is now truncated.
  • Fixed activity creation throwing when multiple tracer providers returned a
    sampler attribute with the same key.
  • Fixed logger, meter and tracer providers leaking background threads if an
    exception is thrown by their constructor after resource creation.
  • Avoid formatting exceptions and creating exception attributes when
    RecordException is called on a span that is not recorded.
  • Fixed UseOtlpExporter to respect options configured with
    services.Configure<OtlpExporterOptions>(...).
  • Clamped the server-supplied OTLP/gRPC retry delay (RetryInfo.retry_delay) to
    a minimum value of 100 milliseconds.
  • Fixed serialization failures leaving failed trace, metric, and log batches in
    the serializer's per-thread state.
  • Fixed the persistent-storage retry thread terminating permanently on an
    unexpected exception.
  • Fixed the OTLP exporter from retrying certain non-transient HTTP failures.
  • Improved OTLP log attribute serialization performance by avoiding unnecessary
    boxing.
  • Improved OTLP histogram serialization performance by avoiding a redundant
    scan of explicit bucket bounds.
  • Fixed persistent storage allowing a blob write to exceed the configured
    maximum storage size.
  • Improved OTLP/gRPC response status handling performance by avoiding unnecessary
    header enumeration on .NET 8+.
  • Fixed the Zipkin exporter to read responses with HttpCompletionOption.ResponseHeadersRead
    for the .NET Framework and .NET Standard targets.
  • Fixed inefficient parsing of the Jaeger uber-trace-id header when targeting
    net462 or netstandard2.0.

v1.17.0

Release details: 1.17.0

  • Added support for a Schema URL on Resource instances.
  • The Resource Schema URL is now printed alongside the resource attributes
    when using the Console and OTLP exporters.
  • Added ExcludedTagKeys property to MetricStreamConfiguration to support
    excluding specific tag keys from metric streams.
  • Updated tracestate key validation to comply with the W3C Trace Context
    Level 2 grammar.
  • The SDK now depends on Microsoft.Extensions.Configuration.EnvironmentVariables
    instead of using a vendored implementation.
  • All libraries are now marked as trim and AOT compatible.
  • Fixed a metric storage leak that occurred when meters and instruments were
    repeatedly created and disposed.
  • Fixed TraceContextPropagator to normalize empty tracestate header values
    to null when extracting trace context.
  • Fixed OtlpLogExporter so OtlpExporterOptions.ExportProcessorType and
    OtlpExporterOptions.BatchExportProcessorOptions are respected when
    LogRecordExportProcessorOptions are not configured.
  • Fixed the OTLP exporter dropping retryable data instead of saving it to disk
    when persistent storage retry is enabled and an export exceeds the configured
    timeout.
  • Fixed the OTLP/HTTP exporter silently dropping data when an export timed out.
  • Fixed the OTLP/gRPC exporter logging incorrectly when an export timed out.
  • Performance and memory improvements for the OTLP exporter when exporting logs
    and metrics.

v1.16.0

Release details: 1.16.0

  • Breaking Change Explicit histogram boundaries no longer allow more than
    10 million values.
  • Fix BaggagePropagator to correctly follow Key and Value Encoding rules.
  • Add support for the W3C randomness flag.
  • Fixed TraceContextPropagator to deduplicate duplicate tracestate keys.
  • ObservedTimestamp will now be exported for logs in the console exporter.
  • Fixed NullReferenceException when exporting OTLP logs if the scope key is
    null.
  • Added opt-in support for gzip compression to the OTLP exporter.
  • Fixed OTLP disk retry data being stored incorrectly when using persistent
    storage retry.
  • Fixed OtlpLogExporter integration with IHttpClientFactory.
  • Do not enable the OTLP integration with IHttpClientFactory when mTLS is
    enabled.
  • Handle Retry-After response headers that specify a date instead of a delay.
  • observed_time_unix_nano will no longer always be identical to time_unix_nano
    when using the logs bridge API.
  • Stop validating View-provided metric stream Name against the instrument name
    syntax.
  • Fix incorrect validation of OTEL_BSP_* and OTEL_BLRP_* environment variables.
  • Fix observable instrument callbacks running once per reader instead of once per
    collection cycle.
  • Added exception safety for user-supplied ExemplarReservoir implementations.
  • Fixed a circular reference which could cause a LoggerProvider to fail to
    resolve when one of its dependencies depends on ILogger or ILoggerFactory.

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.

@renovate
renovate Bot force-pushed the renovate/opentelemetry-dotnet-monorepo branch from ed5e5ad to b41bad1 Compare July 16, 2026 17:42
@renovate renovate Bot changed the title Update opentelemetry-dotnet monorepo to 1.16.0 Update opentelemetry-dotnet monorepo to 1.17.0 Jul 16, 2026
@renovate
renovate Bot force-pushed the renovate/opentelemetry-dotnet-monorepo branch from b41bad1 to 11367bd Compare August 21, 2026 13:52
@renovate renovate Bot changed the title Update opentelemetry-dotnet monorepo to 1.17.0 Update opentelemetry-dotnet monorepo to 1.18.0 Aug 21, 2026
@renovate
renovate Bot force-pushed the renovate/opentelemetry-dotnet-monorepo branch from 11367bd to e24ab81 Compare September 15, 2026 09:11
@renovate
renovate Bot force-pushed the renovate/opentelemetry-dotnet-monorepo branch from e24ab81 to cc80d0a Compare September 18, 2026 15:50
@renovate renovate Bot changed the title Update opentelemetry-dotnet monorepo to 1.18.0 Update opentelemetry-dotnet monorepo to 1.19.0 Sep 18, 2026
@renovate
renovate Bot force-pushed the renovate/opentelemetry-dotnet-monorepo branch from cc80d0a to 8274b41 Compare September 21, 2026 10:31
@renovate renovate Bot changed the title Update opentelemetry-dotnet monorepo to 1.19.0 Update opentelemetry-dotnet monorepo to 1.19.1 Sep 21, 2026

This branch had an error being deployed

1 failed deployment
dev 8274b419 Deployed Sep 21, 2026 by renovate[bot] via deploy_to_dev / Deploy API Server #225
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants