6.3

Table Of Contents
n
How do you classify your logically dened workloads, such as production clusters, test or development
clusters, and clusters used for batch workloads? Or, do you include all clusters in a single workload?
n
How do you capture peak use times or spikes in system activity? In some cases, you might need to
reduce alerts so that they are meaningful when you apply policies.
When you have privileges applied to your user account through the roles assigned, you can create and
modify policies, and apply them to objects. For example:
n
Create a policy from an existing base policy, inherit the base policy seings, then override specic
seings to analyze and monitor your objects.
n
Use policies to analyze and monitor vCenter Server objects and non-vCenter Server objects.
n
Set custom thresholds for analysis seings on all object types to have vRealize Operations Manager
report on workload, anomalies, faults, capacity, stress, and so on.
n
Enable specic aributes for collection, including metrics, properties, and super metrics.
n
Enable or disable alert denitions and symptom denitions in your custom policy seings.
n
Apply the custom policy to object groups.
When you use an existing policy to create a custom policy, you override the policy seings to meet your own
needs. You set the allocation and demand, the overcommit ratios for CPU and memory, and the thresholds
for capacity risk and buers. To allocate and congure what your environment is actually using, you use the
allocation model and the demand model together. Depending on the type of environment you monitor, such
as a production environment versus a test or development environment, whether you over allocate at all
and by how much depends on the workloads and environment to which the policy applies. You might be
more conservative with the level of allocation in your test environment and less conservative in your
production environment.
vRealize Operations Manager applies policies in priority order, as they appear on the Active Policies tab.
When you establish the priority for your policies, vRealize Operations Manager applies the congured
seings in the policies according to the policy rank order to analyze and report on your objects. To change
the priority of a policy, you click and drag a policy row. The default policy is always kept at the boom of
the priority list, and the remaining list of active policies starts at priority 1, which indicates the highest
priority policy. When you assign an object to be a member of multiple object groups, and you assign a
dierent policy to each object group, vRealize Operations Manager associates the highest ranking policy
with that object.
Your policies are unique to your environment. Because policies direct vRealize Operations Manager to
monitor the objects in your environment, they are read-only and do not alter the state of your objects. For
this reason, you can override the policy seings to ne-tune them until vRealize Operations Manager
displays the results that are meaningful and that aect for your environment. For example, you can adjust
the capacity buer seings in your policy, and then view the data that appears in the dashboards to see the
eect of the policy seings.
Policies Provided with vRealize Operations Manager
vRealize Operations Manager includes sets of policies that you can use to monitor your environment, or as
the starting point to create your own policies.
Verify that you are familiar with the policies provided with vRealize Operations Manager so that you can
use them in your own environment, and to include seings in new policies that you create.
Where You Find the Policies Provided with vRealize Operations Manager Policies
Click Administration, click Policies, click the Policy Library tab. To see the policies provided with
vRealize Operations Manager, expand the Base Seings policy.
vRealize Operations Manager Customization and Administration Guide
84 VMware, Inc.