6.3

Policies That vRealize Operations Manager Includes
All policies exist under the Base Seings, because the data adapters and solutions installed in your
vRealize Operations Manager instance provide a collective group of base seings that apply to all objects. In
the policy navigation tree on the Policy Library tab, these seings are called Base Seings.
The Base Seings policy is the umbrella policy for all other policies, and appears at the top of the policy list
in the policy library. All of the other policies reside under the Base Seings, because the data adapters and
solutions installed in your vRealize Operations Manager instance provide a collective group of base seings
that apply to all objects.
The Cong Wizard Based Policy set includes policies provided with vRealize Operations Manager that you
use for specic seings on objects to report on your objects. The Cong Wizard Based Policy set includes
several types of policies:
n
Capacity Management policies for Network I/O and Storage I/O
n
Eciency alerts policies for infrastructure objects and virtual machines
n
Health alerts policies for infrastructure objects and virtual machines
n
Overcommit policies for CPU and Memory
n
Risk alerts policies for infrastructure objects and virtual machines
The Default Policy includes a set of rules that applies to the majority of your objects.
The VMware Management Policies set includes policies that you use for your type of environment, such as
production as opposed to test and development. These policies contain seings that monitor for peak
periods, batch and interactive workloads, and demand and allocation models. The VMware Management
Policies set provided with vRealize Operations Manager include the following policies:
Table 3‑4. Functions of VMware Management Policies
VMware Management Policy What it does
VMware Excludes over-sized analysis Does not calculate reclaimable capacity from oversized
virtual machines
VMware Optimized for 15-minute peak periods Congured to cause capacity alerts for workloads that
spike for 15 minutes.
VMware Optimized for 30-minute peak periods Congured to cause capacity alerts for workloads that
spike for 30 minutes.
VMware Policy for Batch workloads Optimized for batch workloads that run less than four
hours.
VMware Policy for Interactive workloads Congured to be sensitive toward interactive workloads,
such as a desktop or Web server, based on 15-minute peaks
with large buers.
VMware Production Policy (Demand only) Optimized for production loads, without using allocation
limits, to obtain the most capacity.
VMware Production Policy (with Allocation) Optimized for production loads that require the demand
and allocation capacity models.
VMware Production Policy (without Allocation) Optimized for production loads that require demand
capacity models, and provides the highest overcommit
without contention.
VMware Test and Dev Policy (without Allocation). Optimized for Dev and Test environments to maximize
capacity without causing signicant contention, because it
does not include capacity planning at the virtual machine
level.
Chapter 3 Customizing How vRealize Operations Manager Monitors Your Environment
VMware, Inc. 85