Released 2024-Jun-18
- Updated OpenTelemetry core component version(s) to
1.9.0
. (#1888)
Released 2024-May-20
- Update
OpenTelemetry.Api
to1.8.1
. (#1668)
Released 2024-Apr-05
Released 2024-Jan-03
- Update
OpenTelemetry.Api
to1.7.0
. (#1486)
Released 2023-Sep-06
-
Add a metric
process.runtime.dotnet.gc.duration
for total paused duration in GC for .NET 7 and greater versions (#1239) -
Update OpenTelemetry API to 1.5.1 (#1255)
Released 2023-Jun-06
- Update OpenTelemetry API to 1.5.0 (#1220)
Released 2023-Jun-01
- Bumped the version to
1.4.0
to keep it in sync with the release versions ofOpenTelemetry.API
. This makes it more intuitive for the users to figure out what version of core packages would work with a given version of this package.
Released 2023-Feb-27
- Update OpenTelemetry API to 1.4.0 (#1038)
Released 2023-Feb-13
- Update OpenTelemetry API to 1.4.0-rc.4 (#990)
Released 2023-Feb-02
- Update OpenTelemetry API to 1.4.0-rc.3 (#944)
Released 2023-Jan-11
- Update OpenTelemetry API to 1.4.0-rc.2 (#880)
Released 2022-Dec-13
- Update OpenTelemetry API to 1.4.0-rc.1 (#820)
Released 2022-Nov-22
-
Update OpenTelemetry API to 1.4.0-beta.3 (#774)
-
Change ObservableGauge to ObservableUpDownCounter for the below metrics (which better fit UpDownCounter semantics as they are additive.)
"process.runtime.dotnet.gc.heap.size", "process.runtime.dotnet.gc.heap.fragmentation.size", "process.runtime.dotnet.thread_pool.threads.count", "process.runtime.dotnet.thread_pool.queue.length", "process.runtime.dotnet.timer.count", "process.runtime.dotnet.assemblies.count" (#675)
If your backend system distinguishes between ObservableUpDownCounter and ObservableGauge, then you may need to adjust your queries. Systems like Prometheus are unaffected by this.
-
Removes NETCoreApp3.1 target as .NET Core 3.1 and .NET 5 are going out of support. The package keeps
netstandard2.0
target, so it can still be used with .NET Core 3.1/.NET 5 apps, however certain metrics will not be available there. Additionally, apps 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.The build warning can be suppressed by setting the SuppressTfmSupportBuildWarnings MSBuild property, but there is no guarantee that this package will continue to work on older versions of .NET.
This does not affect applications targeting .NET Framework.
-
Add "process.runtime.dotnet.gc.objects.size" metric (#683)
Released 2022-Aug-03
- Rename
RuntimeInstrumentOptions
toRuntimeInstrumentationOptions
(#556)
Released 2022-Jul-25
- Add gc.heap.fragmentation.size back for .NET 7 and later (#524)
Released 2022-Jul-19
-
Refined some metrics names (assembly.count->assemblies.count, exception.count-> exceptions.count, attribute name: gen->generation) and descriptions (#475)
-
Change API for GC Heap Size for .NET 6 where the API has a bug (#495)
-
Remove gc.heap.fragmentation.size metrics due to buggy API on .NET 6 (#509)
Released 2022-Jun-29
Major refactor of the runtime instrumentation. Renamed API signature and metrics. Removed the options to turn off certain metrics.
Major redesign of the runtime instrumentation. Renamed metrics to be more user-friendly and better logical grouping. Removed the process related metrics which are not .NET Runtime specific.
-
Updated OpenTelemetry SDK package version to 1.3.0 (#411)
-
Fix some bugs in Runtime metrics (#409)
-
Add GC heap size and refactor GC count as multi-dimensional metrics in Runtime metrics (#412)
- This is the first release of
OpenTelemetry.Instrumentation.Runtime
package.
For more details, please refer to the README.