Chapter 15 – Monitoring Sharepoint 2010

Wrox Professional Sharepoint 2010 Administration (P. 411)

ULS (Unified Logging Service) – (1) trace logs (2) event viewer and (3) new reporting database.

ULS doesn’t take actions on the events occurred.

Trace Logs – (in SP 2010, they’re officially referred to as trace logs)
Location – c:\program Files\Common\Microsoft Sharted\Web Server Extensions\14\ (or called Sharepoint Root)

ULS log creation is 30 minutes apart by default. NTFS compression.

Event Throttling Central Admin Configure Diagnostic logging

Every time you can a setting, the setting will turn bold.

Trace log settings —

Powershell –

Use this to get a lit of farm configurations —

set number of days to keep the log:
Set-SPDiagnosticConfig –DaysToKeepLogs 30

New-SPLogFile tells SP to create a new trace file.
Merge-SPLogFile to merge all trace log files in your farm into a single file on the local computer.

Correlation ID’s — Uniq GUID’s that are assigned to each user conversation with Sharepoint. Correlation ID’s are persisted across different servers in the same farm. (the id is the same on multile servers)

Correlation ID is generated for every conversation, no error needed. To get a Correlation ID without an error, you need to enable the developer dashboard.

Enable develop dashboard:
(1) Run command windows as Admin
(2) CD to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\BIN
(3) stsadm -o setproperty -pn developer-dashboard -pv on

$dash = [Microsoft.SharePoint.Administration.SPWebService]::


$dash.DisplayLevel = ‘OnDemand’;

$dash.TraceEnabled = $true;

This is a FARM Setting – but only site collection administrator will see it.

Logging Database – a repository of Sharepoint events from every machine in your farm. It aggregates information from many different locations and write them all to a single database. (you can delete it and let SP re-create it)

Configure the Logging Database —

Central Admin Monitoring Health Data Collection (enabled by default)

Usage data logs – saved in the 14 Hive, next to Trace lOgs, file name *.usage.

Default logging database: WSS_Logging

I might make sense to move this DB to another SQL server. To change the DB in PowerShell —
Set-SPUsageApplication -DatabaseServer <Database server name> -DatabaseName
<Database name> [-DatabaseUsername <User name>] [-DatabasePassword <Password>] [-Verbose]

Central Admin Monitoring Reporting uses data from the Logging Database.

Health report – to identity the slowest page or user-active page. (Slowest Page & Most Active Users)

Web Analytics Report – also from logging database à Choose an application first, and then find out the total page view, visitors, etc. It provides functons similar to Webtrends!!!

To see the Web Analytics report for Central Admin, Site Actions à Site Settings, under Site Action, click [Site web analytics reports]

Health Analyzer – use time job to run rules to periodically check on system metrics.

Reviewing Problems – heath Analyzer (red bar when you go to Central Admin)

To see all warnings/problems, go to: Central Admin à Monitoring à Review Problems and Solutions

Use the button “Re-analyze Now” to re-analyze the problem. “Repair Automatically”,if presented, to repait the issue.

Rule Definitions —

Cenral Admin à Motoring à Review Rule Definitions

Timer Jobs —

Time Job management —

You can choose a server to run Timer Jobs on a specific Content Database:
Central Admin à Application Management à Manage Content Database.

Post a comment or leave a trackback: Trackback URL.

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: