Monitoring SharePoint 2010

Monitoring SharePoint 2010

Table of Contents
Monitoring SharePoint 2010 .................................................................................................. 1
Exercise 1 Define a Service Level Objective Against SharePoint Server ........................................................................2
Exercise 2 Service Level Dashboard ...............................................................................................................................4
Monitoring SharePoint 2010

Monitoring SharePoint 2010

Objectives
The objective of this lab is to provide a basic introduction to using Service Level
Monitoring to monitor services provided by SharePoint Server 2010.
By the end of this lab you will:
 Create a Service Level Object
 Generate a Report of SharePoint Services Availability
 Configure a Service Level Dashboard

Scenario
Organizations rely on the availability of collaborative infrastructure to enable
corporate collaboration, which is often governed by aggressive service level
agreements (SLAs). Organizations face challenges in providing continuous
availability of their globally distributed and business-critical collaborative
infrastructure. When any problems arise, organizations must have the expertise
to quickly trace the source of the problems and resolve them. Within these
organizations, administrators must meet these SLAs and ensure that
®
collaboration systems running Microsoft SharePoint 2010 are operating
reliably.

Estimated Time to 30 Minutes

Complete This Lab

Computers used in this

Lab DC

OpsMgr

Sharepoint

The password for the Administrator account on all computers in this lab is:
P@ssw0rd

Page 1 of 5
Monitoring SharePoint 2010

Exercise 1
Define a Service Level Objective Against SharePoint
Server

Scenario
In this scenario, you will see the importance of ensuring that resources, such as SharePoint Server services, are
available and performing at acceptable levels. Contoso Inc. has set goals for their service availability and
response times. Microsoft System Center Operations Manager 2007 R2 provides the capability to monitor these
service goals through service level tracking.
To ensure that SharePoint Server is available in System Center Operations Manager 2007 R2, we can define an
SLO that states that 99.6 percent of the servers must be continuously available. We can also generate reports
that show how SharePoint Server has performed against those goals. Using the information from these reports,
we can identify any shortfalls between the SLOs and the actual performance, enabling us to track the business
effects of these problems.

Tasks Detailed Steps

Complete the following a. If not restoring from a saved state, Start DC and allow it to reach the Log in screen
tasks on: before starting the rest of the virtual machines.
b. Log on to OpsMgr using the following credentials:
DC  User Name: Administrator
1. Start the Virtual  Password: P@ssw0rd
Machines  Domain: Contoso
Note: Ensure that your screen resolution is equal or greater than 1024 x 786. This will
give you a better view of the environment.
2. Create a Service a. Click Start | Administrative Tools | Services and start Operations Manager Audit
Level Objective Collection Service and System Canter Management
b. On the desktop, double-click Operations Console.
c. Open the Authoring pane.
d. Expand Management Pack Objects, and then click Service Level Tracking.
e. Click Create to create a new Service Level Tracking.
f. In the Name box, type SharePoint Server SLO; you may add an optional
description.
g. Click Next.
h. Click Select to select a class object to target.
i. In the Select a Target Class window, select SharePoint Service.
j. In the Management Pack dropdown, select the Microsoft SharePoint Foundation
2010 Beta management pack, and then click Next.
k. Click Add and then click Monitor state SLO.
l. In the Service level objective name box, type Availability Rule SLO.

Page 2 of 5
Monitoring SharePoint 2010
Tasks Detailed Steps
m. In the Monitor drop-down box, Select Availability.
n. In the Service Level Objective goal box, type 99.600.
o. Under Specify the states you want to be counted as downtime in this objective,
select all of the objectives and then click OK.
p. Click Next, and then click Finish.
q. Click Close to close the window when you have successfully created the SLO.
3. Generate the Report Note: The Service Level Tracking Summary Report compares the results for one or
more service levels to the defined target objectives. From this report, you can examine
a more detailed report, the State view, or the Service Level Agreement view.
a. In the Reporting view of the Operations console, click Microsoft Service Level
Report Library.
b. Double-click the Service Level Tracking Summary Report.
c. Click Add.
d. Click Search.
e. Under Available Items, select the SharePoint Server SLO and then click Add.
f. Click OK to close the Add Service Levels window.
g. In the Data Aggregation drop-down box, select Hourly.
h. In the From drop-down box, select Yesterday.
i. In the Time Zone drop-down box, select (UTC-8:00) Pacific Time (US & Canada).
j. On the right side of the screen, under Additional time intervals, select Last 24
Hours.
k. Click Run to generate the report.
l. Close the report window.
Note: Due to the fact that these machines have been off, there may not be any
populated data.

