Which SLO or SLOs should you add?

Your company has a private cloud that is managed by using a System Center 2012 Operations
Manager infrastructure.
You have a distributed application named App1. App1 has the following service level objectives
(SLOs):
At least 99.9 percent uptime
No more than 85 percent average CPU utilization
You need to add the SLOs that monitor the required information to Service Level Tracking.
Which SLO or SLOs should you add? (Each correct answer presents part of the solution. Choose all
that apply.)

Your company has a private cloud that is managed by using a System Center 2012 Operations
Manager infrastructure.
You have a distributed application named App1. App1 has the following service level objectives
(SLOs):
At least 99.9 percent uptime
No more than 85 percent average CPU utilization
You need to add the SLOs that monitor the required information to Service Level Tracking.
Which SLO or SLOs should you add? (Each correct answer presents part of the solution. Choose all
that apply.)

A.
Monitor state SLO – Availability

B.
Monitor state SLO – Security

C.
Collection rule SLO

D.
Monitor state SLO – Performance

E.
Monitor state SLO – Configuration

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

To define a service level objective for an application
Open the Operations console with an account that is a member of the Operations Manager
Administrators user role.
Click Authoring.
In the navigation pane, expand Management Pack Objects, and then click Service Level Tracking.
In the Tasks pane, click Create.
In the Service Level Tracking dialog box, type a name for the service level that you are defining. For
example, type LOB Application 1. Optionally, you can provide a description. Click Next.
On the Objects to Track page, under Targeted class, click Select.
In the Select a Target Class dialog box, select a class for the service level, such as Distributed
Application, from the list in the text box. You can search for a class by typing its name into the Look
For text box. Click OK to close the Select a Target dialog box.
You can use the Scope option to specify the scope for the service level. The default selection is to
use all objects of the targeted class.
Select the management pack that this service level will be saved in. You can use an existing
management pack or create a new one.
Click Next.
On the Service Level Objectives page, click Add, and then click Monitor state SLO to create a new
monitor.
This monitor will track the availability of the application.
Define the state monitor as follows:
In the Service level objective name text box, type a name for the service level objective. For this
scenario, type Availability.
From the Monitor drop-down list, choose the specific monitor that you want to use to measure the
objective. For this scenario, choose Availability.
Using the Service level objective goal (%) spin box, provide the numerical measure for your
objective. For example, select 99.990 to indicate that your goal is 99.99% availability.
You can refine what the monitor tracks to determine availability by selecting or clearing any of the
following state criteria:
Unplanned maintenance
Unmonitored
Monitoring unavailable
Monitor disabled
Planned maintenance
Warning
Click OK.
On the Service Level Objectives page, click Add, and then click Collection rule SLO to create a new
collection rule. This rule will track the performance of the application Define the performance
collection rule as follows:
In the Service level objective name: text box, type a name for the service level objective. For this
scenario, type Performance.
Under Targeted class, click Select to open the Select a Target Class dialog box. Specify the target
class for the rule from the list of targets in the text box. Note that this class must be contained in the
distributed application.
For this scenario, select the specific class the rule is targeted to, such as Windows Server 2008
Operating System.
Under Performance collection rule, click Select to open the Select a Rule dialog box. Specify the
performance collection rule to use. For this scenario, choose Collect Processor\\ % Processor Time
performance counter, and then click OK.
Using one of the Aggregation method options, choose one of the following:
Average
Min
Max

Use the Service level objective goal drop-down list to specify either Less than or More than, and
enter a value in the adjacent text box. For this scenario, choose Less Than and 80. This indicates that
the performance goal is to never exceed 80% processor time.
Click OK.
On the Service Level Objectives page, click Next.
On the Summary page, review the settings, and then click Finish.
When the Completion page appears, click Close.



Leave a Reply 0

Your email address will not be published. Required fields are marked *