You can significantly impact the end-user’s experience through customization of your SharePoint environment.
System Center Operations Manager allows you to monitor your SharePoint 2010 Web Front-end components. Additionally, you can monitor standard and custom SharePoint webpages for performance degradation.
Monitoring for SharePoint Applications
Most of time your SharePoint Front-end is already discovered by the IIS management pack. It’s great, but not enough if you use customized code.
To be able to monitor SharePoint application monitoring, we will use the .NET Application Performance Monitoring template. Then, the APM agent will collect and analyze data to monitor performance. The agent will:
- Collect relevant SharePoint method parameters from SharePoint servers, API calls and Web Part calls containing Application Diagnostics Events,
- Track the execution times for the slowest calls to collect names of slow web parts and their locations in the pages.
You must install:
- Operations Manager Web Console
- Import the IIS 7.0 management pack (Microsoft.Windows.InternetInformationServices.2008.mp)
- Import the Operations Manager APM Web IIS 7 management pack (Microsoft.SystemCenter.Apm.Web.IIS7.mp).
- Deploy Agents on Front-end servers
If your Front-end server is a Windows server 2012, you have to import the Microsoft.InternetInformationServices.2012.mp management pack (in the management pack catalog) and the Microsoft.SystemCenter.Apm.Web.IIS8.mp management pack.
My advice is to wait until the IIS Application Pools have been discovered and ASP.NET Web Applications start to appear in the ASP.NET Web Application Inventory view before you begin monitoring. You should see your Application Pool as “Healthy”.
Installation and Monitoring
In my lab I’ve deploy a WebApp with WPI (Web Platform Installer). I have one Front-end server with my application. If you have more than one server, you should create a group for your servers. Then, you will be able to apply the template to the group.
Step 1: Go in authoring and start the “.NET Application Performance Monitoring”
Step 2: Choose the right Monitoring type (the first step for me).
Step 3: Give a name and select a Management Pack (I’ve create a specific one for my application here).
Step 4: Select your Application and search for your group (or your server) to feed the bottom field.
Step 5: For Server Side Monitoring, adjust the performance event threshold if you need to. Here, I decided to gather data on the end user experience in the lab.
Step 6: For the Client side, I keep the default setting and do not exclude pages.
Now you have your resume. Next, click on Create. The last thing to do is restart the IIS on the Front-end to enable monitoring. By default you will have some reporting information, such as:
- Resources Utilization
- The raw performance data about the site can be seen at the URL: http://localhost/AppDiagnostics/ on the SCOM server.
- Graph for Performance data
- All of the available APM performance data can be viewed if you create a pivot view, filter on the "Operations Manager APM Library", and break this down by the available counters. This will be shown in a SCOM Performance Cube.
I would love to hear some feedback, so if you have any questions or opinions please feel free to comment below.
GSX Solutions is the leading provider of monitoring and reporting solutions for Unified Communications applications, whether on-premises or in the cloud. Find out more now >>