For developers and operations teams building and managing applications with the ASP.NET framework (including MVC, MVC 2, MVC 3, MVC 4, and MVC 5), the AppDynamics platform provides a comprehensive solution for monitoring and managing the performance of your .NET applications. With rapid installation and the most scalable architecture in the industry, AppDynamics solutions help you deploy your applications more quickly and with more confidence.
In this example, AppDynamics auto-discovers two ASP.NET tiers and two backends. The NWTraders-WebLog and NWTraders-Portal tiers are ASP.NET. The flow map shows the communication as the average number of calls per minute between the tiers and the average response time for a single call.
AppDynamics detects user requests for an ASP.NET web application. It creates business transactions for the URI name, such as “order-detail.aspx”, and displays them in the business transaction dashboard. The business transaction dashboard shows the overall health of the transaction and critical statistics, such as the number of calls per minute and the number of slow transactions, to help you monitor business transaction performance.
AppDynamics takes transaction snapshots which contain diagnostic data to help you quickly analyze and troubleshoot problems with ASP.NET business transactions. Transaction snapshots automatically begin when AppDynamics detects a slow or stalled transaction. In this example, the /admin/orders.aspx business transaction is running very slow.
Drill down into a transaction snapshot to display the call graph for ASP.NET transactions. The call graph displays the code execution sequence timing so you can identify which methods have problems. In this example, the GetResponse method is taking 264 milliseconds, 83.5% of the time for the business transaction. It also shows an exit call to an HTTP backend.
AppDynamics collects metrics on the overall application performance of ASP.NET applications. Use the metric browser to create graphs of critical statistics. The graph at right shows a spike in the calls per minute (in green) at 2:03 pm. The spike doesn’t affect the average response time (in blue) or the number of errors per minute (red). When spikes do cause problems, graphs can help you correlate different system events.