Releases: open-telemetry/opentelemetry-dotnet-contrib
Resources.Container-1.10.0-beta.1
-
NuGet: OpenTelemetry.Resources.Container v1.10.0-beta.1
-
Drop support for .NET 6 as this target is no longer supported
and add .NET 8/.NET Standard 2.0 targets.
(#2166) -
Updated OpenTelemetry core component version(s) to
1.10.0
.
(#2317)
See CHANGELOG for details.
-
Resources.Azure-1.10.0-beta.1
-
NuGet: OpenTelemetry.Resources.Azure v1.10.0-beta.1
-
Drop support for .NET 6 as this target is no longer supported and add .NET 8 target.
(#2165) -
Added direct reference to
System.Text.Json
for thenet8.0
target with
minimum version of8.0.5
in response to
CVE-2024-43485.
(#2198) -
Updated OpenTelemetry core component version(s) to
1.10.0
.
(#2317)
See CHANGELOG for details.
-
Instrumentation.Wcf-1.10.0-beta.1
-
NuGet: OpenTelemetry.Instrumentation.Wcf v1.10.0-beta.1
-
Drop support for .NET 6 as this target is no longer supported and add .NET 8 target.
(#2263) -
Updated OpenTelemetry core component version(s) to
1.10.0
.
(#2317) -
Added a
RecordException
property to specify if exceptions should be
recorded (defaults tofalse
). This is only supported by client instrumentation.
(#2271) -
Trace instrumentation will now call the Activity.SetStatus
API instead of the deprecated OpenTelemetry API package extension when setting
span status. For details see: Setting Status.
(#2358)
See CHANGELOG for details.
-
Instrumentation.StackExchangeRedis-1.10.0-beta.1
-
NuGet: OpenTelemetry.Instrumentation.StackExchangeRedis v1.10.0-beta.1
-
Drop support for .NET 6 as this target is no longer supported and add .NET 8 target.
(#2160) -
Updated OpenTelemetry core component version(s) to
1.10.0
.
(#2317)
See CHANGELOG for details.
-
Instrumentation.SqlClient-1.10.0-beta.1
-
NuGet: OpenTelemetry.Instrumentation.SqlClient v1.10.0-beta.1
-
Drop support for .NET 6 as this target is no longer supported.
(#2159) -
The new database semantic conventions can be opted in to by setting
theOTEL_SEMCONV_STABILITY_OPT_IN
environment variable. This allows for a
transition period for users to experiment with the new semantic conventions
and adapt as necessary. The environment variable supports the following
values:database
- emit the new, frozen (proposed for stable) database
attributes, and stop emitting the old experimental database
attributes that the instrumentation emitted previously.database/dup
- emit both the old and the frozen (proposed for stable) database
attributes, allowing for a more seamless transition.- The default behavior (in the absence of one of these values) is to continue
emitting the same database semantic conventions that were emitted in
the previous version. - Note: this option will be be removed after the new database
semantic conventions is marked stable. At which time this
instrumentation can receive a stable release, and the old database
semantic conventions will no longer be supported. Refer to the
specification for more information regarding the new database
semantic conventions for
spans.
(#2229,
#2277,
#2262,
#2279)
-
Breaking change: The
peer.service
andserver.socket.address
attributes
are no longer emitted. Users should rely on theserver.address
attribute
for the same information. Note thatserver.address
is only included when
theEnableConnectionLevelAttributes
option is enabled.
(#2229) -
Breaking change: When
EnableConnectionLevelAttributes
is enabled, the
server.port
attribute will now be written as an integer to be compliant with
the semantic conventions.
Previously, it was written as a string.
(#2233) -
The
EnableConnectionLevelAttributes
option is now enabled by default.
(#2249) -
The following attributes are now provided when starting an activity for a database
call:db.system
,db.name
(old conventions),db.namespace
(new conventions),
server.address
, andserver.port
. These attributes are now available for sampling
decisions.
(#2277) -
Breaking change: The
SetDbStatementForStoredProcedure
option has been removed.
(#2284) -
Add support for metric
db.client.operation.duration
from new database semantic conventions
on .NET 8+.
(#2309) -
Add support for metric
db.client.operation.duration
from new database semantic conventions
on .NET Framework.
(#2311)- Only the following attributes are available when a trace is not captured:
db.system
,db.response.status_code
, anderror.type
- Only the following attributes are available when a trace is not captured:
-
Updated OpenTelemetry core component version(s) to
1.10.0
.
(#2317)
See CHANGELOG for details.
-
Instrumentation.Quartz-1.10.0-beta.1
-
NuGet: OpenTelemetry.Instrumentation.Quartz v1.10.0-beta.1
-
Updated OpenTelemetry core component version(s) to
1.10.0
.
(#2317) -
Trace instrumentation will now call the Activity.SetStatus
API instead of the deprecated OpenTelemetry API package extension when setting
span status. For details see: Setting Status.
(#2358)
See CHANGELOG for details.
-
Instrumentation.Process-1.10.0-beta.1
-
NuGet: OpenTelemetry.Instrumentation.Process v1.10.0-beta.1
- Updated OpenTelemetry core component version(s) to
1.10.0
.
(#2317)
See CHANGELOG for details.
- Updated OpenTelemetry core component version(s) to
Instrumentation.GrpcNetClient-1.10.0-beta.1
-
NuGet: OpenTelemetry.Instrumentation.GrpcNetClient v1.10.0-beta.1
-
Drop support for .NET 6 as this target is no longer supported.
(#2150) -
Updated OpenTelemetry core component version(s) to
1.10.0
.
(#2317)
See CHANGELOG for details.
-
Instrumentation.EntityFrameworkCore-1.10.0-beta.1
-
NuGet: OpenTelemetry.Instrumentation.EntityFrameworkCore v1.10.0-beta.1
-
The new database semantic conventions can be opted in to by setting
theOTEL_SEMCONV_STABILITY_OPT_IN
environment variable. This allows for a
transition period for users to experiment with the new semantic conventions
and adapt as necessary. The environment variable supports the following
values:database
- emit the new, frozen (proposed for stable) database
attributes, and stop emitting the old experimental database
attributes that the instrumentation emitted previously.database/dup
- emit both the old and the frozen (proposed for stable) database
attributes, allowing for a more seamless transition.- The default behavior (in the absence of one of these values) is to continue
emitting the same database semantic conventions that were emitted in
the previous version. - Note: this option will be be removed after the new database
semantic conventions is marked stable. At which time this
instrumentation can receive a stable release, and the old database
semantic conventions will no longer be supported. Refer to the
specification for more information regarding the new database
semantic conventions for
spans.
(#2130)
-
Updated OpenTelemetry core component version(s) to
1.10.0
.
(#2317) -
Trace instrumentation will now call the Activity.SetStatus
API instead of the deprecated OpenTelemetry API package extension when setting
span status. For details see: Setting Status.
(#2358)
See CHANGELOG for details.
-
Instrumentation.AspNet-1.10.0-beta.1
-
NuGet: OpenTelemetry.Instrumentation.AspNet v1.10.0-beta.1
-
Updated registration extension code to retrieve environment variables through
IConfiguration
.
(#1976) -
Updated OpenTelemetry core component version(s) to
1.10.0
.
(#2317) -
Fixed an issue in ASP.NET instrumentation where route extraction failed for
attribute-based routing with multiple HTTP methods sharing the same route template.
(#2250)
See CHANGELOG for details.
-
-
NuGet: OpenTelemetry.Instrumentation.AspNet.TelemetryHttpModule v1.10.0-beta.1
-
TelemetryHttpModule
will now pass theurl.path
tag (set to
Request.Unvalidated.Path)
when startingActivity
instances for incoming requests so that it is
available to samplers and may be used to influence the sampling decision made
by custom
implementations.
(#1871) -
Updated OpenTelemetry core component version(s) to
1.10.0
.
(#2317)
See CHANGELOG for details.
-