-
Notifications
You must be signed in to change notification settings - Fork 114
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
dotnet-monitor captures incomplete metrics #7175
Comments
Welcome to dotnet-monitor!Thanks for creating your first issue; let us know what you think of dotnet-monitor by filling out our survey. |
version: 8.0.4 |
Would you be able to try collection using dotnet-counters? This will help isolate the issue. Not necessarily related, but we have seen scenarios where there is interference between collectors (for example OpenTelemetry) or strange behavior for trimmed/self-contained apps. See #1241 |
Thank you very much, I'll try it out when I have time. |
I have similar issue - the http.server.request.duration is not collected from .net 8.0 process. I tried with dotnet-monitor version {
"$schema": "https://aka.ms/dotnet-monitor-schema",
"DefaultProcess": {
"Filters": [
{
"Key": "ProcessId",
"Value": "<pid>",
"MatchType": "Exact"
}
]
},
"Metrics": {
"Providers": [
{
"ProviderName": "Microsoft.AspNetCore.Hosting"
}
]
}
} Command line:
Other metrics from same provider are collected properly ( At the same time I'm able to show this metric using dotnet-counter tool, version
|
After installing dotnet-monitor globally, some indicators are missing (microsoftaspnetcorehosting_current_requests, microsoftaspnetcorehosting_failed_requests)
Two machines, one of which is normal, and the other is wrong, but I tried to reinstall dotnet-monitor and it didn't work
/metrics
The text was updated successfully, but these errors were encountered: