.NET 2.0 Instrumentation Update
- How can I monitor my standalone WCF applications?
- Where can I find performance insights for my MVC applications?
- How can I easily see the end user experience for my .NET app?
Sound familiar? We have some great news – the new AppNeta .NET agent makes it extremely simple to monitor large complex .NET applications in production so that you can identify production issues quicker and optimize your .NET apps.
Standalone App Support
AppNeta now provides deep performance visibility into non-IIS hosted applications and services. In high throughput production environments you might have an IIS hosted web application that interacts with multiple standalone applications or services during the life of a single request. Tracking transactions across this environment is tough and visibility into the performance of these transactions is even more complicated.
In the example below, an IIS hosted web application makes an RPC call using WCF-Client to a WCF authentication app which can be either a standalone application or a service. The authentication app then performs some read and write operations on an Oracle database. For every request isolated by AppNeta’s workflow the visual identification of performance bottlenecks becomes a simple task.
The custom API also supports non-IIS hosted applications which means the number of .NET applications that you can monitor has expanded significantly.
How it Works?
- Update your .NET instrumentation simply by re-installing the agent. Please note the new installer option for non-IIS instrumentation support.
- Add the non-IIS hosted applications to the agent.config file.
Auto-RUM for IIS
Real User Monitoring (RUM) can be enabled and added to your TraceView traces without a single code update. While the manual method of adding code snippets to template files is still supported, it is no longer necessary.
TraceView RUM extends the visibility of a trace from the server to include data from the end-user’s client-side experience. Adding RUM to your application enables network, DOM processing and page rendering times to be reported and the ability to view and filter both server and client-side data by the user’s browser, location and page viewed.
How it Works?
- Update your .NET instrumentation.
- Go to the Real User Monitoring settings page to enable Auto-RUM per App.
Yes, it’s that easy!
Note: If you use our manual .NET RUM and would like to update to use Auto-RUM for .NET, you will need to remove the AppNeta Header and Footer code snippets previously added to your template files.
ASP.NET MVC Reporting
The .NET Agent now reports instrumentation details for ASP.NET MVC apps. We have added out-of-the-box visibility into the performance of your controllers and actions for MVC framework version 3, 4, and 5.
On upgrading, you will see an additional layer ‘mvc’ when an application built using MVC framework is being monitored. Along with getting the performance over time of the MVC layer, you can answer questions like:
- Which of my controller-action pairs are non-performant?
- Is template-rendering fast for my mvc applications?
Scroll down the page to find the Controllers table populated with insights like Standard Deviation, Frequency, Average and more for the relevant controller-action pairs.
Every cell in this table can act as a filter, so if you would like to monitor performance of an action like ‘Login’ over a period of time, it becomes really easy.
In addition to all of this good stuff, if you like tweaking with software to accomplish unique tasks, we have added additional configuration controls that enable to do things like:
- Get full transaction traces for a rarely accessed business critical endpoint
- Trace methods inlined by the CLR
- And more…
As always, we love hearing from you so please feel free to get in touch at email@example.com with your comments or feedback.