Page 3 of 5
Monitoring SharePoint 2010

Exercise 2
Service Level Dashboard

Scenario
Today’s IT organizations have myriad business applications. For most applications there is some type of service
level agreement (SLA) between the IT department and the departments IT serves. These SLAs govern conditions
such as outage response time and disk space availability. Because the collaborative infrastructure is typically a
critical part of an organization, the IT department must meet SLAs with optimal application availability and
performance.
To meet organizational needs, IT departments seek an integrated solution for tracking and reporting on the
Microsoft® SharePoint Server infrastructure. They need a model that allows IT administrators to define all
components of the SharePoint Server system and services that affect infrastructure health and the SLA calculation.
They also need a single point at which to measure the performance and availability of SharePoint services. IT staff
need to be able to quickly identify SharePoint Server performance or availability problems and possible causes.
Service Level Dashboard evaluates SharePoint Server over a selected period, determines whether it meets the
defined service level commitment, and displays summarized data.

Tasks Detailed Steps

Complete the following Note: A distributed application is made of distinct components that may have
tasks on: separate runtime environments. When you use a distributed application, you can set
rules to monitor the application and its individual components. SharePoint Server is a
distributed application because it contains a number of discrete components that may
OpsMgr run on different servers. To monitor a distributed application in Operations Manager
1. Create the you must first make it aware of the application.
Distributed a. In the Operations console, click Authoring.
Application
b. Right-click Distributed Applications, and then click Create a new distributed
application.
c. In the Name box, type SharePoint 2010 Service; you may enter an optional
description.
d. In the Template box, select Line of Business Web Application.
e. In the Management Pack list, select ContosoMP and then click OK.
f. Click Save.
g. Close the designer window.

2. Define a Service level Note: Service level objectives (SLOs) help to define availability and performance goals
Objective for an application. In the following procedure, you will create a new service level
objective for Microsoft SharePoint Services, to define availability and performance
according to the service level agreement.
a. In the Operations console, open the Authoring pane.
b. Expand Management Pack Objects and then click Service Level Tracking.
c. Click Create.

Page 4 of 5
Monitoring SharePoint 2010
Tasks Detailed Steps
d. For Name, type SharePointSLO and click Next.
e. Click Select to select a class of object to target.
f. For Targeted Class, click Select and select Web Service In SPService and then click
OK.
g. In the Select destination management pack list, select ContosoMP and then click
Next.
h. Click Add and select Monitor State SLO.
i. In the Service level objective name box, type Availability Rule SLO.
j. In the Monitor list, select Availability.
k. In the Service level objective goal box, enter 99.600.
l. For Specify the states you want to be counted as downtime in this objective,
select all of the checkboxes and click OK.
m. Click Next, and then click Finish.
n. After the service level objective is created successful, click Close.

3. Configure the Note: The Service Level Dashboard is an application built on Windows SharePoint
Dashboard Services 3.0. The dashboard is designed to work with an existing Operations Manager
2007 R2 infrastructure that is configured to monitor business-critical applications. The
dashboard evaluates an application or group over a period that the administrator
selects during setup, determines whether the defined service level commitment was
met, and displays summarized data about the service levels.
a. Open Internet Explorer, and in the address bar, type HTTP://OPSMGR:51918 to
open the Service Level Dashboard site.
b. Click Site Actions, and then click Edit Page.
c. In the Service Level Selection are, select the SharePointSLO check box.
d. In the Dashboard Refresh box, type 5.
e. In the Dashboard Default View list, select Last 24 Hours.
f. In the Aggregation Type list, select Hourly.
g. Click Apply Filter.
h. In the upper-right corner of the page, click Exit Edit Mode.
Note: Due to the fact that these machines have been off, there may not be any
populated data.

Page 5 of 5