Skip to content

Releases: dotnet/dotnet-monitor

Dotnet-Monitor Release - v8.0.0-preview.3.23180.9

11 Apr 15:49
133957c

Choose a tag to compare

Today we are releasing the next official preview version of the dotnet monitor tool. This release includes:

  • Represent System.Diagnostics.Metrics Counters as Gauges in Prometheus Exposition Format. (#4098)
  • Fixes issue where trace operations with an egress provider and rundown on Linux would cause dotnet-monitor to lose connectivity with the target application. (#3960)
  • Added EventMeter Trigger for Collection Rules. (#3812)
Packages released to NuGet
  • dotnet-monitor.8.0.0-preview.3.23180.9.nupkg

Dotnet-Monitor Release - v7.1.1

11 Apr 15:49
a681b6c

Choose a tag to compare

Today we are releasing the 7.1.1 build of the dotnet monitor tool. This release includes:

  • Represent System.Diagnostics.Metrics Counters as Gauges in Prometheus Exposition Format. (#4101)
  • Fixes issue where trace operations with an egress provider and rundown on Linux would cause dotnet-monitor to lose connectivity with the target application. (#3960)
Packages released to NuGet
  • dotnet-monitor.7.1.1.nupkg

Dotnet-Monitor Release - v8.0.0-preview.2.23155.4

14 Mar 15:50
8763c49

Choose a tag to compare

Today we are releasing the next official preview version of the dotnet monitor tool. This release includes:

  • Add substitution tokens for other process info (#3759)
  • Add Azure Active Directory authentication support. For more details see our Azure AD documentation. (#3755)
Packages released to NuGet
  • dotnet-monitor.8.0.0-preview.2.23155.4.nupkg

Dotnet-Monitor Release - v7.1.0

14 Mar 15:49
97a9c61

Choose a tag to compare

Today we are releasing the 7.1.0 build of the dotnet monitor tool. This release includes:

  • Produce RID-specific, TFM-specific, framework dependent archives (#3507)
  • Add substitution tokens for other process info (#3793)
  • Add Azure Active Directory authentication support. For more details see our Azure AD documentation. (#3792)
  • Add support for System.Diagnostics.Metrics (#3750)
  • Add Swagger UI to dotnet-monitor as the default endpoint. This will provide documentation of endpoints, and also the ability to use them. (#3450)
  • Add Tags For API Requests (#3162)
  • Add Metadata Support For Metrics (#3084)
  • 🔬 Add support for thread names stack artifacts. (#3004)
  • Add support for gracefully stopping a requested trace on demand while also collecting rundown, via Stop Operation. All artifact requests are now also recorded under the Operations API, regardless of if they have an egress provider specified. (#2893)
  • Add the option to specify a StoppingEvent on the CollectTrace action. The trace will be stopped once either the duration is reached or the specified event occurs. (#2884)
  • Handle exceptions when determining additional information about discovered processes. (#2813)

*🔬 indicates an experimental feature

Packages released to NuGet
  • dotnet-monitor.7.1.0.nupkg

Dotnet-Monitor Release - v8.0.0-preview.1.23113.9

21 Feb 16:54
15d7220

Choose a tag to compare

Today we are releasing the next official preview version of the dotnet monitor tool. This release includes:

  • Produce RID-specific, TFM-specific, framework dependent archives (#3507)
  • Add support for System.Diagnostics.Metrics (#3479)
  • Add Swagger UI to dotnet-monitor as the default endpoint. This will provide documentation of endpoints, and also the ability to use them. (#3241)
  • 🔬 Add support for thread names stack artifacts. (#2941)
  • Add Metadata Support For Metrics (#2939)
  • Add Tags For API Requests (#2919)
  • Add support for gracefully stopping a requested trace on demand while also collecting rundown, via Stop Operation. All artifact requests are now also recorded under the Operations API, regardless of if they have an egress provider specified. (#2828)
  • Handle exceptions when determining additional information about discovered processes. (#2806)
  • 🔬 Add support for speedscope format when capturing stacks. (#2795)
  • Add support of egress provider to deliver data to a S3 storage (#2016)
  • Add the option to specify a StoppingEvent on the CollectTrace action. The trace will be stopped once either the duration is reached or the specified event occurs. (#2884)

*🔬 indicates an experimental feature

Packages released to NuGet
  • dotnet-monitor.8.0.0-preview.1.23113.9.nupkg

Dotnet-Monitor Release - v7.0.2

14 Feb 17:43
710aee0

Choose a tag to compare

Today we are releasing the 7.0.2 build of the dotnet monitor tool. This release includes:

  • Produce RID-specific, TFM-specific, framework dependent archives (#3520)
Packages released to NuGet
  • dotnet-monitor.7.0.2.nupkg

Dotnet-Monitor Release - v6.3.2

14 Feb 17:42
68aa7e8

Choose a tag to compare

Today we are releasing the 6.3.2 build of the dotnet monitor tool. This release includes:

  • Produce RID-specific, TFM-specific, framework dependent archives (#3521)
Packages released to NuGet
  • dotnet-monitor.6.3.2.nupkg

Dotnet-Monitor Release - v7.0.1

13 Dec 17:05
efc97fa

Choose a tag to compare

Today we are releasing the 7.0.1 build of the dotnet monitor tool. This release includes:

  • Handle exceptions when determining additional information about discovered processes. (#2813)
Packages released to NuGet
  • dotnet-monitor.7.0.1.nupkg

Dotnet-Monitor Release - v6.3.1

13 Dec 16:49
5116e36

Choose a tag to compare

Today we are releasing the 6.3.1 build of the dotnet monitor tool. This release includes:

  • Fixed an issue where AspNet* collection rules could stop functioning after collecting a trace with the Http profile. The fix was made in dotnet/diagnostics#3425. (#2786)
  • Handle exceptions when determining additional information about discovered processes. (#2814)
Packages released to NuGet
  • dotnet-monitor.6.3.1.nupkg

Dotnet-Monitor Release - v7.0.0

07 Nov 21:06
0c07973

Choose a tag to compare

Today we are releasing the 7.0.0 build of the dotnet monitor tool. This release includes:

  • Fixed an issue where AspNet* collection rules could stop functioning after collecting a trace with the Http profile. The fix was made in dotnet/diagnostics#3425. (#2764)
  • Change the default Garbage Collector mode to Workstation, except when running inside one of the official dotnet monitor docker images with more than 1 logical CPU core available. Learn more here. (#2737)
Packages released to NuGet
  • dotnet-monitor.7.0.0.nupkg