Client side monitoring is fully integrated into the SCOM 2012 beta console. Just be aware before configuring client side monitoring:
- Server side monitoring must be implemented before client side monitoring for a web application (you can use client side monitoring without server side monitoring for a specific web application).
- The CSM Collector is now automatically local to the client agent.
- Make sure that you check to ensure that your application is suitable for client side monitoring
If you plan to monitor browser performance, check application compatibility before you begin to configure client-side monitoring for the ASP.NET application. You will need this information during the client-side application monitoring steps of the wizard.
To see a view of all the ASP.NET applications that Operations Manager 2012 finds, in the Operations Manager 2012 console, in the navigation pane, click the Monitoring button, expand Application Monitoring, expand .NET Monitoring, and click ASP.NET Web Application Inventory.
To check applications for compatibility with client-side monitoring, click an application name and in the Tasks pane, in the IIS 7 ASP.NET Application Endpoint Tasks section, click Check Client Side Monitoring Compatibility, and then click Run. This task does an analysis and lets you know if the application has compatibility issues with client-side monitoring.
The results page displays whether incompatibilities are found. If an application has incompatibilities, you will want to exclude the incompatible pages from client-side monitoring later when you are configuring client-side monitoring.
This application is not suitable for client side monitoring as it contains methods which, if called, could cause incorrect content to be returned to the browser.
I am going to assume that the client application passed the check and enable client side monitoring for the NOPCommerce web application. This is not good practice as I have been warned by the check client side
monitoring capability check that this application is not suitable for client side monitoring.
A quick caveat on SCOM 2012 beta – this should not be in the final release
Click the Excluded Pages link, and on the Excluded Pages page, click Add to add the pages that you want to exclude from client-side monitoring. The pages you add to this list are the pages that the Check Client Side Monitoring Compatibility task found incompatible when you ran the task before configuring your application for monitoring.
On the Enable Client Side Monitoring page, in the Monitored Servers section, you can target a group to limit the scope of the monitoring to a group of servers. To choose a targeted group, click Search and use the Group Search page to search for the group by name and management pack and then add them to the selected objects list. The targeted group you choose are the only servers hosting the web application that will instrument the application pages to return browser-side events. This group allows you to limit client-side monitoring independent of server-side monitoring.
On the Client Side Configuration tab, choose how you want to monitor performance and exception events, page load threshold, and Ajax and WCF threshold. What you enter into the Configure client IP address filter section
determines the client requests that are monitored. By default the filter is set to the localhost so only connections from the local host will be instrumented for monitoring (set \ remove filters as required).
After the client-side monitoring has been configured, you will receive an alert to recycle IIS on the affected servers once the client-side monitoring settings have been applied to the server. You can use the link in the knowledge base article to recycle the IIS application pools on the server.
Alerts
Tags: APM (Avicode), CSM
[...] Part 3 – Client Side Monitoring [...]