Experimental Dotnet Monitor Tool Now Fully Supported

The dotnet monitor tool that debuted as an experimental tool last year is now fully supported, helping developers access diagnostics information in a dotnet application.

"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 HTTP API regardless of where your application is run," says the project's GitHub site documentation.

Features of the .NET Foundation project (as of preview 4) include:

  • 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.
  • Security and Hardening: Requiring authentication is part of the work that's gone into hardening dotnet monitor to make it suitable for deployment in production environments. Additionally, to protect the credentials sent over the wire as part of authentication, dotnet monitor will also default to requiring that the underlying channel uses HTTPS.

"We've previously introduced dotnet monitor as an experimental tool to access diagnostics information in a dotnet process," Microsoft said in a recent blog post. "We're now pleased to announce dotnet monitor has graduated to a supported tool in the .NET ecosystem. dotnet monitor will be fully supported beginning with our first stable release later this year."

About the Author

David Ramel is an editor and writer for Converge360.

comments powered by Disqus