The side car approach for setting up Dotnet Monitor in a Windows Container to get the diagnostics logs of a different container is currently not supported as mentioned by Jander-MSFT in this Github Issue which might get resolved by this Issue.
As a Solution , You will have to install the tool on the same Windows container by running the below command :
dotnet tool install --global dotnet-monitor --version 6.0.0
You can refer this blog by Scott Hanselman for more details on the same .
.net - How to use dotnet monitor in windows containers to collect application metrics - Stack Overflow
Introducing dotnet-monitor, an experimental tool
Intro:
dotnet-monitor is an experimental tool that makes it easier to get access to diagnostics information in a dotnet process.
When running a dotnet application differences in diverse local and production environments can make collecting diagnostics artifacts (e.g., logs, traces, process dumps) challenging. dotnet-monitor aims to simplify the process by exposing a consistent REST API regardless of where your application is run.
This blog post details how to get started with dotnet-monitor and covers the following:
How to setup dotnet-monitor What diagnostics artifacts can be collected; and How to collect each of the artifacts
More on reddit.comazure devops - dotnet-monitor v5 works ok but v8 can't find processes in AKS Kubernetes - DevOps Stack Exchange
[QUESTION] Understanding dotnet-monitor LiveMetrics
Videos
https://devblogs.microsoft.com/dotnet/introducing-dotnet-monitor/
Intro:
dotnet-monitor is an experimental tool that makes it easier to get access to diagnostics information in a dotnet process.
When running a dotnet application differences in diverse local and production environments can make collecting diagnostics artifacts (e.g., logs, traces, process dumps) challenging. dotnet-monitor aims to simplify the process by exposing a consistent REST API regardless of where your application is run.
This blog post details how to get started with dotnet-monitor and covers the following:
How to setup dotnet-monitor What diagnostics artifacts can be collected; and How to collect each of the artifacts
you really should include some information other than the link.
https://github.com/dotnet/dotnet-monitor/blob/main/documentation/api/livemetrics-get.md
I use dotnet-monitor as a sidecar container and I can get LiveMetrics via API. Well, just make a request via curl and return LiveMetrics. But how can I collect them? I have not seen anything like this not in Prometheus, not in Grafana, not in Zabbix. All I Googled is that they are parsed well using Azure Monitor. How can I collect and parse them if I'm not in Azure?
Hi, I would love to hear how you monitor your .NET web applications.
What tools do you use? What metrics are you collecting?
We currently try to use ELK stack as much as possible, but we're struggling to find clean solution to monitor CPU, Memory, GC and other metrics on ELK.