github open-telemetry/opentelemetry-dotnet core-1.3.0-beta.2
1.3.0-beta.2 of core components

pre-release2 years ago

OpenTelemetry

  • Exposed public setters for LogRecord.State, LogRecord.StateValues,
    and LogRecord.FormattedMessage.
    (#3217)

OpenTelemetry.Api

OpenTelemetry.Exporter.Console

OpenTelemetry.Exporter.InMemory

OpenTelemetry.Exporter.Jaeger

  • Removes net5.0 target and replaced with net6.0
    as .NET 5.0 is going out of support.
    The package keeps netstandard2.1 target, so it
    can still be used with .NET5.0 apps.
    (#3147)

OpenTelemetry.Exporter.OpenTelemetryProtocol

  • LogExporter to support Logging Scopes.
    (#3218)

  • Support HttpProtobuf protocol with logs & added HttpClientFactory
    option
    (#3225)

  • Removes net5.0 target and replaced with net6.0
    as .NET 5.0 is going out of support.
    The package keeps netstandard2.1 target, so it
    can still be used with .NET5.0 apps.
    (#3147)

  • Fix handling of array-valued attributes for the OTLP trace exporter.
    (#3238)

  • Improve the conversion and formatting of attribute values to the OTLP format.
    The list of data types that must be supported per the
    OpenTelemetry specification
    is more narrow than what the .NET OpenTelemetry SDK supports. Numeric
    built-in value types
    are supported by converting to a long or double as appropriate except for
    numeric types that could cause overflow (ulong) or rounding (decimal)
    which are converted to strings. Non-numeric built-in types - string,
    char, bool are supported. All other types are converted to a string.
    Array values are also supported.
    (#3262)
    (#3274)

OpenTelemetry.Exporter.Prometheus

OpenTelemetry.Exporter.Zipkin

  • Removes net5.0 target and replaced with net6.0
    as .NET 5.0 is going out of support.
    The package keeps netstandard2.0 target, so it
    can still be used with .NET5.0 apps.
    (#3147)

Don't miss a new opentelemetry-dotnet release

NewReleases is sending notifications on new releases.