6.3

Table Of Contents
4 In the Symptom Denitions pane, modify the critical Co-Stop level for virtual machines so that
vRealize Operations Manager triggers an alert based on the threshold level dened for this symptom.
a In the Object Type drop-down menu, click vCenter Adapter and Virtual Machine.
b In the Search text box, enter stop to display the symptom denitions that apply to the Co-Stop
performance metric for virtual machines.
c For the symptom denition named Virtual Machine CPU Co-stop is at Critical level, click the
State drop-down menu and click Enabled.
d Click the Condition drop-down menu, and click Override.
For a production policy, a typical critical threshold value is >3. For a development or test
environment policy, a typical critical threshold value is >10.
e In the Override Symptom Denition Threshold dialog box, enter >3 to change the threshold value,
and click Apply.
5 Modify the immediate Co-Stop level for virtual machines.
a For the symptom denition named Virtual Machine CPU Co-stop is at Immediate level, click
the State drop-down menu and click Enabled.
b Click the Condition drop-down menu, and click Override.
c In the Override Symptom Denition Threshold dialog box, enter >2 to change the threshold value,
and click Apply.
6 Modify the warning Co-Stop level for virtual machines.
a For the symptom denition named Virtual Machine CPU Co-stop is at Warning level, click the
State drop-down menu and click Enabled.
b Click the Condition drop-down menu, and click Override.
c In the Override Symptom Denition Threshold dialog box, enter >1 to change the threshold value,
and click Apply.
7 Click Save to save your policy.
You changed the Co-Stop CPU performance metric for virtual machines to minimize the delay on your SQL
Server virtual machines because of CPU scheduling contention.
What to do next
Create a group type to use to categorize your group of virtual SQL Servers, create an object group that
contains your virtual SQL Servers, and apply the policy to your object group.
Apply the Custom Policy to vSphere Object Groups
You create an object group type to categorize your virtual SQL Server machines. Then you create an object
group that contains your virtual SQL Server machines, and apply your custom policy to this group of SQL
Server virtual machine objects.
To have vRealize Operations Manager analyze your SQL Server machines according to the performance
criteria in your custom policy, you must apply the custom policy to your group of SQL Server objects.
For this scenario, you create a static object group that contains your SQL Server virtual machines. In your
own environment, you might need to create a dynamic object group so that vRealize Operations Manager
discovers new SQL Server instances that become available to analyze and report on.
Chapter 3 Customizing How vRealize Operations Manager Monitors Your Environment
VMware, Inc. 91