Releases: open-telemetry/opentelemetry-dotnet
1.0.0-rc9.6
OpenTelemetry.Instrumentation.AspNetCore
-
Removed
netstandard2.0
andnetstandard2.1
targets. .NET 5 reached EOL
in May 2022 and .NET Core 3.1 reaches EOL in December 2022. The
instrumentation for ASP.NET Core now requires .NET 6 or later.
(#3567) -
Fixed an issue where activity started within middleware was modified by
instrumentation library.
(#3498) -
Updated to use Activity native support from
System.Diagnostics.DiagnosticSource
to set activity status.
(#3118)
(#3555)
OpenTelemetry.Instrumentation.GrpcNetClient
- Updated to use Activity native support from
System.Diagnostics.DiagnosticSource
to set activity status.
(#3118)
(#3569)
OpenTelemetry.Instrumentation.Http
-
Updated to use Activity native support from
System.Diagnostics.DiagnosticSource
to set activity status.
(#3118)
(#3555) -
Changed activity source name from
OpenTelemetry.HttpWebRequest
toOpenTelemetry.Instrumentation.Http.HttpWebRequest
forHttpWebRequest
s
and fromOpenTelemetry.Instrumentation.Http
toOpenTelemetry.Instrumentation.Http.HttpClient
forHttpClient
.
(#3515)
core-1.4.0-alpha.2
OpenTelemetry
- Added
Sdk.CreateLoggerProviderBuilder
method and support for dependency
injection scenarios when configuringOpenTelemetryLoggerProvider
(#3504)
OpenTelemetry.Api
-
Updated to System.Diagnostics.DiagnosticSource preview version 7.0.0.
With this update, applications targeting .NET 5 and lower will receive a
warning at build time as described here
(note: building using older versions of the .NET SDK produces an error at
build time). This is because .NET 5 reached EOL in May 2022 and .NET
Core 3.1 reaches EOL in December 2022.There is no guarantee that System.Diagnostics.DiagnosticSource will continue
to work on older versions of .NET. However, the build warning can be
suppressed by setting theSuppressTfmSupportBuildWarnings
MSBuild property.This does not affect applications targeting .NET Framework.
#3539
OpenTelemetry.Exporter.OpenTelemetryProtocol
- When using Attribute
Limits
the OTLP exporter will now send "dropped" counts where applicable (ex:
dropped_attributes_count).
(#3580)
OpenTelemetry.Exporter.Prometheus.AspNetCore
-
Split up Prometheus projects based on its hosting mechanism,
HttpListener and AspNetCore, into their own projects
and assemblies.
(#3430
#3503
#3507) -
Added
IEndpointRouteBuilder
extension methods to help with Prometheus
middleware configuration on ASP.NET Core
(#3295)
OpenTelemetry.Exporter.Prometheus.HttpListener
1.0.0-rc9.5
OpenTelemetry.Instrumentation.AspNetCore
- Fix Remote IP Address - NULL reference exception.
(#3481) - Metrics instrumentation to correctly populate
http.flavor
tag.
(1.1 instead of HTTP/1.1 etc.)
(#3379) - Tracing instrumentation to populate
http.flavor
tag.
(#3372) - Tracing instrumentation to populate
http.scheme
tag.
(#3392)
OpenTelemetry.Instrumentation.Http
-
Added
http.scheme
tag to tracing instrumentation.
(#3464) -
[Breaking] Removes
SetHttpFlavor
option. "http.flavor" is
now always automatically populated.
To remove this tag, set "http.flavor" to null usingActivityProcessor
.
(#3380) -
Fix
Enrich
not getting invoked when SocketException due to HostNotFound
occurs.
(#3407)
OpenTelemetry.Instrumentation.SqlClient
- Update the
ActivitySource.Name
from "OpenTelemetry.SqlClient" to
"OpenTelemetry.Instrumentation.SqlClient".
(#3435)
core-1.4.0-alpha.1
OpenTelemetry
TracerProviderSDK
modified for spans with remote parent. For such spans
activity will be created irrespective of SamplingResult, to maintain context
propagation.
(#3329)- Fix issue where a measurement would be dropped when recording it with a
null-valued tag.
(#3325) CompositeProcessor
will now ensureParentProvider
is set on its children
(#3368)- Added
ForceFlush
and helper ctors onOpenTelemetryLoggerProvider
(#3364) Timestamp
,TraceId
,SpanId
,TraceFlags
,TraceState
,CategoryName
,
LogLevel
,EventId
, &Exception
properties onLogRecord
now expose
set
methods
(#3378)- Handle possible exception when initializing the default service name.
(#3405) LogRecord
instances are now reused to reduce memory pressure
(#3385)- Fix exact match of activity source name when
wildcard
is used.
(#3446) - Added AddOpenTelemetry
ILoggingBuilder
extensions which accept
OpenTelemetryLoggerProvider
directly
(#3489)
OpenTelemetry.Api
- Add
Activity.RecordException
overload accepting additional attributes to
add to theActivityEvent
.
#3433
OpenTelemetry.Exporter.Console
- The
MetricReaderOptions
defaults can be overridden using
OTEL_METRIC_EXPORT_INTERVAL
andOTEL_METRIC_EXPORT_TIMEOUT
environmental variables as defined in the
specification.
(#3424)
OpenTelemetry.Exporter.InMemory
-
InMemoryExporter
will now buffer scopes when exportingLogRecord
(#3360) -
The
MetricReaderOptions
defaults can be overridden using
OTEL_METRIC_EXPORT_INTERVAL
andOTEL_METRIC_EXPORT_TIMEOUT
environmental variables as defined in the
specification.
(#3424)
OpenTelemetry.Exporter.OpenTelemetryProtocol
-
Adds support for limiting the length and count of attributes exported from
the OTLP exporter. These
Attribute Limits
are configured via the environment variables defined in the specification.
(#3376) -
The
MetricReaderOptions
defaults can be overridden using
OTEL_METRIC_EXPORT_INTERVAL
andOTEL_METRIC_EXPORT_TIMEOUT
environmental variables as defined in the
specification.
(#3424)
OpenTelemetry.Extensions.Propagators
- Add
JaegerPropagator
.
(1881)
1.0.0-rc9.4 of all non core
All packages is updated to refer to 1.3.0 of the core API/.SDK. Rest of the changelog is below:
OpenTelemetry.Exporter.ZPages
- Removes .NET Framework 4.6.1. The minimum .NET Framework
version supported is .NET 4.6.2. (#3190)
OpenTelemetry.Extensions.Hosting
OpenTelemetry.Extensions.Propagators
Use own EventSource named "OpenTelemetry.Extensions.Propagators"
for internal logging.
OpenTelemetry.Instrumentation.AspNet
OpenTelemetry.Instrumentation.AspNet.TelemetryHttpModule
OpenTelemetry.Instrumentation.AspNetCore
-
Added additional metric dimensions.
(3247) -
Removes net5.0 target 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.Instrumentation.GrpcNetClient
- Add
netstandard2.0
target enabling the Grpc.Net.Client instrumentation to
be consumed by .NET Framework applications.
(#3105)
OpenTelemetry.Instrumentation.Http
OpenTelemetry.Instrumentation.SqlClient
OpenTelemetry.Instrumentation.StackExchangeRedis
OpenTelemetry.Shims.OpenTracing
- Removes .NET Framework 4.6.1. The minimum .NET Framework version supported is
.NET 4.6.2.
(#3190)
1.3.0 core components
Same as 1.3.0-rc.2
1.3.0-rc.2 of core components
OpenTelemetry
- Fix null reference exception when a metric view does not match an instrument.
(#3285) - Swallow
ObjectDisposedException
inBatchExportProcessor
and PeriodicExportingMetricReader
.
(#3291)
OpenTelemetry.Api
B3Propagator
class fromOpenTelemetry.Extensions.Propagators
namespace has
been deprecated and moved as is to a newOpenTelemetry.Extensions.Propagators
namespace, shipped as part of theOpenTelemetry.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 along
ordouble
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 astring
.
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 exportMetric
as new
typeMetricSnapshot
.
(#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 along
ordouble
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 astring
.
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 exportedActivity
. 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 along
ordouble
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 astring
.
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 exportedActivity
. Now,
array-valued attributes are serialzed to a JSON-array representation.
(#3281)
OpenTelemetry.Extensions.Propagators
- Initial release. This has been ported as is from
OpenTelemetry.Api package.
1.3.0-beta.2 of core components
OpenTelemetry
- Exposed public setters for
LogRecord.State
,LogRecord.StateValues
,
andLogRecord.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 & addedHttpClientFactory
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 along
ordouble
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 astring
.
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)
1.3.0-beta.1 of Core
Starting the 1.3.0-beta series. No code updates in this release.
1.2.0 of Core Components
1st Stable Release of Metrics SDK.
Same as 1.2.0-rc5, except the following changes.
OpenTelemetry
- Make setter for
MetricReaderOptions.PeriodicExportingMetricReaderOptions
property public.
(#3184)
OpenTelemetry.Exporter.OpenTelemetryProtocol