25 February, 2014

How to monitor SharePoint – Part -2


If you have any queries / questions regarding the first part then please feel free to ask so that we can discuss and proceed further…

We are going to discuss the remaining sections today in descriptive manner-

Usage data and health data collection
 As we discussed, ULS, Event Viewer logs, SharePoint Health Analyzer are vital enough to provide the cause behind the issues but sometimes not everything gets captured inside these logs, example-

1.   Traffic Reports - How many hits a page got, how the user got there, and what browser they used to get there.
2.   Search Reports - What was searched for, top clicks, failed queries.
3.   Inventory Reports - What space is being used by whom, how many sites you have, what languages those sites use.

"Site usage reports" have been renamed as Web Analytics.

You can access Web Analytics reports by going to Site Actions -> Site Settings.  Under the Site Actions heading you will see two links, Site Web Analytics Reports and Site Collection Web Analytics Reports.

Inventory Reports:
The inventory reports are targeted to help the site administrators in managing the site by keeping track of the site structure and storage and version issues.

1.   How much disk space is being consumed?
2.   How many sites have been created?
3.   What languages are in use?

Developer Dashboard

Developer Dashboard is one of the clean and neat tools to troubleshoot performance issues. This functionality is disabled by default but pretty useful. With the help of developer dashboard (DD), we can easily recognize type of problem, either programmatically by using the object model or visually by looking at page output, critical events, database queries, service calls, and SharePoint requests allocation.

How to enable this:-
$svc=[Microsoft.SharePoint.Administration.SPWebService]::ContentService
$ddsetting=$svc.DeveloperDashboardSettings
$ddsetting.DisplayLevel=[Microsoft.SharePoint.Administration.SPDeveloperDashboardLevel]::OnDemand
$ddsetting.Update()

Best Practices on Memory Leak
Microsoft has created an awesome too to find out the memory leaks.


If you have any questions/queries then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

Product applies to:
a.    SharePoint Server 2010
b.    SharePoint Foundation 2010

References:
Capacity requirements for the Web Analytics Shared Service in SharePoint Server 2010: http://technet.microsoft.com/en-us/library/gg440601.aspx

Reporting and usage analysis overview (SharePoint Server 2010)

Web Analytics in SharePoint 2010: Insights into Reports and Metrics

No comments:

Post a Comment

Your feedback is always appreciated. I will try to reply to your queries as soon as possible- Amol Ghuge

Note: Only a member of this blog may post a comment.