How to monitor SharePoint – Part -2

This article in in continuation with the first part – 

http://sharepointknowledgebase.blogspot.com/2014/02/how-to-monitor-sharepoint-part-1.html

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.

More details- http://archive.msdn.microsoft.com/SPDisposeCheck

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)

http://technet.microsoft.com/en-us/library/gg266383.aspx

Web Analytics in SharePoint 2010: Insights into Reports and Metrics

http://blogs.msdn.com/b/ecm/archive/2010/05/03/web-analytics-in-sharepoint-2010-insights-into-reports-and-metrics.aspx

Available drive space is less than twice the value of physical memory. This is dangerous because it does not provide enough room for a full memory dump with continued operation

SharePoint Health Analyzer is a good feature or we call it as a revolution for SharePoint administrators as it helps you to detect the issues in your farm and keep the SharePoint up and working without any worries :)

It’s very important to take an immediate action in reference to the critical errors which are reflecting in the health analyzer.

Overview of SharePoint Health Analyzer

http://msdn.microsoft.com/en-us/library/ee534957(v=office.14).aspx

SharePoint Health Analyzer rules reference (SharePoint Foundation 2010)

http://technet.microsoft.com/en-us/library/ff686788(v=office.14).aspx

SharePoint Health Analyzer rules reference (SharePoint Server 2010)

http://technet.microsoft.com/en-us/library/ff686816(v=office.14).aspx

As per the error message, make sure that the mention drive is having enough space as per the Microsoft recommendations. If you are pretty sure that space is already there and still you are getting that error in the health analyzer then you need to follow the following theory which has been explained by MVP-PAUL STORK

This theory suggest- “the threshold is built into the code and can't be changed.  You can go into the configuration for the Health Analyzer and turn off that particular rule.  To do this go to Central Administration and navigate to Monitoring > Health Analyzer > Review Rule Definitions.  Then find the specific rule, edit it and disable it.  It will stop telling you that the disks are running out of space.  I'm also not sure that this rule only pertains to the drive where you have your log files, but the only thing you can do is disable the rule.  There is no way to edit it.”

What you can check to free up the space:

-       Check the log files which are stored on the drive – this consumes most of the space

-       Check the backup files which are present over there

-       Check the old deployment files which are present on the same drive

-       Check the software’s which has been used long way back and still using the same space

-       Check the misc stuff which we kept during any critical situations (example: any files, tools etc)

As per Microsoft MSFT- Rock Wang—“This rule checks disk space as a proportion of the RAM on the computer. When disk space is less than twice the RAM on the computer, the health rule triggers an error. When disk space is less than five times the RAM on the computer, the health rule triggers a warning. Accordingly, server computers with lots of RAM are more likely to experience a failure of this rule.”

Once you remove the unnecessary stuff or irrelevant data from the mention drive then click on “Reanalyze now” so that it will verify the error and shows the results immediately.

If you have any queries/questions regarding the above mentioned information then please let me know, Thank you…