Skip to content

Releases: open-telemetry/opentelemetry-dotnet-contrib

Resources.Container-1.10.0-beta.1

09 Dec 06:41
729546b
Compare
Choose a tag to compare
Pre-release

Resources.Azure-1.10.0-beta.1

09 Dec 06:38
661c98a
Compare
Choose a tag to compare
Pre-release

Instrumentation.Wcf-1.10.0-beta.1

09 Dec 06:35
05e64b2
Compare
Choose a tag to compare
Pre-release
  • 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 to false). 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

09 Dec 06:34
f0a032c
Compare
Choose a tag to compare

Instrumentation.SqlClient-1.10.0-beta.1

09 Dec 06:30
feeffa2
Compare
Choose a tag to compare
Pre-release
  • 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
      the OTEL_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 and server.socket.address attributes
      are no longer emitted. Users should rely on the server.address attribute
      for the same information. Note that server.address is only included when
      the EnableConnectionLevelAttributes 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, and server.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, and error.type
    • Updated OpenTelemetry core component version(s) to 1.10.0.
      (#2317)

    See CHANGELOG for details.

Instrumentation.Quartz-1.10.0-beta.1

09 Dec 06:23
61c117c
Compare
Choose a tag to compare
Pre-release

Instrumentation.Process-1.10.0-beta.1

09 Dec 06:20
e5b1a17
Compare
Choose a tag to compare
Pre-release

Instrumentation.GrpcNetClient-1.10.0-beta.1

09 Dec 06:17
dfc2b74
Compare
Choose a tag to compare

Instrumentation.EntityFrameworkCore-1.10.0-beta.1

09 Dec 06:13
b7c1883
Compare
Choose a tag to compare
  • NuGet: OpenTelemetry.Instrumentation.EntityFrameworkCore v1.10.0-beta.1

    • The new database semantic conventions can be opted in to by setting
      the OTEL_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

09 Dec 06:08
d0d7761
Compare
Choose a tag to compare
Pre-release