The dotnet-monitor global tool is a way to monitor .NET applications in production environments and to collect diagnostic artifacts (for example, dumps, traces, logs, and metrics) on-demand or using automated rules for collecting under specified conditions.

2 weeks ago - If the dotnet-counters tool isn't installed, run the following command: ... If your app is running a version of .NET older than .NET 9, the output UI of dotnet-counters will look slightly different than below; see dotnet-counters for details.

This repository contains the source code for .NET Monitor - a tool that allows you to gather diagnostic data from running applications using HTTP endpoints - dotnet-monitor/documentation/api/metrics.md at main · dotnet/dotnet-monitor

April 17, 2025 - An overview on using metrics to monitor a .NET application

August 14, 2024 - Monitor user registration and management. Track authentication patterns and potential security issues. Measure performance of Identity operations. Observe two-factor authentication usage. You can view these metrics using dotnet-counters to monitor them in real-time or export them to Prometheus and visualize them in Grafana using the techniques described earlier in this article.

January 27, 2026 - When running in production, you'll likely want to collect your metrics using an OpenTelemetry exporter integration or another solution (e.g. Datadog can collect these metrics without requiring application changes), but for local testing dotnet-counters is a very convenient tool. dotnet-counters is a .NET tool shipped by Microsoft that you can install by running: ... Alternatively, you can specify a command to run when starting the tool, and it will monitor the target process:

January 12, 2021 - dotnet-monitor is a command line tool that makes it easier to get access to diagnostics information in a dotnet process.In the episode, Rich is joined by Sourabh who explains to us the importance of gathering application diagnostics and also gives us a demo of how to run dotnet-monitor in Kubernetes[01:43] - Why was dotnet-monitor created?[05:37] - dotnet-monitor setup in kubernetes[14:50] - Integrating dotnet-monitor into other tools[16:45] - Support for additional metrics and event logs[19:12] - Exposing Prometheus style metrics Useful LinksIntroducing dotnet-monitor.NET Diagnostics on GitHubCollect diagnostics in containersWhat diagnostic tools are available in .NET Core?

Run the new process and use dotnet-counters as before in a second shell to view the metrics: > dotnet-counters monitor -n metric-demo.exe --counters HatCo.Store Press p to pause, r to resume, q to quit.

With the Prometheus data source ... in your pod. The dashboard shows the key default metrics relating to Memory, CPU, Requests and Garbage collection....

Whenever a request is made to this ... dotnet-counters global tool. You can run the following command to see the metrics: dotnet-counters monitor -n MetricsDemo --counters MetricsDemo.ProductStore...

To collect metrics using dotnet-counters, it needs to be run as the same user as the user running target process or as root. Otherwise, the tool will fail to establish a connection with the target process. Collect all counters at a refresh interval of 3 seconds and generate a csv as output: > dotnet-counters collect --process-id 1902 --refresh-interval 3 --format csv --counters is unspecified. Monitoring System.Runtime counters by default.

February 3, 2021 - dotnet-monitor is a command line tool that makes it easier to get access to diagnostics information i... Tagged with dotnet, diagnostics, metrics, performance.

When using a collection tool like Prometheus, it is recommended that you set your scrape interval to MetricCount * GlobalCounter:IntervalSeconds. In the default configuration, we recommend you scrape dotnet monitor for metrics every 15 seconds.

The Metrics Endpoint in dotnet monitor is a cornerstone for performance monitoring, delivering critical insights into application health through various metrics. These metrics include CPU usage, memory consumption, and application-specific counters, ...

This article describes the built-in metrics for .NET runtime libraries that are produced using the System.Diagnostics.Metrics API.

This Grafana dashboard provides comprehensive monitoring of .NET Core runtime metrics, giving you deep insights into your application's performance, memory management, threading, and exception handling. Source code for this dashboard is available at: https://github.com/petabridge/dotnet-grafa...

May 20, 2021 - When deploying in-cluster, a common pattern to collect metrics is to use Prometheus or another monitoring tool to scrape the metrics endpoint exposed by your application. As an example, when running in Azure Kubernetes Services (AKS), you can configure Azure Monitor to scrape prometheus metrics exposed by dotnet-monitor.

October 11, 2022 - In addition to the collection of System.Runtime and Microsoft.AspNetCore.Hosting metrics, it is now possible to collect additional metrics (emitted via EventCounters) for exporting in the Prometheus exposition format. You can configure dotnet monitor to collect additional metrics as shown in the example below:

This library allows you to instrument your code with custom metrics and provides some built-in metric collection integrations for ASP.NET Core.

Egress providers: Developers can configure dotnet monitor to egress artifacts to other destinations: Azure Blob Storage and the local filesystem. It is possible to specify multiple egress providers via configuration. Custom metrics: In addition to the collection of System.Runtime and Microsoft.AspNetCore.Hosting metrics, it is now possible to collect additional metrics (emitted via EventCounters) for exporting in the Prometheus exposition format.