6.3

User Scenario: Create a Custom Operational Policy for a vSphere Production
Environment
As a system administrator of vRealize Operations Manager, you are responsible for ensuring that the objects
in your vSphere environment conform to specic policies. You must ensure that your objects have enough
memory and CPU to support your Test, Development, and Production environments.
Large IT environments might include four to six production environments that are organized according to
object types, with a minor policy applied to each area. These large environments typically include a default
policy, a single production policy that applies to the entire environment, and individual policies for
dedicated areas.
You typically apply a default policy to most of the objects in your environment. To have
vRealize Operations Manager monitor and analyze dedicated groups of objects, you create a separate policy
for each object group, and make only minor changes in the seings for that policy. For example, you might
apply a default operational policy for all of the objects in your vSphere production environment, but you
also need to closely track the health and risk of virtual SQL Server instances, including their capacity levels.
To have vRealize Operations Manager analyze only the virtual SQL Server instances, and to monitor them,
you create a separate, dedicated policy and apply that policy to that group of objects. The seings in the
policy that you create to monitor the virtual SQL Server instances diers only slightly from the main
production policy.
This scenario shows you how to use multiple policies to analyze and monitor specic objects, so that you
can manage them to ensure continuous operation. In this scenario, your vSphere production environment is
one part of your overall production environment. You must create a custom operational policy to monitor
the virtual SQL Server objects in your vSphere production environment.
Prerequisites
n
Understand the purpose of using a policy. See “Managing and Administering Policies for vRealize
Operations Manager,” on page 81.
n
Verify that your vRealize Operations Manager instance is working properly.
n
Verify that your vRealize Operations Manager instance includes the Default Policy and one or more
other policies. See “Default Policy in vRealize Operations Manager,” on page 83.
n
Understand the sections and elements in the policy, such as the aributes, alert and symptom
denitions, and how the policy inherits seings from the base policies that you select. See “Policy
Workspace in vRealize Operations Manager,” on page 102.
n
Understand the analysis seings in the policy, such as capacity remaining and stress on hosts and
virtual machines, and the actions used to override the seings inherited from the base policies. See the
vRealize Operations Manager Information Center.
Procedure
1 Determine the vSphere Operational Requirements on page 87
You must continuously monitor the capacity levels of your virtual SQL Server machines, and have
vRealize Operations Manager notify you about any degradation in the performance of these objects.
You want vRealize Operations Manager to notify you 60 days before these objects begin to experience
problems with their capacity levels.
2 Create a Policy to Meet vSphere Operational Needs on page 88
You will create an operational policy for your virtual SQL Server instances, where only these seings
dier from the main production policy. In this policy, you change the memory and CPU seings for
specic objects. You then congure vRealize Operations Manager to send alerts to you when the
performance degrades on your virtual SQL Servers.
vRealize Operations Manager Customization and Administration Guide
86 VMware, Inc.