Application trace monitoring
How to monitor DOTNET?


ServicePilot apptrace-dotnet




What is .NET App Trace?

.NET, or dotnet, it the name given by Microsoft to its set of products and technologies that enable application development and internet portability. The .NET platform builds its foundation on several Microsoft technology layers such as Windows OS, .NET framework, ASP.NET, C# object-oriented language, vb.net and more.

The NET Framework app has its own best practices and tools for assessing performance while development phase, when you have hands on code and application internals, which is not always the case. The Redgate ANTS Performance Profiler or the Jetbrains suite dottrace are the industry leading development performance profiling tools available for dev .NET environments.

Unlike development, dotnet production application monitoring differs. One cannot trace each request to code level without a performance, time or cost related tradeoff. Plus, as previously said, we do not always have hands on each production application code with a dedicated development team, which is why the ServicePilot application instrumentation happens without modifying or touching the existing codebase.

ServicePilot provides a production application monitoring package which aims at being the first step to any application improvement and operational performance reporting.

ServicePilot standard .NET production application monitoring is the monitoring of real user experience, every single business transaction, application usage metrics, regardless of its application code.

In order to provide a real full-stack performance visibility over your application, several packages can be added to fill in application topology map, testing or application dependencies monitoring: Microsoft IIS traces, Microsoft IIS counters, W3C and application logs, HTTP(S) web tests and scenario, MSSQL and many more.

DotNET Trace monitoring

This package monitors HTTP(S) web transactions from .NET processes. ServicePilot Windows agents can be provisioned to instrument .NET processes to automatically log their web connections.

This allows to gather summarized statistics (min,max,avg...) per .NET application such as:

  • Requests per minute
  • HTTP return codes and methods
  • Number of transactions in each response time range
  • Established transactions

In order to provide deep dotNET application insights, details collected per transaction include:

  • URL and web page path
  • IP client and HTTP host
  • Real User Response time
  • HTTP Return code and method

Other Application Traces integrations