Skip to main content

Visual Studio–View .NET Counters while debugging

The .NET runtime exposes multiple metrics through the concept of Event Counters. They were originally introduced in .NET Core as a cross-platform alternative to Performance Counters that only worked on a Windows OS. With the recent introduction of OpenTelemetry support in .NET and the System.Diagnostics.Metrics API, there is a clear path forward. But this doesn’t mean that Event Counters are not useful anymore.

The tooling and ecosystem around it is evolving to support both Event Counters and System.Diagnostics.Metrics. For example, you can see this in action when using the global dotnet-counters tool.

Where I before always used the dotnet-counters tool to monitor the .NET counters, I recently discovered during a debugging session in Visual Studio, that you directly can access this information in the Diagnostics Tools:

  • During a debugging session, go to Diagnostics Tools:



  • Select the .NET Counters option from the Select Tool dropdown if the Counters are not yet enabled:
  • Go to the Counters tab to see the available counters:

 

That’s it!

More information

Monitor your application using Event Counters–Part I (bartwullems.blogspot.com)

Monitor your application using Event Counters–Part II (bartwullems.blogspot.com)

Monitor your application using Event Counters - Part III (bartwullems.blogspot.com)

Well-known EventCounters in .NET - .NET | Microsoft Learn

dotnet-counters diagnostic tool - .NET CLI - .NET | Microsoft Learn

Labels:

Popular posts from this blog

Podman– Command execution failed with exit code 125

After updating WSL on one of the developer machines, Podman failed to work. When we took a look through Podman Desktop, we noticed that Podman had stopped running and returned the following error message: Error: Command execution failed with exit code 125 Here are the steps we tried to fix the issue: We started by running podman info to get some extra details on what could be wrong: >podman info OS: windows/amd64 provider: wsl version: 5.3.1 Cannot connect to Podman. Please verify your connection to the Linux system using `podman system connection list`, or try `podman machine init` and `podman machine start` to manage a new Linux VM Error: unable to connect to Podman socket: failed to connect: dial tcp 127.0.0.1:2655: connectex: No connection could be made because the target machine actively refused it. That makes sense as the podman VM was not running. Let’s check the VM: >podman machine list NAME         ...
Read more

Azure DevOps/ GitHub emoji

I’m really bad at remembering emoji’s. So here is cheat sheet with all emoji’s that can be used in tools that support the github emoji markdown markup: All credits go to rcaviers who created this list.
Read more

Cleaner switch expressions with pattern matching in C#

Ever find yourself mapping multiple string values to the same result? Being a C# developer for a long time, I sometimes forget that the C# has evolved so I still dare to chain case labels or reach for a dictionary. Of course with pattern matching this is no longer necessary. With pattern matching, you can express things inline, declaratively, and with zero repetition. A small example I was working on a small script that should invoke different actions depending on the environment. As our developers were using different variations for the same environment e.g.  "tst" alongside "test" , "prd" alongside "prod" .  We asked to streamline this a long time ago, but as these things happen, we still see variations in the wild. This brought me to the following code that is a perfect example for pattern matching: The or keyword here is a logical pattern combinator , not a boolean operator. It matches if either of the specified pattern...
Read more