Introduction

Microsoft .NET is one of the most popular technologies in the web application development space, and provides the building blocks for many modern-day, business-critical web applications - eg., Windows client applications, client-server applications, distributed applications, database applications, etc. With millions riding on these .NET applications, it is only natural that administrators constantly fuss over "Application downtime" and "Application slowness". If users frequently complain of application inaccessibility or its poor responsiveness to transaction requests, the enterprise can lose dearly, in terms of revenue, support cycles, productivity, penalties, and reputation!

To avoid this, administrators should continuously observe user interactions with their .NET applications and measure overall user experience with these applications. At the first sign of user dissatisfaction, administrators should identify the precise transactions where users are experiencing slowness, accurately isolate its root-cause, and resolve the bottleneck, well before users complain!

This is where eG Enterprise helps! Using the eG Real User Monitor (RUM), administrators can track transaction requests to a .NET application, measure the responsiveness of each transaction, rapidly identify the slow transactions , and precisely pinpoint what is causing the slowness - is it a problem with the application front-end (i.e., browser)? a flaky network connection? or a server-side processing delay?

If eG RUM reveals issues in server-side processing, then the eG .NET BTM steps in to provide in-depth visibility into transaction performance across the server-side tiers. In the process, the eG .NET BTM leads you the exact source of your transaction troubles.

This document focuses on the eG .NET Business Transaction Monitor (BTM), discusses how it works, and reveals how it helps ensure rapid diagnosis and resolution of delays in your mission-critical .NET transactions.