dotnet-counters not showing metric names

[sjrulandch]

Description

Trying out dotnet-counters with a service built using .NET8.
The System.Runtime counters are showing, but the AspNetCore.Hosting are not. Or, maybe they are showing but there are not labels (see attached image).

At the very least, I suspect that the labels are mis-alligned? I say this because the metric at the bottom appears to be the 'working set' (200.29). Several of the other values seem mis-labled as well (Thread Count at 98,384 seems ridiculously high for a web services that just started and has no traffic)

One, maybe abnormal thing is the design pattern for this service. It is part of a service oriented architecture. There is a single host process and it uses a plugin architecture. The process startup pipeline looks at a cmd line arg indicating which plugin to load. With that, it loads the assembly and determines if there are controllers, background tasks extra that needs to be supported. Because of this, it cannot use startup.cs. It uses all of the same steps (ie: IHostBuilder, etc). Is it possible that there are new, undocumented metric items that must be added to the pipeline?

Configuration

.NET8 - v8.0.204
dotnet-counters 8.0.510501+8c08c89a0643d31db91e119b1adb463be3e0ffe5

• installed as global tool

• WinVer reports: 22H2, OS Build 19045.429, 1

Other information

[noahfalk]

The System.Runtime counters are showing, but the AspNetCore.Hosting are not

It looks like when you invoked dotnet-counters you didn't specify which counters you wanted to see using the --counters argument. Without passing that argument the tool defaults to showing System.Runtime. If you do want to see other counters you could run the tool like this:

dotnet-counters monitor --process-id --counters System.Runtime,Microsoft.AspNetCore.Hosting

At the very least, I suspect that the labels are mis-alligned?

Yep, that is definitely a rendering bug. I recall seeing this behavior in older versions of dotnet-counters and I believe it was fixed. Likely #3816.

Could you try running dotnet tool update -g dotnet-counters to update to the latest version and then let us know if this problem still reproduces? I'm guessing it will not.

Hope that helps!

[dotnet-policy-service]

Hi @sjrulandch. We have added the "Needs: Author Feedback" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.