You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
Description
Trying out
dotnet-counters
with a service built using .NET8.The
System.Runtime
counters are showing, but theAspNetCore.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
The text was updated successfully, but these errors were encountered: