[dependabot]

Updated OpenTelemetry from 1.20.1 to 1.21.0.

Release notes

Sourced from OpenTelemetry's releases.

1.21.0

For highlights and announcements pertaining to this release see: Release Notes > 1.21.0.

The following changes are from the previous release 1.21.0-rc.2.

• NuGet: OpenTelemetry v1.21.0

  • OpenTelemetryLoggerOptions is now bound from the Logging:OpenTelemetry
    configuration section using the configuration binding source generator instead
    of reflection, making it fully trim and Native AOT compatible. An empty value
    for a boolean option is now ignored on all target frameworks rather than
    throwing on some, depending on the version of
    Microsoft.Extensions.Configuration.Binder in use.
    (#​8100)

  • Fixed the self-diagnostics environment snapshot leaving a dangling comma in a
    redacted OTEL_RESOURCE_ATTRIBUTES value when it contained empty entries.
    (#​8104)

  See CHANGELOG for details.

• NuGet: OpenTelemetry.Api v1.21.0

  • Update System.Diagnostics.DiagnosticSource dependency to 11.0.0
    for all target frameworks.
    (#​8066)

  See CHANGELOG for details.

• NuGet: OpenTelemetry.Api.ProviderBuilderExtensions v1.21.0

  No notable changes.

  See CHANGELOG for details.

• NuGet: OpenTelemetry.Exporter.Console v1.21.0

  No notable changes.

  See CHANGELOG for details.

• NuGet: OpenTelemetry.Exporter.InMemory v1.21.0

  No notable changes.

  See CHANGELOG for details.

• NuGet: OpenTelemetry.Exporter.OpenTelemetryProtocol v1.21.0

  • Hardened the experimental disk retry feature.
    • Breaking: When running on .NET on non-Windows platforms, creating the
      ... (truncated)

1.21.0-rc.2

The following changes are from the previous release 1.21.0-rc.1.

• NuGet: OpenTelemetry v1.21.0-rc.2

  • Fixed an exception when downscaling empty exponential histogram buckets after
    a reset.
    (#​8064)

  • Fixed tracing callbacks continuing after provider shutdown or disposal on older
    target frameworks.
    (#​8065)

  • Fixed initialization failures when environment variable access is denied.
    Configuration reloads retain the last successful values when access is denied.
    (#​8070)

  • Fixed a source, meter or legacy activity name with a trailing line feed
    matching a wildcard pattern which does not end in a wildcard.
    (#​8074)

  • Fixed OTEL_RESOURCE_ATTRIBUTES values being decoded as form data, which
    changed a + to a space. Values are now only percent-decoded, as defined by
    the Resource SDK specification.
    (#​8074)

  • Updated the schema URL of resources created by the SDK to use OpenTelemetry
    Semantic Conventions version 1.45.0.
    (#​8079)

  • Added support for batching the metric points exported by
    PeriodicExportingMetricReader. When a maximum export batch size is set,
    using the new constructor overload or
    PeriodicExportingMetricReaderOptions.MaxExportBatchSize, the metric
    points of each collection are split into batches of at most that many
    metric points, even if that splits up the metric points of a single
    metric. The batches are exported serially with the export timeout
    applying to each export. It can also be configured with the
    OTEL_METRIC_EXPORT_MAX_BATCH_SIZE environment variable.
    (#​8053)

  • Fixed PeriodicExportingMetricReader exporting a collection which was still
    in progress when Shutdown() timed out to its exporter after the exporter
    had been shut down.
    (#​8053)

  • Fixed PeriodicExportingMetricReader not making its final collection when
    Shutdown() was called before its background task had started running on
    platforms where threading is not available, such as browsers.
    (#​8053)

... (truncated)

1.21.0-rc.1

The following changes are from the previous release 1.20.1.

• NuGet: OpenTelemetry v1.21.0-rc.1

  • Fixed a race in the self-diagnostics sink dispatcher where disposing it
    while its pump thread was exiting could throw ArgumentNullException on
    .NET Framework.
    (#​7983)

  • SelfDiagnosticsOptions is now automatically bound from the
    OpenTelemetry:SelfDiagnostics configuration section, when present.
    (#​8008)

  • Fixed a race where collecting a metric with delta temporality concurrently
    with the creation of a new MetricPoint could reclaim the MetricPoint
    while it was being created, losing the measurement.
    (#​8019)

  • Fixed a race where collecting a metric with delta temporality could export
    the same series twice in a single collection.
    (#​8019)

  • Fixed wildcard matching timeouts that could prevent configured source, meter,
    legacy activity, or metric view patterns from matching.
    (#​8014)

  • The timeout passed to MetricReader.Collect() (for example by
    MeterProvider.ForceFlush()), the ExportTimeoutMilliseconds of
    PeriodicExportingMetricReader and the ExporterTimeoutMilliseconds of
    BatchExportProcessor<T> are now made available to the exporter instead of
    being ignored once the export has started, so that the OTLP exporter can
    cancel an export which runs past the timeout. The ExportTimeoutMilliseconds
    of PeriodicExportingMetricReader now also limits exports which are not
    started by the reader itself, such as those of MeterProvider.ForceFlush().
    (#​7996)

  • Fixed a race where collecting a cumulative metric concurrently with the
    creation of a new MetricPoint could export a MetricPoint that was not yet
    fully initialized, could case a NullReferenceException when enumerating Tags.
    (#​8018)

  • Breaking Change Dropped support for net8.0 and net9.0.
    (#​6899)

  • Add support for .NET 11.0.
    (#​6899)

  • Added support for enabling ActivitySources from configuration using the
    Microsoft.Extensions.Diagnostics tracing APIs introduced in .NET 11 (for
    example, services.AddTracing(b => b.AddConfiguration(section))).
    ... (truncated)

1.21.0-beta.1

The following changes are from the previous release 1.20.1-beta.1.

• NuGet: OpenTelemetry.Exporter.Prometheus.AspNetCore v1.21.0-beta.1

  • Fixed OpenMetrics scrape responses containing a # UNIT line whose unit is
    not an underscore-separated suffix of the metric family name (for example
    auth.failedlogins with the unit logins), which caused scrapers such as
    Prometheus to reject the whole response. The # UNIT line is now omitted
    for such metrics; exported metric names are unchanged.
    (#​7993)

  • Fixed scrapes that negotiate different response formats within the
    ScrapeResponseCacheDurationMilliseconds window each triggering their own
    metrics collection. A collection now also writes the response for other
    formats whose scrapes arrived alongside a previous collection, so scrapes
    that keep arriving together are served from the cache. Fresh cached responses
    remain available while another format is serialized, even if that
    serialization fails.
    (#​7994)

  • Fixed array- and map-valued attributes being serialized as the .NET type
    name (e.g. System.Byte[], System.Int32[]) instead of being JSON-encoded
    as per the specification. byte[]-valued attributes are now
    Base64-encoded, and other array- and map-valued attributes are now
    JSON-encoded.
    (#​7694)

  • Fixed arrays of string-valued key/value pairs being
    serialized as JSON arrays of strings instead of JSON objects.
    (#​7694)

  • Fixed scrape clients which stop reading their response delaying other
    scrapes until ScrapeResponseTimeoutMilliseconds elapses.
    (#​8041)

  • Breaking Change Dropped support for net8.0 and net9.0.
    (#​6899)

  • Add support for .NET 11.0.
    (#​6899)

  • Fixed a scrape response containing the same series (metric name and labels)
    more than once, which causes Prometheus to reject the whole response, such as
    when metric or tag names are the same once escaped, tag names become the same
    when UTF-8 encoded, or the scope information is disabled. Duplicate series are
    now dropped, and a warning event is written.
    A metric which has the name of a sample that is generated for another one
    (for example _sum of a histogram) is now dropped, and a warning event is
    written.
    (#​8076)
    ... (truncated)

Commits viewable in compare view.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Superseded by #139.