OpenTelemetry - CNCF/opentelemetry-dotnet: Release core-1.3.0-rc.2

Name: opentelemetry-dotnet

Owner: OpenTelemetry - CNCF

Release: 1.3.0-rc.2 of core components

Released: 2022-06-01

License: Apache-2.0

Release Assets:

OpenTelemetry

  • Fix null reference exception when a metric view does not match an instrument. (#3285)
  • Swallow ObjectDisposedException in BatchExportProcessor and
  • PeriodicExportingMetricReader. (#3291)

OpenTelemetry.Api

  • B3Propagator class from OpenTelemetry.Extensions.Propagators namespace has been deprecated and moved as is to a new OpenTelemetry.Extensions.Propagators namespace, shipped as part of the OpenTelemetry.Extensions.Propagators package. It will be removed in the next major release, see issue #3259

OpenTelemetry.Exporter.Console

  • Improve the conversion and formatting of attribute values. 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. (#3311)
  • Fix conversion of array-valued attributes. They were previously converted to a string like "System.String[]". (#3311)

OpenTelemetry.Exporter.InMemory

  • Adds new AddInMemoryExporter extension method to export Metric as new type MetricSnapshot. (#2361)

OpenTelemetry.Exporter.Jaeger

  • Improve the conversion and formatting of attribute values. 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. (#3281)
  • Fix conversion of array-valued resource attributes. They were previously converted to a string like "System.String[]". (#3281)
  • Fix exporting of array-valued attributes on an Activity. Previously, each item in the array would result in a new tag on an exported Activity. Now, array-valued attributes are serialzed to a JSON-array representation. (#3281)

OpenTelemetry.Exporter.OpenTelemetryProtocol

OpenTelemetry.Exporter.OpenTelemetryProtocol.Logs

OpenTelemetry.Exporter.Prometheus

OpenTelemetry.Exporter.Zipkin

  • Improve the conversion and formatting of attribute values. 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. (#3281)
  • Fix conversion of array-valued resource attributes. They were previously converted to a string like "System.String[]". (#3281)
  • Fix exporting of array-valued attributes on an Activity. Previously, each item in the array would result in a new tag on an exported Activity. Now, array-valued attributes are serialzed to a JSON-array representation. (#3281)

OpenTelemetry.Extensions.Propagators

To top