In this post, I will talk about my SharePoint Performance Dashboard Project. It has mainly two major types of reporting features, Part 1. CPU Monitor, Memory Monitor, Top Users of the farm, Top Site Collections in the farm and many more and Part 2. List of content database with the size – for each web application, per content database how many site collections are there and what is the quota of each site collection and how much is used out of it.
So this project was planned in two parts, 1. Server Performance Reporting 2. Farm Content Size Reporting
Considering the length of the information, I will divide each part into two posts, so lets start with Part 1. Server Performance Reporting
For this functionality, We wanted mainly five types of reporting
- CPU trend in SharePoint servers in the farm for last 10 days
- Memory trend in SharePoint servers in the farm for last 10 days
- Top users of the farm
- Top Site Collections of the farm
- Tools used for the access
To begin with, I did my initial research in SharePoint’s Usage and Health data collection functionality. I studied how this functionality is and what type of information it collects. For more information about this functionality, please refer to Configure usage and health data collection (SharePoint Server 2010)
In WSS_Logging database, we have various views available and it really contains very useful information, it’s the data source for our reporting in this part.
Also, I evaluated SharePoint Diagnostic Studio 2010 (SPDiag 3.0) (SharePoint Server 2010). Based on it and by checking the various views from WSS_logging database I could derive all the necessary SQL queries that are required to get various performance information about each server in the farm.
CPU Monitor :
Top Users of the farm
Top URL/Site Collection Requests
Information about the other reporting and how I did the UI part & packaging, I have covered in my next post.