Skip to content

1.4.0-beta.3 / 1.0.0-rc9.9

Pre-release
Pre-release
Compare
Choose a tag to compare
@utpilla utpilla released this 07 Nov 20:12
· 1027 commits to main since this release
core-1.4.0-beta.3
273c205
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Learn about vigilant mode.

1.4.0-beta.3

OpenTelemetry

  • Fix instrument naming enforcement implementation to match the spec.
    (#3821)

  • Added support for loading environment variables from IConfiguration when
    using the MetricReaderOptions & BatchExportActivityProcessorOptions
    classes.
    (#3760,
    #3776)

  • Added dependency injection support in the ResourceBuilder class and added
    support for loading environment variables from IConfiguration for the
    AddEnvironmentVariableDetector extension
    (#3782,
    #3798)

  • Breaking: MetricPoint API to retrieve Histogram Min, Max changed. The existing
    pattern of checking if Min/Max is available with HasMinMax() and then
    retrieving the same using GetHistogramMin(), GetHistogramMax() is replaced
    with a single API TryGetHistogramMinMaxValues(out double min, out double max).
    (#3822)

OpenTelemetry.Api

  • Updated to System.Diagnostics.DiagnosticSource version 7.0.0-rc.2.22472.3.

OpenTelemetry.Exporter.Console

  • Bumped the minimum required version of System.Text.Json to 4.7.2 in response
    to CVE-2021-26701.
    (#3789)

LogRecordExporter to print full exception details instead of just Message, when
using ILogger to log exception.
(#3784)

Added support to print Histogram Min, Max in MetricExporter.

OpenTelemetry.Exporter.InMemory

OpenTelemetry.Exporter.Jaeger

  • Bumped the minimum required version of System.Text.Json to 4.7.2 in response
    to CVE-2021-26701.
    (#3789)

OpenTelemetry.Exporter.OpenTelemetryProtocol

  • Log Exporter modified to no longer prefix scope-depth when exporting ILogger
    scopes as attributes. Empty keys and {OriginalFormat} key will be ignored from
    scopes.
    (3843)

OpenTelemetry.Exporter.OpenTelemetryProtocol.Logs

OpenTelemetry.Exporter.Prometheus.AspNetCore

  • Support named options in UseOpenTelemetryPrometheusScrapingEndpoint &
    MapPrometheusScrapingEndpoint extensions
    (#3780)

OpenTelemetry.Exporter.Prometheus.HttpListener

OpenTelemetry.Exporter.Zipkin

  • Bumped the minimum required version of System.Text.Json to 4.7.2 in response
    to CVE-2021-26701.
    (#3789)

OpenTelemetry.Extensions.Propagators

1.0.0-rc9.9

OpenTelemetry.Exporter.ZPages

OpenTelemetry.Extensions.Hosting

OpenTelemetry.Instrumentation.AspNetCore

  • Breaking change The Enrich callback option has been removed.
    For better usability, it has been replaced by three separate options:
    EnrichWithHttpRequest, EnrichWithHttpResponse and EnrichWithException.
    Previously, the single Enrich callback required the consumer to detect
    which event triggered the callback to be invoked (e.g., request start,
    response end, or an exception) and then cast the object received to the
    appropriate type: HttpRequest, HttpResponse, or Exception. The separate
    callbacks make it clear what event triggers them and there is no longer the
    need to cast the argument to the expected type.
    (#3749)

  • Added back netstandard2.0 and netstandard2.1 targets.
    (#3755)

OpenTelemetry.Instrumentation.GrpcNetClient

Breaking change The Enrich callback option has been removed. For better
usability, it has been replaced by two separate options:
EnrichWithHttpRequestMessageand EnrichWithHttpResponseMessage. Previously,
the single Enrich callback required the consumer to detect which event
triggered the callback to be invoked (e.g., request start or response end) and
then cast the object received to the appropriate type: HttpRequestMessage
and HttpResponseMessage. The separate callbacks make it clear what event
triggers them and there is no longer the need to cast the argument to the
expected type.
(#3804)

OpenTelemetry.Instrumentation.Http

  • Added back netstandard2.0 target.
    (#3787)

  • Breaking change: The Enrich callback option has been removed. For better
    usability, it has been replaced by three separate options: In case of
    HttpClient the new options are EnrichWithHttpRequestMessage,
    EnrichWithHttpResponseMessage and EnrichWithException and in case of
    HttpWebRequest the new options are EnrichWithHttpWebRequest,
    EnrichWithHttpWebResponse and EnrichWithException. Previously, the single
    Enrich callback required the consumer to detect which event triggered the
    callback to be invoked (e.g., request start, response end, or an exception)
    and then cast the object received to the appropriate type:
    HttpRequestMessage, HttpResponsemessage, or Exception in case of
    HttpClient and HttpWebRequest,HttpWebResponse and Exception in case of
    HttpWebRequest. The separate callbacks make it clear what event triggers
    them and there is no longer the need to cast the argument to the expected
    type.
    (#3792)

  • Fixed an issue which prevented custom propagators from being called on .NET 7+
    runtimes for non-sampled outgoing HttpClient spans.
    (#3828)

  • Breaking change: The same API is now exposed for net462 and
    netstandard2.0 targets. The Filter property on options is now exposed as
    FilterHttpRequestMessage (called for .NET & .NET Core) and
    FilterHttpWebRequest (called for .NET Framework).
    (#3793)

OpenTelemetry.Instrumentation.SqlClient

OpenTelemetry.Shims.OpenTracing

Assets 2
Loading