Vrealize Operations Manager 75 Help

vRealize Operations
Manager 7.5 Help

20 NOV 2020
vRealize Operations Manager 7.5
vRealize Operations Manager 7.5 Help
You can find the most up-to-date technical documentation on the VMware website at:
https://docs.vmware.com/
VMware, Inc.
3401 Hillview Ave.
Palo Alto, CA 94304
www.vmware.com
©
Copyright 2020 VMware, Inc. All rights reserved. Copyright and trademark information.
VMware, Inc. 2
Contents
VMware vRealize Operations Manager 7.5 Help 9
1 About VMware vRealize Operations Manager 10
2 Planning 11
Reference Architecture 11
Best Practices for Deploying vRealize Operations Manager 11
Initial Considerations for Deploying vRealize Operations Manager 12
Scalability Considerations 14
High Availability Considerations 15
Adapter and Management Packs Considerations 16
Hardware Requirements for Analytic Nodes and Remote Collectors 17
Port Requirements for vRealize Operations Manager 18
Small Deployment Profile for vRealize Operations Manager 19
Medium Deployment Profile for vRealize Operations Manager 20
Large Deployment Profile for vRealize Operations Manager 22
Extra Large Deployment Profile for vRealize Operations Manager 24
Secure Configuration 28
vRealize Operations Manager Security Posture 28
Secure Deployment of vRealize Operations Manager 29
Secure Configuration of vRealize Operations Manager 30
Network Security and Secure Communication 59
Auditing and Logging on your vRealize Operations Manager System 70
3 Installing 72
About Installing 72
Workflow of vRealize Operations Manager Installation 72
Sizing the Cluster 74
Complexity of Your Environment 75
Cluster Nodes 77
About Remote Collector Nodes 78
About High Availability 79
Preparing for Installation 80
Requirements 80
Installing vRealize Operations Manager 85
Deployment of vRealize Operations Manager 85
Installation Types 87
Installing vRealize Operations Manager on VMware Cloud on AWS 94
VMware, Inc. 3
Resize your Cluster by Adding Nodes 98

Gathering More Data by Adding a Remote Collector Node 99
Adding High Availability 101
Cluster and Node Maintenance 102
Post-Installation Considerations 105
About Logging In 105
After You Log In 106
Secure the Console 107
Log in to a Remote Console Session 108
About New Installations 109
Upgrade, Backup and Restore 110
Obtain the Software Update PAK File 111
Create a Snapshot as Part of an Update 111
How To Preserve Customized Content 112
Back Up and Restore 113
Software Updates 113
Before Upgrading to vRealize Operations Manager 7.5 116
4 Configuring 121
Connecting to Data Sources 122
VMware vSphere Solution 123
vRealize Application Remote Collector 132
Application Monitoring 169
Log Insight 210
Business Management 215
vRealize Automation Solution 228
vSAN 235
End Point Operations Management Solution 240
Installing Optional Solutions 299
Configuring Alerts and Actions 309
All Alerts 309
Types of Alerts 313
Configuring Alerts 323
Viewing Actions 388
Configuring Policies 397
Policies 397
Operational Policies 404
Types of Policies 405
Using the Monitoring Policy Workspace to Create and Modify Operational Policies 408
Define Monitoring Goals for vRealize Operations Manager Solutions 426
Configuring Compliance 428
VMware, Inc. 4
Defining Compliance Standards 428

Analyzing Compliance Standards 437
Configuring Super Metrics 442
Create a Super Metric 443
Enhancing Your Super Metrics 446
Exporting and Importing a Super Metric 447
Super Metrics Tab 448
Configuring Objects 454
Object Discovery 454
Configuring Data Display 486
Widgets 486
Dashboards 626
Views 658
Reports 675
Configuring Administration Settings 686
License Keys 687
License Groups 688
Maintenance Schedules 690
Manage Maintenance Schedules 691
Managing Users and Access Control 691
Passwords and Certificates 726
Modifying Global Settings 736
Transfer Ownership of Dashboards and Report Schedules 741
Logs 741
Create a Support Bundle 743
Dynamic Thresholds 745
Adapter Redescribe 745
Customizing Icons 746
Allocate More Virtual Memory 749
About the Administration Interface 749
Cluster Status and Management 750
Logs 752
Support Bundles 753
Update the Reference Database for vRealize Operations Manager 754
Configuring and Using Workload Optimization 754
Configuring Workload Optimization 755
Using Workload Optimization 763
Workload Optimization Page 767
Rightsizing 771
Manage Optimization Schedules 774
Workload Automation Policy Settings 775
VMware, Inc. 5
View DRS Summary 775

Optimization Schedules 776
Optimize Placement 777
5 Monitoring Objects in Your Managed Environment 778

Enhanced Search Capability 778
What to Do When... 780
User Scenario: A User Calls with a Problem 780
User Scenario: An Alert Arrives in Your Inbox 785
User Scenario: You See Problems as You Monitor the State of Your Objects 794
Monitoring and Responding to Alerts 803
Monitoring Alerts 804
Monitoring and Responding to Problems 808
Evaluating Object Information Using Badge Alerts and the Summary Tab 809
Investigating Object Alerts 823
Evaluating Metric Information 830
Capacity Tab Overview 837
Using Troubleshooting Tools to Resolve Problems 839
Creating and Using Object Details 846
Examining Relationships in Your Environment 858
User Scenario: Investigate the Root Cause of a Problem by Using the Troubleshooting Tab
Options 859
Running Actions from vRealize Operations Manager 864
Run Actions from Toolbars in vRealize Operations Manager 864
Troubleshoot Actions in vRealize Operations Manager 891
Monitor Recent Task Status 894
Troubleshoot Failed Tasks 898
Viewing Your Inventory 906
Inventory Tab 906
6 Capacity Optimization for Your Managed Environment 907

Capacity Analytics 908
Example: Excluding VMs from Reclaim Action 912
What-If Analysis: Modeling Workload, Capacity, or Migration Planning 914
Example: Run a What-If Scenario 915
Example: Import Workload from an Existing VM Scenario 916
Allocation Model 918
Capacity Overview 918
Reclaim 921
Reclamation Settings 925
What-If Analysis - Workload 926
Add or Remove Workloads 928
VMware, Inc. 6
Select VMs 930

Advanced Configuration - Workload 931
What-If Analysis - Physical Infrastructure 931
Add or Remove Physical Infrastructure 933
What-If-Analysis - Migration Planning 934
Migration Planning 935
What-If-Analysis - Hyperconverged Infrastructure 937
Add HCI Nodes 937
Custom Profiles 938
Custom Profiles Details and Related Policies 938
Custom Profiles Add and Edit Workspace 939
Custom Data Centers in VMware vRealize Operations Manager 939
Custom Datacenters List 940
Custom Datacenters Add and Edit Workspace 941
7 Metric, Property, and Alert Definitions 942

Metric Definitions in vRealize Operations Manager 942
Metrics for vCenter Server Components 943
Operating System Metrics Collected by vRealize Application Remote Collector 1036
Application Service Metrics Collected by vRealize Application Remote Collector 1038
Calculated Metrics 1055
Self-Monitoring Metrics for vRealize Operations Manager 1066
vRealize Automation Metrics 1093
Metrics for vSAN 1098
Metrics for the Operating Systems and Remote Service Monitoring Plug-ins in End Point
Operations Management 1110
Alert Definitions in vRealize Operations Manager 1128
Cluster Compute Resource Alert Definitions 1129
Host System Alert Definitions 1134
vRealize Automation Alert Definitions 1148
vSAN Alert Definitions 1149
Alerts in the vSphere Web Client 1161
vSphere Distributed Port Group 1161
Virtual Machine Alert Definitions 1162
vSphere Distributed Switch Alert Definitions 1168
vCenter Server Alert Definitions 1169
Datastore Alert Definitions 1170
Data Center Alert Definitions 1176
Custom Data Center Alert Definitions 1177
Property Definitions in vRealize Operations Manager 1178
Properties for vCenter Server Components 1179
Self-Monitoring Properties for vRealize Operations Manager 1194
VMware, Inc. 7
Properties for vSAN 1196

Properties for vRealize Automation 1197
VMware, Inc. 8
VMware vRealize Operations Manager 7.5
Help
This documentation contains information for vRealize Operations Manager administrators, virtual
infrastructure administrators, and operations engineers who install, configure, and manage
objects in your environment.
You can find guidance on commonly performed management activities such as connecting to
data sources, configuring users and object groups, responding to alerts, troubleshooting
problems, planning capacity, and customizing how data is collected and displayed.
VMware, Inc. 9
About VMware vRealize
Operations Manager 1
With vRealize Operations Manager enterprise software, you can proactively identify and solve
emerging issues with predictive analysis and smart alerts, ensuring optimal performance and
availability of system resources - across physical, virtual, and cloud infrastructures.
vRealize Operations Manager gives you complete monitoring capability in one place, across
applications, storage, and network devices, with an open and extensible platform supported by
third-party management packs. In addition, vRealize Operations Manager increases efficiency by
streamlining key processes with preinstalled and customizable policies while retaining full control.
Using data collected from system resources (objects), vRealize Operations Manager identifies
issues in any monitored system component, often before the customer notices a problem.
vRealize Operations Manager also frequently suggests corrective actions you can take to fix the
problem right away. For more challenging problems, vRealize Operations Manager offers rich
analytical tools that allow you to review and manipulate object data to reveal hidden issues,
investigate complex technical problems, identify trends or drill down to gauge the health of a
single object.
VMware, Inc. 10
Planning
2
You plan your environment with recommendations for deployment and secure baseline for the
deployment of vRealize Operations Manager.
This chapter includes the following topics:
n Reference Architecture
n Secure Configuration
Reference Architecture
When planning your environment, consider these recommendations for deployment topology,
hardware requirements, and interoperability, and scalability.
Best Practices for Deploying vRealize Operations Manager

Implement all best practices when you deploy a production instance of vRealize Operations
Manager.
Analytics Nodes
Analytics nodes consist of a primary node, primary replica node, and data nodes.
Note The master node is now referred to as the primary node. The master replica node is now
referred to as the primary replica node.
n Deploy analytics nodes in the same vSphere Cluster.
n Deploy analytics nodes on storage of the same type.
n Depending on the size and performance requirements for analytics nodes, apply Storage DRS
Anti-Affinity rules to ensure that nodes are on separate datastores.
n Set Storage DRS to manual for all vRealize Operations Manager analytics nodes.
n If you deploy analytics nodes into a highly consolidated vSphere cluster, configure resource
reservation to ensure optimal performance. Ensure that the virtual CPU to physical CPU ratio
is not negatively impacting the performance of analytic nodes by validating CPU ready time
and CPU co-stop.
VMware, Inc. 11
n Analytics nodes have a high number of vCPUs to ensure performance of the analytics
computation that occurs on each node. Monitor CPU Ready time and CPU Co-Stop to ensure
that analytics nodes are not competing for CPU capacity.
If the sizing guideline provides several configurations for the same number of objects, use the
configuration which has the least number of nodes. For example, if the number of objects is 120,
000, configure the node size as 4 extra large nodes instead of 12 large nodes.
Management Packs and Adapters

Various management packs and adapters have specific configuration requirements. Ensure that
you are familiar with all prerequisites before you install a solution and configure the adapter
instance.
Deployment Formats
n Deploy vRealize Operations Manager with VMware virtual appliance.
Initial Considerations for Deploying vRealize Operations Manager

For the production instance of vRealize Operations Manager to function optimally, your
environment must conform to certain configurations. Review and familiarize yourself with these
configurations before you deploy a production instance of vRealize Operations Manager.
Sizing
vRealize Operations Manager supports up to 240,000 monitored resources spread across six
extra large analytic nodes.
Size your vRealize Operations Manager instance to ensure performance and support. For
more information about sizing, see the following KB article 2093783.
Environment
Deploy analytic nodes in the same vSphere cluster and use identical or similar hosts and
storage. If you cannot deploy analytic nodes in the same vSphere cluster, you must deploy
them in the same geographical location. vRealize Operations Manager does not support
deploying analytics nodes in multiple geographical locations.
Analytics nodes must be able to communicate with one another always. The following
vSphere events might disrupt connectivity.
n vMotion
n Storage vMotion
n High Availability (HA)
n Distributed Resource Scheduler (DRS)
VMware, Inc. 12
Due to a high level of traffic between analytics nodes, all analytics nodes should be located
on the same VLAN and IP subnet, and that VLAN is not stretched between data centers.
Latency between analytics nodes cannot exceed 5 milliseconds, and the bandwidth must be
equal to or higher than 1 GB per second. It is recommended that bandwidth be 10 GB per
second at minimum.
If you deploy analytics nodes in to a highly consolidated vSphere cluster, configure resource
reservations. A full analytics node, for example a large analytics node that monitors 10,000
resources, requires one virtual CPU to physical CPU. If you experience performance issues,
review the CPU ready and co-stop to determine if the virtual to physical CPU ratio is the
cause of the issues. For more information about how to troubleshoot VM performance and
interpret CPU performance metrics, see Troubleshooting a virtual machine that has stopped
responding: VMM and Guest CPU usage comparison (1017926).
You can deploy remote collectors behind a firewall. You cannot use NAT between remote
collectors and analytics nodes.
Multiple Data Centers
If vRealize Operations Manager is monitoring resources in additional data centers, you must
use remote collectors and deploy the remote collectors in the remote data centers. You
might need to modify the intervals at which the configured adapters on the remote collector
collect information depending on latency.
It is recommended that latency between sites is less than 200ms.
Certificates
A valid certificate signed by a trusted Certificate Authority, private, or public, is an important

component when you configure a production instance of vRealize Operations Manager.
Configure a Certificate Authority signed certificate against the system before you configure
End Point Operations Management agents.
You must include all analytics, remote collectors, and load balancer DNS names in the Subject
Alternative Names field of the certificate.
You can configure End Point Operations Management agents to trust the root or intermediate
certificate to avoid having to reconfigure all agents if the certificate on the analytics nodes
and remote collectors are modified. For more information about root and intermediate
certificates, see Specify the End Point Operations Management Agent Setup Properties.
Adapters
It is recommended that you configure adapters to remote collectors in the same data center
as the analytics cluster for large and extra large deployment profiles. Configuring adapters to
remote collectors improves performance by reducing load on the analytics node. As an
example, you might decide to configure an adapter to remote collectors if the total resources
on a given analytics node begins to degrade the node's performance. You might configure
the adapter to a large remote collector with the appropriate capacity.
VMware, Inc. 13
Configure adapters to remote collectors when the number of resources the adapters are
monitoring exceeds the capacity of the associated analytics node.
Authentication
You can use the Platform Services Controller for user authentication in vRealize Operations
Manager. For more information about deploying a highly available Platform Services
Controller instance, see VMware vCenter Server 6.0 Deployment Guide.
Load Balancer
For more information about load balancer configuration, see the vRealize Operations
Manager Load Balancing Guide.
Scalability Considerations
Configure your initial deployment of vRealize Operations Manager based on anticipated usage.
Analytics Nodes
Analytics nodes consist of a primary node, primary replica node, and data nodes.
For enterprise deployments of vRealize Operations Manager, deploy all nodes as large or
extra large deployments, depending on sizing requirements and your available resources.
Scaling Vertically by Adding Resources
If you deploy analytics nodes in a configuration other than large, you can reconfigure the
vCPU and memory. It is recommended to scale up the analytics nodes in the cluster before
scaling out the cluster with additional nodes. vRealize Operations Manager supports various
node sizes.
Table 2-1. Analytics Nodes Deployment Sizes

Node Size vCPU Memory
Extra small 2 8 GB
Small 4 16 GB
Medium 8 32 GB
Large 16 48 GB
Extra large 24 128 GB
Scaling Vertically -by Increasing Storage
You can increase storage independently of vCPU and Memory.
To maintain a supported configuration, data nodes deployed in the cluster must be the same
node size.
For more information about increasing storage, see the topic, Add Data Disk Space to a
vRealize Operations Manager vApp Node. You cannot modify the disks of virtual machines
that have a snapshot. You must remove all snapshots before you increase disk size.
VMware, Inc. 14
Scaling Horizontally (Adding nodes)
vRealize Operations Manager 6.7 supports up to 6 extra large analytic nodes in a cluster.
To maintain a supported configuration, analytics nodes deployed in the cluster must be the
same node size.
Remote Collectors
vRealize Operations Manager supports two sizes for remote collectors, standard and large.
The maximum number of resources is based on the aggregate resources that are collected
for all adapters on the remote collector. In large-scale vRealize Operations Manager
monitored environment, you might experience a slow responding UI, and metrics are slow to
be displayed. Determine the areas of the environment in which the latency is greater than 20
milliseconds and install a remote collector in those areas.
Table 2-2. Supported Remote Collector Sizes

Collector Size Resources End Point Operations Management Agents
Standard 6000 250
Large 32,000 2,000
For more information about sizing see the following KB article 2093783.
High Availability Considerations

High availability creates a replica for the vRealize Operations Manager primary node and protects
the analytics cluster against the loss of a node.
Cluster Management
Clusters consist of a primary node, and primary replica node.
When you enable High Availability, information is stored in two different analytics nodes
within the cluster which consist of a primary node, and primary replica node, or data nodes.
If either the primary node, and primary replica node is permanently lost, then you must
disable and re-enable high availability to reassign the primary role or replica role. This
process, which includes a hidden cluster rebalance, can take a long time.
Analytics Nodes
Analytics nodes consist of a primary node, and primary replica node and data nodes.
Enabling High Availability within vRealize Operations Manager is not a disaster recovery
solution. Enabling High Availability duplicates data in the system, and doubles the system's
compute and capacity requirements. When you enable high availability, you protect vRealize
Operations Manager from data loss in the event that a single node is lost. If two or more
nodes are lost, there may be permanent data loss.
VMware, Inc. 15
Deploy all analytics nodes to separate hosts to reduce the chance of data loss in the event
that a host fails. You can use DRS anti-affinity rules to ensure that VMs remain on separate
hosts.
Remote Collectors
In vRealize Operations Manager 6.1 and later, you can create a collector group. A collector
group is a collection of nodes (analytic nodes and remote collectors). You can assign
adapters to a collector group, rather than assigning an adapter to a single node.
If the node running the adapter fails, the adapter is automatically moved to another node in
the collector group.
Assign all normal adapters to collector groups, and not to individual nodes. Do not deploy
hybrid adapters in collector groups. For more information about adapters, see the
documentation for the specific adapters.
Adapter and Management Packs Considerations

Adapters and management packs have specific configuration considerations.
Normal Adapters
Normal adapters require one-way communication to the monitored endpoint. Deploy normal
adapters into collector groups, which are sized to handle failover.
Following is a sample list of adapters provided by VMware for vRealize Operations Manager.
Additional adapters can be found on the VMware Solutions Exchange website.
n VMware vSphere
n Management Pack for NSX for vSphere
n Management Pack for OpenStack
n Management Pack for Storage Devices
n Management Pack for Log Insight
Hybrid Adapters
Hybrid adapters require two-way communication between the adapter and the monitored
endpoint.
You must deploy hybrid adapters to a dedicated remote collector. Configure only one hybrid
adapter type for each remote collector. You cannot configure hybrid adapters as part of a
collector group. For example, two vRealize Operations for Published Applications adapters
can exist on the same node, and two vRealize Operations for Horizon adapters can exist on
the same node, but a vRealize Operations for Published Applications adapter and a vRealize
Operations for Horizon adapter cannot exist on the same node.
Several hybrid adapters are available for vRealize Operations Manager.
n vRealize Operations for Horizon adapter
VMware, Inc. 16
n vRealize Operations for Published Applications adapter
n Management Pack for vRealize Hyperic
End Point Operations Management Adapter
By default, End Point Operations Management adapters are installed on all data nodes. Large
and extra large analytic nodes can support 2,500 end point agents and large remote
collectors can support 2,000 per node. To reduce ingestion load on the cluster, you can point
End Point Operations Management adapters at remote collectors. Assign the dedicated
remote collectors to their own collector group, which helps the End Point Operations
Management adapter maintain the state of End Point Operations Management resources if a
node in the collector group fails.
To reduce the cost of reconfiguring the system, it is recommended that you install End Point
Operations Management agents against a DNS entry specific to End Point Operations
Management agents if you plan to scale the system beyond a single node.
Remote Collectors Behind a Load Balancer for End Point Operations

Management Agents
EP Ops Agents
LB epops
AIM Collectors Group
Remote Collector Remote Collector Remote Collector

epops-1 epops-2 epops-3
Hardware Requirements for Analytic Nodes and Remote Collectors

Analytics nodes and remote collectors have various hardware requirements for virtual machines
and physical machines.
The following table specifies the components to install on each server profile in your deployment,
and the required hardware specifications.
Table 2-3. Hardware Requirements for System Components

Storage
Server Roles Virtual CPU Memory CPU Requirements Requirements
Medium analytic 8 vCPU 32 GB 2.0 Ghz minimum, 1875 IOPS

node 2.4 Ghz
recommended
Large analytic node 16 vCPU 48 GB 2.0 Ghz minimum, 3750 IOPS

2.4 Ghz
recommended
VMware, Inc. 17
Table 2-3. Hardware Requirements for System Components (continued)

Storage
Server Roles Virtual CPU Memory CPU Requirements Requirements
Standard remote 2 vCPU 4 GB 2.0 Ghz minimum, N/A

collector 2.4 Ghz
recommended
Large remote 4 vCPU 16 GB 2.0 Ghz minimum, N/A

collector 2.4 Ghz
recommended
Storage requirements are based on the maximum supported resources for each node.
vRealize Operations Manager has a high CPU requirement. In general, the more physical CPU that
you assign to the analytics cluster, the better the performance. You must use a minimum of eight
physical CPU dual socket hosts.
Port Requirements for vRealize Operations Manager

vRealize Operations Manager has certain port requirements for its components. All ports
specified are default ports.
Port Requirements for vRealize Operations Manager
Ports Information for vRealize Operations Manager

Ports information for vRealize Operations Manager is available on Ports and Protocol.
VMware, Inc. 18
Small Deployment Profile for vRealize Operations Manager

The small deployment profile is intended for systems that manage up to 20,000 resources.
Virtual Appliance Name

The small deployment profile contains a single large analytics node, analytic-1.ra.local.
Deployment Profile Support

The small deployment profile supports the following configuration.
n 20,000 resources
n 2,500 End Point Operations Management agents
n Data retention for six months
n Additional Time Series Retention for 36 months
Additional DNS Entries

You can add additional DNS entries for your organization's future requirements. If you do not
expect your planned deployment to exceed a single node, you can configure End Point
Operations Management agents against the analytics nodes.
epops.ra.local -> analytic-1.ra.local
Certificate
The certificate must be signed by a Certificate Authority. The Subject Alternative Name contains
the following information.
n DNS Name = epops.refarch.local
n DNS Name = analytic-1.ra.local
This is an example of a small deployment profile.
Table 2-4. Adapter Properties

Collector Group Collector Adaptor Resources
DEFAULT analytic-1 A 2,000
DEFAULT analytic-1 B 4,000
DEFAULT analytic-1 C 2,000
DEFAULT analytic-1 D 3,000
VMware, Inc. 19
vRealize Operations Manager Small Deployment Profile Architecture
User EP Ops Agents
DNS epops
Analytic Node
analytic-1
A,B,C,D
Resources
Medium Deployment Profile for vRealize Operations Manager

The medium deployment profile is intended for systems that manage 68,000 resources, 34,000
of which are enabled for High Availability. In the medium deployment profile, adapters are
deployed on the analytics nodes by default. If you experience problems with data ingestion,
move these adapters to remote controllers.
Virtual Appliance Names

The medium deployment profile contains eight medium analytics nodes.
n analytic-1.ra.lcoal

The medium deployment profile supports the following configuration.
n 68,000 total resources, 34,000 enabled for HA
VMware, Inc. 20
Load Balanced Addresses

n analytics.ra.local
n epops.ra.local
Certificate
n DNS Name = analytic-1.ra.local
This is an example of a medium deployment profile.

Collector Group Collector Adaptor Resources
DEFAULT analytic-1 A 2,000
DEFAULT analytic-2 B 4,000
DEFAULT analytic-3 C 2,000
DEFAULT analytic-4 D 3,000
DEFAULT analytic-5 E 1,000
DEFAULT analytic-6 F 2,000
DEFAULT analytic-7 G 1,500
DEFAULT analytic-8 H 4,500
vRealize Operations Manager Medium Deployment Profile Architecture
User EP Ops Agents
LB analytics LB epops
Analytics Cluster
Analytic Node Analytic Node Analytic Node Analytic Node

analytic-1 analytic-2 analytic-3 analytic-4
A B C D

E F G H
Endpoint
VMware, Inc. 21
Large Deployment Profile for vRealize Operations Manager

The large deployment profile is intended for systems that manage 128,000 resources, 64,000 of
which are enabled with High Availability. All adapters are deployed to remote controllers in large
deployment profiles to offload CPU usage from the analytics cluster.

The large deployment profile contains eight large analytics nodes, large remote collectors for
adapters, and large remote collectors for End Point Operations Management agents.

The large deployment profile supports the following configuration.

n epops.ra.local
Certificate
n DNS Name = analytic.refarch.local
n DNS Name = analytic-1.ra.local to DNS Name = analytic-8.ra.local
n DNS Name = remote-1.ra.local to DNS Name = remote-N.ra.local
n DNS Name = epops-1.ra.lcoal to DNS Name = epops-N.ra.local
VMware, Inc. 22
This is an example of a large deployment profile.

End Point Operations
Collector Group Remote Collector Adapter Resources Management Agents
1 remote-1 A 5,000 N/A
1 remote-2 B 5,000 N/A
Total 10,000 N/A
2 remote-3 C 10,000 N/A
2 remote-4 D 5,000 N/A
2 remote-5 E 5,000 N/A
Total 20,000 N/A
AIM epops-1 epops 4,800 800
epops-2 epops 4,800 800
Total 9,600 1,600
If a remote collector is lost from these collector groups, you might have to manually rebalance
the adapters to comply with the limit of 32,000 resource for each remote collector.
The estimate of 9,600 resources uses six resources for each End Point Operations Management
agent.
VMware, Inc. 23
vRealize Operations Manager Large Deployment Profile Architecture
User EP Ops Agents
LB analytics LB epops
AIM Collectors Group
Remote Collector Remote Collector

epops-1 epops-2
Analytics Cluster


Collectors Group 1 Collectors Group 2
Remote Collector Remote Collector Remote Collector Remote Collector Remote Collector
remote-1 remote-2 remote-1 remote-2 remote-3
A B C D E
Collector Group 1 Collector Group 2

Endpoint Endpoint
Extra Large Deployment Profile for vRealize Operations Manager

The extra large deployment profile is intended for systems that manage 240,000 resources,
120,000 of which are enabled for High Availability. This deployment is divided into two data
centers and is the maximum supported analytics cluster deployment.

The extra large deployment profile contains six extra large analytics nodes, X large remote
collectors for adapters, and Y large remote collectors for End Point Operations Management
agents.
n analytic-1.ra.local
VMware, Inc. 24


n epops-a.ra.local
n epops-b.ra.local
Certificate
n DNS Name = analytic.refarch.local
n DNS Name = epops-a.refarch.local
n DNS Name = epops-b.refarch.local
n DNS Name = analytic-1.ra.local to analytic-16.ra.local
n DNS Name = remote-1.ra.local to remote-N.ra.local
n DNS Name = epops-1.ra.local to epops-N.ra.local
This is an example of an extra large deployment profile. The adapter in the example provides N-1
redundancy, meaning, if two adapters support 20,000 resources, then a third adapter is added
to attain a supported configuration that allows for a single failure.

End Point
Operations
Remote Management
Collector Group Data Center Collector Adapter Resources agents
1 A remote-1 A 5,000 N/A
1 A remote-2 B 5,000 N/A
Total 10,000
2 A remote-3 C 2,000 N/A
2 A remote-3 D 2,000 N/A
2 A remote-3 E 1,000 N/A
VMware, Inc. 25
Table 2-7. Adapter Properties (continued)

End Point
Operations
Remote Management
Collector Group Data Center Collector Adapter Resources agents
2 A remote-4 F 7,000 N/A
2 A remote-5 G 8,000 N/A
2 A remote-6 H 5,000 N/A
2 A remote-7 I 6,000 N/A
Total 31,000
3 B remote-8 J 10,000 N/A
3 B remote-9 K 5,000 N/A
3 B remote-10 L 5,000 N/A
Total 20,000
AIM-1 A epops-1 epops 8,004 1,334
AIM-1 A epops-2 epops 7,998 1,333
A epops-3 epops 7,998 1,333
Total 24,000 4,000
AIM-2 B epops-4 epops 8,004 1,334
Total 24,000 4,000
If a remote collector is lost from these collector groups, you might have to manually rebalance
the adapters to comply with the limit of 32,000 resource for each remote collector.
The estimate of 24,000 resources for AIM-1 and AIM-2 collector groups uses six resources for
each End Point Operations Management agent.
VMware, Inc. 26
vRealize Operations Manager Extra Large Deployment Profile Architecture -

Data Center A
Data Center A
User
EP Ops Agents
LB analytics LB epops-a
AIM-1 Collectors Group
Remote Remote Remote

Collector Collector Collector
epops-1 epops-2 epops-3
Analytic Cluster
Analytic Analytic Analytic Analytic Analytic Analytic

Node Node Node Node Node Node
analytic-1 analytic-2 analytic-3 analytic-4 analytic-5 analytic-6
Collectors Group 1 Collectors Group 2
Remote Remote Remote Remote Remote Remote

Collector Collector Collector Collector Collector Collector
remote -1 remote -2 remote -3 remote -4 remote -5 remote -6
A B C,D,E F G H
Remote
Collector
remote -7
I
Collector Group1 Collector Group2

Endpoint Endpoint
VMware, Inc. 27
vRealize Operations Manager Extra Large Deployment Profile Architecture -

Data Center B
Data Center B Collector Group 3

EP Ops Agents Endpoint
LB epops-b
Collectors Group 3
AIM-2 Collectors Group
Remote Collector Remote Collector
Remote Collector Remote Collector remote-8 remote-9
epops-4 epops-5 J K
Remote Collector
Remote Collector
remote-10
epops-6
L
200 ms latency
Data Center A
200 ms latency
Analytics Cluster
Secure Configuration
Ensure you meet the security requirements in your environment with the recommendations
provided.
vRealize Operations Manager Security Posture

The security posture of vRealize Operations Manager assumes a complete secure environment
based on system and network configuration, organizational security policies, and best practices.
It is important that you perform the hardening activities according to your organization's security
policies and best practices.
The document is broken down into the following sections:
n Secure Deployment
n Secure Configuration
n Network Security
n Communication
The guide details the installation of the Virtual Application.
To ensure that your system is securely hardened, review the recommendations and assess them
against your organization's security policies and risk exposure.
VMware, Inc. 28
Secure Deployment of vRealize Operations Manager

You must verify the integrity of the installation media before you install the product to ensure
authenticity of the downloaded files.
Verify the Integrity of Installation Media

After you download the media, use the MD5/SHA1 sum value to verify the integrity of the
download. Always verify the MD5/SHA1 hash after you download an ISO, offline bundle, or patch
to ensure the integrity and authenticity of the downloaded files. If you obtain physical media from
VMware and the security seal is broken, return the software to VMware for a replacement.
Procedure
u Compare the MD5/SHA1 hash output with the value posted on the VMware website.
SHA1 or MD5 hash should match.
Note The vRealize Operations Manager 6.x-x.pak/7.x-x.pak files are signed by the
VMware software publishing certificate. vRealize Operations Manager validates the signature
of the PAK file before installation.
Hardening the Deployed Software Infrastructure

As part of your hardening process, you must harden the deployed software infrastructure that
supports your VMware system.
Before you harden your VMware system, review and address security deficiencies in your
supporting software infrastructure to create a completely hardened and secure environment.
Software infrastructure elements to consider include operating system components, supporting
software, and database software. Address security concerns in these and other components
according to the manufacturer's recommendations and other relevant security protocols.
Hardening the VMware vSphere Environment

vRealize Operations Manager relies on a secure VMware vSphere environment to achieve the
greatest benefits and a secured infrastructure.
Assess the VMware vSphere environment and verify that the appropriate level of vSphere
hardening guidance is enforced and maintained.
For more guidance about hardening, see http://www.vmware.com/security/hardening-

guides.html.
Reviewing Installed and Unsupported Software

Vulnerabilities in unused software might increase the risk of unauthorized system access and
disruption of availability. Review the software that is installed on VMware host machines and
evaluate its use.
Do not install software that is not required for the secure operation of the system on any of the
vRealize Operations Manager node hosts. Uninstall unused or nonessential software.
VMware, Inc. 29
Installing unsupported, untested, or unapproved software on infrastructure products such as

vRealize Operations Manager is a threat to the infrastructure.
To minimize the threat to the infrastructure, do not install or use any third-party software that is
not supported by VMware on VMware supplied hosts.
Assess your vRealize Operations Manager deployment and inventory of installed products to
verify that no unsupported software is installed.
For more information about the support policies for third-party products, see the VMware
support at http://www.vmware.com/security/hardening-guides.html.
Verify Third-Party Software

Do not use third-party software that VMware does not support. Verify that all third-party
software is securely configured and patched in accordance with third-party vendor guidance.
Inauthentic, insecure, or unpatched vulnerabilities of third-party software installed on VMware

host machines might put the system at risk of unauthorized access and disruption of availability.
All software that VMware does not supply must be appropriately secured and patched.
If you must use third-party software that VMware does not support, consult the third-party
vendor for secure configuration and patching requirements.
VMware Security Advisories and Patches

VMware occasionally releases security advisories for products. Being aware of these advisories
can ensure that you have the safest underlying product and that the product is not vulnerable to
known threats.
Assess the vRealize Operations Manager installation, patching, and upgrade history and verify
that the released VMware Security Advisories are followed and enforced.
It is recommended that you always remain on the most recent vRealize Operations Manager
release, as this will include the most recent security fixes also.
For more information about the current VMware security advisories, see http://
www.vmware.com/security/advisories/.
Secure Configuration of vRealize Operations Manager

As a security best practice, you must secure the vRealize Operations Manager console and
manage Secure Shell (SSH), administrative accounts, and console access. Ensure that your
system is deployed with secure transmission channels.
You must also follow certain security best practices for running End Point Operations
Management agents.
Secure the vRealize Operations Manager Console

After you install vRealize Operations Manager, you must log in for the first time and secure the
console of each node in the cluster.
VMware, Inc. 30
Prerequisites
Install vRealize Operations Manager.
Procedure
1 Locate the node console in vCenter or by direct access.
In vCenter, press Alt+F1 to access the login prompt. For security reasons, vRealize Operations
Manager remote terminal sessions are disabled by default.
2 Log in as root.
vRealize Operations Manager does not allow you to access the command prompt until you
create a root password.
3 At the password prompt, press Enter.
4 At the old password prompt, press Enter.
5 At the prompt for a new password, enter the root password that you want and note it for
future reference.
6 Reenter the root password.
7 Log out of the console.
Change the Root Password

You can change the root password for any vRealize Operations Manager primary or data node at
any time by using the console.
The root user bypasses the pam_cracklib module password complexity check, which is found in
etc/pam.d/common-password. All hardened appliances enable enforce_for_root for the pw_history
module, found in the etc/pam.d/common-password file. The system remembers the last five
passwords by default. Old passwords are stored for each user in the /etc/security/opasswd file.
Prerequisites
Verify that the root password for the appliance meets your organization’s corporate password
complexity requirements. If the account password starts with $6$, it uses a sha512 hash. This is
the standard hash for all hardened appliances.
Procedure
1 Run the # passwd command at the root shell of the appliance.
2 To verify the hash of the root password, log in as root and run the # more /etc/shadow
command.
The hash information appears.
3 If the root password does not contain a sha512 hash, run the passwd command to change it.
VMware, Inc. 31
Manage Password Expiry

Configure all account password expirations in accordance with your organization's security
policies.
By default, all hardened VMware appliances use a 60-day password expiry. On most hardened
appliances, the root account is set to a 365-day password expiry. As a best practice, verify that
the expiry on all accounts meets security and operation requirements standards.
If the root password expires, you cannot reinstate it. You must implement site-specific policies to
prevent administrative and root passwords from expiring.
Procedure
1 Log in to your virtual appliance machines as root and run the # more /etc/shadow command to
verify the password expiry on all accounts.
2 To modify the expiry of the root account, run the # passwd -x 365 root command.
In this command, 365 specifies the number of days until password expiry. Use the same
command to modify any user, substituting the specific account for root and replacing the
number of days to meet the expiry standards of the organization.
By default, the root password is set for 365 days.
Managing Secure Shell, Administrative Accounts, and Console Access

For remote connections, all hardened appliances include the Secure Shell (SSH) protocol. SSH is
disabled by default on the hardened appliance.
SSH is an interactive command-line environment that supports remote connections to a vRealize

Operations Manager node. SSH requires high-privileged user account credentials. SSH activities
generally bypass the role-based access control (RBAC) and audit controls of the vRealize
Operations Manager node.
As a best practice, disable SSH in a production environment and enable it only to diagnose or
troubleshoot problems that you cannot resolve by other means. Leave it enabled only while
needed for a specific purpose and in accordance with your organization's security policies. If you
enable SSH, ensure that it is protected against attack and that you enable it only for as long as
required. Depending on your vSphere configuration, you can enable or disable SSH when you
deploy your Open Virtualization Format (OVF) template.
As a simple test to determine whether SSH is enabled on a machine, try to open a connection by
using SSH. If the connection opens and requests credentials, then SSH is enabled and is available
for making connections.
Secure Shell Root User

Because VMware appliances do not include preconfigured default user accounts, the root
account can use SSH to directly log in by default. Disable SSH as root as soon as possible.
VMware, Inc. 32
To meet the compliance standards for nonrepudiation, the SSH server on all hardened appliances
is preconfigured with the AllowGroups wheel entry to restrict SSH access to the secondary group
wheel. For separation of duties, you can modify the AllowGroups wheel entry in the /etc/ssh/
sshd_config file to use another group such as sshd.
The wheel group is enabled with the pam_wheel module for superuser access, so members of the
wheel group can use the su-root command, where the root password is required. Group
separation enables users to use SSH to the appliance, but not to use the su command to log in as
root. Do not remove or modify other entries in the AllowGroups field, which ensures proper
appliance function. After making a change, restart the SSH daemon by running the # service
sshd restart command.
Enable or Disable Secure Shell on a vRealize Operations Manager Node

You can enable Secure Shell (SSH) on a vRealize Operations Manager node for troubleshooting.
For example, to troubleshoot a server, you might require console access to the server through
SSH. Disable SSH on a vRealize Operations Manager node for normal operation.
Procedure
1 Access the console of the vRealize Operations Manager node from vCenter.
2 Press Alt + F1 to access the login prompt then log in.
3 Run the #chkconfig command.
4 If the sshd service is off, run the #chkconfig sshd on command.
5 Run the #service sshd start command to start the sshd service.
6 Run the #service sshd stop command to stop the sshd service.
You can also enable or disable Secure Shell from the SSH Status column of the vRealize
Operations Manager administration interface.
Create a Local Administrative Account for Secure Shell

You must create local administrative accounts that can be used as Secure Shell (SSH) and that
are members of the secondary wheel group, or both before you remove the root SSH access.
Before you disable direct root access, test that authorized administrators can access SSH by
using AllowGroups, and that they can use the wheel group and the su command to log in as root.
Procedure
1 Log in as root and run the following commands.
# useradd -d /home/vropsuser -g users -G wheel –m

# passwd username
Wheel is the group specified in AllowGroups for SSH access. To add multiple secondary
groups, use -G wheel,sshd.
VMware, Inc. 33
2 Switch to the user and provide a new password to ensure password complexity checking.
# su – username
username@hostname:~>passwd
If the password complexity is met, the password updates. If the password complexity is not
met, the password reverts to the original password, and you must rerun the password
command.
After you create the login accounts to allow SSH remote access and use the su command to
log in as root using the wheel access, you can remove the root account from the SSH direct
login.
3 To remove direct login to SSH, modify the /etc/ssh/sshd_config file by replacing

(#)PermitRootLogin yes with PermitRootLogin no.
What to do next
Disable direct logins as root. By default, the hardened appliances allow direct login to root
through the console. After you create administrative accounts for nonrepudiation and test them
for wheel access (su-root), disable direct root logins by editing the /etc/securetty file as root
and replacing the tty1 entry with console.
Restrict Secure Shell Access

As part of your system hardening process, restrict Secure Shell (SSH) access by configuring the
tcp_wrappers package appropriately on all VMware virtual appliance host machines. Also
maintain required SSH key file permissions on these appliances.
All VMware virtual appliances include the tcp_wrappers package to allow tcp-supported
daemons to control the network subnets that can access the libwrapped daemons. By default,
the /etc/hosts.allow file contains a generic entry, sshd: ALL : ALLOW, that allows all access to
the secure shell. Restrict this access as appropriate for your organization.
Procedure
1 Open the /etc/hosts.allow file on your virtual appliance host machine in a text editor.
2 Change the generic entry in your production environment to include only the local host
entries and the management network subnet for secure operations.
sshd:127.0.0.1 : ALLOW
sshd: [::1] : ALLOW
sshd: 10.0.0.0 :ALLOW
In this example, all local host connections and connections that the clients make on the
10.0.0.0 subnet are allowed.
3 Add all appropriate machine identification, for example, host name, IP address, fully qualified
domain name (FQDN), and loopback.
4 Save the file and close it.
VMware, Inc. 34
Maintain Secure Shell Key File Permissions

To maintain an appropriate level of security, configure Secure Shell (SSH) key file permissions.
Procedure
1 View the public host key files, located in /etc/ssh/*key.pub.
2 Verify that these files are owned by root, that the group is owned by root, and that the files
have permissions set to 0644.
The permissions are (-rw-r--r--).
3 Close all files.
4 View the private host key files, located in /etc/ssh/*key.
5 Verify that root owns these files and the group, and that the files have permissions set to
0600.
The permissions are (-rw-------).
6 Close all files.
Harden the Secure Shell Server Configuration

Where possible, the Virtual Application Installation (OVF) has a default hardened configuration.
Users can verify that their configuration is appropriately hardened by examining the server and
client service in the global options section of the configuration file.
If possible, restrict use of the SSH server to a management subnet in the /etc/hosts.allow file.
Procedure
1 Open the /etc/ssh/sshd_config server configuration file and verify that the settings are
correct.
Setting Status
Server Daemon Protocol Protocol 2
Ciphers Ciphers aes256-ctr, aes128-ctr
TCP Forwarding AllowTCPForwarding no
Server Gateway Ports Gateway Ports no
X11 Forwarding X11Forwarding no
SSH Service Use the AllowGroups field and specify a group permitted to access
and add members to the secondary group for users permitted to
use the service.
GSSAPI Authentication GSSAPIAuthentication no, if unused
Kerberos Authentication KerberosAuthentication no, if unused
Local Variables (AcceptEnv global option) Set to disabled by commenting out or enabled for only LC_* or
LANG variables
Tunnel Configuration PermitTunnel no
VMware, Inc. 35
Setting Status
Network Sessions MaxSessions 1
Strict Mode Checking Strict Modes yes
Privilege Separation UsePrivilegeSeparation yes
rhosts RSA Authentication RhostsRSAAuthentication no
Compression Compression delayed or Compression no
Message Authentication code MACs hmac-sha1
User Access Restriction PermitUserEnvironment no
2 Save your changes and close the file.
Harden the Secure Shell Client Configuration

As part of your system hardening monitoring process, verify hardening of the SSH client by
examining the SSH client configuration file on virtual appliance host machines to ensure that it is
configured according to VMware guidelines.
Procedure
1 Open the SSH client configuration file, /etc/ssh/ssh_config, and verify that the settings in
the global options section are correct.
Setting Status
Client Protocol Protocol 2
Client Gateway Ports Gateway Ports no
GSSAPI Authentication GSSAPIAuthentication no
Local Variables (SendEnv global Provide only LC_* or LANG variables

option)
CBC Ciphers Ciphers aes256-ctr,aes128-ctr
Message Authentication Codes Used in the MACs hmac-sha1 entry only
2 Save your changes and close the file.
Disable Direct Logins as Root

By default, the hardened appliances allow you to use the console to log in directly as root. As a
security best practice, you can disable direct logins after you create an administrative account
for nonrepudiation and test it for wheel access by using the su-root command.
Prerequisites
n Complete the steps in the topic called Create a Local Administrative Account for Secure Shell.
n Verify that you have tested accessing the system as an administrator before you disable
direct root logins.
VMware, Inc. 36
Procedure
1 Log in as root and navigate to the /etc/securetty file.
You can access this file from the command prompt.
2 Replace the tty1 entry with console.
Disable SSH Access for the Admin User Account

As a security best practice, you can disable SSH access for the admin user account. The vRealize
Operations Manager admin account and the Linux admin account share the same password.
Disabling SSH access to the admin user enforces defense in depth by ensuring all users of SSH
first login to a lesser privileged service account with a password that differs from the vRealize
Operations Manager admin account and then switch user to a higher privilege such as the admin
or root.
Procedure
1 Edit the /etc/ssh/sshd_config file.
You can access this file from the command prompt.
2 Add the DenyUsers admin entry anywhere in the file and save the file.
3 To restart the sshd server, run the service sshd restart command.
Set Boot Loader Authentication

To provide an appropriate level of security, configure boot loader authentication on your
VMware virtual appliances. If the system boot loader requires no authentication, users with
console access to the system might be able to alter the system boot configuration or boot the
system to single user or maintenance mode, which can result in denial of service or unauthorized
system access.
Because boot loader authentication is not set by default on the VMware virtual appliances, you
must create a GRUB password to configure it.
Procedure
1 Verify whether a boot password exists by locating the password --md5 <password-hash> line in
the /boot/grub/menu.lst file on your virtual appliances.
2 If no password exists, run the # /usr/sbin/grub-md5-crypt command on your virtual appliance.
An MD5 password is generated, and the command supplies the md5 hash output.
3 Append the password to the menu.lst file by running the # password --md5 <hash from grub-
md5-crypt> command.
VMware, Inc. 37
Single-User or Maintenance Mode Authentication

If the system does not require valid root authentication before it boots into single-user or
maintenance mode, anyone who invokes single-user or maintenance mode is granted privileged
access to all files on the system.
Procedure
u Review the/etc/inittab file and ensure that the following two lines appear: ls:S:wait:/etc/
init.d/rc S and ~~:S:respawn:/sbin/sulogin.
Monitor Minimal Necessary User Accounts

You must monitor existing user accounts and ensure that any unnecessary user accounts are
removed.
Procedure
u Run the host:~ # cat /etc/passwd command and verify the minimal necessary user accounts:
bin:x:1:1:bin:/bin:/bin/bash
daemon:x:2:2:Daemon:/sbin:/bin/bash
haldaemon:x:101:102:User for haldaemon:/var/run/hald:/bin/false
mail:x:8:12:Mailer daemon:/var/spool/clientmqueue:/bin/false
man:x:13:62:Manual pages viewer:/var/cache/man:/bin/bash
messagebus:x:100:101:User for D-Bus:/var/run/dbus:/bin/false
nobody:x:65534:65533:nobody:/var/lib/nobody:/bin/bash
ntp:x:74:106:NTP daemon:/var/lib/ntp:/bin/false
polkituser:x:103:104:PolicyKit:/var/run/PolicyKit:/bin/false
postfix:x:51:51:Postfix Daemon:/var/spool/postfix:/bin/false
root:x:0:0:root:/root:/bin/bash
sshd:x:71:65:SSH daemon:/var/lib/sshd:/bin/false
suse-ncc:x:104:107:Novell Customer Center User:/var/lib/YaST2/suse-ncc-fakehome:/bin/bash
uuidd:x:102:103:User for uuidd:/var/run/uuidd:/bin/false
wwwrun:x:30:8:WWW daemon apache:/var/lib/wwwrun:/bin/false
admin:x:1000:1003::/home/admin:/bin/bash
postgres:x:1002:100::/var/vmware/vpostgres/9.3:/bin/bash
Monitor Minimal Necessary Groups

You must monitor existing groups and members to ensure that any unnecessary groups or group
access is removed.
Procedure
u Run the <host>:~ # cat /etc/group command to verify the minimum necessary groups and
group membership.
audio:x:17:
bin:x:1:daemon
cdrom:x:20:
console:x:21:
daemon:x:2:
dialout:x:16:u1,tcserver,postgres
VMware, Inc. 38
disk:x:6:
floppy:x:19:
haldaemon:!:102:
kmem:x:9:
mail:x:12:
man:x:62:
messagebus:!:101:
modem:x:43:
nobody:x:65533:
nogroup:x:65534:nobody
ntp:!:106:
polkituser:!:105:
public:x:32:
root:x:0:admin
shadow:x:15:
sshd:!:65:
suse-ncc:!:107:
sys:x:3:
tape:!:103:
trusted:x:42:
tty:x:5:
utmp:x:22:
uuidd:!:104:
video:x:33:u1,tcserver,postgres
wheel:x:10:root,admin
www:x:8:
xok:x:41:
maildrop:!:1001:
postfix:!:51:
users:x:100:
vami:!:1002:root
nginx:!:108:
admin:!:1003:
Resetting the vRealize Operations Manager Administrator Password (Linux)

As a security best practice, you can reset the vRealize Operations Manager password on Linux
clusters for vApp or Linux installations.
Procedure
1 Log in to the remote console of the primary node as root.
2 Enter the $VMWARE_PYTHON_BIN $VCOPS_BASE/../vmware-vcopssuite/utilities/

sliceConfiguration/bin/vcopsSetAdminPassword.py --reset command and follow the prompts.
Configure NTP on VMware Appliances

For critical time sourcing, disable host time synchronization and use the Network Time Protocol
(NTP) on VMware appliances. You must configure a trusted remote NTP server for time
synchronization. The NTP server must be an authoritative time server or at least synchronized
with an authoritative time server.
VMware, Inc. 39
The NTP daemon on VMware virtual appliances provides synchronized time services. NTP is
disabled by default, so you need to configure it manually. If possible, use NTP in production
environments to track user actions and to detect potential malicious attacks and intrusions
through accurate audit and log keeping. For information about NTP security notices, see the NTP
Web site.
The NTP configuration file is located in the /etc/ntp.conf file on each appliance.
Procedure
1 Navigate to the /etc/ntp.conf configuration file on your virtual appliance host machine.
2 Set the file ownership to root:root.
3 Set the permissions to 0640.
4 To mitigate the risk of a denial-of-service amplification attack on the NTP service, open
the /etc/ntp.conf file and ensure that the restrict lines appear in the file.
restrict default kod nomodify notrap nopeer noquery

restrict -6 default kod nomodify notrap nopeer noquery
restrict 127.0.0.1
restrict -6 ::1
5 Save any changes and close the files.
For information on NTP security notices, see http://support.ntp.org/bin/view/Main/

SecurityNotice.
Disable the TCP Timestamp Response on Linux

Use the TCP timestamp response to approximate the remote host's uptime and aid in further
attacks. Additionally, some operating systems can be fingerprinted based on the behavior of
their TCP time stamps.
Procedure
u Disable the TCP timestamp response on Linux.
a To set the value of net.ipv4.tcp_timestamps to 0, run the sysctl -w

net.ipv4.tcp_timestamps=0 command.
b Add the ipv4.tcp_timestamps=0 value in the default sysctl.conf file.
Enable FIPS 140-2 Mode

The version of OpenSSL that is shipped with vRealize Operations Manager 6.3 and later releases
is FIPS 140-2 certified. However, the FIPS mode is not enabled by default.
You can enable the FIPS mode if there is a security compliance requirement to use FIPS certified
cryptographic algorithms with the FIPS mode enabled.
VMware, Inc. 40
Procedure
1 To replace the mod_ssl.so file run the following command:
cd /usr/lib64/apache2-prefork/
cp mod_ssl.so mod_ssl.so.old
cp mod_ssl.so.FIPSON.openssl1.0.2 mod_ssl.so
2 Modify your Apache2 configuration by editing the /etc/apache2/ssl-global.conf file.
3 Search for the <IfModule mod_ssl.c> line and add the SSLFIPS on directive below it.
4 To reset the Apache configuration, run the service apache2 restart command.
TLS for Data in Transit

As a security best practice, ensure that the system is deployed with secure transmission
channels.
Configure Strong Protocols for vRealize Operations Manager

Protocols such as SSLv2 and SSLv3 are no longer considered secure. In addition, TLS 1.0 and TLS
1.1 have also been disabled and only TLS 1.2 is enabled by default.
Note When you upgrade your vRealize Operations Manager instance to the 7.5 version, both
TLS 1.0 and TLS 1.1 are disabled on all vRealize Operations Manager nodes. TLS 1.2 is the only
protocol that is supported by default. However, if you want to lower the security bar and enable
TLS 1.0 and 1.1, see the following KB article 67108.
Verify the Correct Use of Protocols in Apache HTTPD

vRealize Operations Manager disables SSLv2, SSLv3, TLSv1, and TLSv1.1 by default. You must
disable weak protocols on all load balancers before you put the system into production.
Procedure
1 Run the grep SSLProtocol /usr/lib/vmware-vcopssuite/utilities/conf/vcops-

apache.conf | grep -v '#' command from the command prompt to verify that SSLv2,
SSLv3, TLSv1, and TLSv1.1 are disabled.
If the protocols are disabled, the command returns the following output: SSLProtocol All -
SSLv2 -SSLv3 -TLSv1 -TLSv1.1.
2 To restart the Apache2 server, run the /etc/init.d/apache2 restart command from the
command prompt.
Verify the Correct Use of Protocols in the GemFire TLS Handler
vRealize Operations Manager disables SSLv3, TLS 1.0, and TLS 1.1 by default. You must disable
weak protocols on all load balancers before you put the system into production.
VMware, Inc. 41
Procedure
1 Verify that the protocols are enabled. To verify that the protocols are enabled, run the
following commands on each node:
grep cluster-ssl-protocol /usr/lib/vmware-vcops/user/conf/gemfire.properties | grep -v '#'
The following result is expected:
cluster-ssl-protocols=TLSv1.2
grep cluster-ssl-protocol /usr/lib/vmware-vcops/user/conf/gemfire.native.properties | grep -v '#'
grep cluster-ssl-protocol /usr/lib/vmware-vcops/user/conf/gemfire.locator.properties | grep -v '#'
2 Re-enable TLS 1.0 and TLS 1.1.
a Navigate to the administrator user interface to bring the cluster offline: url/admin.
b Click Bring Offline.
c To ensure that TLS 1.0 and TLS 1.1 are enabled, run the following commands:
sed -i "/^[^#]*cluster-ssl-protocol/ c\cluster-ssl-protocols=TLSv1.2 TLSv1.1

TLSv1" /usr/lib/vmware-vcops/user/conf/gemfire.properties
TLSv1" /usr/lib/vmware-vcops/user/conf/gemfire.native.properties
TLSv1" /usr/lib/vmware-vcops/user/conf/gemfire.locator.properties
Repeat this step for each node.
d Navigate to the administrator user interface to bring the cluster online.
e Click Bring Online.
Configure vRealize Operations Manager to Use Strong Ciphers

For maximum security, you must configure vRealize Operations Manager components to use
strong ciphers. To ensure that only strong ciphers are selected, disable the use of weak ciphers.
Configure the server to support only strong ciphers and to use sufficiently large key sizes. Also,
configure the ciphers in a suitable order.
vRealize Operations Manager disables the use of cipher suites using the DHE key exchange by
default. Ensure that you disable the same weak cipher suites on all load balancers before you put
the system into production.
VMware, Inc. 42
Using Strong Ciphers

The encryption cipher negotiated between the server and the browser determines the key
exchange method and encryption strength that is used in a TLS session.
Verify the Correct Use of Cipher Suites in Apache HTTPD
For maximum security, verify the correct use of cipher suites in Apache httpd.
Procedure
1 To verify the correct use of cipher suites in Apache httpd, run the grep
SSLCipherSuite /usr/lib/vmware-vcopssuite/utilities/conf/vcops-apache.conf | grep
-v '#' command from the command prompt.
If Apache httpd uses the correct cipher suites, the command returns the following output:
SSLCipherSuite HIGH:!aNULL!ADH:!EXP:!MD5:!3DES:!CAMELLIA:!PSK:!SRP:!DH:@STRENGTH
2 To configure the correct use of cipher suites, run the sed -i "/^[^#]*SSLCipherSuite/ c
\SSLCipherSuite HIGH:\!aNULL\!ADH:\!EXP:\!MD5:\!3DES:\!CAMELLIA:\!PSK:\!SRP:\!
DH:@STRENGTH" /usr/lib/vmware-vcopssuite/utilities/conf/vcops-apache.conf
command from the command prompt.
Run this command if the output in Step 1 is not as expected.

This command disables all cipher suites that use DH and DHE key exchange methods.
3 Run the /etc/init.d/apache2 restart command from the command prompt to restart the
Apache2 server.
4 To reenable DH, remove !DH from the cipher suites by running the sed -i "/
^[^#]*SSLCipherSuite/ c\SSLCipherSuite HIGH:\!aNULL\!ADH:\!EXP:\!MD5:\!3DES:\!
CAMELLIA:\!PSK:\!SRP:@STRENGTH" /usr/lib/vmware-vcopssuite/utilities/conf/vcops-
apache.conf command from the command prompt.
5 Run the /etc/init.d/apache2 restart command from the command prompt to restart the
Apache2 server.
Verify the Correct Use of Cipher Suites in GemFire TLS Handler
For maximum security, verify the correct use of cipher suites in GemFire TLS Handler.
Procedure
1 To verify that the cipher suites are enabled, run the following commands on each node to
verify that the protocols are enabled:
grep cluster-ssl-ciphers /usr/lib/vmware-vcops/user/conf/gemfire.properties |

grep -v '#'
grep cluster-ssl-ciphers /usr/lib/vmware-vcops/user/conf/
gemfire.native.properties | grep -v '#'
grep cluster-ssl-ciphers /usr/lib/vmware-vcops/user/conf/
gemfire.locator.properties | grep -v '#'
VMware, Inc. 43
2 Configure the correct cipher suites.
a Navigate to the administrator user interface at URL/admin.
b To bring the cluster offline, click Bring Offline.
c To configure the correct cipher suites, run the following commands:
sed -i "/^[^#]*cluster-ssl-ciphers/ c\cluster-ssl-

ciphers=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384" /usr/lib/vmware-vcops/user/conf/
gemfire.properties
gemfire.native.properties
gemfire.locator.properties
Repeat this step for each node.
d Navigate to the administrator user interface at URL/admin.
e Click Bring Online.
Enabling TLS on Localhost Connections

By default, the localhost connections to the PostgreSQL database do not use TLS. To enable TLS,
you have to either generate a self-signed certificate with OpenSSL or provide your own
certificate.
To enable TLS on localhost connections to PostgreSQL, complete the following steps:
1 Generate or Provide Your Own Self-Signed Certificate with OpenSSL
2 Install the Certificate for PostgreSQL
3 Enable TLS on PostgreSQL
Generate or Provide Your Own Self-Signed Certificate with OpenSSL

Localhost connections to the PostgreSQL database do not use TLS. To enable TLS, you can
generate your own self-signed certificate with OpenSSL or provide your own certificate.
n To generate a self-signed certificate with OpenSSL, run the following commands:
openssl req -new -text -out cert.req

openssl rsa -in privkey.pem -out cert.pem
openssl req -x509 -in cert.req -text -key cert.pem -out cert.cert
VMware, Inc. 44
n To provide your own certificate, complete the following steps:
n Modify the ownership of the CAcerts.crt file to postgres.
n Edit the postgresql.conf file to include the directive ssl_ca_file = 'CAcerts.crt.
If you are using a certificate with a CA chain, you must add a CAcerts.crt file containing
the intermediate and root CA certificates to the same directory.
Install the Certificate for PostgreSQL

You must install the certificate for PostgreSQL when you enable TLS on localhost connections to
PostgreSQL.
Procedure
1 Copy the cert.pem file to /storage/db/vcops/vpostgres/data/server.key.
2 Copy the cert.cert file to /storage/db/vcops/vpostgres/data/server.crt.
3 Run the chmod 600 /storage/db/vcops/vpostgres/data/server.key command.
4 Run the chmod 600 /storage/db/vcops/vpostgres/data/server.crt command.
5 Run the chown postgres /storage/db/vcops/vpostgres/data/server.key and chown

postgres /storage/db/vcops/vpostgres/data/server.crt commands to change the
ownership of the server.crt and server.key files from root to postgres.
Enable TLS on PostgreSQL

You must edit the postgresql.conf file to enable TLS on localhost connections to PostgreSQL.
Procedure
u Edit the postgresql.conf file at /storage/db/vcops/vpostgres/data/ and make the

following changes:
a Set ssl = on.
b Set ssl_cert_file = 'server.crt'.
c Set ssl_key_file = 'server.key'.
Application Resources That Must be Protected

As a security best practice, ensure that the application resources are protected.
Follow the steps to ensure that the application resources are protected.
VMware, Inc. 45
Procedure
1 Run the Find / -path /proc -prune -o -type f -perm +6000 -ls command to verify that
the files have a well-defined SUID and GUID bits set.
The following list appears:
354131 24 -rwsr-xr-x 1 polkituser root 23176 /usr/lib/PolicyKit/polkit-set-default-helper

354126 20 -rwxr-sr-x 1 root polkituser 19208 /usr/lib/PolicyKit/polkit-grant-helper
354125 20 -rwxr-sr-x 1 root polkituser 19008 /usr/lib/PolicyKit/polkit-explicit-grant-
helper
354130 24 -rwxr-sr-x 1 root polkituser 23160 /usr/lib/PolicyKit/polkit-revoke-helper
354127 12 -rwsr-x--- 1 root polkituser 10744 /usr/lib/PolicyKit/polkit-grant-helper-pam
354128 16 -rwxr-sr-x 1 root polkituser 14856 /usr/lib/PolicyKit/polkit-read-auth-helper
73886 84 -rwsr-xr-x 1 root shadow 77848 /usr/bin/chsh
73888 88 -rwsr-xr-x 1 root shadow 85952 /usr/bin/gpasswd
73887 20 -rwsr-xr-x 1 root shadow 19320 /usr/bin/expiry
73890 84 -rwsr-xr-x 1 root root 81856 /usr/bin/passwd
73799 240 -rwsr-xr-x 1 root root 238488 /usr/bin/sudo
73889 20 -rwsr-xr-x 1 root root 19416 /usr/bin/newgrp
73884 92 -rwsr-xr-x 1 root shadow 86200 /usr/bin/chage
73885 88 -rwsr-xr-x 1 root shadow 82472 /usr/bin/chfn
73916 40 -rwsr-x--- 1 root trusted 40432 /usr/bin/crontab
296275 28 -rwsr-xr-x 1 root root 26945 /usr/lib64/pt_chown
353804 816 -r-xr-sr-x 1 root mail 829672 /usr/sbin/sendmail
278545 36 -rwsr-xr-x 1 root root 35792 /bin/ping6
278585 40 -rwsr-xr-x 1 root root 40016 /bin/su
278544 40 -rwsr-xr-x 1 root root 40048 /bin/ping
278638 72 -rwsr-xr-x 1 root root 69240 /bin/umount
278637 100 -rwsr-xr-x 1 root root 94808 /bin/mount
475333 48 -rwsr-x--- 1 root messagebus 47912 /lib64/dbus-1/dbus-daemon-launch-helper
41001 36 -rwsr-xr-x 1 root shadow 35688 /sbin/unix_chkpwd
41118 12 -rwsr-xr-x 1 root shadow 10736 /sbin/unix2_chkpwd
2 Run the find / -path */proc -prune -o -nouser -o -nogroup command to verify that all
the files in the vApp have an owner.
All the files have an owner if there are no results.
3 Run the find / -name "*.*" -type f -perm -a+w | xargs ls -ldb command to verify that
none of the files are world writable files by reviewing permissions of all the files on the vApp.
Others should not have write permission. The permissions on these files should be ##4 or
##5, where # equals the default given set of permissions for the Owner and Group, such as 6
or 7.
4 Run the find / -path */proc -prune -o ! -user root -o -user admin -print command
to verify that the files are owned by the correct user.
All the files belong to either root or admin if there are no results.
5 Run the find /usr/lib/vmware-casa/ -type f -perm -o=w command to ensure that files in
the /usr/lib/vmware-casa/ directory are not world writable.
There must be no results.
VMware, Inc. 46
6 Run the find /usr/lib/vmware-vcops/ -type f -perm -o=w command to ensure that files in
the /usr/lib/vmware-vcops/ directory are not world writable.
7 Run the find /usr/lib/vmware-vcopssuite/ -type f -perm -o=w command to ensure that files in
the /usr/lib/vmware-vcopssuite/ directory are not world writable.
Apache Configuration
Disable Web Directory Browsing

As a security best practice, ensure that a user cannot browse through a directory because it can
increase the risk of exposure to directory traversal attacks.
Procedure
u Verify that web directory browsing is disabled for all directories.
a Open the /etc/apache2/default-server.conf and /usr/lib/vmware-vcopssuite/

utilities/conf/vcops-apache.conf files in a text editor.
b Verify that for each <Directory> listing, the option called Indexes for the relevant tag is
omitted from the Options line.
Remove the Sample Code for the Apache2 Server

Apache includes two sample Common Gateway Interface (CGI) scripts, printenv and test-cgi. A
production Web server must contain only components that are operationally necessary. These
components have the potential to disclose critical information about the system to an attacker.
As a security best practice, delete the CGI scripts from the cgi-bin directory.
Procedure
u To remove test-cgi and prinenv scripts, run the rm /usr/share/doc/packages/apache2/

test-cgi and rm /usr/share/doc/packages/apache2/printenv commands.
Verify Server Tokens for the Apache2 Server

As part of your system hardening process, verify server tokens for the Apache2 server. The Web
server response header of an HTTP response can contain several fields of information.
Information includes the requested HTML page, the Web server type and version, the operating
system and version, and ports associated with the Web server. This information provides
malicious users important information without the use of extensive tools.
The directive ServerTokens must be set to Prod. For example, ServerTokens Prod. This directive
controls whether the response header field of the server that is sent back to clients includes a
description of the operating system and information about compiled-in modules.
VMware, Inc. 47
Procedure
1 To verify server tokens, run the cat /etc/apache2/sysconfig.d/global.conf | grep

ServerTokens command.
2 To modify ServerTokens OS to ServerTokens Prod, run the sed -i 's/$ServerTokens\s\+

$OS/\1Prod/g' /etc/apache2/sysconfig.d/global.conf command.
Disable the Trace Method for the Apache2 Server

In standard production operations, use of diagnostics can reveal undiscovered vulnerabilities that
lead to compromised data. To prevent misuse of data, disable the HTTP Trace method.
Procedure
1 To verify the Trace method for the Apache2 server, run the following command grep
TraceEnable /usr/lib/vmware-vcopssuite/utilities/conf/vcops-apache.conf.
2 To disable the Trace method for the Apache2 server, run the following command sed -i "/
^[^#]*TraceEnable/ c\TraceEnable off" /usr/lib/vmware-vcopssuite/utilities/conf/
vcops-apache.conf.
Disable Configuration Modes

As a best practice, when you install, configure, or maintain vRealize Operations Manager, you can
modify the configuration or settings to enable troubleshooting and debugging of your
installation.
Catalog and audit each of the changes you make to ensure that they are properly secured. Do
not put the changes into production if you are not sure that your configuration changes are
correctly secured.
Managing Nonessential Software Components

To minimize security risks, remove or configure nonessential software from your vRealize
Operations Manager host machines.
Configure all software that you do not remove in accordance with manufacturer
recommendations and security best practices to minimize the potential to create security
breaches.
Secure the USB Mass Storage Handler

Secure the USB mass storage handler to prevent it from loading by default on vRealize
appliances and to prevent its use as the USB device handler with the vRealize appliances.
Potential attackers can exploit this handler to install malicious software.
Procedure
1 Open the/etc/modprobe.conf.local file in a text editor.
2 Ensure that the install usb-storage /bin/true line appears in the file.
VMware, Inc. 48
Secure the Bluetooth Protocol Handler

Secure the Bluetooth protocol handler on your vRealize Appliances to prevent potential attackers
from exploiting it.
Binding the Bluetooth protocol to the network stack is unnecessary and can increase the attack
surface of the host. Prevent the Bluetooth protocol handler module from loading by default on
vRealize Appliances.
Procedure
1 Open the /etc/modprobe.conf.local file in a text editor.
2 Ensure that the line install bluetooth /bin/true appears in this file.
Secure the Stream Control Transmission Protocol

Prevent the Stream Control Transmission Protocol (SCTP) module from loading on vRealize
appliances by default. Potential attackers could exploit this protocol to compromise your system.
Configure your system to prevent the SCTP module from loading unless it is absolutely
necessary. SCTP is an unused IETF-standardized transport layer protocol. Binding this protocol to
the network stack increases the attack surface of the host. Unprivileged local processes might
cause the kernel to dynamically load a protocol handler by using the protocol to open a socket.
Procedure
2 Ensure that the following line appears in this file.
install sctp /bin/true
Secure the Datagram Congestion Control Protocol

As part of your system hardening activities, prevent the Datagram Congestion Control Protocol
(DCCP) module from loading on vRealize appliances by default. Potential attackers can exploit
this protocol to compromise your system.
Avoid loading the DCCP module, unless it is absolutely necessary. DCCP is a proposed transport
layer protocol, which is not used. Binding this protocol to the network stack increases the attack
surface of the host. Unprivileged local processes can cause the kernel to dynamically load a
protocol handler by using the protocol to open a socket.
Procedure
VMware, Inc. 49
2 Ensure that the DCCP lines appear in the file.
install dccp /bin/true

install dccp_ipv4 /bin/true
install dccp_ipv6 /bin/true
Secure Reliable Datagram Sockets Protocol

As part of your system hardening activities, prevent the Reliable Datagram Sockets (RDS)
protocol from loading on your vRealize appliances by default. Potential attackers can exploit this
protocol to compromise your system.
Binding the RDS protocol to the network stack increases the attack surface of the host.
Unprivileged local processes might cause the kernel to dynamically load a protocol handler by
using the protocol to open a socket.
Procedure
2 Ensure that the install rds /bin/true line appears in this file.
Secure the Transparent Inter-Process Communication Protocol

As part of your system hardening activities, prevent the Transparent Inter-Process
Communication protocol (TIPC) from loading on your virtual appliance host machines by default.
Potential attackers can exploit this protocol to compromise your system.
Binding the TIPC protocol to the network stack increases the attack surface of the host.
Unprivileged local processes can cause the kernel to dynamically load a protocol handler by
using the protocol to open a socket.
Procedure
2 Ensure that the install tipc /bin/true line appears in this file.
Secure Internet Packet Exchange Protocol

Prevent the Internetwork Packet Exchange (IPX) protocol from loading vRealize appliances by
default. Potential attackers could exploit this protocol to compromise your system.
Avoid loading the IPX protocol module unless it is absolutely necessary. IPX protocol is an
obsolete network-layer protocol. Binding this protocol to the network stack increases the attack
surface of the host. Unprivileged local processes might cause the system to dynamically load a
protocol handler by using the protocol to open a socket.
VMware, Inc. 50
Procedure
2 Ensure that the line install ipx /bin/true appears in this file.
Secure AppleTalk Protocol

Prevent the AppleTalk protocol from loading on vRealize appliances by default. Potential
attackers might exploit this protocol to compromise your system.
Avoid loading the AppleTalk Protocol module unless it is necessary. Binding this protocol to the
network stack increases the attack surface of the host. Unprivileged local processes might cause
the system to dynamically load a protocol handler by using the protocol to open a socket.
Procedure
2 Ensure that the line install appletalk /bin/true appears in this file.
Secure DECnet Protocol

Prevent the DECnet protocol from loading on your system by default. Potential attackers might
exploit this protocol to compromise your system.
Avoid loading the DECnet Protocol module unless it is absolutely necessary. Binding this protocol
to the network stack increases the attack surface of the host. Unprivileged local processes could
cause the system to dynamically load a protocol handler by using the protocol to open a socket.
Procedure
1 Open the DECnet Protocol /etc/modprobe.conf.local file in a text editor.
2 Ensure that the line install decnet /bin/true appears in this file.
Secure Firewire Module

Prevent the Firewire module from loading on vRealize appliances by default. Potential attackers
might exploit this protocol to compromise your system.
Avoid loading the Firewire module unless it is absolutely necessary.
Procedure
2 Ensure that the line install ieee1394 /bin/true appears in this file.
VMware, Inc. 51
Kernel Message Logging

The kernel.printk specification in the /etc/sysctl.conf file specifies the kernel print logging
specifications.
There are 4 values specified:
n console loglevel. The lowest priority of messages printed to the console.
n default loglevel. The lowest level for messages without a specific log level.
n The lowest possible level for the console log level.
n The default value for console log level.
There are eight possible entries per value.
n define KERN_EMERG "<0>" /* system is unusable */
n define KERN_ALERT "<1>" /* action must be taken immediately */
n define KERN_CRIT "<2>" /* critical conditions */
n define KERN_ERR "<3>" /* error conditions */
n define KERN_WARNING "<4>" /* warning conditions */
n define KERN_NOTICE "<5>" /* normal but significant condition */
n define KERN_INFO "<6>" /* informational */
n define KERN_DEBUG "<7>" /* debug-level messages */
Set the kernel.printk values to 3 4 1 7 and ensure that the line kernel.printk=3 4 1 7 exists
in the /etc/sysctl.conf file.
End Point Operations Management Agent

The End Point Operations Management agent adds agent-based discovery and monitoring
capabilities to vRealize Operations Manager.
The End Point Operations Management agent is installed on the hosts directly and might or might
not be at the same level of trust as the End Point Operations Management server. Therefore, you
must verify that the agents are securely installed.
Security Best Practices for Running End Point Operations Management Agents
You must follow certain security best practices while using user accounts.
n For a silent installation, remove any credentials and server certificate thumbprints that were
stored in the AGENT_HOME/conf/agent.properties file.
n Use a vRealize Operations Manager user account reserved specifically for End Point
Operations Management agent registration. For more information, see the topic called "Roles
and Privileges" in vRealize Operations Manager in the vRealize Operations Manager Help.
VMware, Inc. 52
n Disable the vRealize Operations Manager user account that you use for agent registration
after the installation is over. You must enable the user’s access for agent administration
activities. For more information, see the topic called Configuring Users and Groups in vRealize
Operations Manager in the vRealize Operations Manager Help.
n If a system that runs an agent is compromised, you can revoke the agent certificate using the
vRealize Operations Manager user interface by removing the agent resource. See the section
called Revoking an Agent for more detail.
Minimum Required Permissions for Agent Functionality

You require permissions to install and modify a service. If you want to discover a running process,
the user account you use to run the agent must also have privileges to access the processes and
programs. For Windows operating system installations, you require permissions to install and
modify a service. For Linux installations, you require permission to install the agent as a service, if
you install the agent using a RPM installer.
The minimum credentials that are required for the agent to register with the vRealize Operations
Manager server are those for a user granted the Agent Manager role, without any assignment to
objects within the system.
Linux Based Platform Files and Permissions
After you install the End Point Operations Management agent, the owner is the user that installs
the agent.
The installation directory and file permissions such as 600 and 700, are set to the owner when
the user who installs the End Point Operations Management agent extracts the TAR file or installs
the RPM.
Note When you extract the ZIP file, the permissions might not be correctly applied. Verify and
ensure that the permissions are correct.
All the files that are created and written to by the agent are given 700 permissions with the
owner being the user who runs the agent.
Table 2-8. Linux Files and Permissions

Permissio
Directory or File ns Groups or Users Read Write Execute
agent directory/bin 700 Owner Yes Yes Yes
Group No No No
All No No No
agent directory/conf 700 Owner Yes Yes Yes
Group No No No
All No No No
agent directory/log 700 Owner Yes Yes No
Group No No No
All No No No
VMware, Inc. 53
Table 2-8. Linux Files and Permissions (continued)

Permissio
Directory or File ns Groups or Users Read Write Execute
agent directory/data 700 Owner Yes Yes Yes
Group No No No
All No No No
agent directory/bin/ep- 600 Owner Yes Yes No

agent.bat
Group No No No
All No No No
agent directory/bin/ep- 700 Owner Yes Yes Yes

agent.sh
Group No No No
All No No No
agent directory/conf/* 600 Owner Yes Yes Yes

(all files in the conf
Group No No No
directory)
All No No No
agent directory/log/* 600 Owner Yes Yes No

(all files in the log
Group No No No
directory)
All No No No
agent directory/data/* 600 Owner Yes Yes No

(all files in the data
Group No No No
directory)
All No No No
Windows Based Platform Files and Permissions

For a Windows based installation of the End Point Operations Management agent, the user
installing the agent must have permissions to install and modify the service.
After you install the End Point Operations Management agent, the installation folder including all
subdirectories and files should only be accessible by the SYSTEM, the administrators group, and
the installation user. When you install the End Point Operations Management agent using ep-
agent.bat, ensure that the hardening process succeeds. As the user installing the agent, it is
advised that you take note of any error messages. If the hardening process fails, the user can
apply these permissions manually.
Table 2-9. Windows Files and Permissions

Groups or Read and
Directory or File Users Full Control Modify Execute Read Write
<agent SYSTEM Yes - - - -

directory>/bin
Administrator Yes - - - -
Installation Yes - - - -
User
Users - - - -
VMware, Inc. 54
Table 2-9. Windows Files and Permissions (continued)

Groups or Read and
<agent directory>/ SYSTEM Yes - - - -

conf
User
Users - - - -

directory>/log
User
Users - - - -

data
User
Users - - - -

directory>/bin/hq-
agent.bat
User
Users - - - -

directory>/bin/hq-
agent.sh
User
Users - - - -

conf/*
(all files in the conf
directory) Installation Yes - - - -
User
Users - - - -

directory>/log/*
(all files in the log
User
Users - - - -
VMware, Inc. 55
Table 2-9. Windows Files and Permissions (continued)

Groups or Read and

data/*
(all files in data
User
Users - - - -
Open Ports on Agent Host

The agent process listens for commands on two ports 127.0.0.1:2144 and 127.0.0.1:32000 that are
configurable. These ports might be arbitrarily assigned, and so, the exact port number might
vary. The agent does not open ports on external interfaces.
Table 2-10. Minimum Required Ports

Port Protocol Direction Comments
443 TCP Outgoing Used by the agent for outgoing connections over HTTP, TCP, or ICMP.
2144 TCP Listening Internal Only. Configurable. Used for inter-process communication between the
agent and the command line that loads and configures it. The agent process
listens on this port.
Note The port number is assigned arbitrarily and might differ.
32000 TCP Listening Internal Only. Configurable. Used for inter-process communication between the
agent and the command line that loads and configures it. The agent process
listens on this port.
Note The port number is assigned arbitrarily and might differ.
Revoking an Agent
If for any reason you need to revoke an agent, for example when a system with a running agent
is compromised, you can delete the agent resource from the system. Any subsequent request
will fail verification.
Use the vRealize Operations Manager user interface to revoke the agent certificate by removing
the agent resource. For more information, see Removing the Agent Resource.
When the system is secured again, you can reinstate the agent. For more information, see
Reinstate an Agent Resource.
Removing the Agent Resource
You can use the vRealize Operations Manager to revoke the agent certificate by removing the
agent resource.
Prerequisites
To preserve the continuity of the resource with previously recorded metric data, take a record of
the End Point Operations Management agent token that is displayed in the resource details.
VMware, Inc. 56
Procedure
1 Navigate to the Inventory page in the vRealize Operations Manager user interface.
2 Open the Adapter Types tree.
3 Open the EP Ops Adapter list.
4 Select EP Ops Agent - *HOST_DNS_NAME*.
5 Click Edit Object.
6 Record the agent ID, which is the agent token string.
7 Close the Edit Object dialog box .
8 Select EP Ops Agent - *HOST_DNS_NAME* and click Delete Object.

Reinstate an Agent Resource
When the secure state of a system is recovered, you can reinstate a revoked agent. This ensures
that the agent continues to report on the same resources without losing historical data. To do
this you must create a new End Point Operations Management token file by using the same
token recorded before you removed the agent resource. See the section called Removing The
Agent Resource.
Prerequisites
n Ensure that you have the recorded End Point Operations Management token string.
n Use the resource token recorded prior to removing the agent resource from the vRealize
Operations Manager server.
n Ensure that you have the Manage Agent privilege.
Procedure
1 Create the agent token file with the user that runs the agent.
For example, run the command to create a token file containing the 123-456-789 token.
n On Linux:
echo 123-456-789 > /etc/epops/epops-token
n On Windows:
echo 123-456-789 > %PROGRAMDATA%\VMware\Ep Ops Agent\epops-token
In the example, the token file is written to the default token location for that platform
2 Install a new agent and register it with the vRealize Operations Manager server. Ensure that
the agent loads the token you inserted in the token file.
You must have the Manage Agent privilege to perform this action.
VMware, Inc. 57
Agent Certificate Revocation and Update of Certificates

The reissue flow is initiated from the agent using the setup command line argument. When an
agent that is already registered uses the setup command line argument ep-agent.sh setup and
fills in the required credentials, a new registerAgent command is sent to the server.
The server detects that the agent is already registered and sends the agent a new client
certificate without creating another agent resource. On the agent side, the new client certificate
replaces the old one. In cases where the server certificate is modified and you run the ep-
agent.sh setup command, you see a message that asks you to trust the new certificate. You can
alternatively provide the new server certificate thumbprint in the agent.properties file before
running the ep-agent.sh setup command, to make the process silent.
Prerequisites
Manage agent privilege to revoke and update certificates.
Procedure
u On Linux based operating systems, run the ep-agent.sh setup command on the agent host.
On Windows based operating systems, run the ep-agent.bat setup command.
If the agent detects that the server certificate has been modified, a message is displayed.
Accept the new certificate if you trust it and it is valid.
Patching and Updating the End Point Operations Management Agent

If required, new End Point Operations Management agent bundles are available independent of
vRealize Operations Manager releases.
Patches or updates are not provided for the End Point Operations Management agent. You must
install the latest available version of the agent that includes the latest security fixes. Critical
security fixes will be communicated as per the VMware security advisory guidance. See the topic
on Security Advisories.
Additional Secure Configuration Activities

Verify the server user accounts and delete unnecessary applications from the host servers. Block
unnecessary ports and disable the services running on your host server that are not required.
Verify Server User Account Settings

It is recommended that you verify that no unnecessary user accounts exist for local and domain
user accounts and settings.
Restrict any user account not related to the functioning of the application to those accounts
required for administration, maintenance, and troubleshooting. Restrict remote access from
domain user accounts to the minimum required to maintain the server. Strictly control and audit
these accounts.
VMware, Inc. 58
Delete and Disable Unnecessary Applications

Delete the unnecessary applications from the host servers. Each additional and unnecessary
application increases the risk of exposure because of their unknown or unpatched vulnerabilities.
Disabling Unnecessary Ports and Services

Verify the host server's firewall for the list of open ports that allow traffic.
Block all the ports that are not listed as a minimum requirement for vRealize Operations Manager
in the Configuring Ports and Protocols section of this document, or are not required. In addition,
audit the services running on your host server and disable those that are not required.
Network Security and Secure Communication

As a security best practice, review and edit the network communication settings of your VMware
virtual appliances and host machines. You must also configure the minimum incoming and
outgoing ports for vRealize Operations Manager.
Configuring Network Settings for Virtual Application Installation

To ensure that your VMware virtual appliance and host machines allow only safe and essential
communication, review and edit their network communication settings.
Prevent User Control of Network Interfaces

As a security best practice, restrict the ability to change the network interface setting to
privileged users. If users manipulate network interfaces, it might result in bypassing network
security mechanisms or denial of service. Ensure that network interfaces are not configured for
user control.
Procedure
1 To verify user control settings, run the #grep -i '^USERCONTROL=' /etc/sysconfig/

network/ifcfg* command.
2 Make sure that each interface is set to NO.
Set the Queue Size for TCP Backlog

As a security best practice, configure a default TCP backlog queue size on VMware appliance
host machines. To mitigate TCP denial or service attacks, set an appropriate default size for the
TCP backlog queue size. The recommended default setting is 1280.
Procedure
1 Run the # cat /proc/sys/net/ipv4/tcp_max_syn_backlog command on each VMware

appliance host machine.
VMware, Inc. 59
2 Set the queue size for TCP backlog.
a Open the /etc/sysctl.conf file in a text editor.
b Set the default TCP backlog queue size by adding the following entry to the file.
net.ipv4.tcp_max_syn_backlog=1280
c Save your changes and close the file.
Deny ICMPv4 Echoes to Broadcast Address

Responses to broadcast Internet Control Message Protocol (ICMP) echoes provide an attack
vector for amplification attacks and can facilitate network mapping by malicious agents.
Configuring your system to ignore ICMPv4 echoes provides protection against such attacks.
Procedure
1 Run the # cat /proc/sys/net/ipv4/icmp_echo_ignore_broadcasts command to verify that the

system is not sending responses to ICMP broadcast address echo requests.
2 Configure the host system to deny ICMPv4 broadcast address echo requests.
b If the value for this entry is not set to 1, add the net.ipv4.icmp_echo_ignore_broadcasts=1
entry.
c Save the changes and close the file.
Configure the Host System to Disable IPv4 Proxy ARP

IPv4 Proxy ARP allows a system to send responses to ARP requests on one interface on behalf of
hosts connected to another interface. You must disable IPv4 Proxy ARP to prevent unauthorized
information sharing. Disable the setting to prevent leakage of addressing information between
the attached network segments.
Procedure
1 Run the # grep [01] /proc/sys/net/ipv4/conf/*/proxy_arp|egrep "default|all"

command to verify whether the Proxy ARP is disabled.
2 Configure the host system to disable IPv4 Proxy ARP.
b If the values are not set to 0, add the entries or update the existing entries accordingly.
Set the value to 0.
net.ipv4.conf.all.proxy_arp=0
net.ipv4.conf.default.proxy_arp=0
c Save any changes you made and close the file.
VMware, Inc. 60
Configure the Host System to Ignore IPv4 ICMP Redirect Messages

As a security best practice, verify that the host system ignores IPv4 Internet Control Message
Protocol (ICMP) redirect messages. A malicious ICMP redirect message can allow a man-in-the-
middle attack to occur. Routers use ICMP redirect messages to notify hosts that a more direct
route exists for a destination. These messages modify the host's route table and are
unauthenticated.
Procedure
1 Run the # grep [01] /proc/sys/net/ipv4/conf/*/accept_redirects|egrep "default|

all" command on the host system to check whether the host system ignores IPv4 redirect
messages.
2 Configure the host system to ignore IPv4 ICMP redirect messages.
a Open the /etc/sysctl.conf file.
b If the values are not set to 0, add the following entries to the file or update the existing
entries accordingly. Set the value to 0.
net.ipv4.conf.all.accept_redirects=0
net.ipv4.conf.default.accept_redirects=0
Configure the Host System to Ignore IPv6 ICMP Redirect Messages

As a security best practice, verify that the host system ignores IPv6 Internet Control Message
Protocol (ICMP) redirect messages. A malicious ICMP redirect message might allow a man-in-the-
middle attack to occur. Routers use ICMP redirect messages to tell hosts that a more direct route
exists for a destination. These messages modify the host's route table and are unauthenticated.
Procedure
1 Run the # grep [01] /proc/sys/net/ipv6/conf/*/accept_redirects|egrep "default|

all" command on the host system and check whether it ignores IPv6 redirect messages.
2 Configure the host system to ignore IPv6 ICMP redirect messages.
a Open the /etc/sysctl.conf to configure the host system to ignore the IPv6 redirect
messages.
net.ipv6.conf.all.accept_redirects=0
net.ipv6.conf.default.accept_redirects=0
VMware, Inc. 61
Configure the Host System to Deny IPv4 ICMP Redirects

As a security best practice, verify that the host system denies IPv4 Internet Control Message
Protocol (ICMP) redirects. Routers use ICMP redirect messages to inform servers that a direct
route exists for a particular destination. These messages contain information from the system's
route table that might reveal portions of the network topology.
Procedure
1 Run the # grep [01] /proc/sys/net/ipv4/conf/*/send_redirects|egrep "default|all"

on the host system to verify whether it denies IPv4 ICMP redirects.
2 Configure the host system to deny IPv4 ICMP redirects.
a Open the /etc/sysctl.conf file to configure the host system.
net.ipv4.conf.all.send_redirects=0
net.ipv4.conf.default.send_redirects=0
Configure the Host System to Log IPv4 Martian Packets

As a security best practice, verify that the host system logs IPv4 Martian packets. Martian
packets contain addresses that the system knows to be invalid. Configure the host system to log
the messages so that you can identify misconfigurations or attacks in progress.
Procedure
1 Run the # grep [01] /proc/sys/net/ipv4/conf/*/log_martians|egrep "default|all"

command to check whether the host logs IPv4 Martian packets.
2 Configure the host system to log IPv4 Martian packets.
net.ipv4.conf.all.log_martians=1
net.ipv4.conf.default.log_martians=1
Configure the Host System to use IPv4 Reverse Path Filtering

As a security best practice, configure your host machines to use IPv4 reverse path filtering.
Reverse path filtering protects against spoofed source addresses by causing the system to
discard packets with source addresses that have no route or if the route does not point towards
the originating interface.
VMware, Inc. 62
Configure your system to use reverse-path filtering whenever possible. Depending on the system
role, reverse-path filtering might cause legitimate traffic to be discarded. In such cases, you might
need to use a more permissive mode or disable reverse-path filtering altogether.
Procedure
1 Run the # grep [01] /proc/sys/net/ipv4/conf/*/rp_filter|egrep "default|all"

command on the host system to check whether the system uses IPv4 reverse path filtering.
2 Configure the host system to use IPv4 reverse path filtering.
net.ipv4.conf.all.rp_filter=1
net.ipv4.conf.default.rp_filter=1
Configure the Host System to Deny IPv4 Forwarding

As a security best practice, verify that the host system denies IPv4 forwarding. If the system is
configured for IP forwarding and is not a designated router, it could be used to bypass network
security by providing a path for communication that is not filtered by network devices.
Procedure
1 Run the # cat /proc/sys/net/ipv4/ip_forward command to verify whether the host denies
IPv4 forwarding.
2 Configure the host system to deny IPv4 forwarding.
a Open the /etc/sysctl.conf to configure the host system.
b If the value is not set to 0, add the following entry to the file or update the existing entry
accordingly. Set the value to 0.
net.ipv4.ip_forward=0
Configure the Host System to Deny Forwarding of IPv4 Source Routed Packets
Source-routed packets allow the source of the packet to suggest that routers forward the packet
along a different path than what is configured on the router, which can be used to bypass
network security measures.
This requirement applies only to the forwarding of source-routed traffic, such as when IPv4
forwarding is enabled and the system is functioning as a router.
VMware, Inc. 63
Procedure
1 Run the # grep [01] /proc/sys/net/ipv4/conf/*/accept_source_route|egrep "default|

all" command to verify whether the system does not use IPv4 source routed packets
2 Configure the host system to deny forwarding of IPv4 source routed packets.
a Open the /etc/sysctl.conf file with a text editor.
b If the values are not set to 0, ensure that net.ipv4.conf.all.accept_source_route=0 and the
et.ipv4.conf.default.accept_source_route=0 are set to 0.
c Save and close the file.
Configure the Host System to Deny IPv6 Forwarding

As a security best practice, verify that the host system denies IPv6 forwarding. If the system is
configured for IP forwarding and is not a designated router, it can be used to bypass network
security by providing a path for communication that is not filtered by network devices.
Procedure
1 Run the # grep [01] /proc/sys/net/ipv6/conf/*/forwarding|egrep "default|all"

command to verify whether the host denies IPv6 forwarding.
2 Configure the host system to deny IPv6 forwarding.
net.ipv6.conf.all.forwarding=0
net.ipv6.conf.default.forwarding=0
Configure the Host System to Use IPv4 TCP SYN Cookies

As a security best practice, verify that the host system uses IPv4 Transmission Control Protocol
(TCP) SYN cookies. A TCP SYN flood attack might cause a denial of service by filling a system's
TCP connection table with connections in the SYN_RCVD state. SYN cookies are used so as not
to track a connection until a subsequent ACK is received, verifying that the initiator is attempting
a valid connection and is not a flood source.
This technique does not operate in a fully standards-compliant manner, but is only activated
when a flood condition is detected, and allows defense of the system while continuing to service
valid requests.
Procedure
1 Run the # cat /proc/sys/net/ipv4/tcp_syncookies command to verify whether the host

system uses IPv4 TCP SYN cookies.
VMware, Inc. 64
2 Configure the host system to use IPv4 TCP SYN cookies.
b If the value is not set to 1, add the following entry to the file or update the existing entry
accordingly. Set the value to 1.
net.ipv4.tcp_syncookies=1
Configure the Host System to Deny IPv6 Router Advertisements

As a security best practice, verify that the host system denies the acceptance of router
advertisements and Internet Control Message Protocol (ICMP) redirects unless necessary. A
feature of IPv6 is how systems can configure their networking devices by automatically using
information from the network. From a security perspective, it is preferable to manually set
important configuration information rather than accepting it from the network in an
unauthenticated way.
Procedure
1 Run the # grep [01] /proc/sys/net/ipv6/conf/*/accept_ra|egrep "default|all"

command on the host system to verify whether the system denies the acceptance of router
advertisements and ICMP redirects unless necessary.
2 Configure the host system to deny IPv6 router advertisements.
net.ipv6.conf.all.accept_ra=0
net.ipv6.conf.default.accept_ra=0
Configure the Host System to Deny IPv6 Router Solicitations

As a security best practice, verify that host system denies IPv6 router solicitations unless
necessary. The router solicitations setting determines how many router solicitations are sent
when bringing up the interface. If addresses are assigned statically, there is no need to send any
solicitations.
Procedure
1 Run the # grep [01] /proc/sys/net/ipv6/conf/*/router_solicitations|egrep

"default|all" command to verify whether the host system denies IPv6 router solicitations
unless necessary.
VMware, Inc. 65
2 Configure the host system to deny IPv6 router solicitations.
a Open the /etc/sysctl.conf.
net.ipv6.conf.all.router_solicitations=0
net.ipv6.conf.default.router_solicitations=0
Configure the Host System to Deny IPv6 Router Preference in Router Solicitations
As a security best practice, verify that your host system denies IPv6 router solicitations unless
necessary. The router preference in the solicitations setting determines router preferences. If
addresses are assigned statically, there is no need to receive any router preference for
solicitations.
Procedure
1 Run the # grep [01] /proc/sys/net/ipv6/conf/*/accept_ra_rtr_pref|egrep "default|

all" on the host system to verify whether the host system denies IPv6 router solicitations.
2 Configure the host system to deny IPv6 router preference in router solicitations.
net.ipv6.conf.all.accept_ra_rtr_pref=0
net.ipv6.conf.default.accept_ra_rtr_pref=0
Configure the Host System to Deny IPv6 Router Prefix

As a security best practice, verify that the host system denies IPv6 router prefix information
unless necessary. The accept ra pinfo setting controls whether the system accepts prefix
information from the router. If addresses are statically assigned, the system does not receive any
router prefix information.
Procedure
1 Run the # grep [01] /proc/sys/net/ipv6/conf/*/accept_ra_pinfo|egrep "default|all"

to verify if that system denies IPv6 router prefix information.
VMware, Inc. 66
2 Configure the host system to deny IPv6 router prefix.
net.ipv6.conf.all.accept_ra_pinfo=0
net.ipv6.conf.default.accept_ra_pinfo=0
Configure the Host System to Deny IPv6 Router Advertisement Hop Limit Settings
As a security best practice, verify that the host system denies IPv6 router advertisement Hop
Limit settings from a router advertisement unless necessary. The accept_ra_defrtr setting
controls whether the system will accept Hop Limit settings from a router advertisement. Setting it
to 0 prevents a router from changing your default IPv6 Hop Limit for outgoing packets.
Procedure
1 Run the # grep [01] /proc/sys/net/ipv6/conf/*/accept_ra_defrtr|egrep "default|

all" command to verify that the host system denies IPv6 router Hop Limit settings.
2 If the values are not set to 0, configure the host system to deny IPv6 router advertisement
Hop Limit settings.
net.ipv6.conf.all.accept_ra_defrtr=0
net.ipv6.conf.default.accept_ra_defrtr=0
Configure the Host System to Deny IPv6 Router Advertisement Autoconf Settings
As a security best practice, verify that the host system denies IPv6 router advertisement autoconf
settings. The autoconf setting controls whether router advertisements can cause the system to
assign a global unicast address to an interface.
Procedure
1 Run the # grep [01] /proc/sys/net/ipv6/conf/*/autoconf|egrep "default|all"

command to verify whether the host system denies IPv6 router advertisement autoconf
settings.
VMware, Inc. 67
2 If the values are not set to 0, configure the host system to deny IPv6 router advertisement
autoconf settings.
net.ipv6.conf.all.autoconf=0
net.ipv6.conf.default.autoconf=0
Configure the Host System to Deny IPv6 Neighbor Solicitations

As a security best practice, verify that the host system denies IPv6 neighbor solicitations unless
necessary. The dad_transmits setting determines how many neighbor solicitations are to be sent
out per address including global and link-local, when you bring up an interface to ensure the
desired address is unique on the network.
Procedure
1 Run the # grep [01] /proc/sys/net/ipv6/conf/*/dad_transmits|egrep "default|all"

command to verify whether the host system denies IPv6 neighbor solicitations.
2 If the values are not set to 0, configure the host system to deny IPv6 neighbor solicitations.
net.ipv6.conf.all.dad_transmits=0
net.ipv6.conf.default.dad_transmits=0
Configure the Host System to Restrict IPv6 Maximum Addresses

As a security best practice, verify that the host restricts the maximum number of IPv6 addresses
that can be assigned. The maximum addresses setting determines how many global unicast IPv6
addresses can be assigned to each interface. The default is 16 but you must set the number to
the statically configured global addresses required.
Procedure
1 Run the # grep [1] /proc/sys/net/ipv6/conf/*/max_addresses|egrep "default|all"

command to verify whether the host system restricts the maximum number of IPv6
addresses that can be assigned.
VMware, Inc. 68
2 If the values are not set to 1, configure the host system to restrict the maximum number of
IPv6 addresses that can be assigned.
b Add the following entries to the file or update the existing entries accordingly. Set the
value to 1.
net.ipv6.conf.all.max_addresses=1
net.ipv6.conf.default.max_addresses=1
Configuring Ports and Protocols

As a security best practice, disable all non-essential ports and protocols.
Configure the minimum incoming and outgoing ports for vRealize Operations Manager
components as required for important system components to operate in production.
Minimum Default Incoming Ports

As a security best practice, configure the incoming ports required for vRealize Operations
Manager to operate in production.
Table 2-11. Minimum Required Incoming Ports

Port Protocol Comments
443 TCP Used to access the vRealize Operations Manager user

interface and the vRealize Operations Manager
administrator interface.
123 UDP Used by vRealize Operations Manager for Network Time

Protocol (NTP) synchronization to the primary node.
5433 TCP Used by the primary and replica nodes to replicate the
global database (vPostgreSQL ) when high availability is
enabled .
7001 TCP Used by Cassandra for secure inter-node cluster

communication.
Do not expose this port to the Internet. Add this port to
a firewall.
9042 TCP Used by Cassandra for secure client-related

communication among nodes.
Do not expose this port to the Internet. Add this port to
a firewall.
6061 TCP Used by clients to connect to the GemFire Locator to

get connection information to servers in the distributed
system. Also monitors server load to send clients to the
least-loaded servers.
VMware, Inc. 69
Table 2-11. Minimum Required Incoming Ports (continued)

10000-10010 TCP and UDP GemFire Server ephemeral port range used for unicast
UDP messaging and for TCP failure detection in a peer-
to-peer distributed system.
20000-20010 TCP and UDP GemFire Locator ephemeral port range used for unicast
UDP messaging and for TCP failure detection in a peer-
to-peer distributed system.
Table 2-12. Optional Incoming Ports

22 TCP Optional. Secure Shell (SSH). The SSH

service listening on port 22, or any
other port, must be disabled in a
production environment, and port 22
must be closed.
80 TCP Optional. Redirects to 443.
3091-3101 TCP When Horizon View is installed, used

to access data for vRealize Operations
Manager from Horizon View.
Auditing and Logging on your vRealize Operations Manager System

As a security best practice, set up auditing and logging on your vRealize Operations Manager
system.
The detailed implementation of auditing and logging is outside the scope of this document.
Remote logging to a central log host provides a secure store for logs. By collecting log files to a
central host, you can easily monitor the environment with a single tool. You can also perform
aggregate analysis and search for coordinated attacks on multiple entities within the
infrastructure. Logging to a secure, centralized log server can help prevent log tampering and
also provide a long-term audit record.
Securing the Remote Logging Server

As a security best practice, ensure that the remote logging server can be configured only by an
authorized user and is secure.
Attackers who breach the security of your host machine might search for and attempt to tamper
with log files to cover their tracks and maintain control without being discovered.
Use an Authorized NTP Server

Ensure that all the host systems use the same relative time source, including the relevant
localization offset. You can correlate the relative time source to an agreed-upon time standard
such as Coordinated Universal Time (UTC).
VMware, Inc. 70
You can easily track and correlate an intruder's actions when you review the relevant log files.
Incorrect time settings can make it difficult to inspect and correlate log files to detect attacks,
and can make auditing inaccurate. You can use at the least three NTP servers from outside time
sources or configure a few local NTP servers on a trusted network that obtain their time from at
least three outside time sources.
Client Browser Considerations

As a security best practice, do not use vRealize Operations Manager from untrusted or
unpatched clients or from clients that use browser extensions.
VMware, Inc. 71
Installing
3
You install VMware vRealize Operations Manager to create and configure one or more VMware
vRealize Operations Manager nodes that collect and analyze object data from your environment.
n About Installing
n Preparing for Installation
n Installing vRealize Operations Manager
n Resize your Cluster by Adding Nodes
n vRealize Operations Manager Post-Installation Considerations
n Upgrade, Backup and Restore
About Installing
You prepare for vRealize Operations Manager installation by evaluating your environment and
deploying enough vRealize Operations Manager cluster nodes to support how you want to use
the product.
Workflow of vRealize Operations Manager Installation

The vRealize Operations Manager virtual appliance installation process consists of deploying the
vRealize Operations Manager OVF or an installer once for each cluster node, accessing the
product to set up cluster nodes according to their role, and logging in to configure the
installation.
VMware, Inc. 72
Figure 3-1. vRealize Operations Manager Installation Architecture
Download OVF/Installers
Yes No
New
install
Expansion of
New installation
existing installation
Licensing Run data node Run remote collector
Custom certificates
Add new solution
Configure solution
Configure monitoring policies
Monitor your environment
To automate installation, configuration, upgrade, patch, configuration management, drift

remediation and health from within a single pane of glass, you can use vRealize Suite Lifecycle
Manager. If you are a new user, click here to install vRealize Suite Lifecycle Manager. This
provides the IT Managers of Cloud admin resources to focus on business-critical initiatives, while
improving time to value (TTV), reliability and consistency.
VMware, Inc. 73
You can also install and upgrade vRealize Operations Manager by using vRealize Suite Lifecycle
Manager. For more information, see the Creating an Environment from Configure vRealize
Products.
Sizing the vRealize Operations Manager Cluster

The resources needed for vRealize Operations Manager depend on how large of an environment
you expect to monitor and analyze, how many metrics you plan to collect, and how long you
need to store the data.
It is difficult to broadly predict the CPU, memory, and disk requirements that will meet the needs
of a particular environment. There are many variables, such as the number and type of objects
collected, which includes the number and type of adapters installed, the presence of HA, the
duration of data retention, and the quantity of specific data points of interest, such as symptoms,
changes, and so on.
VMware expects vRealize Operations Manager sizing information to evolve, and maintains
Knowledge Base articles so that sizing calculations can be adjusted to adapt to usage data and
changes in versions of vRealize Operations Manager.
Knowledge Base article 2093783
The Knowledge Base articles include overall maximums, plus spreadsheet calculators in which
you enter the number of objects and metrics that you expect to monitor. To obtain the numbers,
some users take the following high-level approach, which uses vRealize Operations Manager
itself.
1 Review this guide to understand how to deploy and configure a vRealize Operations Manager
node.
2 Deploy a temporary vRealize Operations Manager node.
3 Configure one or more adapters, and allow the temporary node to collect overnight.
4 Access the Cluster Management page on the temporary node.
5 Using the Adapter Instances list in the lower portion of the display as a reference, enter
object and metric totals of the different adapter types into the appropriate sizing
spreadsheet from Knowledge Base article 2093783.
6 Deploy the vRealize Operations Manager cluster based on the spreadsheet sizing
recommendation. You can build the cluster by adding resources and data nodes to the
temporary node or by starting over.
If you have a large number of adapters, you might need to reset and repeat the process on the
temporary node until you have all the totals you need. The temporary node will not have enough
capacity to simultaneously run every connection from a large enterprise.
Another approach to sizing is through self monitoring. Deploy the cluster based on your best
estimate, but create an alert for when capacity falls below a threshold, one that allows enough
time to add nodes or disk to the cluster. You also have the option to create an email notification
when thresholds are passed.
VMware, Inc. 74
During internal testing, a single-node vApp deployment of vRealize Operations Manager that
monitored 8,000 virtual machines ran out of disk storage within one week.
Add Data Disk Space to a vRealize Operations Manager vApp Node

You add to the data disk of vRealize Operations Manager vApp nodes when space for storing the
collected data runs low.
Prerequisites
n Note the disk size of the analytics cluster nodes. When adding disk, you must maintain
uniform size across analytics cluster nodes.
n Use the vRealize Operations Manager administration interface to take the node offline.
n Verify that you are connected to a vCenter Server system with a vSphere Client, and log in to
the vSphere Client.
Procedure
1 Shut down the virtual machine for the node.
2 Edit the hardware settings of the virtual machine, and add another disk.
Note Do not expand disks. vRealize Operations Manager does not support expanding disks.
3 Power on the virtual machine for the node.
Results
During the power-on process, the virtual machine expands the vRealize Operations Manager data
partition.
Complexity of Your Environment

When you deploy vRealize Operations Manager, the number and nature of the objects that you
want to monitor might be complex enough to recommend a Professional Services engagement.
Complexity Levels
Every enterprise is different in terms of the systems that are present and the level of experience
of deployment personnel. The following table presents a color-coded guide to help you
determine where you are on the complexity scale.
n Green
Your installation only includes conditions that most users can understand and work with,
without assistance. Continue your deployment.
n Yellow
Your installation includes conditions that might justify help with your deployment, depending
on your level of experience. Consult your account representative before proceeding, and
discuss using Professional Services.
VMware, Inc. 75
n Red
Your installation includes conditions that strongly recommend a Professional Services

engagement. Consult your account representative before proceeding, and discuss using
Professional Services.
Note that these color-coded levels are not firm rules. Your product experience, which increases
as you work with vRealize Operations Manager and in partnership with Professional Services,
must be taken into account when deploying vRealize Operations Manager.
Table 3-1. Effect of Deployment Conditions on Complexity

Complexity
Level Current or New Deployment Condition Additional Notes
Green You run only one vRealize Operations Manager Lone instances are usually easy to create in
deployment. vRealize Operations Manager.
Green Your deployment includes a management pack The compatibility guide indicates whether the
that is listed as Green according to the supported management pack for vRealize
compatibility guide on the VMware Solutions Operations Manager is a compatible 5.x one or a
Exchange Web site. new one designed for this release. In some cases,
both might work but produce different results.
Regardless, users might need help in adjusting
their configuration so that associated data,
dashboards, alerts, and so on appear as
expected.
Note that the terms solution, management pack,
adapter, and plug-in are used somewhat
interchangeably.
Yellow You run multiple instances of vRealize Multiple instances are typically used to address
Operations Manager. scaling or operator use patterns.
Yellow Your deployment includes a management pack The compatibility guide indicates whether the
that is listed as Yellow according to the supported management pack for vRealize
expected.
Yellow You are deploying vRealize Operations Manager Remote collector nodes gather data but leave the
remote collector nodes. storage and processing of the data to the
analytics cluster.
Yellow You are deploying a multiple-node vRealize Multiple nodes are typically used for scaling out
Operations Manager cluster. the monitoring capability of vRealize Operations
Manager.
Yellow Your new vRealize Operations Manager instance Linux deployments are not as common as vApp
will include a Linux based deployment. deployments and often need special
consideration.
VMware, Inc. 76
Table 3-1. Effect of Deployment Conditions on Complexity (continued)

Complexity
Level Current or New Deployment Condition Additional Notes
Yellow Your vRealize Operations Manager instance will High availability and its node failover capability is
use high availability (HA). a unique multiple-node feature that you might
want additional help in understanding.
Yellow You want help in understanding the new or vRealize Operations Manager is different than
changed features in vRealize Operations vCenter Operations Manager in areas such as
Manager and how to use them in your policies, alerts, compliance, custom reporting, or
environment. badges. In addition, vRealize Operations Manager
uses one consolidated interface.
Red You run multiple instances of vRealize Multiple instances are typically used to address
Operations Manager, where at least one includes scaling, operator use patterns, or because
virtual desktop infrastructure (VDI). separate VDI (V4V monitoring) and non-VDI
instances are needed.
Red Your deployment includes a management pack The compatibility guide indicates whether the
that is listed as Red according to the supported management pack for vRealize
expected.
Red You are deploying multiple vRealize Operations Multiple clusters are typically used to isolate
Manager clusters. business operations or functions.
Red Your current vRealize Operations Manager If your environment was complex enough to
deployment required a Professional Services justify a Professional Services engagement in the
engagement to install it. previous version, it is possible that the same
conditions still apply and might warrant a similar
engagement for this version.
Red Professional Services customized your vRealize If your environment was complex enough to
Operations Manager deployment. Examples of justify a Professional Services engagement in the
customization include special integrations, previous version, it is possible that the same
scripting, nonstandard configurations, multiple conditions still apply and might warrant a similar
level alerting, or custom reporting. engagement for this version.
About vRealize Operations Manager Cluster Nodes

All vRealize Operations Manager clusters consist of a primary node, an optional replica node for
high availability, optional data nodes, and optional remote collector nodes.
When you install vRealize Operations Manager, you use a vRealize Operations Manager vApp
deployment to create role-less nodes. After the nodes are created and have their names and IP
addresses, you use an administration interface to configure them according to their role.
You can create role-less nodes all at once or as needed. A common as-needed practice might be
to add nodes to scale out vRealize Operations Manager to monitor an environment as the
environment grows larger.
VMware, Inc. 77
The following node types make up the vRealize Operations Manager analytics cluster:
Master Node
The master node is the primary node and the initial, required node in vRealize Operations
Manager. All other nodes are managed by the primary node.
In a single-node installation, the primary node manages itself, has adapters installed on it, and
performs all data collection and analysis.
Data Node
In larger deployments, additional data nodes have adapters installed and perform collection
and analysis.
Larger deployments usually include adapters only on the data nodes so that primary and
replica node resources can be dedicated to cluster management.
Replica Node
To use vRealize Operations Manager high availability (HA), the cluster requires that you
convert a data node into a replica of the primary node.
The following node type is a member of the vRealize Operations Manager cluster but not part of
the analytics cluster:
Remote Collector Node
Distributed deployments might require a remote collector node that can navigate firewalls,
interface with a remote data source, reduce bandwidth across data centers, or reduce the
load on the vRealize Operations Manager analytics cluster. Remote collectors only gather
objects for the inventory, without storing data or performing analysis. In addition, remote
collector nodes may be installed on a different operating system than the rest of the cluster.
About vRealize Operations Manager Remote Collector Nodes

A remote collector node is an additional cluster node that allows vRealize Operations Manager to
gather more objects into its inventory for monitoring. Unlike data nodes, remote collector nodes
only include the collector role of vRealize Operations Manager, without storing data or
processing any analytics functions.
A remote collector node is usually deployed to navigate firewalls, reduce bandwidth across data
centers, connect to remote data sources, or reduce the load on the vRealize Operations Manager
analytics cluster.
Remote collectors do not buffer data while the network is experiencing a problem. If the
connection between remote collector and analytics cluster is lost, the remote collector does not
store data points that occur during that time. In turn, and after the connection is restored,
vRealize Operations Manager does not retroactively incorporate associated events from that
time into any monitoring or analysis.
You must have at least one primary node before adding remote collector nodes.
VMware, Inc. 78
About vRealize Operations Manager High Availability

vRealize Operations Manager supports high availability (HA). HA creates a replica for the vRealize
Operations Manager primary node and protects the analytics cluster against the loss of a node.
With HA, data stored on the primary node is always 100% backed up on the replica node. To
enable HA, you must have at least one data node deployed, in addition to the primary node.
n HA is not a disaster recovery mechanism. HA protects the analytics cluster against the loss of
only one node, and because only one loss is supported, you cannot stretch nodes across
vSphere clusters in an attempt to isolate nodes or build failure zones.
n When HA is enabled, the replica can take over all functions that the primary provides, were
the primary to fail for any reason. If the primary fails, failover to the replica is automatic and
requires only two to three minutes of vRealize Operations Manager downtime to resume
operations and restart data collection.
When a primary node problem causes failover, the replica node becomes the primary node,
and the cluster runs in degraded mode. To get out of degraded mode, take one of the
following steps.
n Return to HA mode by correcting the problem with the primary node. When a primary
node exits an HA-enabled cluster, primary node does not rejoin with the cluster without
manual intervention. Therefore, restart the vRealize Operations Analytics process on the
downed node to change its role to replica and rejoin the cluster.
n Return to HA mode by converting a data node into a new replica node and then removing
the old, failed primary node. Removed primary nodes cannot be repaired and re-added to
vRealize Operations Manager.
n Change to non-HA operation by disabling HA and then removing the old, failed primary
node. Removed primary nodes cannot be repaired and re-added to vRealize Operations
Manager.
n In the administration interface, after an HA replica node takes over and becomes the new
primary node, you cannot remove the previous, offline primary node from the cluster. In
addition, the previous node continues to be listed as a primary node. To refresh the display
and enable removal of the node, refresh the browser.
n When HA is enabled, the cluster can survive the loss of one data node without losing any
data. However, HA protects against the loss of only one node at a time, of any kind, so
simultaneously losing data and primary/replica nodes, or two or more data nodes, is not
supported. Instead, vRealize Operations Manager HA provides additional application level
data protection to ensure application level availability.
n When HA is enabled, it lowers vRealize Operations Manager capacity and processing by half,
because HA creates a redundant copy of data throughout the cluster, as well as the replica
backup of the primary node. Consider your potential use of HA when planning the number
and size of your vRealize Operations Manager cluster nodes. See Sizing the vRealize
Operations Manager Cluster.
VMware, Inc. 79
n When HA is enabled, deploy analytics cluster nodes on separate hosts for redundancy and
isolation. One option is to use anti-affinity rules that keep nodes on specific hosts in the
vSphere cluster.
If you cannot keep the nodes separate, you should not enable HA. A host fault would cause
the loss of more than one node, which is not supported, and all of vRealize Operations
Manager would become unavailable.
The opposite is also true. Without HA, you could keep nodes on the same host, and it would
not make a difference. Without HA, the loss of even one node would make all of vRealize
Operations Manager unavailable.
n When you power off the data node and change the network settings of the VM, this affects
the IP address of the data node. After this point, the HA cluster is no longer accessible and all
the nodes have a status of "Waiting for analytics". Verify that you have used a static IP
address.
n When you remove a node that has one or more vCenter adapters configured to collect data
from a HA-enabled cluster, one or more vCenter adapters associated with that node stops
collecting. You change the adapter configuration to pin them to another node before
removing the node.
n Administration UI shows the resource cache count, which is created for active objects only,
but the Inventory displays all objects. Therefore, when you remove a node from a HA-
enabled cluster allowing the vCenter adapters collect data and rebalance each node, the
Inventory displays a different quantity of objects from that shown in the Administration UI.
Preparing for Installation

When you prepare for your installation, consider some of these best practices, cluster, sizing and
scaling requirements.
Requirements
You have to consider important requirements while creating nodes in a vRealize Operations
Manager.
Using IPv6 with vRealize Operations Manager

vRealize Operations Manager supports both, Internet Protocol version 4 (IPv4) and Internet
Protocol version 6 (IPv6). However, you can use either IPv4 or IPv6 as IPv4 and IPv6 cannot be
combined. If the environment has a dual-stack support with both IPv4 and IPv6 protocols, all
nodes in the cluster must follow the same protocol. When using IPv6, the Prefer IPv6 flag must
be enabled during the OVF deployment for each node. The use of IPv6 with vRealize Operations
Manager requires that certain limitations be observed.
VMware, Inc. 80
Considerations While Using IPv6

n All vRealize Operations Manager cluster nodes, including remote collectors, must have IPv6
addresses. Do not mix IPv6 and IPv4.
n Use global IPv6 addresses only. Link-local addresses are not supported.
n If any nodes use DHCP, your DHCP server must be configured to support IPv6.
n DHCP is only supported on data nodes and remote collectors. Primary nodes and replica
nodes still require fixed addresses, which are true for IPv4 as well.
n Your DNS server must be configured to support IPv6.
n When adding nodes to the cluster, remember to enter the IPv6 address of the primary node.
n When registering a VMware vCenter instance within vRealize Operations Manager, place
square brackets around the IPv6 address of your VMware vCenter Server system if vCenter is
also using IPv6.
For example: [2015:0db8:85a3:0042:1000:8a2e:0360:7334]
Note that, even when vRealize Operations Manager is using IPv6, vCenter Server might still
have an IPv4 address. In that case, vRealize Operations Manager does not need the square
brackets.
Cluster Requirements
When you create the cluster nodes that make up vRealize Operations Manager, you have general
requirements that you must meet.
General vRealize Operations Manager Cluster Node Requirements

You have to follow some general requirements to create a node on your environment.
General Requirements
n vRealize Operations Manager version. All nodes must run the same vRealize Operations
Manager version.
For example, do not add a version 6.1 data node to a cluster of vRealize Operations Manager
6.2 nodes.
n Analytics Cluster Deployment Type. In the analytics cluster, all nodes must be the same kind
of deployment: vApp.
n Remote Collector Deployment Type. A remote collector node does not need to be the same
deployment type as the analytics cluster nodes.
When you add a remote collector of a different deployment type, the following clusters are
supported:
n vApp analytics cluster
n Analytics Cluster Node Sizing. In the analytics cluster, CPU, memory, and disk size must be
identical for all nodes.
VMware, Inc. 81
Primary, replica, and data nodes must be uniform in sizing.
n Remote Collector Node Sizing. Remote collector nodes may be of different sizes from each
other or from the uniform analytics cluster node size.
n Geographical Proximity. You may place analytics cluster nodes in different vSphere clusters,
but the nodes must reside in the same geographical location.
Different geographical locations are not supported.
n Virtual Machine Maintenance. When any node is a virtual machine, you may only update the
virtual machine software by directly updating the vRealize Operations Manager software.
For example, going outside of vRealize Operations Manager to access vSphere to update
VMware Tools is not supported.
n Redundancy and Isolation. If you expect to enable HA, place analytics cluster nodes on
separate hosts. See About vRealize Operations Manager High Availability .
n You can deploy remote collectors behind a firewall. You cannot use NAT between remote
collectors and analytics nodes.
Requirements for Solutions
Be aware that solutions might have requirements beyond those for vRealize Operations Manager
itself. For example, vRealize Operations Manager for Horizon View has specific sizing guidelines
for its remote collectors.
See your solution documentation, and verify any additional requirements before installing
solutions. Note that the terms solution, management pack, adapter, and plug-in are used
somewhat interchangeably.
vRealize Operations Manager Cluster Node Networking Requirements
When you create the cluster nodes that make up vRealize Operations Manager, the associated
setup within your network environment is critical to inter-node communication and proper
operation.
Networking Requirements
Important vRealize Operations Manager analytics cluster nodes need frequent communication
with one another. In general, your underlying vSphere architecture might create conditions where
some vSphere actions affect that communication. Examples include, but are not limited to,
vMotions, storage vMotions, HA events, and DRS events.
n The primary and replica nodes must use static IP address, or fully qualified domain name
(FQDN) with a static IP address.
Data and remote collector nodes can use dynamic host control protocol (DHCP).
n You can successfully reverse-DNS all nodes, including remote collectors, to their FQDN,
currently the node hostname.
Nodes deployed by OVF have their hostnames set to the retrieved FQDN by default.
VMware, Inc. 82
n All nodes, including remote collectors, must be bidirectionally routable by IP address or

FQDN.
n Do not separate analytics cluster nodes with network address translation (NAT), load
balancer, firewall, or a proxy that inhibits bidirectional communication by IP address or FQDN.
n Analytics cluster nodes must not have the same hostname.
n Place analytics cluster nodes within the same data center and connect them to the same local
area network (LAN).
n Place analytics cluster nodes on same Layer 2 network and IP subnet.
A stretched Layer 2 or routed Layer 3 network is not supported.
n Do not span the Layer 2 network across sites, which might create network partitions or
network performance issues.
n Packet Round Trip Time between the analytics cluster nodes must be 5 ms or lower.
n Network bandwidth between the analytics cluster nodes must be one gbps or higher.
n Do not distribute analytics cluster nodes over a wide area network (WAN).
To collect data from a WAN, a remote or separate data center, or a different geographic
location, use remote collectors.
n Remote collectors are supported through a routed network but not through NAT.
n Do not include an underscore in the hostname of any cluster node.
vRealize Operations Manager Cluster Node Best Practices

When you create the cluster nodes that make up vRealize Operations Manager, additional best
practices improve performance and reliability in vRealize Operations Manager.
Best Practices
n Deploy vRealize Operations Manager analytics cluster nodes in the same vSphere cluster in a
single datacenter and add only one node at a time to a cluster allowing it to complete before
adding another node.
n If you deploy analytics cluster nodes in a highly consolidated vSphere cluster, you might need
resource reservations for optimal performance.
Determine whether the virtual to physical CPU ratio is affecting performance by reviewing
CPU ready time and co-stop.
n Deploy analytics cluster nodes on the same type of storage tier.
n To continue to meet analytics cluster node size and performance requirements, apply storage
DRS anti-affinity rules so that nodes are on separate datastores.
n To prevent unintentional migration of nodes, set storage DRS to manual.
VMware, Inc. 83
n To ensure balanced performance from analytics cluster nodes, use ESXi hosts with the same
processor frequencies. Mixed frequencies and physical core counts might affect analytics
cluster performance.
n To avoid a performance decrease, vRealize Operations Manager analytics cluster nodes need
guaranteed resources when running at scale. The vRealize Operations Manager Knowledge
Base includes sizing spreadsheets that calculate resources based on the number of objects
and metrics that you expect to monitor, use of HA, and so on. When sizing, it is better to
over-allocate than under-allocate resources.
See Knowledge Base article 2093783.
n Because nodes might change roles, avoid machine names such as Primary, Data, Replica, and
so on. Examples of changed roles might include making a data node into a replica for HA, or
having a replica take over the primary node role.
n The NUMA placement is removed in the vRealize Operations Manager 6.3 and later.
Procedures related to NUMA settings from the OVA file follow:
Table 3-2. NUMA Setting

Action Description
Set the vRealize Operations Manager cluster status to 1 Shut down the vRealize Operations Manager cluster.
offline 2 Right-click the cluster and click Edit Settings >
Options > Advanced General.
3 Click Configuration Parameters. In the vSphere
Client, repeat these steps for each VM.
Remove the NUMA setting 1 From the Configuration Parameters, remove the
setting numa.vcpu.preferHT and click OK.
2 Click OK.
3 Repeat these steps for all the VMs in the vRealize
Operations cluster.
4 Power on the cluster.
Note To ensure the availability of adequate resources and continued product performance,
monitor vRealize Operations performance by checking its CPU usage, CPU ready and CPU
contention time.
Sizing and Scaling Requirements

The CPU, memory, and disk requirements that meet the needs of a particular environment
depend on the number and type of objects in your environment and the data collected. This
includes the number and type of adapters installed, the use of HA (High Availability), the duration
of data retention, and the quantity of specific data points of interest.
VMware updates Knowledge Base article 2093783 with the most current information about sizing
and scaling. The Knowledge Base article includes overall maximums and spreadsheet calculations
that provide a recommendation based on the number of objects and metrics you expect to
monitor.
VMware, Inc. 84
Installing vRealize Operations Manager

vRealize Operations Manager nodes are virtual appliance (vApp) based systems.
Deployment of vRealize Operations Manager

vRealize Operations Manager consists of one or more nodes in a cluster. To create these nodes,
you have to download and install the vRealize Operations Manager suitable to your environment.
OVF file
vRealize Operations Manager consists of one or more nodes, in a cluster. To create nodes,
you use the vSphere client to download and deploy the vRealize Operations Manager virtual
machine, once for each cluster node.
Create a Node by Deploying an OVF

vRealize Operations Manager consists of one or more nodes, in a cluster. To create nodes, you
use the vSphere client to download and deploy the vRealize Operations Manager virtual machine,
once for each cluster node.
Prerequisites
n Verify that you have permissions to deploy OVF templates to the inventory.
n If the ESXi host is part of a cluster, enable DRS in the cluster. If an ESXi host belongs to a non-
DRS cluster, all resource pool functions are disabled.
n If this node is to be the primary node, reserve a static IP address for the virtual machine, and
know the associated domain name, domain search path, domain name servers, default
gateway, and network mask values.
Plan to keep the IP address because it is difficult to change the address after installation.
n If this node is to be a data node that will become the HA replica node, reserve a static IP
address for the virtual machine, and know the associated domain name, domain search path,
domain name servers, default gateway, and network mask values.
In addition, familiarize yourself with HA node placement as described in About vRealize

Operations Manager High Availability .
n Preplan your domain and machine naming so that the deployed virtual machine name will
begin and end with alphabet (a–z) or digit (0–9) characters, and will only contain alphabet,
digit, or hyphen (-) characters. The underscore character (_) must not appear in the host
name or anywhere in the fully qualified domain name (FQDN).
Plan to keep the name because it is difficult to change the name after installation.
For more information, review the host name specifications from the Internet Engineering Task
Force. See www.ietf.org.
VMware, Inc. 85
n Preplan node placement and networking to meet the requirements described in General
vRealize Operations Manager Cluster Node Requirements and vRealize Operations Manager
Cluster Node Networking Requirements.
n If you expect the vRealize Operations Manager cluster to use IPv6 addresses, review the IPv6
limitations described in Using IPv6 with vRealize Operations Manager.
n Download the vRealize Operations Manager .ova file to a location that is accessible to the
vSphere client.
n If you download the virtual machine and the file extension is .tar, change the file extension
to .ova.
n Verify that you are connected to a vCenter Server system with a vSphere client, and log in to
the vSphere client.
Do not deploy vRealize Operations Manager from an ESXi host. Deploy only from vCenter
Server.
Procedure
1 Select the vSphere Deploy OVF Template option.
2 Enter the path to the vRealize Operations Manager .ova file.
3 Follow the prompts until you are asked to enter a name for the node.
4 Enter a node name. Examples might include Ops1, Ops2 or Ops-A, Ops-B.
Do not include nonstandard characters such as underscores (_) in node names.

Use a different name for each vRealize Operations Manager node.
5 Follow the prompts until you are asked to select a configuration size.
6 Select the size configuration that you need. Your selection does not affect disk size.
Default disk space is allocated regardless of which size you select. If you need additional
space to accommodate the expected data, add more disk after deploying the vApp.
7 Follow the prompts until you are asked to select the disk format.
Option Description
Thick Provision Lazy Zeroed Creates a virtual disk in a default thick format.
Thick Provision Eager Zeroed Creates a type of thick virtual disk that supports clustering features such as
Fault Tolerance. Thick provisioned eager-zeroed format can improve
performance depending on the underlying storage subsystem.
Select the thick provisioned eager-zero option when possible.
Thin Provision Creates a disk in thin format. Use this format to save storage space.
Snapshots can negatively affect the performance of a virtual machine and typically result in a
25–30 percent degradation for the vRealize Operations Manager workload. Do not use
snapshots.
VMware, Inc. 86
8 Click Next.
9 From the drop-down menu, select a Destination Network, for example, Network 1 = TEST,
and click Next.
10 Under Networking Properties, in case of a static IP, specify the associated Default Gateway,
Domain Name, Domain Search Path, Domain Name Servers, Network 1 IP Address, and
Network 1 Netmask values. In case of DHCP, leave all the fields blank. The primary node and
replica node require a static IP. A data node or remote collector node may use DHCP or a
static IP.
Note The hostname is configured using DHCP and DNS. If a static IP is used the hostname is
configured according to the node name specified during node configuration, after
deployment.
11 Optionally, in Properties, under Application, select the option for IPv6 .
12 Enter and confirm a password for the root account.
13 In the Timezone Setting, leave the default of UTC or select a time zone.
The preferred approach is to standardize on UTC. Alternatively, configure all nodes to the
same time zone.
14 Click Next.
15 Review the settings and click Finish.
16 If you are creating a multiple-node vRealize Operations Manager cluster, repeat through all
the steps to deploy each node.
What to do next
Use a Web browser client to configure a newly added node as the vRealize Operations Manager
primary node, a data node, a high availability primary replica node, or a remote collector node.
The primary node is required first.
Caution For security, do not access vRealize Operations Manager from untrusted or unpatched
clients, or from clients using browser extensions.
Installation Types
After you have installed vRealize Operations Manager product, you can either perform a new
installation, an express installation, or expand an existing installation.
n Express Installation
n New installation
n Expand Installation
VMware, Inc. 87
Figure 3-2. Getting Started Setup
Installing vRealize Operations Manager for a New User

After you install vRealize Operations Manager using an OVF or an installer, you are notified to the
main product UI page. You can create a single node or multiple nodes depending on your
environment.
Introduction to a New Installation

You can perform a new installation as a first-time user and create a single node to handle both
administration and data handling.
Figure 3-3. New Installation from the Setup page
Perform a New Installation on the vRealize Operations Manager product UI

You can create a single node and configure this as a primary node or create a primary node in a
cluster to handle additional data. All vRealize Operations Manager installations require a primary
node. With a single node cluster, administration and data functions are on the same primary
node. A multiple-node vRealize Operations Manager cluster contains one primary node and one
or more nodes for handling additional data.
Prerequisites
n Create a node by deploying the vRealize Operations Manager vApp.
n After it is deployed, note the fully qualified domain name (FQDN) or IP address of the node.
n If you plan to use a custom authentication certificate, verify that your certificate file meets the
requirements for vRealize Operations Manager.
Procedure
1 Navigate to the name or IP address of the node that will be the primary node of vRealize
Operations Manager.
The setup wizard appears, and you do not need to log in to vRealize Operations Manager.
2 Click New Installation.
VMware, Inc. 88
3 Click Next.
4 Enter and confirm a password for the admin user account, and click Next.
Passwords require a minimum of 8 characters, one uppercase letter, one lowercase letter,
one digit, and one special character.
The user account name is admin by default and cannot be changed.
5 Select whether to use the certificate included with vRealize Operations Manager or to install
one of your own.
a To use your own certificate, click Browse, locate the certificate file, and click Open to load
the file in the Certificate Information text box.
b Review the information detected from your certificate to verify that it meets the
requirements for vRealize Operations Manager.
6 Click Next.
7 Enter a name for the master node.
For example: Ops-Master
8 Enter the URL or IP address for the Network Time Protocol (NTP) server with which the
cluster will synchronize.
For example: nist.time.gov
9 Click Add.
Leave the NTP blank to have vRealize Operations Manager manage its own synchronization
by having all nodes synchronize with the master node and replica node.
10 Click the add icon to add an another node. This is optional.
a Enter the Node Name and Node Address.
b Select the Current Cluster Role.
Note By checking the Enable High Availability for this cluster option, you can select a node
from the added list of nodes to be the replica node. Although, only one node from the list can
be chosen as a replica node. Before saving the data, you can also delete the node from the
list of added nodes.
11 Click Next, and click Finish.
The administration interface appears, and it takes a moment for vRealize Operations Manager
to finish adding the primary node.
Results
You have created a primary node to which you can add more nodes.
VMware, Inc. 89
What to do next
After creating the primary node, you have the following options.
n Create and add data nodes to the unstarted cluster.
n Create and add remote collector nodes to the unstarted cluster.
n Click Start vRealize Operations Manager to start the single-node cluster, and log in to finish
configuring the product.
The cluster might take from 10 to 30 minutes to start, depending on the size of your cluster
and nodes. Do not make changes or perform any actions on cluster nodes while the cluster is
starting.
About the vRealize Operations Manager Master Node
The master node is the primary node and is the required, initial node in your vRealize Operations
Manager cluster.
The primary node performs administration for the cluster and must be online before you
configure any new nodes. In addition, the primary node must be online before other nodes are
brought online. If the primary node and replica node go offline together, bring them back online
separately. Bring the primary node online first, and then bring the replica node online. For
example, if the entire cluster were offline for any reason, bring the primary node online first.
Advantages of a New installation

You can use the new installation to create a new primary node during the first installation of
vRealize Operations Manager. With the primary node in place, you can then start adding more
nodes to form a cluster and then define an environment for your organization.
In a single-node clusters, administration and data are on the same primary node. A multiple-node
cluster includes one primary node and one or more data nodes. In addition, there might be
remote collector nodes, and there might be one replica node used for high availability. For more
information on creating a primary node, see About the vRealize Operations Manager Master
Node.
Installing vRealize Operations Manager as an Administrator

As an administrator, you can install several instances of vRealize Operations Manager build in
your VM environment.
Introduction to Express Installation

Express installation is one possible way to create primary nodes, add data nodes, form clusters,
and test your connection status. You can use express installation to save time and speed up the
process of installation when compared to a new installation. Do not to use this feature unless the
user is an administrator.
VMware, Inc. 90
Figure 3-4. Express Installation from the Setup screen
Perform an Express Installation on the vRealize Operations Manager product UI

Use express installation on the vRealize Operations Manager cluster to create a primary node.
Select express installation option when installing for the first time.
Prerequisites
Verify that you have a static IP address created from an OVF file.
Procedure
1 Navigate to the name or IP address of the node that will be the primary node of vRealize
Operations Manager.
2 Click Express Installation.
3 Click Next.
4 Enter and confirm a password for the admin user account, and click Next.
Passwords require a minimum of 8 characters, one uppercase letter, one lowercase letter,
one digit, and one special character.
The user account name is admin by default and cannot be changed.
5 Click Next.
6 Click Finish.
Results
You have created a primary node to which you can add more nodes.
Advantages of an Express Installation

Express installation saves time when compared to a new installation to create a new primary
node. The express installation uses the default certificates, which differ from one organization to
another. This feature is mainly used by the developers or the administrators.
Expand an Existing Installation of vRealize Operations Manager

Use this option to add a node to an existing vRealize Operations Manager cluster. You can use
this option if you have already configured a primary node and you want to increase the capacity
by adding more nodes to your cluster.
VMware, Inc. 91
Introduction to Expand an Existing Installation

You can deploy and configure additional nodes so that vRealize Operations Manager can support
larger environments. A primary node always requires an additional node for a cluster to monitor
your environment. With expanding your installation, you can add more than one node to your
cluster.
Adding Data Nodes
Data nodes are the additional cluster nodes that allow you to scale out vRealize Operations
Manager to monitor larger environments.
You can dynamically scale out vRealize Operations Manager by adding data nodes without
stopping the vRealize Operations Manager cluster. When you scale out the cluster by 25% or
more, you should restart the cluster to allow vRealize Operations Manager to update its storage
size, and you might notice a decrease in performance until you restart. A maintenance interval
provides a good opportunity to restart the vRealize Operations Manager cluster.
In addition, the product administration options include an option to re-balance the cluster, which
can be done without restarting. Rebalancing adjusts the vRealize Operations Manager workload
across the cluster nodes.
Figure 3-5. Expand an existing installation from the Setup screen
Note Do not shut down online cluster nodes externally or by using any means other than the
vRealize Operations Manager interface. Shut down a node externally only after taking it offline in
the vRealize Operations Manager interface.
Expand an Existing Installation to Add a Data Node

Larger environments with multiple-node vRealize Operations Manager clusters contain one
primary node and one or more data nodes for additional data collection, storage, processing, and
analysis.
Prerequisites
n Create nodes by deploying the vRealize Operations Manager vApp.
n Create and configure the primary node.
n Note the fully qualified domain name (FQDN) or IP address of the primary node.
Procedure
1 In a Web browser, navigate to the name or IP address of the node that will become the data
node.
VMware, Inc. 92
2 Click Expand an Existing Installation.
3 Click Next.
4 Enter a name for the node (for example, Data-1).
5 From the Node Type drop-down, select Data.
6 Enter the FQDN or IP address of the master node and click Validate.
7 Select Accept this certificate and click Next.
If necessary, locate the certificate on the primary node and verify the thumbprint.
8 Verify the vRealize Operations Manager administrator username of admin.
9 Enter the vRealize Operations Manager administrator password.
Alternatively, instead of a password, type a pass-phrase that you were given by your
vRealize Operations Manager administrator.
The administration interface appears, and it takes a moment for vRealize Operations Manager
to finish adding the data node.
What to do next
After creating a data node, you have the following options.
n New, unstarted clusters:
n Create and add more data nodes.
n Create and add remote collector nodes.
n Create a high availability primary replica node.
n Click Start vRealize Operations Manager to start the cluster, and log in to finish
The cluster might take from 10 to 30 minutes to start, depending on the size of your
cluster and nodes. Do not make changes or perform any actions on cluster nodes while
the cluster is starting.
n Established, running clusters:
n Create and add more data nodes.
n Create a high availability primary replica node, which requires a cluster restart.
Advantages of an Expanding an Installation

A data node shares the load of performing vRealize Operations Manager analysis and it can also
have an adapter installed to perform collection and data storage from the environment. You must
have a primary node before you add data nodes to form a cluster.
VMware, Inc. 93
Installing vRealize Operations Manager on VMware Cloud on AWS

You can use your on-premises vRealize Operations Manager to manage and monitor your cloud
infrastructure on VMware Cloud by simply adding your VMware Cloud based vCenter Server into
vRealize Operations Manager. You can extend the current set of monitoring, troubleshooting,
optimization, and remediation processes of vRealize Operations Manager on to VMware Cloud. It
provides you with a hybrid view of your environment.
Prerequisites
n A VPN or a direct connection to set up the bidirectional access between the nodes and
remote collectors of vRealize Operations Manager on-premises and VMware Cloud.
n Scale the existing vRealize Operations Manager cluster before adding the new VMware Cloud
SDDC sites. To get the appropriate sizing, see vRealize Operations Manager Online Sizer.
Known Limitations
n The cloudadmin@vmc.local user in VMware Cloud has limited privileges. In-guest memory
collection using VMware tools is not supported with virtual machines on VMware Cloud.
Active and consumed memory utilizations continue to work in this case.
n Cost Computation is not supported and computing cost is disabled on the VMware Cloud
inventory.
n VMware manages the vCenter Server and ESXi hosts and so, the existing out of box
compliance checks of the hardening guide do not apply to the VMware Cloud objects. These
checks are disabled by default.
n Only migration planning scenarios with VMware Cloud are supported.
n Workload optimization including pDRS, business intent-based placement, and operational

intent-based placement, is not supported with VMware Cloud since VMware manages cluster
configurations.
Using vRealize Operations Manager on-premises on VMware Cloud on AWS

Extend the monitoring capabilities of your on-premises vRealize Operations Manager to monitor
the VMware Cloud vCenter Server by connecting the VMware Cloud vCenter Server as an end
point inside vRealize Operations Manager. Create an adapter instance both for vCenter Server
and VMware vSAN to collect data from VMware Cloud and bring that into vRealize Operations
Manager. You can either connect directly to thevCenter Server or use a remote collector which
can be deployed inside a VMware Cloud SDDC to ensure that the data can be compressed and
encrypted.
Note If the network latency between vRealize Operations Manager primary node and VMware
Cloud is greater than 5 milliseconds, you should deploy remote collectors in VMware Cloud.
VMware, Inc. 94
Procedure
1 Deploy the vRealize Operations Manager remote collectors in VMware Cloud, see Create a
Remote Collector.
Note Deploy the OVF in the SDDC-Datacenter level and select the Compute Resource Pools
and validate your deployment. You can only select the workload datastore for storage when
deploying the OVF in VMware Cloud.
Since VMware Cloud is set in an isolated network, the remote collectors cannot view or
connect to the primary node. To collect data, you must set up the bidirectional access
between the vRealize Operations Manager primary node and the remote collectors you have
created. To do so, you can use a VPN or create a direct connection with no-NAT.
2 Add and configure an adapter instance in the vRealize Operations Manager cluster in VMware
Cloud. To configure a vCenter adapter, see Configure a vCenter Adapter Instance in vRealize
Operations Manager. To configure a vSAN adapter, see Configure a vSAN Adapter Instance.
Note Incase of a vCenter adapter instance, set the Cloud Type to VMware Cloud on AWS.
Ensure that the remote collector is assigned to the adapter instance and the data collection
happens through the remote collectors that you have set up. Select the newly deployed
remote collectors for Collectors/Groups under Advanced Settings.
Figure 3-6. vRealize Operations On-Premises collecting data from VMware Cloud and AWS
without remote data collectors
AWS
VMC - US West (Oregon)
On-Prem
Datacenter
- San Diego NSX
vROps
vCenter NSX vSAN
vRealize Operation Cluster
VMC - US East (Ohio)

NSX
vCenter NSX vSAN Servers

NSX
APP
vCenter NSX vSAN
Storage Network Container Apps
VMware, Inc. 95
Figure 3-7. vRealize Operations On-Premises collecting data from VMware Cloud and AWS
with remote data collectors
AWS
vROps
vROps Remote Collector(s)
On-Prem
Datacenter
- San Diego NSX
vROps
vCenter NSX vSAN
vRealize Operations cluster
NSX

vROps
APP vROps Remote Collector(s)
NSX
vCenter NSX vSAN
Deploying vRealize Operations Manager on VMware Cloud on AWS

If you have moved a large part of your environment into VMware Cloud, you can deploy or
migrate your vRealize Operations Manager instance into VMware Cloud directly. After the
vRealize Operations Manager cluster is deployed on VMware Cloud, you can collect data from
other VMware Cloud SDDCs and the SDDC located on-prem using remote collectors. You can
deploy remote collectors to send over data into the centralized analytics cluster deployed in
VMware Cloud.
Procedure
1 Deploy the vRealize Operations Manager cluster in VMware Cloud, see Deployment of
Note Deploy the OVF template in the VMware Cloud on the data center level. VMware
Cloud has two resource pools, the regular workload and the administrative workload. You can
only deploy the new OVF template in the workload resource pool.
VMware, Inc. 96
2 Deploy the remote collectors in vRealize Operations Manager, see Create a Remote Collector.
Note VMware Cloud is set in an isolated network and so, the remote collectors cannot view
or connect to the primary node. To collect data, you must set up the bidirectional access
between the vRealize Operations Manager primary node and the remote collector you have
created. To do so, you can use a VPN or a direct connection with no NAT.
3 Add and configure an adapter instance in the vRealize Operations Manager cluster in VMware
Cloud. To configure a vCenter adapter, see Configure a vCenter Adapter Instance in vRealize
Operations Manager. To configure a vSAN adapter, see Configure a vSAN Adapter Instance.
Note If the Remote collectors are deployed on-premises, set Cloud Type to Private Cloud.
However, if you deploy remote collectors in another VMware Cloud, set the Cloud Type to
VMware Cloud on AWS.
Ensure that the remote collector is assigned to the adapter instance and the data collection
of the adapter instance happens through the remote collectors that you have set up. Select
the newly deployed remote collectors for Collectors/Groups under Advanced Settings.
VMware, Inc. 97
Figure 3-8. vRealize Operations in VMware Cloud collecting data from other VMware Cloud
SDDC, AWS and On-Premise with remote data collectors
AWS
On-Prem
Datacenter
- San Diego
vROps vROps
vROps Remote Collector(s) vRealize Operations Cluster
NSX
NSX
vCenter NSX vSAN


APP
vROps
On-Prem
Datacenter NSX
- Seattle
vROps vCenter NSX vSAN
NSX
APP
Resize your Cluster by Adding Nodes

You can deploy and configure additional nodes so that vRealize Operations Manager can support
larger environments.
VMware, Inc. 98
Figure 3-9. Workflow - Resize your cluster
Start
Create role-less nodes Configure the master node
Enable HA Configure a data node
Start vRealize Operations Manager Configure a new installation
Select vCenter monitoring policy goals Configure the built-in vCenter Solution
Add and configure more solutions
Monitor your environment
Gathering More Data by Adding a vRealize Operations Manager

Remote Collector Node
You deploy and configure remote collector nodes so that vRealize Operations Manager can add
to its inventory of objects to monitor without increasing the processing load on vRealize
Operations Manager analytics.
Run the Setup Wizard to Create a Remote Collector Node

In distributed vRealize Operations Manager environments, remote collector nodes increase the
inventory of objects that you can monitor without increasing the load on vRealize Operations
Manager in terms of data storage, processing, or analysis.
Prerequisites
During vApp deployment, select a remote collector size option.
n Ensure any remote adapter instance is running on the correct remote collector. If you have
only one adapter instance, select Default collector group.
n Note the fully qualified domain name (FQDN) or an IP address of the primary node.
VMware, Inc. 99
n Verify that there is one remote collector already added before you add another remote
collector.
Note Remote collectors when added in parallel cause a cluster to crash.
Procedure
1 In a Web browser, navigate to the name or IP address of the deployed OVF that will become
the remote collector node.
2 Click Expand an Existing Installation.
3 Click Next.
4 Enter a name for the node, for example, Remote-1.
5 From the Node Type drop-down menu, select Remote Collector.
6 Enter the FQDN or IP address of the master node and click Validate.
7 Select Accept this certificate and click Next.
If necessary, locate the certificate on the primary node and verify the thumbprint.
8 Verify the vRealize Operations Manager administrator username of admin.
9 Enter the vRealize Operations Manager administrator password.
Alternatively, instead of a password, type a passphrase that you were given by the vRealize
Operations Manager administrator.
The administration interface appears, and it takes several minutes for vRealize Operations
Manager to finish adding the remote collector node.
What to do next
After creating a remote collector node, you have the following options.
n Create and add data nodes.
n Create and add more remote collector nodes.
n Create a high availability primary replica node.
VMware, Inc. 100

n Create and add more remote collector nodes.
n Create a high availability primary replica node, which requires a cluster restart.
Adding High Availability to vRealize Operations Manager

You can dedicate one vRealize Operations Manager cluster node to serve as a replica node for
the vRealize Operations Manager primary node.
Run the Setup Wizard to Add a Primary Replica Node

You can convert a vRealize Operations Manager data node to a replica of the primary node,
which adds high availability (HA) for vRealize Operations Manager.
Note If the cluster is running, enabling HA restarts the cluster.
If you convert a data node that is already in use for data collection and analysis, adapters and
data connections that were provided through that data node fail over to other data nodes.
You may add HA to the vRealize Operations Manager cluster at installation time or after vRealize
Operations Manager is up and running. Adding HA at installation is less intrusive because the
cluster has not yet started.
Prerequisites
n Create and configure a data node with a static IP address.
n Note the fully qualified domain name (FQDN) or IP address of the primary node.
Procedure
1 In a Web browser, navigate to the master node administration interface.
https://master-node-name-or-ip-address/admin
2 Enter the vRealize Operations Manager administrator username of admin.
3 Enter the vRealize Operations Manager administrator password and click Log In.
4 Under High Availability, click Enable.
5 Select a data node to serve as the replica for the master node.
6 Select the Enable High Availability for this cluster option, and click OK.
If the cluster was online, the administration interface displays progress as vRealize Operations
Manager configures, synchronizes, and rebalances the cluster for HA.
VMware, Inc. 101

7 If the master node and replica node go offline, and the master remains offline for any reason
while the replica goes online, the replica node does not take over the master role, take the
entire cluster offline, including data nodes and log in to the replica node command line
console as a root.
8 Open $ALIVE_BASE/persistence/persistence.properties in a text editor.
9 Locate and set the following properties:
db.role=MASTER
db.driver=/data/vcops/xdb/vcops.bootstrap
10 Save and close persistence.properties.
11 In the administration interface, bring the replica node online, and verify that it becomes the
master node and bring the remaining cluster nodes online.
What to do next
After creating a primary replica node, you have the following options.
vRealize Operations Manager Cluster and Node Maintenance

You perform cluster and node maintenance procedures to help your vRealize Operations
Manager perform more efficiently cluster and node maintenance involves activities such as
changing the online or offline state of the cluster or individual nodes, enabling or disabling high
availability (HA), reviewing statistics related to the installed adapters, and rebalancing the
workload for better performance.
You perform most vRealize Operations Manager cluster and node maintenance using the Cluster
Management page in the product interface, or the Cluster Status and Troubleshooting page in
the administration interface. The administration interface provides more options than the product
interface.
VMware, Inc. 102

Table 3-3. Cluster and Node Maintenance Procedures

Procedure Interface Description
Change Cluster Status Administration/Product You can change the status of a node to online or
offline.
In a high availability (HA) cluster, taking the
primary or replica offline causes vRealize
Operations Manager to run from the remaining
node and for HA status to be degraded.
Any manual or system action that restarts the
cluster brings all vRealize Operations Manager
nodes online, including any nodes that you had
taken offline.
If you take a data node that is part of a multi-node
cluster offline and then bring it back online, the
End Point Operations Management adapter does
not automatically come back online. To bring the
End Point Operations Management adapter online,
select the End Point Operations Management
adapter in the Inventory and click the Start
Collector icon .
Enable or Disable High Administration Enabling or disabling high availability requires the
Availability cluster to have at least one data node, with all
nodes online or all offline. You cannot use Remote
Collector nodes.
Disabling high availability removes the replica
node and restarts the vRealize Operations
Manager cluster.
After you disable high availability, the replica node
vRealize Operations Manager converts back to a
data node and restarts the cluster.
Generate Passphrase Administration You can generate a passphrase to use instead of

the administrator credentials to add a node to this
cluster.
The passphrase is only valid for a single use.
Remove a Node Administration When you remove a node, you lose data that the
node had collected unless you are running in high
availability (HA) mode. HA protects against the
removal or loss of one node.
You must not re-add nodes to vRealize Operations
Manager that you already removed. If your
environment requires more nodes, add new nodes
instead.
When you perform maintenance and migration
procedures, you should take the node offline, not
remove the node.
VMware, Inc. 103

Table 3-3. Cluster and Node Maintenance Procedures (continued)

Procedure Interface Description
Configure NTP Product The nodes in vRealize Operations Manager cluster

synchronize with each other by standardizing on
the primary node time or by synchronizing with an
external Network Time Protocol (NTP) source.
Rebalance the Cluster Product You can rebalance adapter, disk, memory, or
network load across vRealize Operations Manager
cluster nodes to increase the efficiency of your
environment.
Cluster Management
vRealize Operations Manager includes a central page where you can monitor and manage the
nodes in your vRealize Operations Manager cluster as well as the adapters that are installed on
the nodes.
How Cluster Management Works

Cluster management lets you view and change the online or offline state of the overall vRealize
Operations Manager cluster or the individual nodes. In addition, you can enable or disable high
availability (HA) and view statistics related to the adapters that are installed on the nodes.
Where You Find Cluster Management

In the left pane, select Administration > Cluster Management.
Cluster Management Options

The options include cluster-level monitoring and management features.
Table 3-4. Initial Setup Status Details

Option Description
Cluster Status Displays the online, offline, or unknown state of the

vRealize Operations Manager cluster.
High Availability Indicates whether HA is enabled, disabled, or degraded.
vRealize Operations Manager provides node-level information as well as a toolbar for taking
nodes online or offline.
Table 3-5. Nodes in the vRealize Operations Manager Cluster

Option Description
Node Name Machine name of the node.

The node that you are logged into displays a dot next to
the name.
Node Address Internet protocol (IP) address of the node. Primary and
replica nodes require static IP addresses. Data nodes may
use DHCP or static IP.
VMware, Inc. 104

Table 3-5. Nodes in the vRealize Operations Manager Cluster (continued)

Option Description
Cluster Role Type of vRealize Operations Manager node: primary, data,

replica, or remote collector.
State Running, Not Running, Going Online, Going Offline,

Inaccessible, Failure, Error
Status Online, offline, unknown, or other condition of the node.
Objects in Process Total environment objects that the node currently

monitors.
Metrics in Process Total metrics that the node has collected since being
added to the cluster.
Build vRealize Operations Manager software build number

installed on the node.
Version vRealize Operations Manager software version installed on

the node.
Deployment Type Type of machine on which the node is running: vApp
In addition, there are adapter statistics for the selected node.
Table 3-6. Adapters on Server

Option Description
Name Name that the installing user gave to the adapter.
Status Indication of whether the adapter is collecting data or not.
Objects Being Collected Total environment objects that the adapter currently
monitors.
Metrics Being Collected Total metrics that the adapter has collected since being
Last Collection Time Date and time of the most recent data collection by the
adapter.
Added On Date and time when the adapter was installed on the node.
vRealize Operations Manager Post-Installation

Considerations
After you install vRealize Operations Manager, there are post-installation tasks that might need
your attention.
About Logging In to vRealize Operations Manager

Logging in to vRealize Operations Manager requires that you point a Web browser to the fully
qualified domain name (FQDN) or IP address of a node in the vRealize Operations Manager
cluster.
VMware, Inc. 105

When you log in to vRealize Operations Manager, there are a few things to keep in mind.
n After initial configuration, the product interface URL is:
https://node-FQDN-or-IP-address
n Before initial configuration, the product URL opens the administration interface instead.
n After initial configuration, the administration interface URL is:
https://node-FQDN-or-IP-address/admin
n The administrator account name is admin. The account name cannot be changed.
n The admin account is different from the root account used to log in to the console, and does
not need to have the same password.
n When logged in to the administration interface, avoid taking the node that you are logged
into offline and shutting it down. Otherwise, the interface closes.
n The number of simultaneous login sessions before a performance decrease depends on

factors such as the number of nodes in the analytics cluster, the size of those nodes, and the
load that each user session expects to put on the system. Heavy users might engage in
significant administrative activity, multiple simultaneous dashboards, cluster management
tasks, and so on. Light users are more common and often require only one or two
dashboards.
The sizing spreadsheet for your version of vRealize Operations Manager contains further
detail about simultaneous login support. See Knowledge Base article 2093783.
n You cannot log in to a vRealize Operations Manager interface with user accounts that are
internal to vRealize Operations Manager, such as the maintenance Admin account.
n You cannot open the product interface from a remote collector node, but you can open the
administration interface.
n For supported Web browsers, see the vRealize Operations Manager Release Notes for your
version.
After You Log In

After you log in to vRealize Operations Manager from a web browser, you see the Quick Start
page. The Quick Start page provides an overview of key areas of vRealize Operations Manager.
You can set any dashboard to be the landing page instead of the Quick Start page. Click the
Actions menu on a dashboard that you want to set as the default Quick Start page and select Set
as Home Page. You cannot modify the default Quick Start page.
Upon first log-in, you must set the currency in the Global Settings page. You can do so from the
message that you see in the Quick Start page when you log in for the first time. Optionally, you
can close the message. Once you set a currency, you cannot change it.
VMware, Inc. 106

A new license key is required for vRealize Operations Manager 7.0 and later versions. All license
keys except vSOM Enterprise Plus and its add-ons are invalidated. The product will work in
evaluation mode until a new valid license key, which can be obtained from the MyVMware portal,
is installed. After login, if you see the "You are using an evaluation license. Please
consider applying a new license by the end of the evaluation period." message in the
Quick Start page, you must add a new license before the end of the 60-day evaluation period in
the Licensing page. To add a new license, from the message, click Actions > Go to Licensing.
Note If you added new licenses when you upgraded to vRealize Operations Manager 7.0, you
may skip this step.
The default Quick Start page has the following sections.
Optimize Performance
Displays links to workload optimization, recommendations, and optimization history.
Optimize Capacity
Displays links to asset capacity, reclaim resources, plan scenarios and assess Costs.
Troubleshoot
Displays links to alerts, logs troubleshooting of objects by type. The Apps in Wavefront link
opens the configured URL if you have already configured Wavefront. If Wavefront is not
configured, the Application Monitoring with Wavefront page opens.
Manage Configuration
Displays links to the compliance page and helps you troubleshoot compliance by object type.
Links to the dashboard that displays the configuration of your virtual machines.
Click View More to access the following sections:
Extend Monitoring
Displays links to apps in the VMware Solutions Exchange website.
Learn and Evaluate
Displays links to the vRealize Operations Guided Tour, Evaluate vRealize Suite and to open
the vRealize Operations Manager micro-site.
Run Assessments
Displays links to dashboards that help you assess vSphere Optimization and Hybrid Cloud.
Secure the vRealize Operations Manager Console

After you install vRealize Operations Manager, you secure the console of each node in the cluster
by logging in for the first time.
VMware, Inc. 107

Procedure
1 Locate the node console in vCenter or by direct access. In vCenter, use Alt+F1 to access the
login prompt.
For security, vRealize Operations Manager remote terminal sessions are disabled by default.
2 Log in as root.
vRealize Operations Manager prevents you from accessing the command prompt until you
create a root password.
3 When prompted for a password, press Enter.
4 When prompted for the old password, press Enter.
5 When prompted for the new password, enter the root password that you want, and note it
for future reference.
6 Re-enter the root password.
7 Log out of the console.
Log in to a Remote vRealize Operations Manager Console Session

As part of managing or maintaining the nodes in your vRealize Operations Manager cluster, you
might need to log in to a vRealize Operations Manager node through a remote console.
For security, remote login is disabled in vRealize Operations Manager by default. To enable
remote login, perform the following steps.
Procedure
1 Log in to a vCenter Server system using a vSphere Web Client and select a vCenter Server
instance in the vSphere Web Client navigator.
a Find the Virtual Machine in the hierarchy and click Launch Console.
Note You can also use the vSphere Client to launch the node console by direct access
after enabling the SSHD service.
The virtual machine console opens in a new tab of the Web browser.
2 Locate the node console and click Launch Console.
3 In vCenter, use Alt+F1 to access the login prompt and log in as root. If this is the first time
logging in, you must set a root password.
a When prompted for a password, press Enter.
b When prompted for the old password, press Enter.
c When prompted for the new password, enter the root password that you want, and note
it for future reference.
d Re-enter the root password.
VMware, Inc. 108

4 To enable remote login, enter the following command:
service sshd start
About New vRealize Operations Manager Installations

A new vRealize Operations Manager installation requires that you deploy and configure nodes.
Then, you add solutions for the kinds of objects to monitor and manage.
After you add solutions, you configure them in the product and add monitoring policies that
gather the kind of data that you want.
Log In and Continue with a New Installation

To finish a new vRealize Operations Manager installation, you log in and complete a one-time
process to license the product and configure solutions for the kinds of objects that you want to
monitor.
Prerequisites
n Create the new cluster of vRealize Operations Manager nodes.
n Verify that the cluster has enough capacity to monitor your environment. See Sizing the
vRealize Operations Manager Cluster.
Procedure
1 In a Web browser, navigate to the IP address or fully qualified domain name of the primary
node.
2 Enter the username admin and the password that you defined when you configured the
primary node, and click Login.
Because this is the first time you are logging in, the administration interface appears.
3 To start the cluster, click Start vRealize Operations Manager.
4 Click Yes.
The cluster might take from 10 to 30 minutes to start, depending on your environment. Do
not make changes or perform any actions on cluster nodes while the cluster is starting.
5 When the cluster finishes starting and the product login page appears, enter the admin
username and password again, and click Login.
A one-time licensing wizard appears.
6 Click Next.
7 Read and accept the End User License Agreement, and click Next.
VMware, Inc. 109

8 Enter your product key, or select the option to run vRealize Operations Manager in evaluation
mode.
Your level of product license determines what solutions you may install to monitor and
manage objects.
n Standard. vCenter only
n Advanced. vCenter plus other infrastructure solutions
n Enterprise. All solutions
vRealize Operations Manager does not license managed objects in the same way that
vSphere does, so there is no object count when you license the product.
Note When you transition to the Standard edition, you no longer have the Advanced and
Enterprise features. After the transition, delete any content that you created in the other
versions to ensure that you comply with EULA and verify the license key which supports the
Advanced and Enterprise features.
9 If you entered a product key, click Validate License Key.
10 Click Next.
11 Select whether or not to return usage statistics to VMware, and click Next.
12 Click Finish.
The one-time wizard finishes, and the vRealize Operations Manager interface appears.
What to do next
n Use the vRealize Operations Manager interface to configure the solutions that are included
with the product.
n Use the vRealize Operations Manager interface to add more solutions.
n Use the vRealize Operations Manager interface to add monitoring policies.
Upgrade, Backup and Restore

You can update your existing vRealize Operations Manager deployments to a newly released
version.
When you perform a software update, you need to make sure you use the correct PAK file for
your cluster. A good practice is to take a snapshot of the cluster before you update the software,
but you must remember to delete the snapshot once the update is complete.
If you have customized the content that vRealize Operations Manager provides such as alerts,
symptoms, recommendations, and policies, and you want to install content updates, clone the
content before performing the update. In this way, you can select the option to reset out-of-the-
box content when you install the software update, and the update can provide new content
without overwriting customized content.
VMware, Inc. 110

Obtain the Software Update PAK File

Each type of cluster update requires a specific PAK file. Make sure you are using the correct one.
Download the Correct PAK files

To update your vRealize Operations Manager environment, you need to download the right PAK
file for the clusters you wish to upgrade. Notice that only the Virtual Appliance clusters use an OS
Update PAK file. User modifications in the /etc/hosts of each node might be reset when you
apply the OS update PAK file of vRealize Operations. Incase modifications are required, you can
manually update the hosts file after completing the software update.
To download the PAK files for vRealize Operations Manager, go to Download VMware vRealize
Operations page.
Table 3-7. Specific PAK Files for Different Cluster Types

Cluster Type OS Update Product Update
Virtual Appliance clusters. vRealize_Operations_Manager-VA-OS- vRealize_Operations_Manager-VA-

Use both the OS and the product xxx.pak xxx.pak
update PAK files.
Create a Snapshot as Part of an Update

It's a good practice to create a snapshot of each node in a cluster before you update a vRealize
Operations Manager cluster. Once the update is complete, you must delete the snapshot to avoid
performance degradation.
For more information about snapshots, see the vSphere Virtual Machine Administration
documentation.
Procedure
1 Log into the vRealize Operations Manager Administrator interface at https://<master-node-

FQDN-or-IP-address>/admin.
2 Click Take Offline under the cluster status.
3 When all nodes are offline, open the vSphere client.
4 Right-click a vRealize Operations Manager virtual machine.
5 Click Snapshot and then click Take Snapshot.
a Name the snapshot. Use a meaningful name such as "Pre-Update."
b Uncheck the Snapshot the Virtual Machine Memory check box.
c Uncheck the Ensure Quiesce Guest File System (Needs VMware Tools installed) check
box.
d Click OK.
6 Repeat these steps for each node in the cluster.
VMware, Inc. 111

What to do next
Start the update process as described in Install a Software Update.
How To Preserve Customized Content

When you upgrade vRealize Operations Manager, it is important that you upgrade the current
versions of content types that allow you to alert on and monitor the objects in your environment.
With upgraded alert definitions, symptom definitions, and recommendations, you can alert on the
various states of objects in your environment and identify a wider range of problem types. With
upgraded views, you can create dashboards and reports to easily identify and report on
problems in your environment.
You might need to perform certain steps before you upgrade the alert definitions, symptom
definitions, recommendations, and views in your vRealize Operations Manager environment.
n If you customized any of the alert definitions, symptom definitions, recommendations, or

views that were provided with previous versions of vRealize Operations Manager, and you
want to retain those customized versions, perform the steps in this procedure.
n If you did not customize any of the alert definitions, symptom definitions, recommendations,
or views that were provided with previous versions of vRealize Operations Manager, you do
not need to back them up first. Instead, you can start the upgrade, and during the upgrade
select the check box named Reset out-of-the-box content.
Prerequisites
You previously customized versions of your alert definitions, symptom definitions,

recommendations, or views.
Procedure
1 Before you begin the upgrade to vRealize Operations Manager, back up the changes to your
alert definitions, symptom definitions, recommendations, and views by cloning them.
2 Start the upgrade of vRealize Operations Manager.
3 During the upgrade, select the check box named Reset out-of-the-box content.
Results
After the upgrade completes, you have preserved your customized versions of alert definitions,
symptom definitions, recommendations, and views, and you have the current versions that were
installed during the upgrade.
What to do next
Review the changes in the upgraded alert definitions, symptom definitions, recommendations,
and views. Then, determine whether to keep your previously modified versions, or to use the
upgraded versions.
VMware, Inc. 112

Back Up and Restore

Back up and restore your vRealize Operations Manager system regularly to avoid downtime and
data loss in case of a system failure. If your system does fail, you can restore the system to the
last full or incremental backup.
You can back up and restore vRealize Operations Manager single or multi-node clusters by using
vSphere Data Protection or other backup tools. You can perform full, differential, and incremental
backups and restores of virtual machines.
To back up and restore vRealize Suite components by using vSphere Data Protection and
NetBackup, see the Back up and Restore section in the vRealize Suite Information Center.
It is highly recommended to take a backup during quiet periods. Since a snapshot based backup
happens at the block level, it is important that there are limited or no changes being performed
by a user on the cluster configuration. This will ensure that you have a healthy backup.
It is best to take the cluster offline before you back up the vRealize Operations Manager nodes.
This will ensure the data consistency across the nodes and internally in the node. You can either
shut down the VM before the backup or enable quiescing.
If the cluster remains online, backup your vRealize Operations Manager multi-node cluster by
using vSphere Data Protection or other backup tools, disable quiescing of the file system.
Note All nodes are backed up and restored at the same time. You cannot back up and restore
individual nodes.
vRealize Operations Manager Software Updates

vRealize Operations Manager includes a central page where you can manage updates to the
product software.
How Software Updates Work

The Software Update option lets you install updates to the vRealize Operations Manager product
itself.
Where You Find Software Updates

Log in to the vRealize Operations Manager administration interface at https://master-node-name-
or-ip-address/admin. On the left, click Software Update.
Software Update Options

The options include a wizard for locating the update PAK file and starting the installation, plus a
list of updates and the vRealize Operations Manager cluster nodes on which they are installed.
VMware, Inc. 113

Table 3-8. Software Update Options

Option Description
Install a Software Update Launch a wizard that allows you to locate, accept the
license, and start the installation of a vRealize Operations
Manager software update.
Node Name Machine name of the node where the update is installed
Node IP Address Internet protocol (IP) address of the node where the
update is installed. Primary and replica nodes require static
IP addresses. Data nodes may use DHCP or static IP.
Update Step Software update progress in step x of y format
Status Success, failure, in-progress, or unknown condition of the

software update
Install a Software Update

If you have already installed vRealize Operations Manager, you can update your software when a
newer version becomes available.
Note Installation might take several minutes or even a couple hours depending on the size and
type of your clusters and nodes.
Prerequisites
n Create a snapshot of each node in your cluster. See Create a Snapshot as Part of an Update
for details.
n Obtain the PAK file for your cluster. See Obtain the Software Update PAK File for details.
n Before you install the PAK file, or upgrade your vRealize Operations Manager instance, clone
any customized content to preserve it. Customized content can include alert definitions,
symptom definitions, recommendations, and views. Then, during the software update, you
select the options named Install the PAK file even if it is already installed and Reset out-of-
the-box content.
n The version 6.2.1 vRealize Operations Manager update operation has a validation process that
identifies issues before you start to update your software. Although it is good practice to run
the pre-update check and resolve any issues found, users who have environmental
constraints can disable this validation check.
To disable the pre-update validation check, perform the following steps:
n Edit the update file to/storage/db/pakRepoLocal/

bypass_prechecks_vRealizeOperationsManagerEnterprise-
buildnumberofupdate.json.
n Change the value to TRUE and run the update.
Note If you disable the validation, you might encounter blocking failures during the update
itself.
VMware, Inc. 114

Procedure
1 Log into the master node vRealize Operations Manager Administrator interface of your
cluster at https://master-node-FQDN-or-IP-address/admin.
2 Click Software Update in the left panel.
3 Click Install a Software Update in the main panel.
4 Follow the steps in the wizard to locate and install your PAK file.
a If you are updating a Virtual Appliance deployment, perform the OS update.
This updates the OS on the virtual appliance and restarts each virtual machine.
b Install the product update PAK file.
Wait for the software update to complete. When it does, the Administrator interface logs
you out.
5 Read the End User License Agreement and Update Information, and click Next.
6 Click Install to complete the installation of software update.
7 Log back into the master node Administrator interface.
The main Cluster Status page appears and cluster goes online automatically. The status page
also displays the Bring Online button, but do not click it.
8 Clear the browser caches and if the browser page does not refresh automatically, refresh the
page.
The cluster status changes to Going Online. When the cluster status changes to Online, the
upgrade is complete.
Note If a cluster fails and the status changes to offline during the installation process of a
PAK file update then some nodes become unavailable. To fix this, you can access the
Administrator interface and manually take the cluster offline and click Finish Installation to
continue the installation process.
9 Click Software Update to check that the update is done.
A message indicating that the update completed successfully appears in the main pane.
What to do next
Delete the snapshots you made before the software update.
Note Multiple snapshots can degrade performance, so delete your pre-update snapshots after
the software update completes.
VMware, Inc. 115

Install a vRealize Operations Manager Software Update from the Administration

Interface
You activate the vRealize Operations Manager product or its additional solutions by registering
licenses.
Prerequisites
n Know the name and location of the software update PAK file.
the-box content.
Procedure
1 In a Web browser, navigate to the vRealize Operations Manager administration interface at

https://master-node-name-or-ip-address/admin.
2 Log in with the admin user name and password for the master node.
3 On the left, click Software Update.
4 Click Install a Software Update.
5 Follow the wizard to locate and install your copy of update-filename.pak.
Installation completes in a couple of minutes, and the administrator interface logs you out. If
you are not logged out automatically after 5 minutes, refresh the page in your browser.
6 Log back in to the master node administrator interface, and click Software Update again.
7 Verify that update name appears on the right. If the update does not appear, wait a few
minutes, and refresh the page in your browser.
Before Upgrading to vRealize Operations Manager 7.5

Many vRealize Operations Manager metrics are discontinued or changed for the 6.7 release. The
changes apply primarily to capacity planning, badges, widgets, and raw metrics. Some vCenter
adapter and vSAN adapter metrics were also discontinued. The changes update the capacity
analytics and improve product scale. VMware has made many of these changes transparent or
nearly so. Still, multiple changes can impact management packs that you might be using, plus
dashboards and reports that you have created. Before upgrading, run the vRealize Operations
Manager Pre-upgrade Readiness Assessment Tool (Assessment Tool) that helps you understand
the precise impact on your environment through a detailed report.
VMware, Inc. 116

Why Run the Assessment Tool

Various changes in vRealize Operations Manager can impact the user experience. When you run
the Assessment Tool, you get an HTML-formatted report identifying all the points in your system
affected by the changes. Further, the Assessment Tool gives recommendations for the correct
changes to be made in your content for the 7.0 release.
If you ran the vRealize Operations Manager Pre-upgrade Readiness Assessment Tool when you
upgraded to vRealize Operations Manager 6.7 or 7.0, you may skip this step when you upgrade
from vRealize Operations Manager 6.7 or 7.0 to vRealize Operations Manager 7.5.
Note You must run the Assessment Tool on the instance of the vRealize Operations Manager
installation that you want to assess - typically your production system. The Assessment Tool
does not alter anything in your system, and deletes itself when it has completed its run. It leaves
behind only the assessment result - a support bundle that you download from the Support
Bundles section of the vRealize Operations Manager Administration user interface.
For detailed instructions on running the Assessment Tool, see Running the vRealize Operations
Manager 7.5 Pre-Upgrade Readiness Assessment Tool.
Running the vRealize Operations Manager 7.5 Pre-Upgrade Readiness

Assessment Tool
Before upgrading, you can gauge the impact on your system by running the vRealize Operations
Manager Pre-Upgrade Readiness Assessment Tool (Assessment Tool). The tool generates a
report detailing the precise impact on your environment and gives suggestions for replacement
metrics.
Using the Assessment Tool consists of four distinct steps:
1 Download the PAK file from https://my.vmware.com/group/vmware/get-download?

downloadGroup=VROPS-750.
2 Run the vRealize Operations Manager Pre-Upgrade Readiness Assessment Tool.
3 Extract the report from the generated ZIP file.
4 Click the various items in the report to link to the solutions grid.
Note You must run the Assessment Tool on the instance of the vRealize Operations Manager
installation that you want to assess - typically your production system. The Assessment Tool
does not alter anything in your system, and deletes itself when it has completed its run. It leaves
behind only the assessment result - a support bundle that you download from the Support
Bundles section of the vRealize Operations Manager Administration user interface.
VMware, Inc. 117

Prerequisites
You must have administrator privileges in your current installation of vRealize Operations
Manager to download and run the Assessment Tool.
Note If you ran the vRealize Operations Manager Pre-upgrade Readiness Assessment Tool when
you upgraded to vRealize Operations Manager 6.7 or 7.0, you may skip this step when you
upgrade from vRealize Operations Manager 6.7 or 7.0 to vRealize Operations Manager 7.5. For
more information on using the upgrade assessment tool, see the following KB article 67311.
Procedure
1 Download the Assessment Tool PAK from https://my.vmware.com/group/vmware/get-

download?downloadGroup=VROPS-750 to your local machine. Search for APUAT or vRealize
Operations - Upgrade Assessment Tool.
2 Open a browser and navigate to thevRealize Operations Manager administrator console:

https://<master_node_IP>/admin.
Then log into the administrator user interface with the user ID admin and the associated
password.
3 In the left pane of the administration home page, click Software Update.
The Software Update screen appears.
4 Click Install a Software Update at the top of the screen.
The Add Software Update workspace appears.
5 Click the Browse link and navigate to the PAK file you downloaded in Step 1.
A check mark appears next to the statement: The selected file is ready to upload and install.
Click UPLOAD to continue.
6 Ensure that a check mark appears next to the statement: Install the PAK file even if it is
already installed.
Leave blank the check box next to Reset Default Content...
7 Click the UPLOAD link.
The PAK file is uploaded from your local machine to vRealize Operations Manager. Uploading
may take a few minutes.
8 Once the PAK file is uploaded, click NEXT.
The End User License Agreement appears.
9 Click the check box next to the statement: I accept the terms of this agreement.
Click NEXT. The Important Update and Release Information screen appears.
VMware, Inc. 118

10 Review the release information and click NEXT. At the Install Software Update screen, click
INSTALL.
The Software Update screen appears again, this time with a rotating icon and an installation
in progress... bar marking the progress of the PAK file and assessment as they run on your
environment. The process can take from five to 20 minutes, depending on the size of your
system.
11 When the process is complete, click Support in the left pane.
The Support screen appears.
12 Select the Support Bundles option above the toolbar.
The available support bundles are listed.
13 Locate the support bundle most recently created. Click the chevron next to the bundle name
to open the file and select it, then click the download link on the toolbar to save the support
bundle ZIP file to your local files.
14 To review the report, extract the files from the ZIP file and open the HTML file. (Do not open
the CSV file, it is for VMware use only.)
The report is a graphical depiction of your vRealize Operations Manager UI components -

dashboards, reports, management packs, alerts, heat maps, and so on - and includes the
number of deprecated metrics impacting each component. For example, you might find that
10 of your 25 dashboards contain a total of 15 deprecated metrics.
15 Click a component.
The report details for that component are listed following the graphics, under Impacted
Component Details. Taking dashboards as an example, the list provides - for each dashboard
- the dashboard name, owner, widgets removed, metric-impacted views, and metric-
impacted widgets. The deprecated metrics are live links.
16 Click a live metric link.
A browser window opens at URL http://partnerweb.vmware.com/programs/vrops/

DeprecatedContent.html with the selected metric highlighted in a table of like metrics. If a
replacement metric is available for the deprecated metric, it is listed in the same row by name
and metric key. You might choose to install the new metric in place of the deprecated metric.
17 Repeat Steps 15 and 16 for all your components.
If you replace the deprecated metrics with new metrics, or update each component to
provide needed information without the deprecated metrics, your system is ready for the
upgrade.
18 Rerun the entire assessment process from Step 1 to confirm that your system is no longer
impacted or at least mostly not impacted by the metrics changes.
19 Once you have upgraded to vRealize Operations Manager 7.5, fix the remaining issues with
replacement metrics available in the new release.
VMware, Inc. 119

Results
Your vRealize Operations Manager components are updated to work correctly in the 7.5 release.
What to do next
Once you have installed vRealize Operations Manager 7.5, conduct, at a minimum, random
testing to determine if system metrics are operating as you expect. Monitor the platform on an
ongoing basis to confirm that you are receiving the correct data.
VMware, Inc. 120

Configuring
4
You configure objects, alerts, actions, policies, dashboards, and reports, in vRealize Operations
Manager to effectively monitor your environment. You use administration settings to manage
your environment.
Configure solutions in vRealize Operations Manager to connect to and analyze data from external
data sources in your environment. Once connected, you use vRealize Operations Manager to
monitor and manage objects in your environment. Solutions that are installed together with
vRealize Operations Manager include vSphere, End Point Operations, Log Insight, vRealize
Automation, VMware vSAN, and Business Management. Configure these adapters to connect to
and integrate with these instances.
Create alert definitions so that whenever there is a problem, vRealize Operations Manager
triggers alerts and provides recommendations to resolve the problem. The process of configuring
alerts involves defining alerts, symptoms, and recommendations.
Enable actions to address a problem in the monitored environment. The actions let you resolve a
problem by remaining in the vRealize Operations Manager environment itself.
Create a policy to define rules for vRealize Operations Manager to use. You can use a policy to
analyze and display information about the objects in your environment.
Define compliance standards to determine the compliance of your objects. You can use vRealize
Operations Manager alert definitions to create compliance standards that notify you when an
object does not comply with a required standard.
Create super metrics to give you a big picture of your environment. A super metric is a
mathematical formula that contains one or more metrics. It is a custom metric that you design
and is useful when you need to track combinations of metrics, either from a single object or from
multiple objects. If a single metric cannot tell you what you need to know about the behavior of
your environment, you can define a super metric.
Create dashboards to determine the nature and timeframe of existing and potential issues with
your environment. You create dashboards by adding widgets to a dashboard and configuring
them.
VMware, Inc. 121

Create views to interpret metrics, properties, and policies of various monitored objects including
alerts. Generate a report to capture details related to current or predicted resource needs. A
report is a scheduled snapshot of views and dashboards.
n Connecting vRealize Operations Manager to Data Sources
n Configuring Alerts and Actions
n Configuring Policies
n Configuring Compliance
n Configuring Super Metrics
n Configuring Objects
n Configuring Data Display
n Configuring Administration Settings
n About the vRealize Operations Manager Administration Interface
n Configuring and Using Workload Optimization
Connecting vRealize Operations Manager to Data Sources

Configure management packs in vRealize Operations Manager to connect to and analyze data
from external data sources in your environment. Once connected, you use vRealize Operations
Manager to monitor and manage objects in your environment.
A management pack might be only a connection to a data source, or it might include predefined
dashboards, widgets, alerts, and views.
vRealize Operations Manager includes the VMware vSphere and VMware vRealize Assessments
solutions. These solutions are installed when you install vRealize Operations Manager.
vRealize Operations Manager also includes management packs that are bundled with vRealize
Operations Manager, but not activated. You can activate these management packs from the
Repository page. The management packs are as follows:
n VMware vSAN
n VMware vRealize Log Insight
n VMware vRealize Automation
n VMware vRealize Application Management Pack
n VMware vRealize Business for Cloud
VMware, Inc. 122

n Operating Systems/Remote Service Monitoring
Note The management packs bundled with vRealize Operations Manager are reinstalled if
vRealize Operations Manager is upgraded. If there is a fresh deployment of vRealize Operations
Manager, only VMware vSphere and vRealize Optimization Assessments are installed and
activated, all other management packs are pre-bundled and require activation for use.
Other management packs such as the VMware Management Pack for NSX for vSphere, can be
added to vRealize Operations Manager as management packs from the Repository page. To
download VMware management packs and other third-party solutions, visit the VMware Solution
Exchange at https://marketplace.vmware.com/vsx/.
VMware vSphere Solution in vRealize Operations Manager

The VMware vSphere solution connects vRealize Operations Manager to one or more vCenter
Server instances. You collect data and metrics from those instances, monitor them, and run
actions in them.
vRealize Operations Manager evaluates the data in your environment, identifying trends in object
behavior, calculating possible problems and future capacity for objects in your system based on
those trends, and alerting you when an object exhibits defined symptoms.
Configuring the vSphere Solution

The vSphere solution is installed together with vRealize Operations Manager. The solution
provides the vCenter Server adapter which you must configure to connect vRealize Operations
Manager to your vCenter Server instances.
Configure the vSphere Solution to

connect vRealize Operations Manager To begin, access
to one or more vCenter instances Administration > Solutions > Configure
Enable/disable actions
Configure and manage
vCenter adapter instances in Update the default monitoring policy
one central workplace
Add vCenter adapter instances
Create roles with permissions to determine

Configure user access so that who can access actions
users can run actions on objects
in vCenter Server from vRealize Create user groups, and assign them
Operations Manager action-specific roles and access to adapter
instances
VMware, Inc. 123

How Adapter Credentials Work

The vCenter Server credentials that you use to connect vRealize Operations Manager to a
vCenter Server instance, determines what objects vRealize Operations Manager monitors.
Understand how these adapter credentials and user privileges interact to ensure that you
configure adapters and users correctly, and to avoid some of the following issues.
n If you configure the adapter to connect to a vCenter Server instance with credentials that
have permission to access only one of your three hosts, every user who logs in to vRealize
Operations Manager sees only the one host, even when an individual user has privileges on
all three of the hosts in the vCenter Server.
n If the provided credentials have limited access to objects in the vCenter Server, even vRealize
Operations Manager administrative users can run actions only on the objects for which the
vCenter Server credentials have permission.
n If the provided credentials have access to all the objects in the vCenter Server, any vRealize
Operations Manager user who runs actions is using this account.
Controlling User Access to Actions

Use the vCenter Server adapter to run actions on the vCenter Server from vRealize Operations
Manager. If you choose to run actions, you must control user access to the objects in your
vCenter Server environment. You control user access for local users based on how you configure
user privileges in vRealize Operations Manager. If users log in using their vCenter Server account,
then the way their account is configured in vCenter Server determines their privileges.
For example, you might have a vCenter Server user with a read-only role in vCenter Server. If you
give this user the vRealize Operations Manager Power User role in vCenter Server rather than a
more restrictive role, the user can run actions on objects because the adapter is configured with
credentials that has privileges to change objects. To avoid this type of unexpected result,
configure local vRealize Operations Manager users and vCenter Server users with the privileges
you want them to have in your environment.
Configure a vCenter Adapter Instance in vRealize Operations Manager

To manage your vCenter Server instances in vRealize Operations Manager, you must configure
an adapter instance for each vCenter Server instance. The adapter requires the credentials that
are used for communication with the target vCenter Server.
Caution Any adapter credentials you add are shared with other adapter administrators and
vRealize Operations Manager collector hosts. Other administrators might use these credentials to
configure a new adapter instance or to move an adapter instance to a new host.
Prerequisites
Verify that you know the vCenter Server credentials that have sufficient privileges to connect
and collect data, see Privileges Required for Configuring a vCenter Adapter Instance. If the
provided credentials have limited access to objects in vCenter Server, all users, regardless of
their vCenter Server privileges see only the objects that the provided credentials can access. At a
VMware, Inc. 124

minimum, the user account must have Read privileges and the Read privileges must be assigned
at the data center or vCenter Server level.
Procedure
1 On the menu, click Administration and in the left pane click Solutions.
2 On the Solutions page, select VMware vSphere and click the Configure icon.
3 Enter a display name and description for the adapter instance.
4 In the vCenter Server text box, enter the FQDN or IP address of the vCenter Server instance
to which you are connecting.
The vCenter Server FQDN or IP address must be reachable from all nodes in the vRealize
Operations Manager cluster.
5 To add credentials for the vCenter Server instance, click the Add icon, and enter the required
credentials. The vCenter credential must have Performance > Modify intervals permission
enabled in the target vCenter to collect VM guest metrics.
6 The adapter is configured to run actions on objects in the vCenter Server from vRealize
Operations Manager. If you do not want to run actions, select Disable.
The credentials provided for the vCenter Server instance are also used to run actions. If you
do not want to use these credentials, you can provide alternative credentials by expanding
Alternate Action Credentials, and clicking the Add icon.
7 Click Test Connection to validate the connection with your vCenter Server instance.
8 In the Review and Accept Certificate dialog box, review the certificate information.
u If the certificate presented in the dialog box matches the certificate for your target
vCenter Server, click OK.
u If you do not recognize the certificate as valid, click Cancel. The test fails and the
connection to vCenter Server is not completed. You must provide a valid vCenter Server
URL or verify the certificate on the vCenter Server is valid before completing the adapter
configuration.
9 To modify the advanced options regarding collectors, object discovery, or change events,
expand the Advanced Settings.
For information about these advanced settings, see the Manage Solution - VMware vSphere
Solution Workspace Options.
10 To adjust the default monitoring policy that vRealize Operations Manager uses to analyze and
display information about the objects in your environment, click Define Monitoring Goals.
For information about monitoring goals, see the Manage Solution - VMware vSphere Solution
Workspace Options.
11 Click Save Settings.
The adapter instance is added to the list.
VMware, Inc. 125

Results
vRealize Operations Manager begins collecting data from the vCenter Server instance.
Depending on the number of managed objects, the initial collection can take more than one
collection cycle. A standard collection cycle begins every five minutes.
For information about the network port that vRealize Operations Manager uses to communicate
with a vCenter Server system and vRealize Operations Manager components, see Port
Requirements for vRealize Operations Manager.
What to do next
If you configured the adapter to run actions, configure user access for the actions by creating
action roles and user groups.
Privileges Required for Configuring a vCenter Adapter Instance

To configure your vCenter Adapter instance in vRealize Operations Manager, you need sufficient
privileges to monitor and collect data and to perform vCenter Server actions. You can configure
these permissions as a single role in vCenter Server to be used by a single service account or
configure them as two independent roles for two separate service accounts.
The vCenter Adapter instance monitors and collects data from vCenter Server and the vCenter
Action Adapter performs some actions in vCenter Server. So, for monitoring or collecting vCenter
Server inventory and their metrics and properties, the vCenter Adapter instance needs
credentials with the following privileges enabled in vCenter Server.
Table 4-1. Privileges for Configuring a vCenter Adapter: Monitoring and Data Collection
Task Privilege
Property Collection System > Anonymous
Note When you add a custom role and do not assign any
privileges to it, the role is created as a Read Only role with
three system-defined privileges: System.Anonymous,
System.View, and System.Read. See, Using Roles to
Assign Privileges .
Objects Discovery Profile-Driven Storage > View

Events Collection Storage views > View
Profile-Driven Storage > Profile-Driven Storage View
Datastore > Browse Datastore
System > View
Note This permission is provided with the Read-Only role.
VMware, Inc. 126

Table 4-1. Privileges for Configuring a vCenter Adapter: Monitoring and Data Collection
(continued)
Task Privilege
Performance Metrics Collection Performance > Modify intervals

System > Read
Note This permission is provided with the Read-Only role.
Tag Collection Global > Global tag

Global > Global health
Global > Manage custom attributes
Note This privilege is required only if the tags are

associated with custom attributes.
Global > System tag

Global > Set custom attribute
Table 4-2. Privileges for Configuring a vCenter Adapter: Performing vCenter Server Actions
Task Privilege
Set CPU Count for VM Virtual Machine > Configuration > Change CPU Count
Set CPU Resources for VM Virtual Machine > Configuration > Change Resource
Set Memory for VM Virtual Machine > Configuration > Change Memory
Set Memory Resources for VM Virtual Machine > Configuration > Change Resource
Delete Idle VM Virtual machine > Edit Inventory > Remove
Delete Powered Off VM Virtual machine > Edit Inventory > Remove
Create Snapshot for VM Virtual Machine > Snapshot Management > Create
Snapshot
Delete Unused Snapshots for Datastore Virtual Machine > Snapshot Management > Remove
Snapshot
Delete Unused Snapshot for VM Virtual Machine > Snapshot Management > Remove
Snapshot
Power Off VM Virtual Machine > Interaction > Power Off
Power On VM Virtual Machine > Interaction > Power On
Shut Down Guest OS for VM Virtual Machine > Interaction > Power Off
Move VM n Resource > Assign Virtual Machine to Resource Pool

n Resource > Migrate Powered Off Virtual Machine
n Resource > Migrate Powered On Virtual Machine
n Datastore > Allocate Space
Note Combining these four permissions allows the service

account to perform Storage vMotion and regular vMotion
of an object therefore allowing vRealize Operations
Manager to perform the given operations.
VMware, Inc. 127

Table 4-2. Privileges for Configuring a vCenter Adapter: Performing vCenter Server Actions
(continued)
Task Privilege
Optimize Container n Resource > Assign Virtual Machine to Resource Pool

Schedule Optimize Container n Resource > Assign Virtual Machine to Resource Pool
Set DRS Automation Host > Inventory > Modify Cluster
Provide data to vSphere Predictive DRS External stats provider > Update
External stats provider > Register
External stats provider > Unregister
For more information about tasks and privileges, see Required Privileges for Common Tasks in
the vSphere Virtual Machine Administration Guide and Defined Privileges in the vSphere Security
Guide.
Configure User Access for Actions

To ensure that users can run actions in vRealize Operations Manager, you must configure user
access to the actions.
You use role permissions to control who can run actions. You can create multiple roles. Each role
can give users permissions to run different subsets of actions. Users who hold the Administrator
role or the default super user role already have the required permissions to run actions.
You can create user groups to add action-specific roles to a group rather than configuring
individual user privileges.
Procedure
1 On the menu, click Administration and in the left pane click Access > Access Control.
2 To create a role:
a Click the Roles tab.
b Click the Add icon, and enter a name and description for the role.
3 To apply permissions to the role, select the role, and in the Permissions pane, click the Edit
icon.
a Expand Environment, and then expand Action.
b Select one or more of the actions, and click Update.
VMware, Inc. 128

4 To create a user group:
a Click the User Groups tab, and click the Add icon.
b Enter a name for the group and a description, and click Next.
c Assign users to the group, and click the Objects tab.
d Select a role that has been created with permissions to run actions, and select the Assign
this role to the user check box.
e Configure the object privileges by selecting each adapter instance to which the group
needs access to run actions.
f Click Finish.
What to do next
Test the users that you assigned to the group. Log out, and log back in as one of the users.
Verify that this user can run the expected actions on the selected adapter.
Manage Solution - VMware vSphere Solution Workspace Options

To begin monitoring your environment with vRealize Operations Manager, you configure the
VMware vSphere solution. The solution includes the vCenter Server adapter that collects data
from the target vCenter Server instances.
Where You Find the Manage Solution - VMware vSphere Workspace

On the menu, click Administration and in the left pane click Solutions. On the Solutions tab,
select VMware vSphere and click the Configure icon on the toolbar.
Manage Solution - VMware vSphere Workspace Options

Configure and modify adapter instances, and define monitoring goals on the Manage Solution
page.
VMware, Inc. 129

Table 4-3. Manage Solution Page Options

Option Description
Adapter Type list Provides a list of the adapters included in the solution.
Configured adapters provide the settings and credentials that vRealize Operations Manager
must communicate with your vCenter Server instances or action instances.
After you update your instance of vRealize Operations Manager and select the option to
overwrite alert definitions and symptom definitions, you must overwrite your existing
compliance alert definitions. To reset the default content, navigate to the Solutions
configuration page, and click Administration > Solutions. Click the VMware vSphere
solution, click Configure, and in the Manage Solution workspace, click Reset Default
Content.
The option named Reset Default Content ensures that compliance standards are current
for your vSphere 6.0 and 5.5 objects. The alert definitions and symptom definitions now
include the compliance standards for both vSphere 6.0 and 5.5.
n When you upgrade your current version of vRealize Operations Manager, you must
select this menu item to overwrite alert definitions and symptom definitions. If you do
not overwrite alert and symptom definitions, compliance rules will use a mixture of new
and outdated definitions.
Instance Name list List of configured adapter instances based on the selected adapter type.
This list is blank until you configure at least one instance.
Instance Settings Settings used to identify the target vCenter Server instance.
n Display name. Enter the name for the vCenter Server instance as you want it to appear
in vRealize Operations Manager. A common practice is to include the IP address so that
you can readily identify and differentiate between instances.
n Description. Enter any additional information that helps you manage your instances.
Basic Settings Minimum settings used to connect to the target vCenter Server.
n vCenter Server. Enter the FQDN or IP address of the target vCenter Server instance.
The FQDN or IP address must be reachable from all nodes in the vRealize Operations
Manager cluster.
n Credentials. Click the Add icon to add credential details.
vCenter Actions Settings used to configure the adapter to run actions on objects in the vCenter Server from
vRealize Operations Manager,
n Enable Actions? The vCenter adapter is configured to run actions on objects in the
vCenter Server instance by default. Select Disable if you do not want the adapter to
run actions. Select Enable to run actions on objects.
n (Optional) Alternate Action Credentials. You can use the same credentials you provided
to connect to the vCenter Server to run actions, or click this menu item to provide
alternative credentials.
n Test Connection. Click to verify that the provided credentials can connect to the target
vCenter Server and so that you can validate the certificate. The certificate presented is
the leaf certificate for the vCenter Server instance, not the complete certificate chain.
Click OK only if the certificate presented in the dialog box matches the certificate for
your target vCenter Server.
Advanced Settings Provides options related to designating specific collectors to manage this adapter instance,
managing object discovery and change events.
VMware, Inc. 130

Table 4-3. Manage Solution Page Options (continued)

Option Description
Collectors/Groups Determines which vRealize Operations Manager collector is used to manage the adapter
processes. If you have only one adapter instance, select Default collector group. If you
have multiple collectors in your environment, and you want to distribute the workload to
optimize performance, select the collector to manage the adapter processes for this
instance.
Auto Discovery Determines whether new objects added to the monitored system are discovered and
added to vRealize Operations Manager after the initial configuration of the adapter.
n If the value is true, vRealize Operations Manager collects information about any new
objects that are added to the monitored system after the initial configuration. For
example, if you add more hosts and virtual machines, these objects are added during
the next collections cycle. This is the default value.
n If the value is false, vRealize Operations Manager monitors only the objects that are
present on the target system when you configure the adapter instance.
Process Change Events Determines whether the adapter uses an event collector to collect and process the events
generated in the vCenter Server instance.
n If the value is true, the event collector collects and publishes events from vCenter
Server. This is the default value.
n If the value is false, the event collector does not collect and publish events.
Enable Collecting vSphere When set to false, reduces the collected data set by omitting collection of the associated
Distributed Switch category.
Enable Collecting Virtual
Machine Folder
Enable Collecting vSphere
Distributed Port Group
Exclude Virtual Machines When set to true, reduces the collected data set by omitting collection of the associated
from Capacity Calculations category.
Maximum Number Of Reduces the collected data set by limiting the number of virtual machine collections.
Virtual Machines Collected To omit data on virtual machines and have vRealize Operations Manager collect only host
data, set the value to zero.
Provide data to vSphere vSphere Predictive DRS proactively load balances a vCenter Server cluster to
Predictive DRS accommodate predictable patterns in the cluster workload.
vRealize Operations Manager monitors virtual machines running in a vCenter Server,
analyzes longer-term historical data, and provides forecast data about predictable patterns
of resource usage to Predictive DRS. Based on these predictable patterns, Predictive DRS
moves to balance resource usage among virtual machines.
Predictive DRS must also be enabled for the Compute Clusters managed by the vCenter
Server instances monitored by vRealize Operations Manager. Refer to the vSphere
Resource Management Guide for details on enabling Predictive DRS on a per Compute
Cluster basis.
When set to true, designates vRealize Operations Manager as a predictive data provider,
and sends predicative data to the vCenter Server. You can only register a single active
Predictive DRS data provider with a vCenter Server at a time.
Enable Actions Enabling this option helps in triggering the actions that are related to vCenter.
Cloud Type Provides an ability to identify the type of vCenter is used in vRealize Operations Manager.
By default, the cloud type is set to Private Cloud.
VMware, Inc. 131

The Define Monitoring Goals page provides you with default policy options which determine how
vRealize Operations Manager collects and analyzes data in your monitored environment. You can
change the options on this page to create a new default policy.
Table 4-4. Define Monitoring Goals Page Options

Option Description
Which objects do you want to be alerted on in your Specify the type of objects that receive alerts. vRealize
environment? Operations Manager can alert on all infrastructure objects
excluding virtual machines, only virtual machines, or all.
Which types of alerts do you want to enable? You can enable vRealize Operations Manager to trigger
Health, Risk, and Efficiency alerts on your objects.
Configure Memory Capacity based on? Set the memory capacity model based on the type of
environment to monitor. For example, to monitor a
production environment, select the vSphere Default model
to use moderate settings to ensure performance. Use Most
Aggressive for test and development environments. Use
Most Conservative to use all allocated memory for
capacity calculations.
Enable vSphere Hardening Guide Alerts? Use the vSphere Hardening Guide to assess and operate
your vSphere objects. When you enable these alerts,
vRealize Operations Manager assesses your objects against
the vSphere Hardening Guide rule.
You can find the vSphere Hardening Guides at http://www.vmware.com/security/hardening-

guides.html.
Click Save Settings to finish configuration of the solution.
vRealize Application Remote Collector

vRealize Application Remote Collector enables virtual infrastructure administrators and
application administrators to discover applications running in provisioned Guest operating
systems at a scale and to collect run-time metrics of the operating system and application for
monitoring and troubleshooting respective entities.
vRealize Application Remote Collector
What is vRealize Application Remote Collector

vRealize Application Remote Collector enables virtual infrastructure administrators and
application administrators to discover applications running in provisioned Guest operating
systems at a scale and to collect run-time metrics of the operating system and application for
monitoring and troubleshooting respective entities. The monitoring and troubleshooting
workflows are enabled from vRealize Operations Manager which include the configuration of a
Wavefront or vRealize Operations Manager account as well as life cycle management of the
agents on the Virtual Machines.
VMware, Inc. 132

vRealize Application Remote Collector is delivered as a standalone Photon OS OVA file. You must
deploy the OVA file using a vSphere client. The OVA is available for download from vRealize
Operations Manager after you log in.
vRealize Application Remote Collector supports the following application services. There are 46
services supported in Wavefront of which 17 are also supported in vRealize Operations Manager.
Table 4-5.
Application Service Support
Active Directory Wavefront and vRealize Operations Manager
Active MQ Wavefront and vRealize Operations Manager
Apache HTTPD Wavefront and vRealize Operations Manager
Apache Solr Wavefront
Atlassian Bitbucket Wavefront
Cassandra Wavefront
Ceph Wavefront
Chef Wavefront
Consul Wavefront
Couchbase Wavefront
Elastic Search Wavefront
etcd Wavefront
Fluentd Wavefront
hadoop-hdfs Wavefront
hadoop-mapreduce Wavefront
hadoop-yarn Wavefront
HAProxy Wavefront
HyperV Wavefront
JBoss Wavefront and vRealize Operations Manager
Jenkins Wavefront
Kafka Wavefront
Kong Wavefront
Lighttpd Wavefront
Marathon Wavefront
Memcached Wavefront
Mesos Wavefront
MongoDB Wavefront and vRealize Operations Manager
MS Exchange Wavefront and vRealize Operations Manager
MS IIS Wavefront and vRealize Operations Manager
VMware, Inc. 133

Table 4-5. (continued)

Application Service Support
MS SQL Wavefront and vRealize Operations Manager
MySQL Wavefront and vRealize Operations Manager
Nginx Wavefront and vRealize Operations Manager
nginx_plus Wavefront
php-fpm Wavefront
Pivotal Server Wavefront and vRealize Operations Manager
Postgres Wavefront and vRealize Operations Manager
RabbitMQ Wavefront and vRealize Operations Manager
Redis Wavefront
Riak Wavefront and vRealize Operations Manager
Sharepoint Wavefront and vRealize Operations Manager
Tomcat Wavefront and vRealize Operations Manager
Twemproxy Wavefront
Varnish Wavefront
Weblogic Wavefront and vRealize Operations Manager
Wildfly Wavefront
Zookeeper Wavefront
Deploy vRealize Application Remote Collector
Supported Platforms
vRealize Application Remote Collector supports monitoring for the following platforms and app
combinations with API support.
Platforms supported by vRealize Application Remote Collector
Platform Version Architecture Application
RedHat 7.x 64-bit OS Metrics and all supported

applications for vRealize
Application Remote
Collector
CentOS 7.x 64-bit OS Metrics and all supported

Application Remote
Collector
Windows 2008 R2 64-bit OS Metrics and all supported

2012 applications for vRealize
Application Remote
2012 R2
Collector
2016
VMware, Inc. 134

Platform Version Architecture Application
OEL 7.x 64-bit OS Metrics and all supported

Application Remote
Collector
SUSE Linux Enterprise 12.x, 15.x 64-bit OS Metrics and all supported
Server applications for vRealize
Application Remote
Collector
Ubuntu Server 17.x, 18.x 64-bit OS Metrics and all supported

Application Remote
Collector
Sizing Reference Data

The sizing reference data helps you select a deployment configuration during the deployment of
the OVA file. VMware expects vRealize Application Remote Collector sizing information to evolve,
and maintains Knowledge Base articles so that sizing calculations can be adjusted to adapt to
usage data and changes in versions of vRealize Operations Manager. For more information, see
the Knowledge Base article 2093783.

Use a vSphere client to deploy vRealize Application Remote Collector. You can deploy the
vRealize Application Remote Collector OVA template from a file.
Prerequisites
You can download the vRealize Application Remote Collector OVA file after you log in to vRealize
Operations Manager. Download vRealize Application Remote Collector OVA file by clicking the
Download icon in the Configure Application Remote Collector page
For critical time sourcing, use the Network Time Protocol (NTP). You must ensure time
synchronization between the endpoint VMs, vCenter Server, ESX Hosts and vRealize Operations
Manager.
Procedure
1 Right-click any inventory object that is a valid parent object of a virtual machine, such as a
data center, folder, cluster, resource pool, or host, and select Deploy OVF Template.
The Deploy OVF Template wizard opens.
2 Select Deploy OVF Template.
VMware, Inc. 135

3 On the Deploy OVF template page do one of the following and click Next:
u If you have a URL to the OVA template which is located on the Internet, type the URL in
the URL field. Supported URL sources are HTTP and HTTPS.
u If you have downloaded the vRealize Application Remote Collector OVA file, click Local
file and browse to the location of the file and select it.
4 On the Select a name and folder page, enter a unique name for the virtual machine or vAPP,
select a deployment location, and click Next.
The default name for the virtual machine is the same as the name of the selected OVF or
OVA template. If you change the default name, choose a name that is unique within each
vCenter Server virtual machine folder.
The default deployment location for the virtual machine is the inventory object where you
started the wizard.
5 On the Select a resource page, select a resource where to run the deployed VM template,
and click Next.
6 On the Review details page, verify the OVF or OVA template details and click Next.
Option Description
Product vRealize Application Remote Collector.
Version Version number of the vRealize Application Remote Collector.
Vendor VMWare.
Publisher Publisher of the OVF or OVA template, if a certificate included in the OVF or
OVA template file specifies a publisher.
Download size Size of the OVF or OVA file.
Size on disk Size on disk after you deploy the OVF or OVA template.
7 On the Accept license agreements page, click Accept and then Next.
8 In the Select configuration page, select the size of the deployment.
9 On the Select storage page, define where and how to store the files for the deployed OVF or
OVA template.
a Select a VM Storage Policy.
This option is available only if storage policies are enabled on the destination resource.
b (Optional) Enable the Show datastores from Storage DRS clusters check box to choose
individual datastores from Storage DRS clusters for the initial placement of the virtual
machine.
c Select a datastore to store the deployed OVF or OVA template.
The configuration file and virtual disk files are stored on the datastore. Select a datastore
large enough to accommodate the virtual machine or vApp and all associated virtual disk
files.
VMware, Inc. 136

10 On the Select networks page, select a source network and map it to a destination network.
Click Next. The source network must have a static FQDN name or static DNS.
The Source Network column lists all networks that are defined in the OVF or OVA template.
11 In the Customize template page, provide inputs to configure the vRealize Application Remote
Collector deployment. It is mandatory to give these details.
Configuration Description
API Admin User's Password Enter a password for the vRealize Application Remote Collector API admin.
The username is admin@ucp.local. This password should be used when
configuring this instance of vRealize Application Remote Collector in vRealize
Operations Manager.
Networking Properties Verify the networking properties.
12 On the Ready to complete page, review the page and click Finish.
13 After the OVA deployment is complete, you can log in to the virtual appliance from vCenter
Server. Right click the virtual appliance that you installed. Click Open Console. Use the
following credentials to log in:
Log In Details Value
Username root
Password vmware
14 Change the root user password.
Note To reset the root user password, see the KB article: 2001476
15 Enable the sshd service to access the virtual machine through ssh.
What to do next
n Perform the post-installation tasks.
n Log in to vRealize Operations Manager and configure the agents to connect to Wavefront or
Supported Versions of vSphere and VMware Cloud on AWS

vRealize Application Remote Collector supports vSphere andVMware Cloud on AWS.
Supported vSphere Versions
n vSphere 6.5
n vSphere 6.5U1
n vSphere 6.5U2
n vSphere 6.7
n vSphere 6.7U1
VMware, Inc. 137

n vSphere 6.7U2
Supported VMware Cloud on AWS Versions
n VMware Cloud on AWS 1.6 and 1.7.
VMware tools from version 10.1.0 till 10.3 is supported. VMware Tools must be installed and
running on the VM on which you want to install the agent.
Configuring Supported Application Services

vRealize Application Remote Collector supports 46 application services in Wavefront, of which 17
application services are also supported in vRealize Operations Manager. The supported
application services are listed here. Some of the application services have mandatory properties
which you must configure. Some of the application services have pre-requirements that you must
configure first. After you configure the properties, vRealize Application Remote Collector starts
collecting data.
Active Directory
Active Directory is supported in vRealize Operations Manager and Wavefront.
Name Mandatory? Comment
Display Name Yes Display Name of the application

instance.
Active MQ
ActiveMQ is supported in vRealize Operations Manager and Wavefront.

instance.
Server URL Yes http://localhost:8161
User name Yes Username for Active MQ. Example :

admin
Password Yes Password
Installed Path Yes The path on the Endpoint where Active

MQ is installed.
Example:
For Linux VMs: /opt/apache-activemq
For Windows VMs: C:\apache-
activemq-5.15.2
Apache HTTPD
Apache HTTPD is supported in vRealize Operations Manager and Wavefront.
VMware, Inc. 138


instance.
Status Page URL Yes http://localhost/server-status?auto
User name No User name for Apache HTTPD service.

Example:root
Password No Password
SSL CA No Path to the SSL CA file on the Endpoint
SSL Certificate No Path to the SSL Certificate file on the

Endpoint
SSL Key No Path to the SSL Key file on the

Endpoint.
Skip SSL Verification No Use SSL but skip chain & host
verification. Expected: True/False.
Apache Solr
Apache Solr is supported in Wavefront.

instance.
Atlassian Bitbucket
Atlassian Bitbucket is supported in Wavefront.

instance.
Server Yes http://localhost:8778
SSL CA No Path to the SSL CA file on the

Endpoint.

Endpoint.

Endpoint.
verification. Expected: true/false.
Cassandra
Cassandra is supported in Wavefront.
VMware, Inc. 139


instance.
Server Yes localhost:8778
Ceph
Ceph is supported in Wavefront.

instance.
Interval Yes Example: 1m
Ceph Binary Yes Path to Ceph Binary.

Example: /usr/bin/ceph
Socket Dir Yes Example: /var/run/ceph
Ceph User Yes Ceph User Details. Example:

client.admin
Ceph Config Yes Path to Ceph Config. Example: /etc/

ceph/ceph.conf
Gather Admin Socket Stats Yes Example: true
Gather Cluster Stats Yes Example: true
Chef
Chef is supported in Wavefront.

instance.
Server Yes http://localhost:9999/nginx_status
Chef Server URL Yes https://localhost/organizations/cmbu
Chef Node Name Yes Node Name. Example: donjoe
Chef Client Name Yes Client Name. Exmample: donejoe
Chef Client Key File Yes Path to the Client Key File.
Example: /etc/telegraf/.chef/
aswinp.pem
Chef SSL Verify Mode Yes verify_none
Consul
Consul is supported in Wavefront.
VMware, Inc. 140


instance.
Couchbase
Couchbase is supported in Wavefront.

instance.
Server URL Yes http://

<username>:<password>@<your.couch
base.sever1>:8091
Example:
http://
Administrator:password@localhost:8
091
Elastic Search
Elastic Search is supported in Wavefront.

instance.

Endpoint.

Endpoint.

Endpoint.
etcd
etcd is supported in Wavefront.

instance.
ETCD URL Yes http://localhost:2379
ETCD ENV Yes Environment. Example : prod

Endpoint.
VMware, Inc. 141


Endpoint.

Endpoint.
Fluentd
Fluentd is supported in Wavefront.

instance.
Status URL Yes http://localhost:24220
Note Open this configuration

file /etc/td-agent/td-agent.conf and
add the below content:
<source>
@type monitor_agent
bind 0.0.0.0
port 24220
</source>
hadoop-hdfs
hadoop-hdfs is supported in Wavefront.

instance.
Hadoop-HDFS Node Name URL Yes http://localhost:7777
Hadoop-HDFS Data Node URL Yes http://localhost:7778

Endpoint.

Endpoint.

Endpoint.
hadoop-mapreduce
hadoop-mapreduce is supported in Wavefront.
VMware, Inc. 142


instance.
Hadoop-Mapreduce URL Yes http://localhost:8088

Endpoint.

Endpoint.

Endpoint.
hadoop-yarn
hadoop-yarn is supported in Wavefront.

instance.
Hadoop-Yarn URL Yes http://localhost:8088

Endpoint.

Endpoint.

Endpoint.
HAProxy
HAProxy is supported in Wavefront.

instance.
HAProxy Server URL Yes http://[username]:

[password]@localhost:5000/haproxy

Endpoint.

Endpoint.
VMware, Inc. 143


Endpoint.
HyperV
HyperV is supported in Wavefront.

instance.
JBoss
JBoss is supported in vRealize Operations Manager and Wavefront.

instance.
Base URL Yes http://localhost:8080
Installed Path Yes The path on the Endpoint where JBoss

is installed.

Endpoint.

Endpoint.

Endpoint.
Jenkins
Jenkins is supported in Wavefront.

instance.
Jenkins Server URL Yes http://localhost:8080

Endpoint.

Endpoint.
VMware, Inc. 144


Endpoint.
Kafka
Kafka is supported in Wavefront.

instance.
Status Page URL Yes http://localhost:8778

Endpoint.

Endpoint.

Endpoint.
Kong
Kong is supported in Wavefront.

instance.
Server Status URL Yes http://localhost:8001/status

Endpoint.

Endpoint.

Endpoint.
Lighttpd
Lighttpd is supported in Wavefront.
VMware, Inc. 145


instance.
Status Page URL Yes http://server1/server-status?auto

Example: https://localhost/server-
status?auto

Endpoint.

Endpoint.

Endpoint.
Marathon
Marathon is supported in Wavefront.

instance.
Marathon Server URL Yes http://<endpoint-ip>:8080

Endpoint.

Endpoint.

Endpoint.
Memcached
Memcached is supported in Wavefront.
Display Name Yes Display name of the application

instance.
Mecached URL Yes localhost:11211
Mesos
Mesos is supported in Wavefront.
VMware, Inc. 146


instance.
Server Timeout Yes 100
Master Nodes Yes Example: 10.196.52.91:5050

Endpoint.
Slave Nodes No Example : 10.196.52.91:5050

Endpoint.

Endpoint.
MongoDB
MongoDB is supported in vRealize Operations Manager and Wavefront.

instance.
Port Yes The port where MongoDB is running.

Example:27017
Hostname No Optional hostname for the MongoDB

Service.
Username No User name for MongoDB. Example:

Root

Endpoint.

Endpoint.

Endpoint.
MS Exchange
MS Exchange is supported in vRealize Operations Manager and Wavefront.

instance.
VMware, Inc. 147

MS IIS
MS IIS is supported in vRealize Operations Manager and Wavefront.

instance.
MS SQL
MS SQL is supported in vRealize Operations Manager and Wavefront.

instance.
Instance Yes Instance name of the MS SQL server
Port No The port where MS SQL is running.

Example:1433
Hostname No Optional hostname for the MS SQL

Service.
Username Yes User name for MS SQL. Example: Root
MySQL
MySQL is supported in vRealize Operations Manager and Wavefront.

instance.
Port Yes The port where MySQL is running.

Example:3306
User name Yes User name for MySQL service.

Example: Root
password Yes Password

Endpoint

Endpoint.
Hostname No Optional hostname for the MySQL

Service
VMware, Inc. 148

Databases No Comma separated list of databases to

monitor. Each of the database names
to be monitored must be enclosed in
single quotes and the databases
themselves should be comma
separated. For example
'database1','database2','database3'
TLS Connection No Allowed values are true, false, skip-

verify
Nginx
Nginx is supported in vRealize Operations Manager and Wavefront.

instance.
Status Page URL Yes http://localhost/nginx_status

Endpoint.

Endpoint.

Endpoint.
nginx_plus
nginx_plus is supported in Wavefront.

instance.
Status Page URL Yes http://localhost/nginx_status
php-fpm
php-fpm is supported in Wavefront.

instance.
Server URL Yes http://localhost/status
Pivotal Server
Pivotal Server is supported in vRealize Operations Manager and Wavefront.
VMware, Inc. 149


instance.
Installed Path Yes The path on the Endpoint where

Pivotal server is installed.

Endpoint.

Endpoint.

Endpoint.
Postgres
Postgres is supported in vRealize Operations Manager and Wavefront.

instance.
Port Yes The port where PostgreSQL is running.

Example:5432
User name Yes User name for PostgreSQL service.

Example: Root
SSL Connection No Allowed values are disable, verify-ca,

verify-full.

Endpoint

Endpoint.
Hostname No Optional hostname for the PostgreSQL

Service.
Default Database No The database for initiating connection

with the server
VMware, Inc. 150

Databases No Comma separated list of databases to

monitor. Each of the database names
to be monitored must be enclosed in
single quotes and the databases
separated for example
Ignored Databases No Comma separated list of databases

that need not be monitored. Each of
the database names to be excluded
from monitoring need to be enclosed
in single quotes and the databases
separated for example
RabbitMQ
RabbitMQ is supported in vRealize Operations Manager and Wavefront.

instance.
Management Plugin URL Yes http://localhost:15672
User name No User name for RabbitMQ. Example:

Guest

Endpoint.

Endpoint.

Endpoint.
Nodes No Each of the RabbitMQ data collection

nodes should be in single quotes and
the nodes themselves should be
comma separated. The list of nodes
needs to be enclosed in square
brackets. For example
['rabbit@node1','rabbit@node2',.....]
Redis
Redis is supported in Wavefront.
VMware, Inc. 151


instance.
Redis URL Yes tcp://password@redis-server-ip:6379

Example: tcp://:Password1!
@10.126.36.4:6379

Endpoint.

Endpoint.

Endpoint.
Riak
Riak is supported in vRealize Operations Manager and Wavefront.

instance.
Sharepoint
Sharepoint is supported in vRealize Operations Manager and Wavefront.

instance.
Tomcat
Tomcat is supported in vRealize Operations Manager and Wavefront.

instance.

Tomcat is installed.

Endpoint.

Endpoint.
VMware, Inc. 152


Endpoint.
Twemproxy

instance.
Host Address Yes localhost:22222
Pools Yes Example :

'alpha','gamma','beta','delta','omega'
Varnish
Varnish is supported in vRealize Operations Manager.

instance.
Varnishstat Binary Path Yes /usr/bin/varnishstat
Weblogic
Weblogic is supported in vRealize Operations Manager and Wavefront.

instance.

WebLogic is installed.
User name Yes User name for WebLogic. Example:

admin

Endpoint.

Endpoint.

Endpoint.
VMware, Inc. 153

Wildfly
Wildfly is supported in vRealize Operations Manager.

instance.
Base URL Yes http://<end-point-ip>:8080

Widlfly is installed. Example: /opt/
wildfly

Endpoint.

Endpoint.

Endpoint.
Zookeeper
Zookeeper is supported in vRealize Operations Manager.

instance.
Pre-Requirements for Application Services

For telegraf agent to collect metrics for some of the application services, you must make
modifications in the endpoint VMs. After you make these modifications, the agent will start
collecting metrics. You must SSH to the virtual machine where you have deployed the agent and
modify the configuration files.
Apache HTTPD
Modify the conf file available in /etc/httpd/conf.modules.d/status.conf and enable the

mod_status for the HTTPD plugin for the agent to collect metrics.
<IfModule mod_status.c>
<Location /server-status>
SetHandler server-status
</Location>
VMware, Inc. 154

ExtendedStatus On
</IfModule>
If the conf file is not available, you must create one. Restart the HTTPD service after modifying
the conf file with the following command:
systemctl restart httpd
Atlassian Bitbucket
1 Download latest Jolokia agent JAR from https://jolokia.org/download.html.
2 Edit the _start-webapp.sh file and edit the below line. Change the Bitbucket arguments like
as below:
BITBUCKET_ARGS="-Datlassian.standalone=BITBUCKET -Dbitbucket.home=$BITBUCKET_HOME -Dbitbucket.install=

$INST_DIR $JVM_OPTS -javaagent:/usr/share/java/jolokia-jvm-1.6.0-agent.jar=port=8778,host=localhost"
Cassandra
n Run the following command to download the latest Jolokia JAR:sudo curl -o /usr/share/
java/jolokia-jvm-1.6.0-agent.jar -L http://search.maven.org/remotecontent?filepath=org/
jolokia/jolokia-jvm/1.6.0/jolokia-jvm-1.6.0-agent.jar
n Run the following command: echo "export JVM_EXTRA_OPTS=\"-javaagent:/usr/share/java/

jolokia-jvm-1.6.0-agent.jar=port=8778,host=localhost\"" | sudo tee -a /etc/default/
cassandra
n Restart the Cassandra service: sudo service cassandra restart
Note The Jolokia Jar is available here: https://jolokia.org/download.html
Chef
Run the following commands in the machine:
chef-server-ctl install opscode-reporting

chef-server-ctl reconfigure
opscode-reporting-ctl reconfigure
hadoop-hdfs
n Download latest Jolokia agent JAR from https://jolokia.org/download.html.
n Deploy the jar jolokia-jvm-1.6.0-agent.jar
n Edit etc/hadoop/hadoop-env.sh and enter the following.
JOLOKIAJAR="[JOLOKIA_JAR_INSTALL_PATH]/jolokia-jolokia-jvm-1.6.0-agent.jar"
export HDFS_NAMENODE_OPTS="-javaagent:${JOLOKIAJAR}=port=7777,host=localhost"
export HDFS_DATANODE_OPTS="-javaagent:${JOLOKIAJAR}=port=7778,host=localhost"
VMware, Inc. 155

Kafka
1 Download latest Jolokia agent JAR from https://jolokia.org/download.html.
2 Save Jolokia on your Kafka broker nodes in /opt/kafka/libs or any location accessible to
Kafka.
3 Configure Kafka to use Jolokia. Add the following lines to kafka-server-start.sh:
export JMX_PORT=9999
export
RMI_HOSTNAME=KAFKA_SERVER_IP_ADDRESS
export
KAFKA_JMX_OPTS="-javaagent:/opt/kafka/libs/jolokia-jvm-1.6.0-agent.jar
-Dcom.sun.management.jmxremote
-Dcom.sun.management.jmxremote.authenticate=false
-Dcom.sun.management.jmxremote.ssl=false
-Djava.rmi.server.hostname=$RMI_HOSTNAME
-Dcom.sun.management.jmxremote.rmi.port=$JMX_PORT"
4 Restart Kafka service.
Nginx
Add the following lines to the conf file available in /etc/nginx/nginx.conf:
http {
server {
location /status {
stub_status on;
access_log off;
allow all;
}
}
}
Restart the Nginx service with the following command:
systemctl restart nginx
Postgres
In the configuration file available in the /var/lib/pgsql/data/pg_hba.conf, change the value of

local all postgres peer to local all postgres md5 and restart the service with the following
command:
sudo service postgresql restart
Configuring HTTP/HTTPS Proxy Server in vRealize Application Remote Collector

vRealize Application Remote Collector requires a working Internet connection to connect to
Wavefront to send OS and application metrics.
VMware, Inc. 156

If a direct Internet connection is not available, a working HTTP/HTTPS proxy must be available
through which vRealize Application Remote Collector can connect to the Internet. vRealize
Application Remote Collector uses pure HTTPS connections to connect to Wavefront. As a result,
the HTTP/HTTPS proxy must be configured to support HTTPS connections. HTTPS ensures that
the connection between vRealize Application Remote Collector and the Wavefront server is fully
encrypted and prevents man-in-the middle attacks.
There are two ways in which the HTTP/HTTPS proxy servers handle HTTPS connections.
n Pass-thru Mode. In this mode, the HTTP/HTTPS proxy server forwards the HTTPS requests
directly to the web server and does not attempt to inspect the content transferred between
the client and the server. The SSL connection is established directly between the client and
the server.
n Intercept Mode. In this mode, the HTTP/HTTPS proxy server acts as a man-in-the middle and
establishes two different SSL connections. One connection between the client and the HTTP/
HTTPS proxy and the other between the HTTP/HTTPS proxy and the web server. So, the
client does not have a direct SSL connection to the web server and the client identifies this as
a man-in-the middle attack and terminates the connection. In this mode, the CA certificate
must be added to the trusted certification authorities of the client so that it accepts the SSL
connection with the HTTP/HTTPS proxy server.
Procedure
1 Add the HTTP/HTTPS proxy details in /ucp/config/config.properties and in /ucp/

wavefront-proxy/config/wavefront.conf.
a proxyHost. The IP or FQDN of the HTTP/HTTPS proxy server.
b proxyPort. The port of the HTTP/HTTPS proxy server.
c proxyUser. The user name. If the HTTP/HTTPS proxy server needs authentication, you can
provide the user name.
d proxyPassword. The password. If the HTTP/HTTPS Proxy server needs authentication, you
can provide the password.
Note For authentication, if the proxy server requires a user name and password, do not use
Basic Authentication as the authentication method. Basic Authentication is not supported
because the password is transmitted in clear text over the network and is not secure.
VMware, Inc. 157

2 Add the HTTP/HTTPS proxy server's CA certificate to the trust store of vRealize Application
Remote Collector.
a Export the CA certificate from the HTTP/HTTPS proxy server. You can refer to the HTTP/
HTTPS Proxy server's documentation for information about how to export the CA
certificate.
b Copy the exported CA certificate to the vRealize Application Remote Collector.
c To import the CA certificate into the trust store of vRealize Application Remote Collector,
run the following command:
n keytool -import -alias charles -keystore /usr/java/jre-vm^Cre/lib/

security/cacerts –file PATH_TO_CERT
n Enter the password when prompted. The password is changeit.
3 Restart the vRealize Application Remote Collector API server and the Wavefront proxy
components.
a docker restart ucp-apis.
b docker restart wavefront-proxy.
The Wavefront proxy components do not run if you have not configured Wavefront
details in vRealize Operations Manager. In such a scenario, you do not have to restart the
Wavefront proxy components.
Upgrade
Before You Upgrade

Follow the recommended upgrade flow if you have version vRealize Operations Manager prior to
version 7.5, and version 1.x of vRealize Application Remote Collector installed. Version 7.5 of
vRealize Application Remote Collector is compatible with version 7.5 of vRealize Operations
Manager only. Prepare for downtime during the vRealize Application Remote Collector upgrade
process. There will be no flow of metrics from the VMs until the upgrade process finishes. After
you upgrade vRealize Application Remote Collector, you must update the agents in the
endpoints.
Recommended Upgrade Flow
n Upgrade vRealize Operations Manager from version 6.x or 7.0 to version 7.5.
n Upgrade vRealize Application Remote Collector to version 7.5.
n If you have configured vRealize Application Remote Collector with Wavefront, update the
endpoint agents to discover new services. For more information, see Manage Agents in
Virtual Machines.
VMware, Inc. 158

Upgrade an Existing Installation

You must upgrade an existing installation of vRealize Application Remote Collector to ensure
enhanced compatibility with vRealize Operations Manager and Wavefront. You must log in to
your existing vRealize Application Remote Collector VAMI portal to perform the upgrade.
Prerequisites
You must have vRealize Application Remote Collector already installed. You must have the root
credentials to log in to the VAMI portal before you perform the upgrade:
Procedure
1 Log in to VAMI using the root credentials. The URL to log in to VAMI is:
https://<IP>:5480
2 Click the Update tab.
3 Click the Status tab, click Check Updates under Actions.
4 Click Install Updates.
5 After the updates have installed, click Reboot in the System tab.
Results
vRealize Application Remote Collector is successfully installed. You can check the version number
in Update tab under Status in VAMI.
What to do next
n If you have configured vRealize Application Remote Collector with Wavefront, update the
endpoint agents to discover new services. For more information, see Manage Agents in
Virtual Machines.
n To access the virtual machine appliance through ssh, start the sshd service.
Post Installation
Configure Network Time Protocol Settings

After you install or upgrade to vRealize Application Remote Collector version 7.5, you must set
up accurate timekeeping as part of the deployment. If the time settings between vRealize
Application Remote Collector and vRealize Operations Manager are not synchronized, you will
face agent installation and metric collection issues. Ensure time synchronization between the
endpoint VMs, vCenter Server, ESX Hosts and vRealize Operations Manager using the Network
Time Protocol (NTP).
VMware, Inc. 159

Procedure
1 Log in to the vRealize Application Remote Collector appliance and modify the ntp.conf file
available in /etc/ntp.conf by adding following in the following format:
server time.vmware.com
Note Replace time.vmware.com with a suitable time server setting. You can use the FQDN or
IP of the time server.
2 Enter the following command to start the NTP daemon:
systemctl start ntpd
3 Enter the following command to enable the NTP daemon:
systemctl enable ntpd
4 Run the following command to verify if NTP is configured correctly:
ntpstat
If NTP is synchronized correctly, you will see a message similar to the following:
synchronised to NTP server (10.113.60.176) at stratum 3
time correct to within 50 ms
polling server every 64 s
Troubleshooting your Deployment
Troubleshoot Agent Installation and Metric Collection Issues

If the time settings between vRealize Application Remote Collector and vRealize Operations
Manager are not synchronized, you may face agent installation and metric collection issues.
Eventually, you may not see any metrics in the Wavefront or vRealize Operations Manager
dashboards.
Problem
You may notice the following issues in vRealize Operations Manager and Wavefront:
n You cannot add vRealize Application Remote Collector to vRealize Operations Manager
n You cannot install an agent in the Windows and Linux target VMs.
n You cannot see the monitored metrics in Wavefront or vRealize Operations Manager.
Cause
Time synchronization is a prerequisite of the TLS/SSO communication between client and server.
VMware, Inc. 160

If the vRealize Operations Manager and vRealize Application Remote Collector are not time
synchronized, the test connection fails while configuring vRealize Application Remote Collector in
If the Windows and Linux target VMs are not time synchronized with vRealize Operations
Manager, communication between vRealize Application Remote Collector and agents will break
after installing the agents. Hence monitored metrics will not be not sent to Wavefront or vRealize
Operations Manager . Alternatively, stop and restart the agent to resolve this issue.
Solution
1 Check the vRealize Operations Manager support bundle in the following path: COLLECTOR/
adapters/APPOSUCPAdapter/ for errors.
2 Check the vRealize Application Remote Collector support bundle, ucpapi.log, for errors.
3 Ensure time synchronization between vRealize Application Remote Collector, vRealize

Operations Manager and the Windows and Linux target VMs.
4 To start and restart the agent, see Manage Agents in Virtual Machines.
Download Support Bundles

Download the support bundles from the virtual machines where you deployed vRealize
Application Remote Collector. For Linux and Windows end point VMs, run the specified command
and access the support bundle. Support bundles are required to troubleshoot any problem
related to vRealize Application Remote Collector.
1 Access the VAMI page by entering https://<vRealize Application Remote Collector

hostname>:5480
2 Log in with root credentials.
3 Click the Support Bundle tab. Click the Generate Logs for VA button.
vRealize Application Remote Collector creates the support bundles which you can download.
For End Point VMs
1 Log in to the end point.
2 Run the following commands based on the end point VM's operating system type:
For Linux End Point VMs
/opt/vmware/ucp/ucp-minion/bin/ucp-minion.sh --config /opt/vmware/ucp/salt-minion/etc/salt/grains

--action gen_support_bundle --log_level INFO
The support bundle is generated and placed as a ZIP file in the /opt/vmware/ucp/support-
bundle-endpoints/ directory.
For Windows End Point VMs
C:\VMware\UCP\ucp-minion\bin\ucp-minion.bat --config C:\VMware\UCP\salt\conf\grains --action

gen_support_bundle --log_level INFO
VMware, Inc. 161

The support bundle is generated and placed as a ZIP file in the %SystemDrive%\VMware\UCP
\support-bundle-endpoints\ directory.
Troubleshooting Upgrade
You may see error messages or may see inconsistent status icons in vRealize Operations
Manager if you do not upgrade to the compatible versions of vRealize Operations Manager and
vRealize Application Remote Collector.
Problem
vRealize Application Remote Collector UI Problems
n You cannot update your endpoint VM to have the latest vRealize Application Remote
Collector agent.
n If you bootstrap/re-bootstrap a VM after upgrading vRealize Application Remote

Collector you cannot activate the newly discovered application. You see an error
message if you try to activate it.
Manage vRealize Application Remote Collector UI Problems
n You can see an option to update the endpoint agent but you are unable to perform the
update.
n Services supported in the latest versions of vRealize Application Remote Collector cannot
be discovered.
Cause
The first set of problems occur because vRealize Application Remote Collector is upgraded to
version 7.5 but vRealize Operations Manager is an old version.
The second set of problems occur because vRealize Operations Manager is upgraded to version
7.5 but vRealize Application Remote Collector is in version 1.x.
Solution
u Upgrade to the compatible versions of vRealize Operations Manager and vRealize Application
Remote Collector.
Backup and Restore a vRealize Application Remote Collector Instance

You can run the backup and restore script to ensure that VMware vRealize Operations Manager
continues to receive data after the vRealize Application Remote Collector instance becomes
unavailable. All the existing endpoints that are configured will automatically connect back to
vRealize Application Remote Collector and continue to send data after you restore the vRealize
Application Remote Collector instance.
The task is divided into two parts. The first part involves performing an on-demand back up of
the vRealize Application Remote Collector connection and configuration details. A cron job also
performs the back up automatically every day.
VMware, Inc. 162

The second part involves restoring the vRealize Application Remote Collector instance using the
backup file that you created, or the backup file created by the cron job.
Prerequisites
n vRealize Application Remote Collector appliance must be configured with a static I.P. or static
FQDN. The endpoints must be configured.
n Back up the network configuration details of the vRealize Application Remote Collector
appliance. Capture the network configuration details of vRealize Application Remote Collector
either using the VAMI UI or vCenter Server Tools. Keep the network details available when
you restore the vRealize Application Remote Collector appliance from the backup.
n The sizing of the new vRealize Application Remote Collector appliance that you are restoring
a backup to, should be greater or equal to the old appliance. The network configuration,
static I.P. or static FQDN should be the same. This is to enable the endpoint VMs to reach the
new appliance.
Procedure
1 Back up a running instance of vRealize Application Remote Collector by making a copy of the
connection and configuration details.
a Connect to the virtual machine running vRealize Application Remote Collector using SSH.
b Enter the following command to access the scripts folder:
cd /ucp/ucp-config-scripts
c Run the arc-state-bundle.sh script with the backup option. The script performs a back
up or restore task based on the option you provide.
./arc-state-bundle.sh backup_state
Running this script pushes the backup file to the /ucp-bkup/state-bundles folder. The
filename is in the format Application-Remote-Collector-State-
Bundle_<<Timestamp>>.tar. This file contains the connection and configuration details for
the endpoints.
d Archive the Application-Remote-Collector-State-Bundle_<<Timestamp>>.tar file to a

remote location.
2 A cron job also runs every day and backs up the Application-Remote-Collector-State-
Bundle_<<Timestamp>>.tar file. The .tar file is stored for five days. On the sixth day, the
oldest .tar file is deleted and replaced. In order to restore the vRealize Application Remote
Collector appliance from the .tar file, archive the file to a remote location.
VMware, Inc. 163

3 Restore the backed up configuration files to a new vRealize Application Remote Collector
appliance.
a Configure the new vRealize Application Remote Collector appliance with the same
network and IP configuration as the previous appliance. This information is available in the
network configuration file that you backed up.
b Connect to the VM running vRealize Application Remote Collector using SSH.
c Retrieve the latest Application-Remote-Collector-State-Bundle_<<Timestamp>>.tar

file from the archive, and copy it to a location which is accessible by the vRealize
Application Remote Collector appliance.
d Enter the following command to access the scripts folder:
cd /ucp/ucp-config-scripts
e Run the arc-state-bundle.sh script. Use the restore option. Provide the location of the
Application-Remote-Collector-State-Bundle_<<Timestamp>>.tar file.
./arc-state-bundle.sh restore_state <<location of the backed up tar file, with the

filename.tar extension>>
The above command looks for the file starting with Application-Remote-Collector-
State-Bundle_<<Timestamp>>.tar to load. The script configures the new vRealize
Application Remote Collector appliance with the same settings as the instance that went
down, and restarts all the containers.
For example, the following command restores the appliance from the state bundle /tmp/
fromArchive/Application-Remote-Collector-State-Bundle_2019-04-02-18:31:36.tar
from the /tmp/fromArchive/ location:
./arc-state-bundle.sh restore_state "/tmp/fromArchive/Application-Remote-Collector-State-

Bundle_2019-04-02-18:31:36.tar"
Results
The restoration of the vRealize Application Remote Collector is complete, and it is available again.
The existing endpoints connect back to vRealize Application Remote Collector and continue to
send data.
What to do next
If the vRealize Application Remote Collector instance was sending data to VMware vRealize
Operations Manager, then adapter collection might fail when the vRealize Application Remote
Collector instance stops working. In the VMware vRealize Operations Manager, the status of the
adapter instances changes to indicate that it has failed. If this happens, you must manually start
the adapter instance after restoring the vRealize Application Remote Collector appliance.
Security Reference
VMware, Inc. 164

vRealize Application Remote Collector Security Information

The operation of vRealize Application Remote Collector depends on certain services, ports, and
external interfaces. Ensure that you secure them. vRealize Application Remote Collector virtual
appliance uses Photon OS by VMware v1.0 as the the guest operating system.
vRealize Application Remote Collector Services
You must secure the following components of vRealize Application Remote Collector:
Component Description
Data Plane (Emqtt) The data plane used to exchange metrics and vRealize
Application Remote Collector specific infra messages.
Ucpapi Runs the REST micro-services on top of the Xenon

platform.
Control-plane Runs saltstack and is used to control actions like triggering

the bootstrap on endpoints.
Nginx Runs the nginx service that is used to download options

and support bundles.
Virtual Appliance (Deployed as an OVF) This is the OVF that is deployed as a virtual appliance. It
comprises six containers running the Data Plane (Emqtt),
Ucpapi, Control-plane and Nginx components. The
operating system is Photon 1.0.
Endpoint Refers to one of the client machines that connects

tvRealize Application Remote Collector.
Communication Ports
vRealize Application Remote Collector uses several communication ports:
Component Port
Data Plane (Emqtt) 8883 (TCP/SSL)
Ucpapi 9000 (HTTPS)
Control-plane 4505 (TCP/SSL), 4506 (TCP/SSL)
Nginx 8999 (HTTPS)
Virtual Appliance (Deployed as an OVF) NA
Endpoint NA
VMware Appliance Management Interface (VAMI) 5480
Communication Path Ports
From To
vRealize Operations Manager vRealize Application Remote 9000, 8883

Collector
VMware, Inc. 165

Communication Path Ports
Endpoint VM vRealize Application Remote 8999, 4505, 4506, 8883

Collector
Browser Access VMware Appliance 5480

Management Interface (VAMI)
Third Party Services

Enable the following third party services for the vRealize Application Remote Collector
components:
Component Service
Virtual Appliance (Deployed as an OVF) n Docker

n Cron
n Vami
n Nginx, Data Plane (Emqtt), Salt-master, Nginx (core
component services)
n SSH (to login to the virtual appliance)
Endpoint n Ensure time-correction (Endpoints and vRealize

Application Remote Collector virtual appliance are in
time-sync)
n Virtual Machines managed under vCenter
n rpc
Location of Configuration Files

Configuration files used by the vRealize Application Remote Collector services are available in the
following locations:
Component Path
Data Plane (Emqtt) /opt/vmware/share/htdocs/ucp/temp/Confs/emqtt/

emq.conf
Ucpapi /ucp/config/config.properties
/ucp/config/endpoint_config.properties
Control-plane /ucp/salt/srv/salt/telegraf-conf/
telegraf.emqtt.windows.conf
/ucp/salt/srv/salt/telegraf-conf/
telegraf.emqtt.conf
Nginx /etc/nginx/nginx.conf
Virtual Appliance (Deployed as an OVF) /ucp/config/config-secrets.properties (Applicable to

Virtual Appliances)
Endpoint /opt/vmware/ucp/salt-minion/etc/salt/grains
VMware, Inc. 166

Default Passwords
The vRealize Application Remote Collector virtual appliance uses root user account as the service
user. No other user is created. The default root password is vmware. The root password must be
changed at first login to the vRealize Application Remote Collector console. SSH is disabled until
the default root password is changed.
The root password must meet the following requirements:
n Must be at least 8 characters long
n Must contain at least one uppercase letter, one lowercase letter, one digit, and one special
character
n Must not repeat the same character four times

vRealize Application Remote Collector Log and Configuration Files
Some configuration files contain settings that affect the security of vRealize Application Remote
Collector.
Component Path
Data Plane (Emqtt) /data1/ucp-emqtt-logs/error <#>.log

/data1/ucp-emqtt-logs/crash <#>.log
Ucpapi /data1/ucpapis/ucpapi.log
Control-plane /data1/ucp-salt/master /data1/ucp-salt/api
Nginx /data1/ucp-nginx/access.log
Virtual Appliance (Deployed as an OVF) /ucp/support-bundle/Logs
Endpoint /tmp/vmware-root/
VMwareUCP_Bootstrap_Scriptsvmware*/
uaf_bootstrap.log
/tmp/*/VMware-UCP_Bootstrap_Scripts*/
/tmp/vmware-root/VMware-
UCP_Bootstrap_Scriptsvmware*/uaf_bootstrap.log
C:\Windows\Temp\VMware-
UCP_Bootstrap_Scriptsvmware*/uaf_bootstrap.log
vRealize Application Remote Collector User Accounts

The following components do not have any user account created at the time of installation:
n Data Plane (Emqtt)
n Ucpapi
n Control-plane
n Nginx
The following accounts are created when you installvRealize Application Remote Collector:
VMware, Inc. 167

Component User Account Created At Install Privileges Assigned
Virtual Appliance (Deployed as The default root password is The root user has superuser privileges
an OVF) vmware. The root password must
be changed at first login to the
vRealize Application Remote
Collector console
Endpoint NA On Windows: LAU (UAC) should be disabled

On Linux: Non-admin users can use password-less
sudo
Security Updates and Patches

For the following components, use vami-upgrade for patching and upgrading:
n Data Plane (Emqtt)
n Ucpapi
n Control-plane
n Nginx
n Virtual Appliance (Deployed as an OVF)
For the endpoints, use the rpm install method for patching and upgrading.
Third-Party Components
vRealize Application Remote Collector use the following third-party components:
Component Third-Party Components
Virtual Appliance (Deployed as an OVF) n Openssl

n Python-2.7.13
n JRE 1.8
Endpoint n Python 2.7.15

n Salt-minion
n Telegraf
n vCenter services
Public Key, Certificate, and Keystore

The public key, the certificate, and the keystore of vRealize Application Remote Collector are
located in the virtual appliance.
VMware, Inc. 168

Component Location
Data Plane (Emqtt) Certificates and keys are stored in pem files.
n /ucp/ssl/emqtt/ca.cert.pem
n /ucp/ssl/emqtt/emqtt.cert.pem
n /ucp/ssl/emqtt/emqtt.key.pem
Ucpapi The following certificates and keys are stored in keydb:

n /ucp/ssl/ucpapi/ca.cert.pem
n /ucp/ssl/ucpapi/ucpapi.cert.pem
n /ucp/ssl/ucpapi/ucpapi.key
Nginx n /ucp/ssl/nginx/ca.cert.pem
n /ucp/ssl/nginx/nginx.cert.pem
n /ucp/ssl/nginx/nginx.key
Endpoint n /opt/vmware/ucp/certkeys/ca.pem
n /opt/vmware/ucp/certkeys/cert.pem
n /opt/vmware/ucp/certkeys/key.pem
n /etc/salt/pki/minion/minion.pem
Open Source Licenses

The open source license files are located on the vRealize Application Remote Collector virtual
appliance. Details of the open source components and licenses are available in /ucp/
open_source_licenses.txt file.
Application Monitoring
You can monitor application services supported by vRealize Application Remote Collector in
vRealize Operations Manager or in Wavefront. You can also manage the life cycle of agents and
application services on virtual machines.
For example, as an administrator, you might need to ensure that the infrastructure provided for
running the application services is sufficient and that there are no problems. If you receive a
complaint that a particular application service is not working properly or is slow, you can
troubleshoot by looking at the infrastructure on which the application is deployed. You can view
important metrics related to the applications and share the information with the team managing
the applications. You can use vRealize Operations Manager to deploy the agents and send the
related application data to Wavefront or vRealize Operations Manager. You can view the data in
the relevant Wavefront dashboard or in vRealize Operations Manager and share it with the team
so that they can troubleshoot the application service.
Using vRealize Operations Advanced edition, you can monitor operating systems in vRealize
Operations Manager or you can monitor operating systems and applications in Wavefront. Using
vRealize Operations Enterprise edition, you can monitor operating systems and applications in
vRealize Operations Manager or Wavefront.
If you had configured application monitoring in vRealize Operations Manager 7.0 using vRealize
Operations Standard edition, and you upgrade to the vRealize Operations Manager 7.5 Standard
edition, you cannot configure application monitoring.
VMware, Inc. 169

vRealize Operations Manager can monitor applications using the End Point Operations
Management Solution and vRealize Application Remote Collector.
Note You cannot run the vRealize Application Remote Collector agent on the same VM as the
End Point Operations Management agent.
To monitor and collect metrics for your applications and operating systems supported by
vRealize Application Remote Collector, follow these steps in vRealize Operations Manager:
1 Activate the VMware vRealize Application Management Pack.
For more information, see Activate the VMware vRealize Application Management Pack.
2 Configure vRealize Operations Manager to monitor applications or provide configuration

details to activate your Wavefront account.
For more information, see Configuring vRealize Operations Manager for Application
Monitoring or Configure the Wavefront Account.
3 Download the vRealize Application Remote Collector by clicking the Download icon in the
Application Remote Collector page.
For information about deploying vRealize Application Remote Collector, see Deploy vRealize
Application Remote Collector .
4 Configure an application remote collector.
For information about configuring vRealize Application Remote Collector, see Configure the
Application Remote Collector and Add and Configure an Application Remote Collector.
5 Install agents on selected VMs and discover and manage application services.
For more information, see Manage Agents in Virtual Machines.
6 Monitor your applications in vRealize Operations Manager or monitor your applications in

Wavefront.
For more information about monitoring your applications in vRealize Operations Manager, see
Monitor Applications In vRealize Operations Manager.
For more information about monitoring your applications in Wavefront, see Monitor
Applications In Wavefront and the Wavefront documentation
Activate the VMware vRealize Application Management Pack

As the first step to monitor applications, you must activate the VMware vRealize Application
Management Pack.
Procedure
1 From the menu, click Administration, and then in the left pane click Solutions > Repository.
VMware, Inc. 170

2 From the VMware Native Management Packs section, select VMware vRealize Application
Management Pack and click Activate to install the management pack.
You can access the management pack from the Configured Adapter Instances section in the
right pane. The Configure icon is enabled after you configure the vRealize Application
Remote Collector.
View the Configuration Details

You can view configuration details of the VMware vRealize Application Management Pack.
Do not add, edit, or modify operations.
To access and view the configuration details, complete the following steps:
1 In the menu, select Administration, and then from the left pane, select Solutions >
Repository.
2 From the Repository page on the right side, select VMware vRealize Application
Management Pack from the VMware Native Management Packs section, and click Activate.
The management pack is installed and appears in the Solutions page.
Configuration.
4 From the Configured Adapter Instances section in the right pane, select VMware vRealize
Application Management Pack.
5 Click the Configure icon.
The Configure icon is enabled after you have configured vRealize Application Remote
Collector.
Table 4-6. Configuration Details of the VMware vRealize Application Management Pack
Options Description
Instance Name Displays the vCenter servers that have been mapped with
the vRealize Application Remote Collector.
Display Name Displays the IP address of the vRealize Application Remote

Collector and the vCenter Server.
Application Proxy Host Displays the IP address of the vRealize Application Remote
Collector you have configured.
Mapped vCenter(s) Displays the IP address of the vCenter Server you mapped
to the vRealize Application Remote Collector.
VMware, Inc. 171

Table 4-6. Configuration Details of the VMware vRealize Application Management Pack
(continued)
Options Description
Credentials Displays the name of the credential, which is the IP address

of the vRealize Application Remote Collector.
To add credentials, click the plus sign.
n Credential Name: The name by which you are
identifying and managing the configured credentials.
n Application Proxy Username: The user account details
used in vRealize Application Remote Collector.
n Application Proxy Password: Password of the user
account in vRealize Application Remote Collector.
Collectors/Groups Select the collector that is used to manage the adapter

processes.
For detailed information about monitoring applications, see this Application Monitoring.
Configure vRealize Operations Manager to Monitor Applications

You can configure vRealize Operations Manager to monitor and collect metrics for your
applications and operating systems.
You configure vRealize Operations Manager only once.
Where You Configure vRealize Operations Manager to Monitor Applications

In the menu, select Home and then select Monitoring Applications from the left panel. Click
Configure Application Monitoring on the top right corner of the Monitoring Applications page.
Click vRealize Operations Manager.
The collection time interval is set to five minutes. Click Save to complete the configuration.
Configure the Wavefront Account

Use the Application Remote Collector page to configure a Wavefront account to monitor and
collect metrics of applications and operating systems supported by vRealize Application Remote
Collector.
You configure the Wavefront account only once.
Procedure
1 In the menu, select Home, and then from the left pane select Monitor Applications.
2 Click Configure Application Monitoring from the top right corner.
3 From the Application Remote Collector page, click VMware Wavefront.
4 Enter your Wavefront service URL, for example, http://longboard.wavefront.com.
5 Enter your API token for the Wavefront account.
You receive the Wavefront URL and the API token in an email.
VMware, Inc. 172

6 Click Test Connection to validate the connection.
7 Click Save to complete configuring your Wavefront account.
The Application Remote Collector page opens.
Configure the Application Remote Collector

The application remote collectors you add and configure are displayed in the Application
Remote Collector page.
You can view the name of the vRealize Application Remote Collector added and the number of
vCenters managed, in the Application Remote Collector page.
Where You Configure the Application Remote Collector
To configure an application remote collector, from the menu, select Administration, and then
from the left pane select Configuration > Application Remote Collector.
Table 4-7. Options

Options Description
Add You can map a vCenter Server with a vRealize Application

Remote Collector as part of the configuration process. For
more information, see Add and Configure an Application
Remote Collector.
When you click Test Connection to validate the
connection, the Review and Accept Certificate dialog box
is displayed. Click Accept if you trust the certificate.
Edit You can modify the vRealize Application Remote Collector

configuration details or the details of the vCenter Servers
that are managed.
After you modify the details and click Test Connection, the
Review and Accept Certificate dialog box is displayed if
you have not already accepted the certificate. Click Accept
if you trust the certificate. The connection is then validated.
Delete You can delete the application remote collector. Data is

sent to Wavefront. Ensure that you uninstall the agents
from the VMs that are monitored before you delete the
application remote collector.
Download You can download vRealize Application Remote Collector.

For information about deploying vRealize Application
Remote Collector, see Deploy vRealize Application Remote
Collector .
You can also view specific details from the options in the data grid.
VMware, Inc. 173

Table 4-8. Data Grid Options

Option Description
Name Displays the FQDN of the vRealize Application Remote Collector.
Application Remote Collector Version Displays the version of vRealize Application Remote Collector. A
gray dot is displayed if there is a newer version of vRealize
Application Remote Collector available.
vCenters Managed Displays the number of vCenter Servers mapped to the vRealize
Application Remote Collector.
Collector Server Status Indicates the health of the vRealize Application Remote Collector.
n Green. Indicates that the vRealize Application Remote Collector
is healthy.
n Red. Indicates that the vRealize Application Remote Collector is
not healthy.
Point to this cell to view a tooltip that displays the cause if the
health status is red.
The progress status is displayed when data collection has not
started.
Wavefront Connection Status Indicates the health of the application remote collector's connection
to Wavefront.
n Green. Indicates a healthy connection.
n Red. Indicates that the connection is not healthy.
Point to this cell to view a tooltip that displays the cause if the
health status is red.
The progress status is displayed when data collection has not
started.
Note This column is displayed only when you have configured

Wavefront for application monitoring.
Under Advanced Settings, the collection interval is set to 5 minutes.

Use a vSphere client to deploy vRealize Application Remote Collector. You can deploy the
vRealize Application Remote Collector OVA template from a file.
Prerequisites
You can download the vRealize Application Remote Collector OVA file after you log in to vRealize
Operations Manager. Download vRealize Application Remote Collector OVA file by clicking the
Download icon in the Configure Application Remote Collector page
For critical time sourcing, use the Network Time Protocol (NTP). You must ensure time
synchronization between the endpoint VMs, vCenter Server, ESX Hosts and vRealize Operations
Manager.
VMware, Inc. 174

Procedure
1 Right-click any inventory object that is a valid parent object of a virtual machine, such as a
data center, folder, cluster, resource pool, or host, and select Deploy OVF Template.
2 Select Deploy OVF Template.
3 On the Deploy OVF template page do one of the following and click Next:
u If you have a URL to the OVA template which is located on the Internet, type the URL in
the URL field. Supported URL sources are HTTP and HTTPS.
u If you have downloaded the vRealize Application Remote Collector OVA file, click Local
file and browse to the location of the file and select it.
4 On the Select a name and folder page, enter a unique name for the virtual machine or vAPP,
select a deployment location, and click Next.
The default name for the virtual machine is the same as the name of the selected OVF or
OVA template. If you change the default name, choose a name that is unique within each
vCenter Server virtual machine folder.
The default deployment location for the virtual machine is the inventory object where you
started the wizard.
5 On the Select a resource page, select a resource where to run the deployed VM template,
and click Next.
6 On the Review details page, verify the OVF or OVA template details and click Next.
Option Description
Product vRealize Application Remote Collector.
Version Version number of the vRealize Application Remote Collector.
Vendor VMWare.
Publisher Publisher of the OVF or OVA template, if a certificate included in the OVF or
OVA template file specifies a publisher.
Download size Size of the OVF or OVA file.
Size on disk Size on disk after you deploy the OVF or OVA template.
7 On the Accept license agreements page, click Accept and then Next.
8 In the Select configuration page, select the size of the deployment.
VMware, Inc. 175

9 On the Select storage page, define where and how to store the files for the deployed OVF or
OVA template.
a Select a VM Storage Policy.
This option is available only if storage policies are enabled on the destination resource.
b (Optional) Enable the Show datastores from Storage DRS clusters check box to choose
individual datastores from Storage DRS clusters for the initial placement of the virtual
machine.
c Select a datastore to store the deployed OVF or OVA template.
The configuration file and virtual disk files are stored on the datastore. Select a datastore
large enough to accommodate the virtual machine or vApp and all associated virtual disk
files.
10 On the Select networks page, select a source network and map it to a destination network.
Click Next. The source network must have a static FQDN name or static DNS.
The Source Network column lists all networks that are defined in the OVF or OVA template.
11 In the Customize template page, provide inputs to configure the vRealize Application Remote
Collector deployment. It is mandatory to give these details.
Configuration Description
API Admin User's Password Enter a password for the vRealize Application Remote Collector API admin.
The username is admin@ucp.local. This password should be used when
configuring this instance of vRealize Application Remote Collector in vRealize
Operations Manager.
Networking Properties Verify the networking properties.
12 On the Ready to complete page, review the page and click Finish.
13 After the OVA deployment is complete, you can log in to the virtual appliance from vCenter
Server. Right click the virtual appliance that you installed. Click Open Console. Use the
following credentials to log in:
Log In Details Value
Username root
Password vmware
14 Change the root user password.
Note To reset the root user password, see the KB article: 2001476
15 Enable the sshd service to access the virtual machine through ssh.
What to do next
VMware, Inc. 176

n Log in to vRealize Operations Manager and configure the agents to connect to Wavefront or
Configure Network Time Protocol Settings

After you install or upgrade to vRealize Application Remote Collector version 7.5, you must set
up accurate timekeeping as part of the deployment. If the time settings between vRealize
Application Remote Collector and vRealize Operations Manager are not synchronized, you will
face agent installation and metric collection issues. Ensure time synchronization between the
endpoint VMs, vCenter Server, ESX Hosts and vRealize Operations Manager using the Network
Time Protocol (NTP).
Procedure
1 Log in to the vRealize Application Remote Collector appliance and modify the ntp.conf file
available in /etc/ntp.conf by adding following in the following format:
server time.vmware.com
Note Replace time.vmware.com with a suitable time server setting. You can use the FQDN or
IP of the time server.
2 Enter the following command to start the NTP daemon:
systemctl start ntpd
3 Enter the following command to enable the NTP daemon:
systemctl enable ntpd
4 Run the following command to verify if NTP is configured correctly:
ntpstat
If NTP is synchronized correctly, you will see a message similar to the following:
synchronised to NTP server (10.113.60.176) at stratum 3
time correct to within 50 ms
polling server every 64 s
Add and Configure an Application Remote Collector

You can add and configure an application remote collector from the Application Remote
Collector page to manage the life cycle of agents and application services.
VMware, Inc. 177

To add and configure a vRealize Application Remote Collector, in the menu, click Administration,
and then in the left pane select Configuration > Application Remote Collector.
Note Time synchronization between vRealize Application Remote Collector and vRealize
Operations Manager is mandatory when you add an application remote collector. If the time
settings are not synchronized, you face problems such as, a failed test connection when you add
an application remote collector, agent installation issues, and issues in metrics collection after the
agent is installed. For more information, see Troubleshoot Agent Installation and Metric Collection
Issues.
For more troubleshooting information on vRealize Application Remote Collector, see

Troubleshooting your Deployment.
Prerequisites
n Verify that you have configured a vCenter adapter. The vCenter Server user account with
which the vCenter adapter is configured in vRealize Operations Manager, should have the
following permissions: Guest operation modifications, Guest operation program execution, and
Guest operation queries. See Install an Agent.
n Ensure that the ports for vRealize Application Remote Collector are open. For more
information on ports, see vRealize Application Remote Collector Security Information.
n Download and deploy vRealize Application Remote Collector.
You can download vRealize Application Remote Collector by clicking the Download icon in
the Configure Application Remote Collector page.
For information about deploying the vRealize Application Remote Collector, see Deploy
vRealize Application Remote Collector .
n Configure network protocol settings. For more information, see Configure Network Time
Protocol Settings.
Procedure
1 To configure a vRealize Application Remote Collector, click the Add icon from the Application
Remote Collector page.
2 In the Application Remote Collector page, enter the following details:
a FQDN of the vRealize Application Remote Collector you have configured during the
installation of vRealize Application Remote Collector.
b You cannot modify the user name which is admin.
c The API password of the vRealize Application Remote Collector you have configured
during the installation of vRealize Application Remote Collector.
d Click Next.
VMware, Inc. 178

3 From the Map vCenters page, complete the following steps:
a Select the vCenter Servers to which you want to map the vRealize Application Remote
Collector.
If you have mapped a vCenter Server to a vRealize Application Remote Collector, it is not
displayed in the drop-down menu.
b The vCenter Servers that are mapped to the vRealize Application Remote Collector are
displayed on the page.
c Click Test Connection to validate the connection. The Review and Accept Certificate
dialog box is displayed. Click Accept if you trust the certificate.
If the mapped vCenter Server turns red, it signifies that vRealize Operations Manager
cannot communicate with the vRealize Application Remote Collector. If the mapped
vCenter Server turns green, it signifies that vRealize Operations Manager can
communicate with the vRealize Application Remote Collector.
d Click Next.
4 From the Summary page, you view details such as the FQDN, user name, and the vCenter
Servers that are mapped to an instance of the vRealize Application Remote Collector.
It might take up to 5 minutes to get the status of vRealize Application Remote Collector.
a Click Finish.
What to do next
Install agents on the VMs you prefer and manage the application services.
Manage Agents in Virtual Machines

After you have configured the vRealize Application Remote Collector and mapped it to a vCenter
Server, you can manage the agents on the VMs from the Inventory page. You can view the data
centers, hosts, and clusters available in the vCenter Servers you have mapped to vRealize
Application Remote Collector. You can install, uninstall, start, stop, and update the agents on the
VMs. You can also discover and manage the services on each agent that you install.
Where You Manage the Agents

To manage the agents and application services, in the menu, select Administration, and then
from the left pane select Inventory. From the right pane, click the Manage Agents tab.
Table 4-9. Options

Options Description
Install Installs the agents on the selected VM. Select the VMs on which you want to install
the agent and click the Install icon.
Uninstall Uninstalls the agent. Select the VMs on which you want to uninstall the agent and
click the Uninstall icon.
VMware, Inc. 179

Table 4-9. Options (continued)

Options Description
Update Updates agents that are at a lower version. Select the VMs on which you want to
update the agent and click the Update icon. After the agents are updated, the
agent status changes to Update Success.
Start If you have temporarily stopped sending metrics to vRealize Operations Manager
or Wavefront, you can use this option to start data collection for the application
service.
Stop During a maintenance period, you can temporarily stop sending application
service metrics to vRealize Operations Manager or Wavefront. Select the VMs on
which you want to stop the agent and click the Stop icon.
Manage Service You can manage the application services that are discovered on the virtual
machines where the agents are installed.
Show Detail Displays the Summary tab of the selected VM.
All Filters Filters the VMs based on the name of the VM, the operating system it runs on, the
application service discovered, and the power status of the VM.
You can also view specific details from the options in the data grid.
Table 4-10. Data Grid Options

Option Description
VM Name Name of the virtual machine.
Operating System Operating system installed on the VM.
Services Discovered List of the supported application services discovered on the VM.
n A red dot against the application service indicates that the
application service has been activated but there is a problem
with data collection.
When there is more than one application service of the same

kind, and one of them is activated, but the other is not collecting
data, a red dot is still displayed against the application service.
n A gray dot before the application service indicates that the
agent requires reactivation. The application service must be
reactivated. For reactivation, see Activate and Deactivate an
Application Service for more information.
n A steel blue dot indicates that the agents have stopped.
n A green dot against the application service indicates that the
application service is activated.
n If an application service has been deactivated or not activated,
you will not see a symbol displayed against the application
service.
n After you have added the parameters and activated the
application service, the progress status is displayed until data
collection starts.
Click the colored dots for more information about the application
services.
VMware, Inc. 180

Table 4-10. Data Grid Options (continued)

Option Description
Agent Status Displays the status of the agent at the end point.
n Blue icon. Indicates that the agent is not installed.
n Green dot. Indicates that the agent is running.
n Red dot. Indicates that the agent has stopped.
Last Operation Status Status of the last operation. The possible values are:
n No Operation
n Install Success
n Install Failed
n Install In Progress
n Start Success
n Start Failed
n Start In Progress
n Stop Success
n Stop Failed
n Stop In Progress
n Update Success
n Update Failed
n Update In Progress
n Uninstall Success
n Uninstall Failed
n Uninstall In Progress
VM State Power status of the VMs. The possible values are:

n Powered On
n Powered Off
ARC FQDN of the instance of the vRealize Application Remote Collector

that you are using.
Agent Version Version of the vRealize Application Remote Collector agent on the
VM. A gray dot is displayed if the VM requires an update.
vCenter Name Name of the vCenter Adapter instance to which that VM resource
belongs.
To manage the agent, follow these steps:
1 Install the agent.
For more information, see Install an Agent.
2 Manage the application services on each agent.
For more information, see Manage Application Services.
3 Stop and start the agents on the VMs.
4 Uninstall the agent.
For more information, see Uninstall an Agent.
VMware, Inc. 181

5 Update agents that are at a lower version.
Install an Agent
You must select the VMs on which you want to install the agent. If you have upgraded an existing
installation of vRealize Application Remote Collector, reinstall the agents that you have previously
installed.
Prerequisites
n Time synchronization between vRealize Application Remote Collector, vRealize Operations

Manager, ESX hosts, and Windows and Linux target VMs is mandatory for secure
communication.
n vRealize Application Remote Collector requires guest operation privileges to install agents on
virtual machines. The vCenter Server user account with which the vCenter adapter is
configured in vRealize Operations Manager, should have the following permissions: Guest
operation modifications, Guest operation program execution, and Guest operation queries.
n Account privilege prerequisites. See User Account Prerequisites for more details.
n End-point VM configuration requirements.
n Linux requirements
Commands: /bin/bash, sudo, tar, awk, curl
Packages: coreutils (chmod, chown, cat), shadow-utils (useradd, groupadd, userdel,

groupdel)
Configure mount point on /tmp directory to allow script execution.
n Windows 2012 R2 requirement
The end point must be updated with the Universal C Runtime. Refer to the following link
for more information.
n Windows requirement
The Visual C++ version must be higher than 14.
n VMware Tools must be installed and running on the VM on which you want to install the
agent. For information about supported VMware Tools versions, click this Supported Versions
of vSphere and VMware Cloud on AWS .
Procedure
1 From the Manage Agents tab, click the Install icon. You see the Manage Agent dialog box.
VMware, Inc. 182

2 From the How do you want to provide VM Credentials page, complete the following steps:
a If you have a common user name and password for all the VMs, select the Common
username and password option.
b If you have different user names and passwords for all the VMs, select the Enter virtual
machine credentials option.
c Click Next.
3 From the Provide Credentials page, depending on whether you have a common credential
for all VMs or different credentials for all VMs, enter the following details:
a If the selected VMs have a common user name and password, enter the common user
name and password.
b For different user names and passwords for each VM, download the CSV template and
add the required details such as the user name, password for each VM. Use the Browse
button to select the template.
c The Create run time user on Linux virtual machines, with required permissions as part
of agent installation check box is selected by default. For more information, see User
Account Prerequisites.
d Click Next.
4 From the Summary page, you can view the list of VMs on which the agent is deployed.
5 Click Install Agent. Refresh the UI to view the agents that are installed.
The agent discovers the application services that are installed on the VMs and the application
services are displayed in the Services Discovered column in the Manage Agents tab. You can
view the status of agent installation from the Agent Status column in the Manage Agents tab.
What to do next
You can manage the services on each agent.

User Account Prerequisites
There are certain user account prerequisites required for the install of agents.
Prerequisites for Windows End Points
n To install agents,
n The user must be either an administrator, or
n A non-administrator who belongs to the administrator group with UAC disabled on the
operating system.
To disable UAC (previously known as LUA) on Windows, complete the following steps:
n In the registry path HKLM:\Software\Microsoft\Windows\CurrentVersion\Policies

\System, set the value for the key EnableLUA to 0.
VMware, Inc. 183

n Reboot the machine for the changes to take effect.
Note If the domain user has UAC enabled, see KB 70780 for more details.
Prerequisites for Linux End Points
n /tmp mount point should be mounted with exec mount option.
n Ensure that the following lines exist in /etc/sudoers.
1.root ALL=(ALL:ALL) ALL

2.Defaults:root !requiretty
3.Defaults:arcuser !requiretty
(1) can be omitted if password-less sudo is already enabled for the root user. (2) and (3) can
be omitted if your end point VMs are already configured to turn off requiretty.
For Linux end points, there are two user accounts, such as the install user and the run-time user.
Install User Prerequisites
You can use one of the following install users for Linux end points.
n root user - All privileges
n A non-root user with all privileges -
Password-less sudo elevation access for a non-root user or a non-root user group.
To enable password-less sudo elevation access for a user called bob, add bob
ALL=(ALL:ALL) NOPASSWD: ALL to /etc/sudoers.
To enable password-less sudo elevation access for a user group called bobg, add %bobg
ALL=(ALL:ALL) NOPASSWD: ALL to /etc/sudoers.
n A non-root user with a specific set of privileges -
Password-less sudo elevation access for a non-root user with access to certain commands.
To enable password-less sudo elevation access for the ARC_INSTALL_USER, add the
following corresponding entries to the sudoers file:
Defaults:ARC_INSTALL_USER !requiretty
Cmnd_Alias ARC_INSTALL_USER_COMMANDS=/usr/bin/cp*,/bin/cp*,/usr/bin/mkdir*,/bin/mkdir*,/usr/bin/
chmod*,/bin/chmod*,/opt/vmware/ucp/bootstrap/uaf-bootstrap.sh,/opt/vmware/ucp/ucp-minion/bin/ucp-
minion.sh
ARC_INSTALL_USER ALL=(ALL)NOPASSWD: ARC_INSTALL_USER_COMMANDS
For example,for a user bob, add the following lines to /etc/sudoers:

Defaults:bob !requiretty
Cmnd_Alias ARC_INSTALL_USER_COMMANDS=/usr/bin/cp*,/bin/cp*,/usr/bin/mkdir*,/bin/mkdir*,/usr/bin/
chmod*,/bin/chmod*,/opt/vmware/ucp/bootstrap/uaf-bootstrap.sh,/opt/vmware/ucp/ucp-minion/bin/ucp-
minion.sh
bob ALL=(ALL)NOPASSWD: ARC_INSTALL_USER_COMMANDS
Run-Time User Prerequisites
VMware, Inc. 184

There are two ways in which a run-time user is created in Linux end points: automatically and
manually. A run-time user has a standard name and group, which is the arcuser and arcgroup
respectively. By default, the arcuser and arcgroup are created automatically. If you choose to
manually create the arcuser and arcgroup, here are the prerequisites:
n Manually created arcuser and arcgroup.
Create the arcgroup and arcuser and associate the arcgroup as the primary group of the
arcuser. Here are the requirements:
a The arcgroup must be the primary group of the arcuser.
For example, the following commands can be used to create the arcgroup and arcuser:
groupadd arcgroup
useradd arcuser -g arcgroup -M -s /bin/false
b The arcuser must be created with no home directory and no access to the login shell.
For example, the etc/passwd entry for the arcuser is as follows after adding arcuser and
arcgroup.
arcuser:x:1001:1001::/home/arcuser:/bin/false
c The arcuser must have either password-less all privileges or password-less specific set of
privileges as mentioned below:
To enable password-less sudo elevation access for the run-time arcuser, add the
following corresponding entries to the sudoers file.
All privileges:
arcuser ALL=(ALL:ALL) NOPASSWD: ALL
Specific set of privileges:
Cmnd_Alias ARC_RUN_COMMANDS=/usr/bin/systemctl * ucp-telegraf*,/bin/systemctl * ucp-

telegraf*, /usr/bin/systemctl * ucp-minion*, /bin/systemctl * ucp-minion*, /usr/bin/systemctl
* salt-minion*, /bin/sytemctl * salt-minion*, /usr/bin/netstat, /bin/netstat, /opt/
vmware/ucp/tmp/telegraf_post_install_linux.sh, /opt/vmware/ucp/bootstrap/uaf-
bootstrap.sh, /opt/vmware/ucp/uaf/runscript.sh, /opt/vmware/ucp/ucp-minion/bin/ucp-minion.sh
arcuser ALL=(ALL) NOPASSWD: ARC_RUN_COMMANDS
Manage Application Services

You can manage the application services supported by vRealize Application Remote Collector on
the VMs where the agents are installed.
Procedure
1 Select a VM on which the agent has been installed and the application services have been
discovered, from the Manage Agents tab.
2 Select Manage Service and then from the drop-down menu select the service name. You see
the Manage <service name> Agent dialog box.
VMware, Inc. 185

3 By default, all metrics are collected for the activated application service.
4 Activate data collection for the application service.
5 Enter the relevant settings for the application service.
6 Click Confirm.
Fields with a star are mandatory.

For more information about the status details that appear against the application services in
the Services Discovered column, see the table called Data Grid Options in Manage Agents in
Virtual Machines.
For information about supported application services and their properties, see Configuring
Supported Application Services.
What to do next
You can view the metrics collected for each application service in the Wavefront dashboards or
monitor the applications services from vRealize Operations Manager.
Activate and Deactivate an Application Service

To monitor application services running on the target VMs, vRealize Application Remote Collector
plugins must be configured in the target VMs after the agent is installed.
After you have installed the agent, you can choose to activate or deactivate vRealize Application
Remote Collector plugins to monitor application services. You can also reactivate plugins that
need to be monitored.
Prerequisite
n If plugin activation requires the location of a file (for example, client certificates for SSL Trust)
on the endpoint VM, the location and the files should have appropriate read permissions for
the arcuser to access those files.
Note If the plugin displays a permission denied status, provide the arcuser with permissions
to the file locations that you have specified during plugin activation.
Activate an Application Service
To monitor an application service, complete the following steps:
1 Navigate to the Inventory > Manage Agents tab.
2 Select the VM on which agent is already installed.
3 Select Manage Service icon and then from the drop-down menu select the service name.
4 Activate the application service from the right pane of the Manage <service name> Agent
dialog box.
5 Click the Add icon in the left pane to add multiple instances of the application service.
6 Click the Delete icon in the left pane to delete instances of the application service.
VMware, Inc. 186

7 Enter the details for each instance that you add and click Save.
For more information about the status details that appear against the application services in
the Services Discovered column, see the table called Data Grid Options in Manage Agents in
Virtual Machines.
The following special characters are permitted in the DB user field: '[]{} (),.<> ?:!|/~@#$%^&*- _
+=
You can provide DB name lists in the following format ['DBNAME_1', 'DBNAME_2', 'DBNAME_3']
where DBNAME_1, DBNAME_2, DBNAME_3 must not contain quotes such as ' and ".
Note When multiple VMs are selected, the Manage Service option is disabled.
Deactivate an Application Service
To deactivate a plugin to stop monitoring the application service that is sending data to vRealize
Operations Manager or Wavefront, complete the following steps:
1 Navigate to the Inventory > Manage Agents tab.
2 Select the VM on which the agent is already installed.
3 Select the Manage Service icon and then from the drop-down menu select the service name.
4 Deactivate the application service from the right pane of the Manage <service name> Agent
dialog box.
5 Click the Add icon in the left pane to add multiple instances of the application service.
6 Click the Delete icon in the left pane to delete instances of the application service.
7 Click Save.
When you stop an agent, you cannot activate or deactivate a plugin. If the VM is powered off or
if you lose connection with vRealize Application Remote Collector, you cannot configure or
activate a plugin.
Uninstall an Agent
You must select the VMs on which you want to uninstall the agent.
Procedure
1 From the Manage Agents tab, click the Uninstall icon. You see the Manage Agent dialog box.
2 From the How do you want to provide VM Credentials page, complete the following steps:
a If you have a common user name and password for all the VMs, select the Common
username and password option.
b If you have different user names and passwords for all the VMs, select the Enter virtual
machine credentials option.
c Click Next.
VMware, Inc. 187

3 From the Provide Credentials page, depending on whether you have a common credential
for all VMs or different credentials for all VMs, enter the following details:
a If your VM has a single user name and password, enter the common user name and
password.
b For multiple user names and passwords for each VM, download the CSV template and
add the details. Use the Browse button to select the template.
c Click Next.
4 From the Summary page, you can view the list of VMs on which the agent is deployed.
5 Click Uninstall Agent. Refresh the UI to view the progress of agent uninstallation.
The Agent Status and Services Discovered columns in the workspace indicate that
uninstallation is complete and that there are no application services discovered on each
agent.
Monitor Applications In vRealize Operations Manager

You can monitor applications and operating systems from vRealize Operations Manager to view
services and processes.
Where You Monitor Applications in vRealize Operations Manager

From the menu, select Home, and then in the left pane select Monitor Applications.
Discovered Operating Systems and Services

You see the application services that are discovered on the virtual machines where the agents
are installed. From the Discovered Operating Systems and Services section in the Monitor
Applications page, click the text next to the number to view the status of the agent, the
operation status, the power status of the VM, and the list of supported application services
discovered on the VM. For more information, see Manage Agents in Virtual Machines.
Supported Operating Systems

You see a list of supported operating systems for which vRealize Operations Manager collects
metrics using the vRealize Application Remote Collector.
Supported Services
You see a list of supported services for which vRealize Operations Manager collects metrics using
the vRealize Application Remote Collector.
Monitor Applications In Wavefront

To monitor metrics for the application services you have activated, open Wavefront and view the
dashboards that are populated with data.
You can also access Wavefront by selecting Administration in the menu, and then from the left
pane, select Configuration > Application Remote Collector. From the right pane, click the View
in Wavefront button at the top right corner of the page.
VMware, Inc. 188

From the Wavefront home page, select Integrations and click the application service you have
activated. From the Dashboard tab, click the application link. Select View > Source and enter the
Virtual Machine name.
When you design custom dashboards, remember that the Virtual Machine Name is the source
tag and data is collected through vRealize Application Remote Collector. In addition to the source
tag, there are two common point tags for all metrics in vRealize Application Remote Collector.
This is the vc_uuid tag that carries the UUID of the vCenter Server that manages the relevant
virtual machine and the vm_mor point tag that carries the Managed Object Reference ID of the
relevant virtual machine.
For more information, see the Wavefront documentation.
Operating System Metrics Collected by vRealize Application Remote Collector

vRealize Application Remote Collector collects metrics for Linux and Windows operating systems.
Linux Platforms
vRealize Application Remote Collector collects the following metrics for Linux Operating Systems:
Table 4-11. Metrics for Linux

Metric Metric Category KPI
Usage Idle CPU FALSE
Usage IO-Wait CPU FALSE
Usage System CPU FALSE
IO Time Disk FALSE
Read Time Disk FALSE
Reads Disk FALSE
Write Time Disk FALSE
Writes Disk FALSE
Cached Memory FALSE
Free Memory FALSE
Inactive Memory FALSE
Total Memory TRUE
Used Memory TRUE
Used Percent Memory TRUE
Blocked Processes TRUE
Dead Processes FALSE
Running Processes FALSE
Sleeping Processes FALSE
Stopped Processes FALSE
Free Swap FALSE
VMware, Inc. 189

Table 4-11. Metrics for Linux (continued)

In Swap FALSE
Out Swap FALSE
Total Swap TRUE
Used Swap TRUE
Used Percent Swap TRUE
Windows Platforms
vRealize Application Remote Collector collects the following metrics for Windows Operating
Systems:
Table 4-12. Metrics for Windows

Idle Time CPU FALSE
Interrupt Time CPU FALSE
Interrupts persec CPU TRUE
Privileged Time CPU FALSE
Processor Time CPU FALSE
User Time CPU FALSE
Avg. Disk Bytes Read Disk FALSE
Avg. Disk sec Read Disk FALSE
Avg. Disk sec Write Disk FALSE
Avg. Disk Write Queue Length Disk FALSE
Disk Read Time Disk FALSE
Disk Write Time Disk FALSE
Free Megabytes Disk FALSE
Free Space Disk FALSE
Idle Time Disk FALSE
Split IO persec Disk FALSE
Available Bytes Memory TRUE
Cache Bytes Memory FALSE
Cache Faults persec Memory FALSE
Committed Bytes Memory TRUE
Demand Zero Faults persec Memory FALSE
Page Faults persec Memory TRUE
Pages persec Memory FALSE
VMware, Inc. 190

Table 4-12. Metrics for Windows (continued)

Pool Nonpaged Bytes Memory TRUE
Pool Paged Bytes Memory FALSE
Transition Faults persec Memory FALSE
Elasped Time Process FALSE
Handle Count Process FALSE
IO Read Bytes persec Process FALSE
IO Read Operations persec Process FALSE
IO Write Bytes persec Process FALSE
IO Write Operations persec Process FALSE
Privileged Time Process FALSE
Processor Time Process FALSE
Thread Count Process FALSE
User Time Process FALSE
Context Switches persec System FALSE
Processes System FALSE
Processor Queue Length System FALSE
System Calls persec System FALSE
System Up Time System FALSE
Threads System FALSE
Application Service Metrics Collected by vRealize Application Remote Collector

vRealize Application Remote Collector collects metrics for 17 application services.
Active Directory Metrics

vRealize Application Remote Collector discovers metrics for Active Directory application service.
Table 4-13. Active Directory Metrics

Metric Name Category KPI
Database Cache % Hit (%) Active Directory Database True
Database Cache Page Faults/sec Active Directory Database True
Database Cache Size Active Directory Database False
Data Lookups Active Directory DFS Replication False
Database Commits Active Directory DFS Replication True
Avg Response Time Active Directory DFSN True
Requests Failed Active Directory DFSN False
VMware, Inc. 191

Table 4-13. Active Directory Metrics (continued)

Requests Processed Active Directory DFSN False
Dynamic Update Received Active Directory DNS False
Dynamic Update Rejected Active Directory DNS False
Recursive Queries Active Directory DNS False
Recursive Queries Failure Active Directory DNS False
Secure Update Failure Active Directory DNS False
Total Query Received Active Directory DNS True
Total Response Sent Active Directory DNS True
Digest Authentications Active Directory Security System- True

Wide Statistics
Kerberos Authentications Active Directory Security System- True

Wide Statistics
NTLM Authentications Active Directory Security System- True

Wide Statistics
Directory Services:<InstanceName>| Active Directory Services True

Base Searches persec

Database adds persec

Database deletes persec

LDAP Active Threads

LDAP Client Sessions

LDAP Writes/sec
No metrics are collected for the category Active Directory.
Apache Tomcat
vRealize Application Remote Collector discovers metrics for Apache Tomcat application service.
Table 4-14. Apache Tomcat

Garbage Collection:<InstanceName>| Tomcat Server False

Total Collection Count

Total Collection Time
JVM Memory|Heap Memory Usage| Tomcat Server True

Committed Memory
VMware, Inc. 192

Table 4-14. Apache Tomcat (continued)

JVM Memory|Heap Memory Usage| Tomcat Server False

Initial Memory

Maximum Memory

Used Memory
JVM Memory|Non Heap Memory Tomcat Server True

Usage|Committed Memory
JVM Memory|Non Heap Memory Tomcat Server False

Usage|Initial Memory

Usage|Maximum Memory

Usage|Used Memory
JVM Memory|Number of Object Tomcat Server True

Pending Finalization Count
JVM Memory|Pool:<InstanceName>| Tomcat Server False

Peak Usage|Committed Memory

Peak Usage|Initial Memory

Peak Usage|Maximum Memory

Peak Usage|Used Memory




Usage|Used Memory
Process CPU Usage (%) Tomcat Server True
System CPU Usage (%) Tomcat Server True
Uptime Tomcat Server True
Cache|Hit Count Tomcat Server Web Module True
Cache|Lookup Count Tomcat Server Web Module False
JSP Count Tomcat Server Web Module False
JSP Reload Count Tomcat Server Web Module False
JSP Unload Count Tomcat Server Web Module False
VMware, Inc. 193


Current Thread Count Tomcat Server Global Request False

Processor
Current Threads Busy Tomcat Server Global Request True

Processor
Total Request Bytes Received Tomcat Server Global Request False

Processor
Total Request Bytes Sent Tomcat Server Global Request False

Processor
Total Request Count Tomcat Server Global Request True

Processor
Total Request Error Count Tomcat Server Global Request True

Processor
Total Request Processing Time Tomcat Server Global Request True

Processor
MS SQL Metrics
vRealize Application Remote Collector discovers metrics for MS SQL application service.
Table 4-15. MS SQL Metrics

CPU:<InstanceName>|CPU Usage (%) Microsoft SQL Server False
Performance|Broker Activation|Stored Microsoft SQL Server False

Procedures Invoked per second
Performance|Buffer Manager|Buffer Microsoft SQL Server False

cache hit ratio (%)
Performance|Buffer Manager|Lazy Microsoft SQL Server False

writes per second
Performance|Buffer Manager|Page life Microsoft SQL Server False

expectancy
Performance|Buffer Manager|Page Microsoft SQL Server False

lookups per second

reads per second

writes per second
Performance|Databases|Active Microsoft SQL Server False

Transactions
Performance|Databases|Data File(s) Microsoft SQL Server False

Size
Performance|Databases|Log File(s) Microsoft SQL Server False

Size
VMware, Inc. 194

Table 4-15. MS SQL Metrics (continued)


Used Size
Performance|Databases|Log Flush Microsoft SQL Server False

Wait Time
Performance|Databases|Log Flushes Microsoft SQL Server False

per second
Performance|Databases|Transactions Microsoft SQL Server False

per second
Performance|Databases|Write Microsoft SQL Server False

Transactions per second
Performance|Databases|XTP Memory Microsoft SQL Server False

Used
Performance|General Statistics|Logins Microsoft SQL Server False

per second
Performance|General Statistics| Microsoft SQL Server False

Logouts per second

Processes Blocked
Performance|General Statistics|User Microsoft SQL Server False

Connections
Performance|Locks|Average Wait Time Microsoft SQL Server False
Performance|Locks|Lock Requests per Microsoft SQL Server False

second
Performance|Locks|Lock Wait Time Microsoft SQL Server False
Performance|Locks|Lock Waits per Microsoft SQL Server False

second
Performance|Locks|Number of Microsoft SQL Server False

Deadlocks per second
Performance|Memory Manager|SQL Microsoft SQL Server False

Cache Memory
Performance|Memory Manager|Target Microsoft SQL Server False

Server Memory
Performance|Memory Manager|Total Microsoft SQL Server False

Server Memory
Performance|Resource Pool Stats| Microsoft SQL Server False

default|Active memory grant amount

default|Disk Read Bytes per second

default|Disk Read IO
VMware, Inc. 195



default|Disk Read IO Throttled per
second

default|Disk Write Bytes per second

default|Disk Write IO Throttled per
second

default|Used memory
Performance|SQL Statistics|Batch Microsoft SQL Server False

Requests per second
Performance|SQL Statistics|SQL Microsoft SQL Server False

Compilations per second
Performance|SQL Statistics|SQL Re- Microsoft SQL Server False


internal|Active memory grant amount

internal|Disk Read Bytes per second

internal|Disk Read IO

internal|Disk Read IO Throttled per
second

internal|Disk Write Bytes per second

internal|Disk Write IO Throttled per
second

internal|Used memory
Performance|Workload Group Stats| Microsoft SQL Server False

default|Blocked Tasks

default|CPU usage (%)

internal|Blocked Tasks

internal|CPU usage (%)
Wait Stats:<InstanceName>|Wait Time Microsoft SQL Server False
VMware, Inc. 196

There are no metrics collected for Microsoft SQL Server Database.
PostgresSQL
vRealize Application Remote Collector discovers metrics for PostgresSQL application service.
Table 4-16. PostgresSQL

Buffers|Buffers Allocated PostgresSQL False
Buffers|Buffers Written by Backend PostgresSQL True
Buffers|Buffers Written by Background PostgresSQL False

Writer
Buffers|Buffers Written During PostgresSQL True

Checkpoints
Buffers|fsync Call Executed by PostgresSQL True

Backend
Disk Blocks|Blocks Cache Hits PostgresSQL Database False
Disk Blocks|Blocks Read PostgresSQL Database False
Disk Blocks|Blocks Read Time PostgresSQL Database True
Disk Blocks|Blocks Write Time PostgresSQL Database True
Statistics|Backends Connected PostgresSQL Database False
Statistics|Data Written by Queries PostgresSQL Database False
Statistics|Deadlocks Detected PostgresSQL Database True
Statistics|Queries Cancelled PostgresSQL Database True
Statistics|Temp Files Created by PostgresSQL Database False

Queries
Transactions|Transactions Committed PostgresSQL Database True
Transactions|Transactions Rolled Back PostgresSQL Database True
Tuples|Tuples Deleted PostgresSQL Database True
Tuples|Tuples Fetched PostgresSQL Database False
Tuples|Tuples Inserted PostgresSQL Database True
Tuples|Tuples Returned PostgresSQL Database False
Tuples|Tuples Updated PostgresSQL Database True
IIS Metrics
vRealize Application Remote Collector discovers metrics for IIS application service.
Table 4-17. IIS Metrics

CurrentQueueSize IIS HTTP Service Request Queues True
RejectedRequests IIS HTTP Service Request Queues False
VMware, Inc. 197

Table 4-17. IIS Metrics (continued)

Web Services:<InstanceName>|Bytes IIS Web Services False

Received
Web Services:<InstanceName>| IIS Web Services False

Connection Attempts/sec
Web Services:<InstanceName>|Current IIS Web Services False

Connections
Web Services:<InstanceName>|Get IIS Web Services False

Requests/sec
Web Services:<InstanceName>|Not IIS Web Services False

Found Errors/sec
Web Services:<InstanceName>|Post IIS Web Services False

Requests/sec
Web Services:<InstanceName>|Service IIS Web Services False

Uptime
Web Services:<InstanceName>|Cache IIS Web Services Cache False

Hits

Hits Percent (%)

Misses
Web Services:<InstanceName>|File IIS Web Services Cache False

Cache Hits Percent
Web Services:<InstanceName>| IIS Web Services Cache False

Flushed URIs
MS Exchange Server Metrics

vRealize Application Remote Collector discovers metrics for MS Exchange Server application
service.
Table 4-18. MS Exchange Server Metrics

Active Manager Server|Active Manager MS Exchange False

Role
Active Manager Server|Database State MS Exchange False

Info Writes per second
Active Manager Server| MS Exchange False

GetServerForDatabase Server-Side
Calls
Active Manager Server|Server-Side MS Exchange True

Calls per second
VMware, Inc. 198

Table 4-18. MS Exchange Server Metrics (continued)

Active Manager Server|Total Number MS Exchange True

of Databases
ActiveSync|Average Request Time MS Exchange True
ActiveSync|Current Requests MS Exchange False
ActiveSync|Mailbox Search Total MS Exchange False
ActiveSync|Ping Commands Pending MS Exchange False
ActiveSync|Requests per second MS Exchange True
ActiveSync|Sync Commands per MS Exchange True

second
ASP.NET|Application Restarts MS Exchange False
ASP.NET|Request Wait Time MS Exchange True
ASP.NET|Worker Process Restarts MS Exchange False
Autodiscover Service|Requests per MS Exchange True

second
Availability Service|Average Time to MS Exchange True

Process a Free Busy Request
Outlook Web Access|Average Search MS Exchange True

Time
Outlook Web Access|Requests per MS Exchange False

second
Outlook Web Access|Current Unique MS Exchange False

Users
Performance|Database Cache Hit (%) MS Exchange Database False
Performance|Database Page Fault MS Exchange Database True

Stalls per second
Performance|I/O Database Reads MS Exchange Database True

Average Latency
Performance|I/O Database Writes MS Exchange Database True

Average Latency
Performance|I/O Log Reads Average MS Exchange Database False

Latency
Performance|I/O Log Writes Average MS Exchange Database False

Latency
Performance|Log Record Stalls per MS Exchange Database False

second
Performance|Log Threads Waiting MS Exchange Database False
Performance|I/O Database Reads MS Exchange Database Instance False

Average Latency
VMware, Inc. 199


Performance|I/O Database Writes MS Exchange Database Instance False

Average Latency
Performance|Log Record Stalls per MS Exchange Database Instance False

second
Performance|Log Threads Waiting MS Exchange Database Instance False
Performance|LDAP Read Time MS Exchange Domain Controller False
Performance|LDAP Search Time MS Exchange Domain Controller False
Performance|LDAP Searches Timed MS Exchange Domain Controller False

Out per minute
Performance|Long Running LDAP MS Exchange Domain Controller False

Operations per minute
Performance|Connection Attempts per MS Exchange Web Server True

second
Performance|Current Connections MS Exchange Web Server False
Performance|Other Request Methods MS Exchange Web Server False

per second
Process|Handle Count MS Exchange Windows Service False
Process|Memory Allocated MS Exchange Windows Service False
Process|Processor Time (%) MS Exchange Windows Service True
Process|Thread Count MS Exchange Windows Service False
Process|Virtual Memory Used MS Exchange Windows Service False
Process|Working Set MS Exchange Windows Service False
JBoss EAP Metrics

vRealize Application Remote Collector discovers metrics for JBoss EAP application service.
Table 4-19. JBoss EAP Metrics

UTILIZATION|Heap Memory Usage Jboss Server True
UTILIZATION|Collection Count Jboss JVM Garbage Collector False
UTILIZATION|Collection Time Jboss JVM Garbage Collector False
UTILIZATION|Heap Memory Usage Jboss JVM Memory True
UTILIZATION|Non Heap Memory Jboss JVM Memory False

Usage
UTILIZATION|Object Pending Jboss JVM Memory True

Finalization Count
UTILIZATION|Collection Usage Jboss JVM Memory Pool True
VMware, Inc. 200

Table 4-19. JBoss EAP Metrics (continued)

UTILIZATION|Peak Usage Jboss JVM Memory Pool False
UTILIZATION|Usage Jboss JVM Memory Pool True
RabbitMQ Metrics
vRealize Application Remote Collector discovers metrics for RabbitMQ application service.
Table 4-20. RabbitMQ Metrics

CPU|Limit RabbitMQ False
CPU|Used RabbitMQ True
Disk|Free RabbitMQ False
Disk|Free limit RabbitMQ False
FileDescriptor|Total RabbitMQ False
FileDescriptor|Used RabbitMQ False
Memory|Limit RabbitMQ False
Memory|Used RabbitMQ True
Messages|Acked RabbitMQ False
Messages|Delivered RabbitMQ False
Messages|Delivered get RabbitMQ False
Messages|Published RabbitMQ False
Messages|Ready RabbitMQ False
Messages|Unacked RabbitMQ False
Socket|Limit RabbitMQ False
Socket|Used RabbitMQ True
UTILIZATION|Channels RabbitMQ True
UTILIZATION|Connections RabbitMQ True
UTILIZATION|Consumers RabbitMQ True
UTILIZATION|Exchanges RabbitMQ True
UTILIZATION|Messages RabbitMQ True
UTILIZATION|Queues RabbitMQ True
Messages|Publish in RabbitMQ Exchange False
Messages|Publish out RabbitMQ Exchange False
There are no metrics collected for RabbitMQ Virtual Host.
VMware, Inc. 201

MySQL Metrics
vRealize Application Remote Collector discovers metrics for MySQL application service.
Table 4-21. MySQL Metrics

Aborted connection count MySQL True
Connection count MySQL True
Event wait average time MySQL False
Event wait count MySQL False
InnoDB|All deadlock count MySQL False
InnoDB|Buffer pool size MySQL True
InnoDB|Open file count MySQL False
InnoDB|Row lock average time MySQL False
InnoDB|Row lock current waits MySQL False
InnoDB|Row lock maximum time MySQL False
InnoDB|Row lock time MySQL False
InnoDB|Row lock waits MySQL True
InnoDB|Table lock count MySQL False
IO waits average time MySQL Database False
IO waits count MySQL Database True
Read high priority average time MySQL Database False
Read high priority count MySQL Database False
Write concurrent insert average time MySQL Database False
Write concurrent insert count MySQL Database False
NGINX Metrics
vRealize Application Remote Collector discovers metrics for NGINX application service.
Table 4-22. NGINX Metrics

HTTP Status Info|Accepts Nginx True
HTTP Status Info|Active connections Nginx False
HTTP Status Info|Handled Nginx True
HTTP Status Info|Reading Nginx False
HTTP Status Info|Requests Nginx False
HTTP Status Info|Waiting Nginx True
HTTP Status Info|Writing Nginx False
VMware, Inc. 202

Sharepoint Metrics
vRealize Application Remote Collector discovers metrics for Sharepoint application service.
Table 4-23. Sharepoint Metrics

Sharepoint Foundation|Active Threads SharePoint Server True
Sharepoint Foundation|Current Page SharePoint Server False

Requests
Sharepoint Foundation|Executing SQL SharePoint Server False

Queries
Sharepoint Foundation|Executing SharePoint Server True

Time/Page Request
Sharepoint Foundation|Incoming Page SharePoint Server False

Requests Rate
Sharepoint Foundation|Object Cache SharePoint Server False

Hit Count
Sharepoint Foundation|Reject Page SharePoint Server False

Requests Rate
Sharepoint Foundation|Responded SharePoint Server True

Page Requests Rate
Sharepoint Foundation|SQL Query SharePoint Server True

Executing Time
Network|Received Data Rate SharePoint Web Server True
Network|Sent Data Rate SharePoint Web Server True
Process|Processor Time (%) SharePoint Windows Service False
Process|Threads SharePoint Windows Service False
Oracle Weblogic Metrics

vRealize Application Remote Collector discovers metrics for Oracle Weblogic application service.
Table 4-24. Oracle Weblogic Metrics

UTILIZATION|Process Cpu Load Oracle WebLogic Server True
UTILIZATION|System Cpu Load Oracle WebLogic Server False
UTILIZATION|System Load Average Oracle WebLogic Server False
UTILIZATION|Collection Time Weblogic Garbage Collector True
UTILIZATION|Connections HighCount Weblogic JMS Runtime True
UTILIZATION|JMS Servers TotalCount Weblogic JMS Runtime False
UTILIZATION|Active Total Count Used Weblogic JTA Runtime False
UTILIZATION|Active Transactions Weblogic JTA Runtime False

TotalCount
VMware, Inc. 203

Table 4-24. Oracle Weblogic Metrics (continued)

UTILIZATION|Transaction Abandoned Weblogic JTA Runtime True

TotalCount
UTILIZATION|Transaction RolledBack Weblogic JTA Runtime True

App TotalCount
UTILIZATION|Heap Memory Usage Weblogic JVM Memory True
UTILIZATION|Non Heap Memory Weblogic JVM Memory False

Usage
UTILIZATION|Peak Usage Weblogic JVM Memory Pool True
UTILIZATION|Usage Weblogic JVM Memory Pool False
UTILIZATION|UpTime Weblogic JVM Runtime False
Pivotal TC Server Metrics

vRealize Application Remote Collector discovers metrics for Pivotal TC Server application service.
Table 4-25. Pivotal TC Server Metrics

Garbage Collection:<InstanceName>| Pivotal TC Server False


Process CPU Usage (%) Pivotal TC Server True
System CPU Usage (%) Pivotal TC Server True
Uptime Pivotal TC Server True
JVM Memory|Heap Memory Usage| Pivotal TC Server True

Committed Memory
JVM Memory|Heap Memory Usage| Pivotal TC Server False

Initial Memory

Maximum Memory

Used Memory
JVM Memory|Non Heap Memory Pivotal TC Server True

JVM Memory|Non Heap Memory Pivotal TC Server False



Usage|Used Memory
VMware, Inc. 204

Table 4-25. Pivotal TC Server Metrics (continued)

JVM Memory|Number of Object Pivotal TC Server True

JVM Memory|Pool:<InstanceName>| Pivotal TC Server False








Usage|Used Memory
Current Thread Count Pivotal TC Server Thread Pool False
Current Threads Busy Pivotal TC Server Thread Pool True
Total Request Bytes Received Pivotal TC Server Thread Pool False
Total Request Bytes Sent Pivotal TC Server Thread Pool False
Total Request Count Pivotal TC Server Thread Pool True
Total Request Error Count Pivotal TC Server Thread Pool True
Total Request Processing Time Pivotal TC Server Thread Pool True
JSP Count Pivotal TC Server Web Module False
JSP Reload Count Pivotal TC Server Web Module False
JSP Unload Count Pivotal TC Server Web Module False
ActiveMQ Metrics
vRealize Application Remote Collector discovers metrics for ActiveMQ application service.
Table 4-26. ActiveMQ Metrics

UTILIZATION|Process CpuLoad Active MQ True
UTILIZATION|Memory Limit ActiveMQ Broker True
UTILIZATION|Memory Percent Usage ActiveMQ Broker True

(%)
UTILIZATION|Total Consumer Count ActiveMQ Broker True
VMware, Inc. 205

Table 4-26. ActiveMQ Metrics (continued)

UTILIZATION|Total Dequeue Count ActiveMQ Broker True
UTILIZATION|Total Enqueue Count ActiveMQ Broker True
UTILIZATION|Total Message Count ActiveMQ Broker True
UTILIZATION|Heap Memory Usage ActiveMQ JVM Memory Usage True
UTILIZATION|Non Heap Memory ActiveMQ JVM Memory Usage False

Usage
UTILIZATION|Object Pending ActiveMQ JVM Memory Usage True

FinalizationCount
UTILIZATION|Process CpuLoad ActiveMQ OS False
UTILIZATION|System Cpu Load ActiveMQ OS False
UTILIZATION|Consumer Count ActiveMQ Topic True
UTILIZATION|Dequeue Count ActiveMQ Topic True
UTILIZATION|Enqueue Count ActiveMQ Topic True
UTILIZATION|Queue Size ActiveMQ Topic True
Apache HTTPD Metrics

vRealize Application Remote Collector discovers metrics for Apache HTTPD application service.
Table 4-27. Apache HTTPD Metrics

UTILIZATION|Busy Workers Apache HTTPD True
UTILIZATION|Bytes Per Req Apache HTTPD False
UTILIZATION|Bytes Per Sec Apache HTTPD False
UTILIZATION|CPU Load Apache HTTPD True
UTILIZATION|Idle Workers Apache HTTPD True
UTILIZATION|Request Per Sec Apache HTTPD True
UTILIZATION|SCBoard DNS Lookup Apache HTTPD False
UTILIZATION|SCBoard Idle Cleanup Apache HTTPD False
UTILIZATION|SCBoard Keep Alive Apache HTTPD False
UTILIZATION|SCBoard Sending Apache HTTPD False
UTILIZATION|SCBoard Waiting Apache HTTPD False
UTILIZATION|Total Accesses Apache HTTPD False
UTILIZATION|Total Bytes Apache HTTPD True
UTILIZATION|Uptime Apache HTTPD True
VMware, Inc. 206

MongoDB Metrics
vRealize Application Remote Collector discovers metrics for MongoDB application service.
Table 4-28. MongoDB Metrics

Acked|Active Reads MongoDB True
Acked|Active Writes MongoDB True
Acked|Current Connections MongoDB True
Acked|Cursor Timed Out MongoDB True
Acked|Deletes Per Sec MongoDB False
Acked|Document Inserted MongoDB False
Acked|Document Deleted MongoDB False
Acked|Flushes Per Sec MongoDB False
Acked|Inserts Per Sec MongoDB False
Acked|Net Input Bytes MongoDB False
Acked|Open Connections MongoDB True
Acked|Net Output Bytes MongoDB False
Acked|Queries Per Sec MongoDB False
Acked|Queued Reads MongoDB True
Acked|Queued Writes MongoDB True
Acked|Total Deletes Per Sec MongoDB False
Acked|Total Passes Per Sec MongoDB False
Acked|Total Refreshing MongoDB False
Acked|Updates Per Sec MongoDB False
Acked|Volume Size MB MongoDB False
Acked|Collection Stats MongoDB DataBases False
Acked|Data Index Stats MongoDB DataBases True
Acked|Data Indexes MongoDB DataBases False
Acked|Data Size Stats MongoDB DataBases True
Acked|Average Object Size stats MongoDB DataBases False
Acked|Num Extents Stats MongoDB DataBases False
Riak Metrics
vRealize Application Remote Collector discovers metrics for Riak application service.
VMware, Inc. 207

Table 4-29. Riak Metrics

UTILIZATION|CPU Average Riak KV False
UTILIZATION|Memory Processes Riak KV False
UTILIZATION|Memory Total Riak KV False
UTILIZATION|Node GETs Riak KV True
UTILIZATION|Node GETs Total Riak KV False
UTILIZATION|Node PUTs Riak KV True
UTILIZATION|Node PUTs Total Riak KV False
UTILIZATION|PBC Active Riak KV True
UTILIZATION|PBC Connects Riak KV True
UTILIZATION|Read Repairs Riak KV True
UTILIZATION|vNODE Index Reads Riak KV True
UTILIZATION|vNODE Index Writes Riak KV True
Troubleshooting the Integration of vRealize Application Remote Collector with

vRealize Operations Manager
Here are troubleshooting tips for errors and install failures during the integration of vRealize
Application Remote Collector with vRealize Operations Manager.
Install Fails When UAC is Disabled
Problem
Install of the agent fails even when UAC is disabled.
Solution
u To disable UAC (previously known as LUA) on Windows, complete the following steps:
a In the registry path HKLM:\Software\Microsoft\Windows\CurrentVersion\Policies

\System, set the value for the key EnableLUA to 0.
b You must reboot the machine for the changes to take effect.
Agent Install Fails on Windows with UAC Enabled
Problem
If UAC is enabled, install of the agent might fail.
Solution
See KB 70780 for more details.
VMware, Inc. 208

vCenter Server User Permissions

vRealize Application Remote Collector requires guest operation privileges to install agents on
virtual machines.
Problem
Agent installation fails with the following error message if there are no guest operation privileges:
An error occurred while trying to verify login with Non Interactive Credentials
for VM : <VM-MOR> Client received SOAP Fault from server: Permission to perform this
operation was denied. Please see the server log to find more detail regarding exact
cause of the failure
Solution
1 Verify that you have configured a vCenter adapter.
2 The vCenter Server user account with which the vCenter adapter is configured in vRealize
Operations Manager, should have the following permissions: Guest operation modifications,
Guest operation program execution, and Guest operation queries.
Installing an Agent on a Linux End Point Fails

Install of an agent on a Linux end point fails for a non-root user with a specific set of privileges.
Problem
Agent installation fails with the following error if the tty command is not added:
Install telegraf
Solution
u If you get an Install telegraf error, verify that the following lines exist in /etc/sudoers.
1. root ALL=(ALL:ALL) ALL

2.Defaults:root !requiretty
3.Defaults:arcuser !requiretty
(1) can be omitted if password-less sudo is already enabled for the root user. (2) and (3) can
be omitted if your endpoint VMs are already configured to turn off requiretty.
Add these lines to /etc/sudoers, if you have not added them.
u To solve other failures on Linux end points, ensure that /tmp mount point is mounted with the
exec mount option.
Configuration Failure When Ports Are Not Enabled

An error occurs when you add a vCenter Server while configuring the vRealize Application
Remote Collector.
VMware, Inc. 209

Problem
Configuration of vRealize Application Remote Collector fails with the following error:
Unable to establish a valid connection to the target system.

Wait for response of Task ‘Test connection’ is timed out for collector
‘vRealize Operations Manager Collector-Master’.
Solution
u Enable the relevant ports. For more information, see vRealize Application Remote Collector
Security Information.
Network Time Protocol Settings

If the actual time of the vRealize Application Remote Collector server is behind or ahead of the
current time, you might face configuration or installation failures.
Problem
n Agent installation fails
n Adapter configuration fails
Solution
u Ensure that you configure network time protocol settings. For more information, see
Configure Network Time Protocol Settings, or
u Run the following command to update the time immediately from an NTP server: ntpdate
time.vmware.com
Ensure that you have stopped the ntpd service before you run the ntpdate command.
Note The system time takes about five minutes to sync with the NTP server time.
Log Insight
When vRealize Operations Manager is integrated with Log Insight, you can view the Log Insight
page, the Troubleshoot with Logs dashboard, and the Logs tab. You can collect and analyze log
feeds. You can filter and search for log messages. You can also dynamically extract fields from
log messages based on customized queries.
Log Insight Page

When vRealize Operations Manager is integrated with vRealize Log Insight, you can search and
filter log events. From the Interactive Analytics tab in the Log Insight page, you can create
queries to extract events based on timestamp, text, source, and fields in log events . vRealize Log
Insight presents charts of the query results.
VMware, Inc. 210

To access the Log Insight page from vRealize Operations Manager, you must either:
n Configure the vRealize Log Insight adapter from the vRealize Operations Manager interface,
or
n Configure vRealize Operations Manager in vRealize Log Insight.
For more information about configuring, see Configuring vRealize Log Insight with vRealize
Operations Manager.
For information about vRealize Log Insight interactive analytics, see the vRealize Log Insight
documentation.
Logs Tab
When vRealize Operations Manager is integrated with vRealize Log Insight, you can view the logs
for a selected object from the Logs tab. You can troubleshoot a problem in your environment by
correlating the information in the logs with the metrics. You can then most likely determine the
root cause of the problem.
How the Logs Tab Works

By default, the Logs tab displays different event types for the last hour. For vSphere objects, the
logs are filtered to show the event types for the specific object you select. For more information
on the different filtering and querying capabilities, see the vRealize Log Insight documentation.
Where You Find the Logs Tab

In the menu, select Environment and then from the left pane select an inventory object. Click the
Logs tab. To view the Logs tab, you have to configure vRealize Operations Manager in vRealize
Log Insight. For more information, see Configuring vRealize Log Insight with vRealize Operations
Manager.
After integrating vRealize Operations Manager with vRealize Log Insight, refresh the browser to
see the Logs tab.
Configuring vRealize Log Insight with vRealize Operations Manager

To use the Log Insight page, the Troubleshoot with Logs dashboard, and Logs tab in vRealize
Operations Manager, you must configure vRealize Log Insight with vRealize Operations Manager.
Configuring the vRealize Log Insight Adapter in vRealize Operations Manager

To access the Log Insight page and the Troubleshoot with Logs dashboard from vRealize
Operations Manager, you must configure the vRealize Log Insight adapter in vRealize Operations
Manager.
vRealize Operations Manager accesses the first instance of the vRealize Log Insight adapter that
is configured.
Prerequisites
n Verify that vRealize Log Insight and vRealize Operations Manager are installed.
VMware, Inc. 211

n Verify that you know the IP address, user name, and password of the vRealize Log Insight
instance you have installed.
Procedure
Repository.
2 From the Repository page on the right side, select VMware vRealize Log Insight from the
VMware Native Management Packs section, and click Activate.
The management pack is installed and appears in the Solutions page.
3 In the menu, click Administration, and then in the left pane click Solutions > Configuration.
4 From the Configuration page, click VMware vRealize Log Insight.
5 From the Configured Adapter Instances section, click the relevant adapter and then click the
Configure icon. You see the Manage Solution-VMware vRealize Log Insight dialog box.
6 In the Manage Solutions dialog box perform the following steps:
n Enter a name in the Display Name text box.
n Enter the IP address in the Log Insight server text box of the vRealize Log Insight you
have installed and want to integrate with.
n Click Test Connection to verify that the connection is successful.
n Click Save Settings.
n Click Close.
7 From the vRealize Operations Manager Home page, click Troubleshoot > Using Logs from
the left pane. If you see a statement at the bottom of the page, click the link and accept the
certificate exception in vRealize Log Insight or contact your IT support for more information.
8 From the vRealize Operations Manager Home page, click Troubleshoot > Using Logs from
the left pane and enter the user name and password of the vRealize Log Insight instance you
have installed.
Configuring vRealize Operations Manager in vRealize Log Insight

You configure vRealize Operations Manager in vRealize Log Insight in the following scenarios:
n To access the Logs tab in vRealize Operations Manager.
n To access the Troubleshoot with Logs dashboard and the Log Insight page from vRealize
Operations Manager.
Prerequisites
n Verify that vRealize Log Insight and vRealize Operations Manager are installed.
n Verify that you know the IP address, hostname, and password of the vRealize Operations
Manager instance you want to integrate with.
VMware, Inc. 212

Procedure
1 From the Administration page of vRealize Log Insight, click the vRealize Operations icon from
the left pane. You see the vRealize Operations Integration pane.
2 In the Hostname and Username text boxes, enter the IP address and hostname of the
vRealize Operations Manager instance you want to integrate with.
3 In the Password text box, select Update Password and enter the password of the vRealize
Operations Manager instance you want to integrate with.
4 Select the Enable launch in context option.
5 Click Test Connection to verify that the connection is successful.
6 Click Save.
You can now view the log details for an object in vRealize Operations Manager.
Log Forwarding
For troubleshooting in the product UI, you can send the logs to an external log server or a
vRealize Log Insight server.
If you have configured log forwarding from Administration > Support > Logs in earlier versions
of vRealize Operations Manager, VMware recommends that you reconfigure in this version of
Where You Find the Log Forwarding Page

In the menu, select Administration and then from the left pane select Management > Log
Forwarding.
Table 4-30. Log Forwarding Page Options

Options Description
Self-monitoring logging configuration Forwards the logs to an external log server.
Forwarded Logs You can select the set of logs you want to forward to the
external log server or the vRealize Log Insight server.
Log Insight Servers You can select an available vRealize Log Insight server IP.
If there is no available vRealize Log Insight server IP, select
Other from the drop-down menu and manually enter the
configuration details.
Host IP address of the external log server where logs have to be

forwarded.
Protocol You can select either cfapi or syslog from the drop-down
menu to send event logging messages.
VMware, Inc. 213

Table 4-30. Log Forwarding Page Options (continued)

Options Description
Port The default port value depends on whether or not SSL has
been set up for each protocol. The following are the
possible default port values:
Protocol SSL Default Port
cfapi No 9000
cfapi Yes 9543
syslog No 514
syslog Yes 6514
Use SSL Allows the vRealize Log Insight agent to send data
securely.
Path to Certificate Authority File You can enter the path to the trusted root certificates
bundle file. If you do not enter a certificate path, the
vRealize Log Insight Windows agent uses system root
certificates and the vRealize Log Insight Linux agent
attempts to load trusted certificates from /etc/pki/tls/
certs/ca-bundle.crt or /etc/ssl/certs/ca-
certificates.crt.
Cluster Name Displays the name of the cluster. You can edit this field.
Modifying Existing Log Types

If you manually modified the existing entries or logs sections and then modify the log forwarding
settings from vRealize Operations Manager, you lose the changes that you made.
The following server entries are overwritten by the vRealize Operations Manager log forwarding
settings.
port
proto
hostname
ssl
reconnect
ssl_ca_path
The following [common | global] tags are being added or overwritten by the vRealize
Operations Manager log forwarding settings.
vmw_vr_ops_appname
vmw_vr_ops_clustername
vmw_vr_ops_clusterrole
vmw_vr_ops_hostname
vmw_vr_ops_nodename
Note Cluster role changes do not change the value of the vmw_vr_ops_clusterrole tag. You can
either manually modify or ignore it.
VMware, Inc. 214

Business Management
SDDC costing is out-of-the box with vRealize Operations Manager. There is no integration
required with vRealize Business for Cloud.
Cost Settings for Financial Accounting Model

You can configure Server Hardware cost driver and resource utilization parameters to calculate
the accurate cost and improve the efficiency of your environment.
Cost Drivers analyzes the resources and the performance of your virtual environment. Based on
the values you define, Cost Drivers can identify reclamation opportunities and can provide
recommendations to reduce wastage of resources and cost.
Configuring Depreciation Preferences

To compute the amortized cost of the Server Hardware cost driver, you can configure the
depreciation method and the depreciation period. Cost Drivers supports two yearly depreciation
methods and you can set the depreciation period from two to seven years.
Note Cost Drivers calculates the yearly depreciation values and then divides the value by 12 to
arrive at the monthly depreciation.
Method Calculation
Straight line Yearly straight line depreciation = [(original cost - accumulated depreciation) / number of
remaining depreciation years]
Max of Double or Yearly max of Double or Straight = Maximum (yearly depreciation of double declining balance
Straight method, yearly depreciation of straight line method)
Yearly depreciation of double declining method= [(original cost - accumulated depreciation) *
depreciation rate].
Depreciation rate = 2 / number of depreciation years.
Note Double declining depreciation for the last year = original cost - accumulated depreciation
Example: Example for Straight Line Depreciation Method
Year Original Cost Accumulated Depreciation Straight Line Depreciation Cost
Year 1 10000 0
[(10000-0)/5] = 2000
Year 2 10000 2000

[(10000-2000)/4] = 2000
Year 3 10000 4000

[(10000-2000)/3] = 2000
Year 4 10000 6000

[(10000-2000)/2] = 2000
Year 5 10000 8000

[(10000-2000)/1] = 2000
VMware, Inc. 215

Example: Example for Max of Double and Straight Line Depreciation Method
Accumulated
Year Original Cost Depreciation Rate Depreciation Straight Line Depreciation Cost
Year 1 10000 0.4 0

Maximum([(10000-0)*0.4],[(10000-0)/5])
= Maximum(4000, 2000) = 4000
which is 333.33 per month.
Year 2 10000 0.4 4000

Maximum([(10000-4000)*0.4],[(10000-4000)/4])
= Maximum (2400, 1500) = 2400
which is 200 per month.
Year 3 10000 0.4 6400

Maximum([(10000-6400)*0.4],[(10000-6400)/3])
= Maximum (1440, 1200) = 1440
Year 4 10000 0.4 7840

Maximum([(10000-7840)*0.4],[(10000-7840)/2])
= Maximum (864, 1080) = 1080
Year 5 10000 0.4 8920

Maximum([(10000-8920)*0.4],[(10000-8920)/1])
= Maximum (432, 1080) = 1080
Overview of Cost Drivers

Cost Drivers are the aspect that contributes to the expense of your business operations. Cost
drivers provide a link between a pool of costs. To provide a granular cost visibility and to track
your expenses of virtual machines accurately in a private cloud, vRealize Operations Manager has
identified eight key cost drivers. You can see the total projected expense on your private cloud
accounts for the current month and the trend of cost over time.
You can now set a total cost for the License, Labor, Network, Maintenance, and facilities cost
drivers in vRealize Operations Manager:
Note The total cost set by you is distributed across resources in the data center. For example, if
you set the total cost for the RHEL license, the cost is divided across all the hosts and VMs which
use the RHEL license.
According to the industry standard, vRealize Operations Manager maintains a reference cost for
these cost drivers. This reference cost helps you for calculating the cost of your setup, but might
not be accurate. For example, you might have received some special discounts during a bulk
purchase or you might have an ELA with VMware that might not match the socket-based pricing
available in the reference database. To get accurate values, you can modify the reference cost of
cost drivers in vRealize Operations Manager, which overrides the values in the reference
database. Based on your inputs, vRealize Operations Manager recalculates the total amount for
VMware, Inc. 216

the private cloud expenses. After you add a private cloud into vRealize Operations Manager,
vRealize Operations Manager automatically discovers one or more vCenter Servers that are part
of your Private Cloud. In addition, it also retrieves the inventory details from each vCenter Server.
The details include:
n Associated clusters: Count and names
n ESXi hosts: Count, model, configuration, and so on.
n Datastores: Count, storage, type, capacity
n VMs: Count, OS type, tags, configuration, utilization
Based on these configuration and utilizations of inventory, and the available reference cost,
vRealize Operations Manager calculates the estimated monthly cost of each cost driver. The total
cost of your private cloud is the sum of all these cost driver expenses.
You can modify the expense of your data center. These costs can be in terms of the percentage
value or unit rate, and might not always be in terms of the overall cost. Based on your inputs, the
final amount of expense is calculated. If you do not provide inputs regarding expenses, the
default values are taken from the reference database.
You can see the projected cost of private cloud for the current month and the trend of total cost
over time. For all the expenses, cost drivers invRealize Operations Manager display the monthly
trend of the cost variations, the actual expense, and a chart that represents the actual expense
and the reference cost of the expense.
Note If the vCenter Server was added from more than six months, the trend displays the total
cost for the last six months only. Otherwise, the trend displays the total cost from the month the
vCenter Server was added into vRealize Operations Manager.
Table 4-31. Expense Types

Cost Drivers Description
Server The Server Hardware cost driver tracks all the expenses for purchasing of hardware servers that are
Hardware : part of vCenter Servers. You see the server cost based on CPU age and server cost details.
Traditional
Note You can now select an individual server from the server group and specify the unique cost for
each individual server.
Server The Server Hardware : Hyper-Converged cost driver, tracks the expenses associated with hyper
Hardware : converged infrastructure components. The Server Hardware : Hyper-Converged cost driver includes
Hyper- expenses for the Hyper Converged servers like vSAN enabled servers and vXRail. The expense
Converged provided is for both compute and storage.
Note The customizations that were performed for vSAN server costing under Server Hardware :
Traditional in the earlier versions will not be carried forward to 7.5 as the vSAN enabled servers will fall
under Server Hardware : Hyper-Converged servers now.
Storage You can calculate the storage cost at the level of a datastore based on the tag category information
collected from vCenter Server. You see the storage total distribution based on category and the
uncategorized cost details.
Note The vSAN datastores are not displayed as part of this cost driver page.
VMware, Inc. 217

Table 4-31. Expense Types (continued)

Cost Drivers Description
License You see the licenses cost distribution for the operating systems cost and VMware license of your
cloud environment.
Note For Non-ESX physical servers, VMware license is not applicable.
Maintenance You see the maintenance cost distribution for the server hardware and operating system maintenance.
You can track your total expense with hardware and operating system vendors.
Labor You see the labor cost distribution for the servers, virtual infrastructure, and operating systems. You
can view the total administrative cost for managing physical servers, operating systems and virtual
machines. You can track all expenses spent on human resources to manage the datacenters.
Note
n Labor cost includes expenses on backup appliance virtual machine (VDP virtual appliance).
n For physical servers, operating system labor cost and servers labor costs are applicable, virtual
infrastructure cost is not considered.
Network You see the networks costs by NIC type. You can track a network expense based on different types of
NICs attached to the ESX server. You can view the total cost of physical network infrastructure that
includes the internet bandwidth, and is estimated by count and type of network ports on the ESXi
Servers.
Note For physical servers, the network details are not captured. So, the network cost is considered as
zero.
Facilities You see the cost distribution for the facilities such as real estate costs, such as rent or cost of data
center buildings, power, cooling, racks, and associated facility management labor cost. You can point
to the chart to see the cost details for each facility type.
Additional Cost You can see the additional expenses such as backup and restore, high availability, management,
licensing, VMware software licensing.
Application You can see the cost of different application services you are running in your environment compared
Cost to your overall expenses. Some examples of application cost are, cost of running SQL server cluster
and cost of running Antivirus on VMs.
You can select a data center to view the information specific to the data center.
Cloud Providers Overview

By default, you can see that Amazon Web Services (AWS), Google Cloud, IBM Cloud, and
Microsoft Azure are included in vRealize Operations Manager. You can also add your own cloud
provider by using a standard vRealize Operations Manager template.
You can configure the new cloud provider as per the standard vRealize Operations Manager
template and perform a migration scenario. The vRealize Operations Manager template contains
data points for vCPU, CPU, RAM, OS, region, plan term, location, and built-in instance storage,
you must provide these values when you add cloud providers. The result of the migration
scenario helps you assess the cost savings achieved using your cloud provider against the
default cloud providers.
You can edit the rate card for new cloud providers and default cloud providers. However, you
cannot delete the default cloud providers.
VMware, Inc. 218

Add Cloud Provider

You can use the Add Cloud Provider workspace to add or edit a cloud provider. You can edit the
cloud provider rate card for default cloud providers and the new cloud provider.
Procedure
1 On the menu, click Administration and in the left pane click Configuration > Cost Settings >
Cloud Providers.
You can also reach the Cloud Providers page from the Home Screen. In the Home screen,
navigate to Optimize Capacity > What-If Analysis > Plan Migration > Add Cloud Providers.
For more information, see What-If-Analysis - Migration Planning section in vRealize
Operations Manager help.
2 Click the Add Cloud icon.
3 Enter the Cloud Provider Name.
4 Select the cloud provider logo and click Upload Logo.
5 Click Next.
6 Click Download Template and specify the required values.
Note When you edit a cloud provider the Download Template link is replaced with
Download Existing Rate Card. You can update the existing rate card and upload the same.
7 Select the updated template and click Upload Rate Card.
8 Click Validate.
Note vRealize Operations Manager validates the rate card and reports success or failure. If
errors are reported, you can correct the errors and proceed further.
9 Click Finish.
Results
The new cloud provider is now part of the vRealize Operations Manager cloud provider list.
Editing Cost Drivers

You can manually edit monthly cost of all the eight expense types from the current month
onwards.
The configuration used for cost drivers determines how vRealize Operations Manager calculates
and displays the cost.
Editing Server Hardware : Traditional

You can view, add, edit, or delete the cost of each server group, based on their configuration and
the purchase date of a batch server running in your cloud environment. You can also specify the
server cost for individual servers in a server group. After you update the server hardware cost,
cost drivers update the total monthly cost and average monthly cost for each server group.
VMware, Inc. 219

Procedure
1 Click Administration and in the left pane click Configuration > Cost Settings.
2 In the Cost Drivers tab, click Server Hardware : Traditional.
3 Click any server from the list of Server Group Description.
The cost drivers groups all server hardware from all data centers in your inventory based on
their hardware configuration.
Category Description
Server Group Description Displays the name of the server in your inventory.
Number of Servers Displays the total number of servers of any particular hardware configuration in your
inventory.
Monthly Cost Displays the average monthly cost for server. This value is calculated as a weighted
average of prices of purchased and leased batches.
4 After selecting a server group, you can manually enter the required fields.
a Enter the Purchase Type and Cost Per Server.
Note You can use the + ADD COST PER SERVER option to create multiple server
batches and set the cost for a specific server in a server group.
b Click Save.
Editing Server Hardware: Hyper-Converged

You can view, add, edit, or delete the cost of Hyper converged Infrastructure (HCI) component in
your server group. You can specify the cost per server and compute percentage exclusively for
the HCI servers. After you update the server hardware cost, cost drivers update the total
monthly cost and average monthly cost for each server group.
Procedure
2 In the Cost Drivers tab, click Server Hardware : Hyper-Converged.
3 Click any server from the list of Server Group Description.
The cost drivers groups all server hardware from all data centers in your inventory based on
their hardware configuration.
Server Group Description Displays the name of servers falling under vSAN clusters and vXrail servers in your
inventory.
Number of Servers Displays the total number of servers of any particular hardware configuration in your
inventory.
VMware, Inc. 220

Monthly Cost Displays the average monthly cost for server. This value is calculated as a weighted
average of prices of purchased and leased batches.
Note You can edit the Compute Pct column to adjust the storage rate of the vSAN
datastores. You can use the same percentage to determine the cost.
4 After selecting a server group, you can manually enter the required fields.
a Enter Purchase Type, Cost Per Server, and Compute Percentage.
Note You can use the + ADD COST PER SERVER option to create multiple server
batches and to customize the cost per server.
b Click Save.
Edit Monthly Cost of Storage

The storage hardware is categorized according to the datastore tag category. You can edit the
monthly cost per storage GB for the datastores based on their storage category (using tags) and
storage type (NAS, SAN, Fiber Channel or Block).
Prerequisites
To edit the cost based on storage category, you must create tags and apply them to the
datastores on the vCenter Server user interface. For more information, see the VMware vSphere
Documentation.
Procedure
2 In the Cost Drivers tab, click Storage.
3 (Optional) Select a tag category.
Assume that you have two tag categories (for example, Profile and Tiers) with three tags in
each category, you can select either Profile or Tiers from Tag Category to categorize the
datastores based on tags.
Tag Category n Category displays the tag categories for datastores and also the tags associated with the
category.
Note If you have performed a fresh installation of vCenter Server 6.0, and not assigned
tags to the datastores, cost drivers displays tag category for datastores as uncategorized.
Datastores Displays the total number of datastores for a specific category or type. You can click the
datastore value to see list of datastores and its details such as monthly cost, total GB for each
datastore.
Total Storage (GB) Displays the total storage for a specific category or type.
VMware, Inc. 221

Monthly Cost Per Displays the monthly cost per GB for a specific category or type. You can edit this value for
GB defining the monthly cost per GB for datastores.
Monthly Cost Displays the total monthly cost for a specific category or type.
4 Click Save.
Edit Monthly Cost of License

You can edit the total operating system licensing cost and VMware license cost of your cloud
environment. You can now set a total fixed cost for the license in vRealize Operations Manager.
The total license cost is divided across all the hosts present in the data center. You can edit the
license cost by either selecting the ELA charging policy or selecting the per socket value.
Procedure
1 Click Administration and in the left pane click Configuration > Cost Drivers.
2 In the Cost Drivers tab, click License.
The Cost drivers display all the licenses in your cloud environment.
Name Displays the category of the operating system. If the operating system is not Windows or Linux, cost
drivers categorize the operating system under Other Operating Systems.
Note Two new cost components, Monthly cost of VMware vSAN Per Socket and Monthly cost of
VMware vSAN SnS have been included for the vSAN cost calculation. The default values for these
components are based on the reference database values.
VMs Displays the number of virtual machines that are running on the specific operating system.
Sockets Displays the number of sockets on which the specific operating system is running.
Charged by Displays whether a cost is charged by socket or ELA.
Note The Charged By column can be edited to mention that the cost is charged by socket, core,
instance, or ELA.
Total Cost Displays the total cost of the specific operating system.
3 Click Save.
Results
According to your inputs, vRealize Operations Manager calculates and displays the total cost and
updates the Charged by column with the option that you have selected.
Edit Monthly Cost of Maintenance

You can edit the monthly cost of maintaining your cloud environment. Maintenance cost is
categorized into hardware maintenance cost and operating system maintenance cost. Hardware
maintenance cost is calculated as a percentage of the purchase cost of servers. Operating
system maintenance cost is calculated as a percentage of the Windows licensing costs. You can
VMware, Inc. 222

snow specify a total fixed cost for maintenance in vRealize Operations Manager. The total
maintenance cost is divided across all the hosts present in the data center.
Procedure
2 In the Cost Drivers tab, click Maintenance.
3 Edit the monthly maintenance cost.
n Edit the percentage value of the hardware maintenance cost.
n Edit the percentage value of the operating system maintenance cost.
4 Click Save.
Edit Monthly Cost of Labor

You can edit the monthly cost of labor for your cloud environment. You can set a total fixed cost
for labor in vRealize Operations Manager. The total labor cost is divided across all the hosts
present in the data center. The labor cost is combination of the total cost of the server
administrator, virtual infrastructure administrator, and the operating system administrator.
Procedure
2 In the Cost Driver tab, click Labor.
The monthly labor cost is displayed.
Category Displays the categories of labor cost, servers, virtual infrastructure, and operating system
Calculated by Displays whether the cost is calculated hourly or monthly.
Total Monthly Cost Displays the total monthly cost of the particular category
Reference Cost Displays the reference cost for the category from the cost drivers database
3 Click Save.
Results
The total monthly cost is updated. The hourly rate option or the monthly cost option that you
select is updated in the Calculated by column.
Edit Monthly Cost of the Network

You can edit the monthly cost for each Network Interface Controller (NIC) type or can edit the
total cost of all the networking expenses associated with the cloud. You can now set a total fixed
cost for network resources in vRealize Operations Manager. The total network cost is divided
across all the hosts present in the data center.
VMware, Inc. 223

Procedure
2 In the Cost Driver tab, click Network.
3 Edit the monthly cost of network.
n Modify the values for 1 Gigabit NIC and the 10 Gigabit NIC.
n Modify the total monthly cost of all network expenses associated with the cloud.
4 Click Save.
Results
The total monthly network expenses are updated.
Edit Monthly Cost of Facilities

For your cloud environment, you can specify the total monthly cost of facilities or edit the
facilities cost for real estate, power, and cooling requirements. You can now set the total fixed
cost for facilities in vRealize Operations Manager. The total facilities cost is divided across all the
hosts present in the data center.
Procedure
2 In the Cost Driver tab, click Facilities.
3 Edit the monthly facilities cost.
n Modify the cost of rent or real estate per rack unit and modify the monthly cost of power
and cooling per kilowatt-hour.
n Modify the total monthly cost of facilities.
4 Click Save.
Results
The monthly facilities cost is updated.
Editing Additional Costs

The additional cost lets you add any additional or extra expense that is not covered by other
expenses categorized by vRealize Operations Manager. No reference value is present for this
expense.
Procedure
2 In the Cost Driver tab, click Additonal Costs.
VMware, Inc. 224

3 Enter or select the cost type for the expenses.
Note As a first time user, you must enter the cost type values manually. The values get
saved and appear for all future selections.
4 Select the Entity Type and Entity Selection.
The Entity Count gets updated automatically.
5 Enter the Monthly Cost per entity .
The Total Cost per month gets computed automatically.
6 Click Save.
Edit Application Cost

vRealize Operations Manager allows you to edit the application cost of an application present in
your cloud environment. You can only modify the cost associated with the application, as all the
other attributes are predefined.
Prerequisites
Create applications in vRealize Operations Manager.
Procedure
1 In the menu, click Administration and in the left pane click Configuration > Cost Settings.
2 In the Cost Drivers tab, click Applications.
3 Click the edit icon next to the application cost you want to edit.
4 Modify the cost of the application.
5 Click Save.
Editing Cluster Cost Calculation Methods

You can now edit the cluster cost calculation method based on your business requirement. Earlier
the cost computation was based on the actual utilization of resources. Now you can calculate the
cluster utilization cost using any one of the following methods:
n Actual Utilization
n Expected Utilization across all clusters
n Expected Utilization per cluster
Procedure
1 In the menu, Click Administration and then in the left pane click Configuration > Cost
Settings.
2 In the Cluster Cost tab, click CHANGE.
The Cluster Cost Calculation Methods dialog box is displayed.
VMware, Inc. 225

3 Select any one of the Cluster Cost Calculation methods.
Option Description
Actual Utilization By default, the cluster cost calculation is based on the actual utilization of
CPU and memory.
Expected Utilization across all You can set the fixed utilization percentages for expected CPU and memory
clusters utilization. If you select this option, the value you enter is applied across all
the server clusters.
Expected Utilization per cluster You can set the expected CPU and memory utilization percentages for each
cluster by entering the value in the Expected CPU Utilization % and Expected
Memory Utilization % text boxes.
4 Click SAVE.
Cluster Cost Overview

vRealize Operations Manager calculates the base rates of CPU and memory so that they can be
used for virtual machine cost computation. Base rates are determined for each cluster, which are
homogeneous provisioning groups. As a result, base rates might change across clusters, but are
the same within a cluster.
1 vRealize Operations Manager first arrives at the fully loaded cost of the cluster from the cost
drivers. After the cost of a cluster is determined, this cost is split into CPU and memory costs
based on the industry standard cost ratios for the different models of the server.
2 The CPU base rate is first computed by dividing the CPU cost of the cluster by the CPU
capacity of the cluster. CPU base rate is then prorated by dividing the CPU base rate by
expected CPU use percentage to arrive at true base rate for charging the virtual machines.
3 The memory base rate is first computed by dividing the memory cost of the cluster by the
memory capacity of the cluster. Memory base rate is then prorated by dividing the memory
base rate by expected memory use percentage to arrive at true base rate for charging the
virtual machines.
4 You can either provide the expected CPU and memory use or you can use the actual CPU
and memory usage values.
Cluster Cost Elements Calculation
Total Compute Cost Total Compute Cost = (Total Infrastructure cost, which is a sum of all cost drivers) – (Storage
cost) – (Direct VM cost, which is sum of OS labor, VM labor and any Windows Desktop
licenses).
Expected CPU and Expected CPU and Memory use = These percentages are arrived based on historical actual
Memory use use of clusters.
Per GHz CPU base rate Per GHz CPU base rate = (Cost attributed to CPU out of Total compute cost) / (Expected
CPU Utilization * Cluster CPU Capacity in gHZ).
Per GB RAM base rate Per GB RAM base rate = (Cost attributed to RAM out of Total compute cost) / (Expected
Memory Utilization * Cluster RAM Capacity in GB).
VMware, Inc. 226

Cluster Cost Elements Calculation
Average CPU Utilization Average CPU Utilization = (Cost attributed to CPU utilization of VMs in a cluster, out of Total
compute cost) / (Total number of VMs in the cluster).
Average Memory Average Memory Utilization = (Cost attributed to Memory utilization of VMs in a cluster, out
Utilization of Total compute cost) / (Total number of VMs in the cluster).
Expected CPU Utilization The utilization percentage level of CPU that the cluster is expected to operate.
Expected Memory The utilization percentage level of Memory that the cluster is expected to operate.
Utilization
Cluster Cost Computation with Allocation Model

You can now use the allocation model to compute the cost of clusters in vRealize Operations
Manager, earlier the cluster cost computation was based on the cluster utilization. When you
perform cost computation using the allocation model, you can set the over commit ratio for CPU,
RAM, and storage.
Note The allocation ratio can be set at both cluster level and datastore cluster level. You can
also mention the storage base rate, which will displayed at the datastore level.
Table 4-32. Cluster Base Rate Computation with Allocation Model

Base Rate Formula
vCPU Base Rate vCPU base rate = B1 = (Cost attributed to CPU) / (Number
of vCPUs in a cluster)
RAM Base Rate RAM base rate = B2 = (Cost attributed to RAM) / Number of
vRAMs in a cluster)
Note The cost computation is based on Over Commit

ratio. If the Over Commit ratio is 1:4, and total cores in
cluster are 6, then vCPU count = 24, in case if the allocated
vCPU exceeds this targeted number, then the maximum
value is selected.
Table 4-33. Virtual Machine Cost Computation with Allocation Model

Cost Formula
Virtual Machine Cost Virtual machine cost = (Number of vCPU allocated x B1 of

cluster it belongs to) + Number of vRAMs allocated x B2 of
cluster it belongs to) + storage cost + direct cost.
Note Storage allocated represents the Storage Base Rate

based on allocation.
Cost Calculation Status Overview

You can check the ongoing status of manually triggered cost calculation process.
VMware, Inc. 227

Cost calculation by default, occurs daily and whenever there is a change in the inventory or cost
drivers values. You can trigger the cost calculation manually so that changes in the inventory and
cost driver values reflect accordingly on the VM cost without having to wait there for any failures
in the cost calculation process. It also shows default schedules time for next cost calculation
process.
Migration of Cost Driver Configuration from vRealize Business for Cloud to vRealize Operations
Manager
vRealize Business for Cloud supports migration of cost driver configuration from vRealize
Business for Cloud to vRealize Operations Manager. You can migrate cost driver configuration
from vRealize Business for Cloud 7.x or later to vRealize Operations Manager 6.7 or vRealize
Operations Manager 7.5.
For more information about the migration process, see the KB article https://kb.vmware.com/s/
article/55785.
vRealize Automation Solution

The vRealize Automation solution extends operational management capabilities of the vRealize
Operations Manager platform to provide tenant-aware operational visibility of the cloud
infrastructure.
The vRealize Automation solution enables you as a cloud provider to monitor the health and
capacity risk of your cloud infrastructure in the context of the tenant's business groups.
You can use the vRealize Automation solution to perform some of the following key tasks:
n To gain visibility into the performance and health of the tenant’s business groups that the
underlying cloud infrastructure supports.
n To minimize the time taken to troubleshoot, if there is a tenant workload or an underlying

infrastructure problem. The vRealize Automation solution provides visibility into the impact to
performance, health, and capacity risk of the business groups because of an operational
problem in the underlying cloud infrastructure layer.
n To manage the placements of VMs that are part of the clusters managed by vRealize
Automation.
n To view capacity for tenants, business groups, and reservations. From the menu, select
Administration and then in the left pane, select Inventory. Select the Objects tab in the right
pane. By default, the usage capacity model is enabled for these objects. You can enable the
allocation model from the policy settings.
Supported vRealize Automation Versions

The vRealize Automation solution is supported with vRealize Automation 7.0 versions. Workload
placement for day 1 operations is supported from vRealize Automation 7.3 onwards with vRealize
Operations Manager 6.6 and above. Workload placement for day 2 operations is supported from
vRealize Automation 7.5 onwards with vRealize Operations Manager 7.0 and above.
VMware, Inc. 228

If you upgrade from a previous version to vRealize Operations Manager 7.0, that has the vRealize
Automation Management Pack 4.0 installed, the following behavior is observed:
n vRealize Automation Management Pack 4.0 is upgraded to 7.0.
Object Types and Relationships

The vRealize Automation solution brings in cloud constructs and their relationships from vRealize
Automation into vRealize Operations Manager for operational analysis.
You can use the following items in the virtual infrastructure as object types in vRealize Operations
Manager.
n Tenant
n Reservation
n Business Group
n Deployment
n Blueprint
n Managed Resources
n Reservation Policy
n Virtual Machine
n Datastore
n vRealize Automation World
n vRealize Automation Management Pack Instance
n User
You can view the different users from the Inventory > List tab. The user object type has a
relationship with VMs, deployments, and business groups.
Objects types in an enterprise environment are related to other objects types in that
environment. Object types are either part of a larger object type, or they contain smaller
component objects, or both. When you select a parent object type, vRealize Operations Manager
shows any related child objects types.
Table 4-34. Relationship Model

Relationship View Parent-Child Relationship Between Objects
vRealize Automation Tenant View Tenant > Business Group > Reservation
vRealize Automation App View Tenant > Blueprint > Deployment > VM
vRealize Automation Custom Data Center CDC > Cluster > Host > VM
View
vRealize Automation Reservation Policy Reservation Policy > Reservation > VM

View
vRealize Automation Virtual Machine View Tenant > Business group > Deployment > VM
VMware, Inc. 229

vRealize Automation Workload Placement

You can enable workload placement when you add vRealize Operations Manager 6.6 as an
endpoint in vRealize Automation 7.3. You cannot enable workload placement by adding a version
of vRealize Operations Manager that is previous to version 6.6, as an endpoint in vRealize
Automation 7.3.
To add vRealize Operations Manager as an endpoint in vRealize Automation 7.3, complete the
following steps.
Procedure
1 Log in to vRealize Automation as a tenant user.
2 Select Infrastructure > Endpoint > Endpoints.
3 Select New > Management > vRealize Operations Manager.
4 Enter the general information for the vRealize Operations Manager endpoint.
5 Click OK.
Port Information
In environments where strict firewalls are in place, specific ports must be open for the vRealize
Automation solution to retrieve data from vRealize Operations Manager.
n vRealize Automation CAFÉ Appliance/VIP URL on port 443
n vRealIze Automation IAAS URL on port 443
n vRealize Automation SSO URL on port 7444
Note The vRealize Automation solution supports only vCenter objects used and managed by
vRealize Automation. No other object kinds such as AWS or Openstack resources are supported
at this time.
Security Guidelines
Solutions in vRealize Operations Manager execute independently. They execute within a common
runtime environment within the vRealize Operations Manager collector host.
Java language security protects the adapters from interference with other adapters. All adapters
execute within the common JRE process trust zone. You must only load and use adapters that
you obtain from a publisher you trust and only after you verify the adapter's code integrity
before loading into vRealize Operations Manager.
VMware, Inc. 230

Even though adapters execute independently, they can make configuration changes to the
collector host or Java runtime environment that may affect the security of other adapters. For
example, at installation time an adapter can modify the list of trusted certificates. During
execution an adapter can change the TLS/SSL certificate validation scheme and thereby change
how other adapters validate certificates. The vRealize Operations Manager system and collector
hosts do not isolate adapters beyond the natural isolation provided by Java execution. The
system trusts all adapters equally.
Adapters are responsible for their own data security. When they collect data or make
configuration changes to data sources, each adapter provides its own mechanisms and
guarantees with regard to the confidentiality, integrity, and authenticity of the collected data.
The vRealize Automation solution enforces certificate checks when communicating with the
vRealize Automation servers. These certificates are presented when the user clicks the Test
button on the Adapter Instance setup page. Once these certificates are accepted by the user,
they will be associated with that adapter instance. Any communication to the vRealize
Automation servers will ensure that the certificates presented by the servers match the ones
accepted by the user.
Configuring vRealize Automation

You can configure an instance of the vRealize Automation from which you are collecting data.
Prerequisites
n The super user must have the following privileges:
n Infrastructure administrator rights for all tenants.
n Infrastructure architect rights for all tenants.
n Tenant administrator rights for all tenants.
n Software architect roles for all tenants.
n Fabric group administrator rights for all fabric groups, in all tenants.
n Configure the vCenter adapter instance for the same vCenter that is added as an endpoint in
the vRealize Automation system.
n Use only DNS names and not IP addresses when you configure the vRealize Automation
solution in a vRealize Automation distributed setup. Add host file entries on all vRealize
Operations Manager nodes in the /etc/hosts location if the DNS is not reachable using
n The super user account must be created for all the tenants by using an identical user name
and password with the required permissions for successful data collection.
Procedure
Repository.
VMware, Inc. 231

2 From the Repository page on the right side, select VMware vRealize Automation
Management Pack from the VMware Native Management Packs section, and click Activate.
The management pack is installed and appears in the Solutions pane.
3 In the menu, click Administration, and then from the left pane click Solutions > Configuration.
4 From the Configured Adapter Instances section in the right pane, select VMware vRealize
Automation and click the Configure icon.
5 Configure the solution.
Option Description
Display Name The name for the adapter instance.
Description (Optional) The description of the adapter instance.
vRealize Automation Appliance URL The URL of the vRealize Automation CAFÉ appliance from which you are
collecting data. Enter the host name, https://HostName, or the IP address,
https://IP.
If there is a load balancer for the CAFÉ appliances, the URL must have
HostName or IP address of the load balancer in the format
https://HostName or https://IP.
Credential To add the credentials to access the vRealize Automation environment, click
the plus sign.
n Credential name. The name by which you are identifying the configured
credentials.
n SysAdmin Username. The user name of the vRealize Automation system
administrator.
n SysAdmin Password. The password of the vRealize Automation system
administrator.
n SuperUser Username. The user name of the vRealize Automation super
user. Create a user in vRealize Automation with specific privileges
mentioned in the following note.
n SuperUser Password. The password of the vRealize Automation super
user.
Advanced Settings To configure the advanced settings, click the drop-down menu.
Collectors/Groups The collector on which the vRealize Automation solution runs.

n For one collector instance, select Automatically select collector.
n For multiple collectors, to distribute the workload and optimize
performance, select the collector to manage the adapter process for this
instance.
VMware, Inc. 232

Option Description
Tenants Collects data for specific tenants associated with vRealize Automation. To
collect data, configure the tenants in the following manner:
n * (by default). Data is collected for all tenants.
Note
n Tenant test is attempted for the first two tenants that are sorted
based on alphabetical order. If some tenants do not have the
required privileges, then the vRealize Automation solution continues
to collect data for the other tenants. Failure in collecting data for a
tenant that does not have the required privileges is logged in the
adapter.log file.
n If any of the tenants do not have the required privileges, data is not
collected for that tenant.
n Comma separated list. Data is collected for the specific tenants that are
listed and separated by comma.
n !. Data is collected for all tenants except the ones listed after !.
vRealize Automation Endpoint n Enabled: Collects and monitors data for all the vRealize Automation
Monitoring object types with the compute clusters under managed resources.
n Disabled: Collects and monitors data for only the reservation object type
with the compute clusters under managed resources.
vRealize Automation Enabled Default is On. Allows vRealize Automation to manage the placements of VMs
Intelligent Placement that are part of the clusters managed by vRealize Automation. This mode is
always On and used for work-load placement (WLP).
Enable vRealize Automation system Enable or disable health monitoring of the vRealize Automation system
health monitoring components. For example, Cafe and IAAS.
vRealize Automation VA FQDN The vRealize Automation VA IP or FQDN details are required when the
vRealize Automation system is HA enabled and runs behind a load balancer
for component discovery.
Enter these details only when you enable vRealize Automation system
health monitoring.
vRealize Automation adapter The time interval between data collections by the vRealize Automation
collection interval (minutes) solution.
Default is 15 minutes. You can increase or decrease the amount of time
between data collections. It is recommended that you do not change this
value in large-scale environments.
To change this value to less than 5 minutes, you must change the collection
interval value in the adapter.
Tenant resource collection interval The time interval between the data collected by the tenants in the vRealize
(minutes) Automation solution.
VMware, Inc. 233

Option Description
Business group resource collection The time interval between the data collected by the business groups in the
interval (minutes) vRealize Automation.
Blueprint resource collection The time interval between the data collected by the blueprints in the
interval (minutes) vRealize Automation solution.
Autodiscovery Discover objects automatically.

n To set automatic discovery for objects, select True.
n To set off the automatic discovery, select False.
6 Click Test Connection to validate the connection.
If one of the tenant connections is successful, Test Connection is successful.
Configuration Properties
In large-scale environments, multiple simultaneous API calls might cause performance problems
in vRealize Automation. When an adapter sends multiple parallel requests to WAPI in particular, it
severely impacts the database. Configuration properties are used to configure the settings with
appropriate values.
Table 4-35. Configuration Properties

Property Name Description Default Value
wapiCollectionMaxSeconds The upper limit for the amount of time 60 (1 minute)

that the adapter needs to try and
retrieve the data from API calls. This
property must be increased in large-
scale environments, in addition to
increasing the adapter's collection time
interval.
wapiThreadCount The number of threads that are 2

querying WAPI at a time.
This property might be increased or
decreased based on speed or
performance requirements.
VMware, Inc. 234

Table 4-35. Configuration Properties (continued)

Property Name Description Default Value
querySuiteAPIPageSize The number of the items to fetch in a 100

suite API call.
queryVraAPIPageSize The number of the items to fetch in a 100

single CAFE query.
Note It is recommended that you keep the
maximum value as 100.
Refer to the sizing guidelines for large-scale

environment guidelines: Sizing Guidelines
Alert Definitions
Alert definitions are combinations of symptoms and recommendations that identify problem
areas in your environment and generate alerts on which you can act. Symptom and alert
definitions are defined for vRealize Automation objects. The alerts are population-based alerts
based on the risk or health of a certain percentage of child objects.
The health and risk thresholds are as follows:
Health
n When 25%-50% of the child objects have health issues, the parent object triggers an alert
with a Warning health level.
with an Immediate health level.
with a Critical health level.
Risk
n When 25%-50% of the child objects have risk issues, the parent object triggers an alert with a
Warning risk level.
n When 50%-75% of the child objects have risk issues, the parent object triggers an alert with
an Immediate risk level.
n When 75%-100% of the child objects have risk issues, the parent object triggers an alert with
a Critical risk level.
vSAN
You can make vSAN operational in a production environment by using dashboards to evaluate,
manage, and optimize the performance of vSAN objects and vSAN-enabled objects in your
vCenter Server system.
vSAN extends the following features:
n Discovers vSAN disk groups in a vSAN datastore.
VMware, Inc. 235

n Identifies the vSAN-enabled cluster compute resource, host system, and datastore objects in
a vCenter Server system.
n Automatically adds related vCenter Server components that are in the monitoring state.
n Support for vSAN datastores in workload optimization with cross-cluster rebalance actions.
n You can move VMs from one vSAN datastore to another vSAN datastore.
n You can optimize the container if all the vSAN clusters are not in resync state.
n VMs with different storage policies for each disk or VMs with different types of storage
for each disk will not be moved.
n You can generate a rebalance plan only if sufficient disk space is available at the
destination vSAN datastore (The vSAN datastore slack space will also be considered).
n The storage policy assigned to the VM will be considered during the workload
optimization (Compatibility check is performed against the storage policy).
n VM migration from vSAN datastore to vSAN stretched clusters is not supported.
Configure a vSAN Adapter Instance

When configuring an adapter instance for vSAN, you add credentials for a vCenter Server. In the
earlier versions of vRealize Operations Manager, the vSAN solution was installed as part of the
vRealize Operations Manager installation. Now, in case of a new installation the vSAN solution is
pre-bundled as part of vRealize Operations Manager OVF, you must install the vSAN solution
separately.
Prerequisites
Only vCenter Server systems that are configured for both the vCenter adapter and the vSAN
adapter appear in the inventory tree under the vSAN and Storage Devices. Verify that the
vCenter Server that you use to configure the vSAN adapter instance is also configured as a
vCenter adapter instance for the VMware vSphere® solution. If not, add a vCenter adapter
instance for that vCenter Server.
You must open port 5989 between the host and any vRealize Operations Manager node on
which the vSAN adapter resides. This is applicable when the vSAN version in vSphere is 6.6 or
lower.
To know how to install the Native Management Packs, see Install Native Management Packs and
Add Management Packs.
Procedure
1 In the vCenter Server text box, enter the FQDN or IP address of the vCenter Server instance
to which you are connecting.
The vCenter Server FQDN or IP address must be reachable from all nodes in the vRealize
Operations Manager cluster.
VMware, Inc. 236

2 To add credentials on the Manage Solution page, click the plus sign.
a In the Credential name text box, enter the name by which you are identifying the
configured credentials.
b Type the User name and Password for the vCenter Server instance.
c Click OK.
You configured credentials to connect to a vCenter Server instance.
3 Click Advanced Settings and specify the following values:
Option Description
Collectors/Groups Determines which vRealize Operations Manager collector

is used to manage the adapter processes. If you have
only one adapter instance, select Default collector
group. If you have multiple collectors in your
environment, and you want to distribute the workload to
optimize performance, select the collector to manage
the adapter processes for this instance.
Auto Discovery Determines whether new objects added to the

monitored system are discovered and added to vRealize
Operations Manager after the initial configuration of the
adapter.
n If the value is true, vRealize Operations Manager
collects information about any new objects that are
added to the monitored system after the initial
configuration. For example, if you add more hosts
and virtual machines, these objects are added during
the next collections cycle. This is the default value.
n If the value is false, vRealize Operations Manager
monitors only the objects that are present on the
target system when you configure the adapter
instance.
Enable SMART data collection When set to true, enables SMART data collection for
physical disk devices.
vCenter ID A global unique identifier associated with this vCenter

instance (VC UUID).
4 Click Test Connection to validate the connection with your vCenter Server instance.
5 Accept the vCenter Server security certificate.
Results
The adapter is added to the Adapter Instance list and is active.
VMware, Inc. 237

What to do next
To verify that the adapter is configured and collecting data from vSAN objects, wait a few
collection cycles, then view application-related data.
n Inventory. Verify that all the objects related to the vSAN instance are listed. Objects should
be in the collecting state and receiving data.
n Dashboards. Verify that vSAN Capacity Overview, Migrate to vSAN, vSAN Operations
Overview, and Troubleshoot vSAN, are added to the default dashboards.
n Under Environment > vSAN and Storage Devices, verify that the vSAN hierarchy includes
the following related vCenter Server system objects:
n vSAN World
n Cache Disk
n Capacity Disk
n vSAN-enabled vCenter Server clusters
n vSAN Fault Domains (optional)
n vSAN-enabled Hosts
n vSAN Datastores
n vSAN Disk Groups
n vSAN Datastore related VMs
n vSAN Witness Hosts (optional)
Verify that the Adapter Instance is Connected and Collecting Data

You configured an adapter instance of vSAN with credentials for a vCenter Server. Now you
want to verify that your adapter instance can retrieve information from vSAN objects in your
environment.
To view the object types, in the menu, click Administration > Configuration > Inventory >
Adapter Instances > vSAN Adapter Instance > <User_Created_Instance>.
Table 4-36. Object Types that vSAN Discovers

Object Type Description
vSAN Adapter Instance The vRealize Operations Management Pack for vSAN instance.
vSAN Cluster vSAN clusters in your data center.
vSAN Datastore vSAN datastores in your data center.
vSAN Disk Group A collection of SSDs and magnetic disks used by vSAN.
vSAN Fault Domain A tag for a fault domain in your data center.
vSAN Host vSAN hosts in your data center.
vSAN Witness Host A tag for a witness host of a stretched cluster, if the stretched cluster feature is enabled on
the vSAN cluster.
VMware, Inc. 238

Table 4-36. Object Types that vSAN Discovers (continued)

Object Type Description
vSAN World A vSAN World is a group parent resource for all vSAN adapter instances. vSAN World
displays aggregated data of all adapter instances and a single root object of the entire vSAN
hierarchy.
Cache Disk A local physical device on a host used for storing VM files in vSAN.
Capacity Disk A local physical device on a host used for read or write caching in vSAN
The vSAN adapter also monitors the following objects discovered by the VMware vSphere
adapter.
n Cluster Compute Resources
n Host System
n Datastore
Procedure
1 In the menu, click Administration and then in the left pane, click Configuration > Inventory .
2 In the list of tags, expand Adapter Instances and expand vSAN Adapter Instance.
3 Select the adapter instance name to display the list of objects discovered by your adapter
instance.
4 Slide the display bar to the right to view the object status.
Object Status Description
Collection State If green, the object is connected.
Collection Status If green, the adapter is retrieving data from the object.
5 Deselect the adapter instance name and expand the Object Types tag.
Each Object Type name appears with the number of objects of that type in your
environment.
What to do next
If objects are missing or not transmitting data, check to confirm that the object is connected.
Then check for related alerts.
To ensure that the vSAN adapter can collect all performance data, the Virtual SAN performance
service must be enabled in vSphere. For instructions on how to enable the service, see Turn on
Virtual SAN Performance Service in the VMware Virtual SAN documentation.
VMware, Inc. 239

If the Virtual SAN performance service is disabled or experiencing issues, an alert is triggered for
the vSAN adapter instance and the following errors appear in the adapter logs.
ERROR com.vmware.adapter3.vsan.metricloader.VsanDiskgroupMetricLoader.collectMetrics
- Failed to collect performance metrics for Disk Group
com.vmware.adapter3.vsan.metricloader.VsanDiskgroupMetricLoader.collectMetrics
- vSAN Performance Service might be turned OFF.
com.vmware.adapter3.vsan.metricloader.VsanDiskgroupMetricLoader.collectMetrics
- (vim.fault.NotFound)
{
faultCause = null,
faultMessage = (vmodl.LocalizableMessage)
[
com.vmware.vim.binding.impl.vmodl.LocalizableMessageImpl@98e1294
]
}
End Point Operations Management Solution in vRealize Operations

Manager
You configure End Point Operations Management to gather operating system metrics and to
monitor availability of remote platforms and applications. This solution is installed with vRealize
Operations Manager.
End Point Operations Management Agent Installation and Deployment

Use the information in these links to help you to install and deploy End Point Operations
Management agents in your environment.
Prepare to Install the End Point Operations Management Agent

Before you can install the End Point Operations Management agent, you must perform
preparatory tasks.
Prerequisites
n To configure the agent to use a keystore that you manage yourself for SSL communication,
set up a JKS-format keystore for the agent on its host and import its SSL certificate. Make a
note of the full path to the keystore, and its password. You must specify this data in the
agent's agent.properties file.
Verify that the agent keystore password and the private key password are identical.
n Define the agent HQ_JAVA_HOME location.
VMware, Inc. 240

vRealize Operations Manager platform-specific installers include JRE 1.8.x . Depending on

your environment and the installer you use, you may need to define the location of the JRE to
ensure that the agent can find the JRE to use. See Configuring JRE Locations for End Point
Operations Management Components.
Supported Operating Systems for the End Point Operations Management Agent
These tables describe the supported operating systems for End Point Operations Management
agent deployments.
These configurations are supported for the agent in both development and production
environments.
Table 4-37. Supported Operating Systems for the End Point Operations Management Agent
Operating System Processor Architecture JVM
RedHat Enterprise Linux (RHEL) 5.x, x86_64, x86_32 Oracle Java SE8
6.x, 7.x
CentOS 5.x, 6.x, 7.x x86_64, x86_32 Oracle Java SE8
SUSE Enterprise Linux (SLES) 11.x, 12.x x86_64 Oracle Java SE8
Windows 2008 Server, 2008 Server R2 x86_64, x86_32 Oracle Java SE8
Windows 2012 Server, 2012 Server R2 x86_64 Oracle Java SE8
Windows Server 2016 x86_64 Oracle Java SE8
Solaris 10, 11 x86_64, SPARC Oracle Java SE7
AIX 6.1, 7.1 Power PC IBM Java SE7
VMware Photon Linux 1. 0 x86_64 Open JDK 1.8.0_72-BLFS
Oracle Linux versions 5, 6, 7 x86_64, x86_32 Open JDK Runtime Environment 1.7
Selecting an Agent Installer Package

The End Point Operations Management agent installation files are included in the vRealize
Operations Manager installation package.
You can install the End Point Operations Management agent from a tar.gz or .zip archive, or
from an operating system-specific installer for Windows or for Linux-like systems that support
RPM.
When you install a non-JRE version of End Point Operations Management agent, to avoid being
exposed to security risks related to earlier versions of Java, it is recommended that you only use
the latest Java version.
n Install the Agent on a Linux Platform from an RPM Package

You can install the End Point Operations Management agent from a RedHat Package
Manager (RPM) package. The agent in the noarch package does not include a JRE.
VMware, Inc. 241

n Install the Agent on a Linux Platform from an Archive

You can install an End Point Operations Management agent on a Linux platform from a
tar.gz archive.
n Install the Agent on a Windows Platform from an Archive

You can install an End Point Operations Management agent on a Windows platform from
a .zip file.
n Install the Agent on a Windows Platform Using the Windows Installer

You can install the End Point Operations Management agent on a Windows platform using a
Windows installer.
n Installing an End Point Operations Management Agent Silently on a Windows Machine

You can install an End Point Operations Management agent on a Windows machine using
silent or very silent installation.
n Install the Agent on an AIX Platform

You can install the End Point Operations Management agent on an AIX platform.
n Install the Agent on a Solaris Platform

You can install the End Point Operations Management agent on a Solaris platform.
Install the Agent on a Linux Platform from an RPM Package

You can install the End Point Operations Management agent from a RedHat Package Manager
(RPM) package. The agent in the noarch package does not include a JRE.
Agent-only archives are useful when you deploy agents to a large number of platforms with
various operating systems and architectures. Agent archives are available for Windows and
UNIX-like environments, with and without built-in JREs.
The RPM performs the following actions:
n Creates a user and group named epops if they do not exist. The user is a service account that
is locked and you cannot log into it.
n Installs the agent files into /opt/vmware/epops-agent.
n Installs an init script to /etc/init.d/epops-agent.
n Adds the init script to chkconfig and sets it to on for run levels 2, 3, 4, and 5.
If you have multiple agents to install, see Install Multiple End Point Operations Management
Agents Simultaneously.
Prerequisites
n Verify that you have sufficient privileges to deploy an End Point Operations Management
agent. You must have vRealize Operations Manager user credentials that include a role that
allows you to install End Point Operations Management agents. See Roles and Privileges in
VMware, Inc. 242

n If you plan to run ICMP checks, you must install the End Point Operations Management agent
with root privileges.
n To configure the agent to use a keystore that you manage yourself for SSL communication,
set up a JKS-format keystore for the agent on its host and configure the agent to use its SSL
certificate. Note the full path to the keystore, and its password. You must specify this data in
the agent agent.properties file.
Verify that the agent keystore password and the private key password are identical.
n If you are installing a non-JRE package, define the agent HQ_JAVA_HOME location.
End Point Operations Management platform-specific installers include JRE 1.8.x. Platform-
independent installers do not. Depending on your environment and the installer you use, you
might need to define the location of the JRE to ensure that the agent can find the JRE to use.
See Configuring JRE Locations for End Point Operations Management Components.
n If you are installing a non-JRE package, verify that you are using the latest Java version. You
might be exposed to security risks with earlier versions of Java.
n Verify that the installation directory for the End Point Operations Management agent does
not contain a vRealize Hyperic agent installation.
n If you are using the noarch installation, verify that a JDK or JRE is installed on the platform.
n Verify that you use only ASCII characters when specifying the agent installation path. If you
want to use non-ASCII characters, you must set the encoding of the Linux machine and SSH
client application to UTF-8.
Procedure
1 Download the appropriate RPM bundle to the target machine.
Operating System RPM Bundle to Download
64bit Operating System epops-agent-x86-64-linux-version.rpm
32bit Operating System epops-agent-x86-linux-version.rpm
No Arch epops-agent-noarch-linux-version.rpm
2 Open an SSH connection using root credentials.
3 Run rpm -i epops-agent-Arch-linux-version.rpm to install the agent on the platform that the
agent will monitor, where Arch is the name of the archive and version is the version number.
Results
The End Point Operations Management agent is installed, and the service is configured to start at
boot.
VMware, Inc. 243

What to do next
Before you start the service, verify that the epops user credentials include any permissions that
are required to enable your plug-ins to discover and monitor their applications, then perform one
of the following processes.
n Run service epops-agent start to start the epops-agent service.
n If you installed the End Point Operations Management agent on a machine running SuSE 12.x,
start the End Point Operations Management agent by running the [EP Ops Home]/bin/ep-
agent.sh start command.
n When you attempt to start an End Point Operations Management agent you might receive a
message that the agent is already running. Run ./bin/ep-agent.sh stop before starting the
agent.
n Configure the agent in the agent.properties file, then start the service. See Activate End
Point Operations Management Agent to vRealize Operations Manager Server Setup
Properties.
Install the Agent on a Linux Platform from an Archive
You can install an End Point Operations Management agent on a Linux platform from a tar.gz
archive.
By default, during installation, the setup process prompts you to provide configuration values.
You can automate this process by specifying the values in the agent properties file. If the installer
detects values in the properties file, it applies those values. Subsequent deployments also use
the values specified in the agent properties file.
Prerequisites
n If you plan to run ICMP checks, you must install the End Point Operations Management agent
with root privileges.
n Verify that you use only ASCII characters when specifying the agent installation path. If you
want to use non-ASCII characters, you must set the encoding of the Linux machine and SSH
client application to UTF-8.
VMware, Inc. 244

Procedure
1 Download and extract the End Point Operations Management agent installation tar.gz file
that is appropriate for your Linux operating system.
Operating System tar.gz Bundle to Download
64bit Operating System epops-agent-x86-64-linux-version.tar.gz
32bit Operating System epops-agent-x86-linux-version.tar.gz
No Arch epops-agent-noJRE-version.tar.gz
2 Run cd agent name/bin to open the bin directory for the agent.
3 Run ep-agent.sh start.
The first time that you install the agent, the command launches the setup process, unless you
already specified all the required configuration values in the agent properties file.
4 (Optional) Run ep-agent.sh status to view the current status of the agent, including the IP
address and port.
What to do next
Register the client certificate for the agent. See Regenerate an Agent Client Certificate.
Install the Agent on a Windows Platform from an Archive
You can install an End Point Operations Management agent on a Windows platform from a .zip
file.
By default, during installation, the setup process prompts you to provide configuration values.
You can automate this process by specifying the values in the agent properties file. If the installer
detects values in the properties file, it applies those values. Subsequent deployments also use
the values specified in the agent properties file.
Prerequisites
n Verify that you have sufficient privileges to deploy a End Point Operations Management
n Verify that you do not have any End Point Operations Management or vRealize Hyperic agent
installed on your environment before running the agent Windows installer.
VMware, Inc. 245

Procedure
1 Download and extract the End Point Operations Management agent installation .zip file that
is appropriate for your Windows operating system.
Operating System ZIP Bundle to Download
64bit Operating System epops-agent-x86-64-win-version.zip
32bit Operating System epops-agent-win32-version.zip
No Arch epops-agent-noJRE-version.zip
2 Run cd agent name\bin to open the bin directory for the agent.
3 Run ep-agent.bat install.
4 Run ep-agent.bat start.
The first time that you install the agent, the command starts the setup process, unless you
already specified the configuration values in the agent properties file.
What to do next
Generate the client certificate for the agent. See Regenerate an Agent Client Certificate.
Install the Agent on a Windows Platform Using the Windows Installer
You can install the End Point Operations Management agent on a Windows platform using a
Windows installer.
You can perform a silent installation of the agent. See Installing an End Point Operations
Management Agent Silently on a Windows Machine.
Prerequisites
n If you already have an End Point Operations Management agent installed on the machine,
verify that it is not running.
n Verify that you do not have any End Point Operations Management or vRealize Hyperic agent
n You must know the user name and password for the vRealize Operations Manager, the
vRealize Operations Manager server address (FQDN), and the server certificate thumbprint
value. You can see additional information about the certificate thumbprint in the procedure.
VMware, Inc. 246

Procedure
1 Download the Windows installation EXE file that is appropriate for your Windows platform.
Operating System RPM Bundle to Download
64bit Operating System epops-agent-x86-64-win-version.exe
32bit Operating System epops-agent-x86-win-version.exe
2 Double-click the file to open the installation wizard.
3 Complete the steps in the installation wizard.
Verify that the user and system locales are identical, and that the installation path contains
only characters that are part of the system locale's code page. You can set user and system
locales in the Regional Options or Regional Settings control panel.
Note the following information related to defining the server certificate thumbprint.
n The server certificate thumbprint is required to run a silent installation.
n Either the SHA1 or SHA256 algorithm can be used for the thumbprint.
n By default, the vRealize Operations Manager server generates a self-signed CA certificate

that is used to sign the certificate of all the nodes in the cluster. In this case, the
thumbprint must be the thumbprint of the CA certificate, to allow for the agent to
communicate with all nodes.
n As a vRealize Operations Manager administrator, you can import a custom certificate

instead of using the default. In this instance, you must specify a thumbprint corresponding
to that certificate as the value of this property.
n To view the certificate thumbprint value, log into the vRealize Operations Manager
Administration interface at https://IP Address/admin and click the SSL Certificate icon
located on the right of the menu bar. Unless you replaced the original certificate with a
custom certificate, the second thumbprint in the list is the correct one. If you did upload a
custom certificate, the first thumbprint in the list is the correct one.
4 (Optional) Run ep-agent.bat query to verify if the agent is installed and running.
Results
The agent begins running on the Windows platform.
Caution The agent will run even if some of the parameters that you provided in the installation
wizard are missing or invalid. Check the wrapper.log and agent.log files in the product
installation path/log directory to verify that there are no installation errors.
Installing an End Point Operations Management Agent Silently on a Windows Machine

You can install an End Point Operations Management agent on a Windows machine using silent
or very silent installation.
VMware, Inc. 247

Silent and very silent installations are performed from a command line interface using a setup
installer executable file.
Verify that you do not have any End Point Operations Management or vRealize Hyperic agent
Use the following parameters to set up the installation process. For more information about these
parameters, see Specify the End Point Operations Management Agent Setup Properties.
Caution The parameters that you specify for the Windows installer are passed to the agent
configuration without validation. If you provide an incorrect IP address or user credentials, the
End Point Operations Management agent cannot start.
Table 4-38. Silent Command Line Installer Parameters

Mandatory
Parameter Value /Optional Comments
-serverAddress FQDN/iP Mandatory FQDN or IP address of the vRealize Operations

address Manager server.
-username string Mandatory
-securePort number Optional Default is 443
-password string Mandatory
-serverCertificateThumbprint string Mandatory The vRealize Operations Manager server certificate

thumbprint. You must enclose the certificate
thumbprint in opening and closing quotation marks,
for example, -serverCertificateThumbprint
"31:32:FA:1F:FD:78:1E:D8:9A:15:32:85:D7:FE:54:49:0A:
1D:9F:6D" .
Parameters are available to define various other attributes for the installation process.
Table 4-39. Additional Silent Command Line Installer Parameters

Default
Parameter Value Comments
/DIR C:\ep-agent Specifies the installation path. You cannot use spaces in the
installation path, and you must connect the /DIR command
and the installation path with an equal sign, for example, /
DIR=C:\ep-agent.
/SILENT none Specifies that the installation is to be silent. In a silent

installation, only the progress window appears.
/VERYSILENT none Specifies that the installation is to be very silent. In a very

silent installation, the progress window does not appear,
however installation error messages are displayed, as is the
startup prompt if you did not disable it.
Install the Agent on an AIX Platform

You can install the End Point Operations Management agent on an AIX platform.
VMware, Inc. 248

Prerequisites
1 Install IBM Java 7.
2 Add the latest JCE from the IBM JRE security directory: JAVA_INSTALLATION_DIR/jre/lib/
security. For more information, see Downloading and installing the unrestricted JCE policy
files
Procedure
1 When you configure the PATH variable, add /usr/java7_64/jre/bin:/usr/java7_64/bin or

PATH=/usr/java7_64/jre/bin:/usr/java7_64/bin:$PATH.
2 Configure HQ_JAVA_HOME=path_to_current_java_directory.
For more information on setting up and checking your AIX environment, see https://
www.ibm.com/support/knowledgecenter/SSYKE2_7.0.0/com.ibm.java.aix.70.doc/diag/
problem_determination/aix_setup.html.
3 Download the noJre version of the End Point Operations Management agent and install the
agent on an AIX machine.
4 For agent installation information, see Install the Agent on a Linux Platform from an Archive
Install the Agent on a Solaris Platform
You can install the End Point Operations Management agent on a Solaris platform.
Prerequisites
1 Install Java 7 or above for Solaris from the Oracle site: https://java.com/en/download/help/
solaris_install.xml
2 Add the latest JCE from http://www.oracle.com/technetwork/java/javase/downloads/jce-7-

download-432124.html
Procedure
1 When you configure the PATH variable, add /usr/java7_64/jre/bin:/usr/java7_64/bin or

PATH=/usr/java7_64/jre/bin:/usr/java7_64/bin:$PATH.
2 Configure HQ_JAVA_HOME=path_to_current_java_directory.
3 Download and install the noJre version of the End Point Operations Management agent on a
Solaris machine.
4 For agent installation information, see Install the Agent on a Linux Platform from an Archive
Java Prerequisites for the End Point Operations Management Agent

All End Point Operations Management agents require Java Cryptography Extension (JCE)
Unlimited Strength Jurisdiction policy files be included as part of the Java package.
Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction policy files are included in the
JRE End Point Operations Management agent installation options.
VMware, Inc. 249

You can install an End Point Operations Management agent package that does not contain JRE
files, or choose to add JRE later.
If you select a non-JRE installation option, you must ensure that your Java package includes Java
Cryptography Extension (JCE) Unlimited Strength Jurisdiction policy files to enable registration of
the End Point Operations Management agent. If you select a non-JRE option and your Java
package does not include Java Cryptography Extension (JCE) Unlimited Strength Jurisdiction
policy files, you receive these error messages Server might be down (or wrong IP/port were
used) and Cannot support TLS_RSA_WITH_AES_256_CBC_SHA with currently installed
providers.
Configuring JRE Locations for End Point Operations Management Components

End Point Operations Management agents require a JRE. The platform-specific End Point
Operations Management agent installers include a JRE. Platform-independent End Point
Operations Management agent installers do not include a JRE.
If you select a non-JRE installation option, you must ensure that your Java package includes Java
Cryptography Extension (JCE) Unlimited Strength Jurisdiction policy files to enable registration of
the End Point Operations Management agent. For more information , see Java Prerequisites for
the End Point Operations Management Agent.
Depending on your environment and the installation package that you use, you might need to
define the location of the JRE for your agents. The following environments require JRE location
configuration.
n Platform-specific agent installation on a machine that has its own JRE that you want to use.
n Platform-independent agent installation.

How the Agent Resolves its JRE
The agent resolves its JRE based on platform type.
UNIX-like Platforms
On UNIX-like platforms, the agent determines which JRE to use in the following order:
1 HQ_JAVA_HOME environment variable
2 Embedded JRE
3 JAVA_HOME environment variable
Linux Platforms
On Linux platforms, you use export HQ_JAVA_HOME= path_to_current_java_directory to define a

system variable.
Windows Platforms
On Windows platforms, the agent resolves the JRE to use in the following order:
1 HQ_JAVA_HOME environment variable
VMware, Inc. 250

The path defined in the variable must not contain spaces. Consider using a shortened
version of the path, using the tild (~) character. For example,c:\Program Files\Java
\jre7 can become c:\Progra~1\Java\jre7. The number after the tild depends on the
alphabetical order (where a = 1, b =2, and so on) of files whose name begins with progra in
that directory.
2 Embedded JRE
You define a system variable from the My Computer menu. Select Properties > Advanced >
Environment Variables > System Variables > New.
Because of a known issue with Windows, on Windows Server 2008 R2 and 2012 R2, Windows
services might keep old values of system variables, even though they have been updated or
removed. As a result, updates or removal of the HQ_JAVA_HOME system variable might not be
propagated to the End Point Operations Management Agent service. In this event, the End Point
Operations Management agent might use an obsolete value for HQ_JAVA_HOME, which causes it to
use the wrong JRE version.
System Prerequisites for the End Point Operations Management Agent

If you do not define localhost as the loopback address, the End Point Operations Management
agent does not register and the following error appears: Connection failed. Server may be
down (or wrong IP/port were used). Waiting for 10 seconds before retrying.
As a workaround, complete the following steps:
Procedure
1 Open the hosts file /etc/hosts on Linux or C:\Windows\System32\Drivers\etc\hosts on

Windows.
2 Modify the file to include a localhost mapping to the IPv4 127.0.0.1 loopback address,
using 127.0.0.1 localhost.
3 Save the file.
Configure the End Point Operations Management Agent to vRealize Operations ManagerServer
Communication Properties
Before first agent startup, you can define the properties that enable the agent to communicate
with the vRealize Operations Manager server, and other agent properties, in the
agent.properties file of an agent. When you configure the agent in the properties file you can
streamline the deployment for multiple agents.
If a properties file exists, back it up before you make configuration changes. If the agent does not
have a properties file, create one.
An agent looks for its properties file in AgentHome/conf. This is the default location of
agent.properties.
VMware, Inc. 251

If the agent does not find the required properties for establishing communications with the
vRealize Operations Manager server in either of these locations, it prompts for the property
values at initial start up of the agent.
A number of steps are required to complete the configuration.
You can define some agent properties before or after the initial startup. You must always
configure properties that control the following behaviors before initial startup.
n When the agent must use an SSL keystore that you manage, rather than a keystore that
vRealize Operations Manager generates.
n When the agent must connect to the vRealize Operations Manager server through a proxy
server.
Prerequisites
Verify that the vRealize Operations Manager server is running.
Procedure
1 Activate End Point Operations Management Agent to vRealize Operations Manager Server
Setup Properties
In the agent.properties file, properties relating to communication between the End Point
Operations Management agent and the vRealize Operations Manager server are inactive by
default. You must activate them.
2 Specify the End Point Operations Management Agent Setup Properties

The agent.properties file contains properties that you can configure to manage
communication.
3 Configure an End Point Operations Management Agent Keystore

The agent uses a self-signed certificate for internal communication, and a second certificate
that is signed by the server during the agent registration process. By default, the certificates
are stored in a keystore that is generated in the data folder. You can configure your own
keystore for the agent to use.
4 Configure the End Point Operations Management Agent by Using the Configuration Dialog
Box
The End Point Operations Management agent configuration dialog box appears in the shell
when you start an agent that does not have configuration values that specify the location of
the vRealize Operations Manager server. The dialog box prompts you to provide the
address and port of the vRealize Operations Manager server, and other connection-related
data.
5 Overriding Agent Configuration Properties

You can specify that vRealize Operations Manager override default agent properties when
they differ from custom properties that you have defined.
VMware, Inc. 252

6 End Point Operations Management Agent Properties

Multiple properties are supported in the agent.properties file for an End Point Operations
Management agent. Not all supported properties are included by default in the
agent.properties file.
What to do next
Start the End Point Operations Management agent.

Activate End Point Operations Management Agent to vRealize Operations Manager Server
Setup Properties
In the agent.properties file, properties relating to communication between the End Point
Operations Management agent and the vRealize Operations Manager server are inactive by
default. You must activate them.
Procedure
1 In the agent.properties file, locate the following section.
## Use the following to automate agent setup

## using these properties.
##
## If any properties do not have values specified, the setup
## process prompts for their values.
##
## If the value to use during automatic setup is the default, use the string *default* as the
value for the option.
2 Remove the hash tag at the beginning of each line to activate the properties.
#agent.setup.serverIP=localhost
#agent.setup.serverSSLPort=443
#agent.setup.serverLogin=username
#agent.setup.serverPword=password
The first time that you start the End Point Operations Management agent, if
agent.setup.serverPword is inactive, and has a plain text value, the agent encrypts the value.
3 (Optional) Remove the hash tag at the beginning of the line

#agent.setup.serverCertificateThumbprint= and provide a thumbprint value to activate pre-
approval of the server certificate.
Specify the End Point Operations Management Agent Setup Properties
The agent.properties file contains properties that you can configure to manage communication.
Agent-server setup requires a minimum set of properties.
VMware, Inc. 253

Procedure
1 Specify the location and credentials the agent must use to contact the vRealize Operations
Manager server.
Property Property Definition
agent.setup.serverIP Specify the address or hostname of the vRealize Operations Manager server.
agent.setup.serverSSLPort The default value is the standard SSL vRealize Operations Manager server
listen port. If your server is configured for a different listen port, specify the
port number.
agent.setup.serverLogin Specify the user name for the agent to use when connecting to the vRealize
Operations Manager server. If you change the value from the username
default value, verify that the user account is correctly configured on the
vRealize Operations Manager server.
agent.setup.serverPword Specify the password for the agent to use, together with the vRealize
Operations Manager user name, when connecting to thevRealize Operations
Manager server. Verify that the password is the one configured in vRealize
Operations Manager for the user account.
2 (Optional) Specify the vRealize Operations Manager server certificate thumbprint.
agent.setup.serverCertificateThumbpr Provides details about the server certificate to trust.

int This parameter is required to run a silent installation.
Either the SHA1 or SHA256 algorithm can be used for the thumbprint.
By default, the vRealize Operations Manager server generates a self-signed
CA certificate that is used to sign the certificate of all the nodes in the
cluster. In this case, the thumbprint must be the thumbprint of the CA
certificate, to allow for the agent to communicate with all nodes.
As a vRealize Operations Manager administrator, you can import a custom
certificate instead of using the default. In this instance, you must specify a
thumbprint corresponding to that certificate as the value of this property.
To view the certificate thumbprint value, log into the vRealize Operations
Manager Administration interface at https://IP Address/admin and click
the SSL Certificate icon located on the right of the menu bar. Unless you
replaced the original certificate with a custom certificate, the second
thumbprint in the list is the correct one. If you did upload a custom
certificate, the first thumbprint in the list is the correct one.
VMware, Inc. 254

3 (Optional) Specify the location and file name of the platform token file.
This file is created by the agent during installation and contains the identity token for the
platform object.
Windows: Provides details about the location and name of the platform token file.
agent.setup.tokenFileWindows The value cannot include backslash (\) or percentage(%) characters, or
Linux: agent.setup.tokenFileLinux environment variables.
Ensure that you use forward slashes (/) when specifying the Windows path.
4 (Optional) Specify any other required properties by running the appropriate command.
Operating System Command
Linux ./bin/ep-agent.sh set-property PropertyKey PropertyValue
Windows ./bin/ep-agent.bat set-property PropertyKey PropertyValue
The properties are encrypted in the agent.properties file.

Configure an End Point Operations Management Agent Keystore
The agent uses a self-signed certificate for internal communication, and a second certificate that
is signed by the server during the agent registration process. By default, the certificates are
stored in a keystore that is generated in the data folder. You can configure your own keystore
for the agent to use.
Important To use your own keystore, you must perform this task before the first agent
activation.
Procedure
1 In the agent.properties file, activate the # agent.keystore.path= and #

agent.keystore.password= properties.
Define the full path to the keystore with agent.keystore.path and the keystore password with
agent.keystore.password.
2 Add the [agent.keystore.alias] property to the properties file, and set it to the alias of the
primary certificate or private key entry of the keystore primary certificate.
Configure the End Point Operations Management Agent by Using the Configuration Dialog Box
The End Point Operations Management agent configuration dialog box appears in the shell when
you start an agent that does not have configuration values that specify the location of the
vRealize Operations Manager server. The dialog box prompts you to provide the address and
port of the vRealize Operations Manager server, and other connection-related data.
The agent configuration dialog box appears in these cases:
n The first time that you start an agent, if you did not supply one or more of the relevant
properties in the agent.properties file.
n When you start an agent for which saved server connection data is corrupt or was removed.
VMware, Inc. 255

You can also run the agent launcher to rerun the configuration dialog box.
Prerequisites
Verify that the server is running.
Procedure
1 Open a terminal window on the platform on which the agent is installed.
2 Navigate to the AgentHome/bin directory.
3 Run the agent launcher using the start or setup option.
Platform Command
UNIX-like ep-agent.sh start
Windows Install the Windows service for the agent, then run the it: ep-agent.bat
install ep-agent.bat start command.
When you configure an End Point Operations Management agent as a
Windows service, make sure that the credentials that you specify are
sufficient for the service to connect to the monitored technology. For
example, if you have anEnd Point Operations Management agent that is
running on Microsoft SQL Server, and only a specific user can log in to that
server, the Windows service login must also be for that specific user.
4 Respond to the prompts, noting the following as you move through the process.
Prompt Description
Enter the server hostname or IP If the server is on the same machine as the agent, you can enter localhost. If
address a firewall is blocking traffic from the agent to the server, specify the address
of the firewall.
Enter the server SSL port Specify the SSL port on the vRealize Operations Manager server to which
the agent must connect. The default port is 443.
The server has presented an If this warning appears, but your server is signed by a trusted certificate or
untrusted certificate you have updated the thumbprint property to contain the thumbprint, this
agent might be subject to a man-in-the-middle attack. Review the displayed
certificate thumbprint details carefully.
Enter your server username Enter the name of a vRealize Operations Manager user with agentManager
permissions.
Enter your server password Enter the password for the specified vRealize Operations Manager. Do not
store the password in the agent.properties file.
Results
The agent initiates a connection to the vRealize Operations Manager server and the server
verifies that the agent is authenticated to communicate with it.
The server generates a client certificate that includes the agent token. The message The agent
has been successfully registered appears. The agent starts discovering the platform and
supported products running on it.
VMware, Inc. 256

Overriding Agent Configuration Properties

You can specify that vRealize Operations Manager override default agent properties when they
differ from custom properties that you have defined.
In the Advanced section of the Edit Object dialog box, if you set the Override agent
configuration data to false, default agent configuration data is applied. If you set Override
agent configuration data to true, the default agent parameter values are ignored if you have set
alternative values, and the values that you set are applied.
If you set the value of Override agent configuration data to true when editing an MSSQL object
(MSSQL, MSSQL Database, MSSQL Reporting Services, MSSQL Analysis Service, or MSSQL
Agent) that runs in a cluster, it might result in inconsistent behavior.
End Point Operations Management Agent Properties
Multiple properties are supported in the agent.properties file for an End Point Operations
Management agent. Not all supported properties are included by default in the
You must add any properties that you want to use that are not included in the default
You can encrypt properties in the agent.properties file to enable silent installation.
Encrypt End Point Operations Management Agent Property Values
After you have installed an End Point Operations Management agent, you can use it to add
encrypted values to the agent.properties file to enable silent installation.
For example, to specify the user password, you can run ./bin/ep-agent.sh set-property
agent.setup.serverPword serverPasswordValue to add the following line to the agent.properties file.
agent.setup.serverPword = ENC(4FyUf6m/c5i+RriaNpSEQ1WKGb4y
+Dhp7213XQiyvtwI4tMlbGJfZMBPG23KnsUWu3OKrW35gB+Ms20snM4TDg==)
The key that was used to encrypt the value is saved in AgentHome/conf/agent.scu. If you
encrypt other values, the key that was used to encrypt the first value is used.
Prerequisites
Verify that the End Point Operations Management agent can access AgentHome/conf/agent.scu.
Following the encryption of any agent-to-server connection properties, the agent must be able
to access this file to start.
Procedure
u Open a command prompt and run ./bin/ep-agent.sh set-property agent.setup.propertyName

propertyValue.
Results
The key that was used to encrypt the value is saved in AgentHome/conf/agent.scu.
VMware, Inc. 257

What to do next
If your agent deployment strategy involves distributing a standard agent.properties file to all
agents, you must also distribute agent.scu. See Install Multiple End Point Operations
Management Agents Simultaneously.
Adding Properties to the agent.properties File

You must add any properties that you want to use that are not included in the default
Following is a list of the available properties.
n agent.keystore.alias Property
This property configures the name of the user-managed keystore for the agent for agents
configured for unidirectional communication with the vRealize Operations Manager server.
n agent.keystore.password Property
This property configures the password for an End Point Operations Management agent's
SSL keystore.
n agent.keystore.path Property
This property configures the location of a End Point Operations Management agent's SSL
keystore.
n agent.listenPort Property
This property specifies the port where the End Point Operations Management agent listens
to receive communication from the vRealize Operations Manager server.
n agent.logDir Property
You can add this property to the agent.properties file to specify the directory where the End
Point Operations Management agent writes its log file. If you do not specify a fully qualified
path, agent.logDir is evaluated relative to the agent installation directory.
n agent.logFile Property
The path and name of the agent log file.
n agent.logLevel Property
The level of detail of the messages the agent writes to the log file.
n agent.logLevel.SystemErr Property
Redirects System.err to the agent.log file.
n agent.logLevel.SystemOut Property
Redirects System.out to the agent.log file.
n agent.proxyHost Property
The host name or IP address of the proxy server that the End Point Operations Management
agent must connect to first when establishing a connection to the vRealize Operations
Manager server.
VMware, Inc. 258

n agent.proxyPort Property
The port number of the proxy server that the End Point Operations Management agent must
connect to first when establishing a connection to the vRealize Operations Manager server.
n agent.setup.acceptUnverifiedCertificate Property
This property controls whether an End Point Operations Management agent issues a
warning when the vRealize Operations Manager server presents an SSL certificate that is not
in the agent's keystore, and is either self-signed or signed by a different certificate authority
than the one that signed the agent's SSL certificate.
n agent.setup.camIP Property
Use this property to define the IP address of the vRealize Operations Manager server for the
agent. The End Point Operations Management agent reads this value only in the event that it
cannot find connection configuration in its data directory.
n agent.setup.camLogin Property
At first startup after installation, use this property to define the End Point Operations
Management agent user name to use when the agent is registering itself with the server.
n agent.setup.camPort Property
Management agent server port to use for non-secure communications with the server.
n agent.setup.camPword Property
Use this property to define the password that the End Point Operations Management agent
uses when connecting to the vRealize Operations Manager server, so that the agent does
not prompt a user to supply the password interactively at first startup.
n agent.setup.camSecure
This property is used when you are registering the End Point Operations Management with
the vRealize Operations Manager server to communicate using encryption.
n agent.setup.camSSLPort Property
Management agent server port to use for SSL communications with the server.
n agent.setup.resetupToken Property
Use this property to configure an End Point Operations Management agent to create a new
token to use for authentication with the server at startup. Regenerating a token is useful if
the agent cannot connect to the server because the token has been deleted or corrupted.
n agent.setup.unidirectional Property
Enables unidirectional communications between the End Point Operations Management
agent and vRealize Operations Manager server.
VMware, Inc. 259

n agent.startupTimeOut Property
The number of seconds that the End Point Operations Management agent startup script
waits before determining that the agent has not started up successfully. If the agent is found
to not be listening for requests within this period, an error is logged, and the startup script
times out.
n autoinventory.defaultScan.interval.millis Property
Specifies how frequently the End Point Operations Management agent performs a default
autoinventory scan.
n autoinventory.runtimeScan.interval.millis Property
Specifies how frequently an End Point Operations Management agent performs a runtime
scan.
n http.useragent Property
Defines the value for the user-agent request header in HTTP requests issued by the End
Point Operations Management agent.
n log4j Properties
The log4j properties for the End Point Operations Management agent are described here.
n platform.log_track.eventfmt Property
Specifies the content and format of the Windows event attributes that an End Point
Operations Management agent includes when logging a Windows event as an event in
n plugins.exclude Property
Specifies plug-ins that the End Point Operations Management agent does not load at
startup. This is useful for reducing an agent's memory footprint.
n plugins.include Property
Specifies plug-ins that the End Point Operations Management agent loads at startup. This is
useful for reducing the agent's memory footprint.
n postgresql.database.name.format Property
This property specifies the format of the name that the PostgreSQL plug-in assigns to auto-
discovered PostgreSQL Database and vPostgreSQL Database database types.
n postgresql.index.name.format Property
discovered PostgreSQL Index and vPostgreSQL Index index types.
n postgresql.server.name.format Property
discovered PostgreSQL and vPostgreSQL server types.
VMware, Inc. 260

n postgresql.table.name.format Property
discovered PostgreSQL Table and vPostgreSQL Table table types.
n scheduleThread.cancelTimeout Property
This property specifies the maximum time, in milliseconds, that the ScheduleThread allows a
metric collection process to run before attempting to interrupt it.
n scheduleThread.fetchLogTimeout Property
This property controls when a warning message is issued for a long-running metric
collection process.
n scheduleThread.poolsize Property
This property enables a plug-in to use multiple threads for metric collection. The property
can increase metric throughput for plug-ins known to be thread-safe.
n scheduleThread.queuesize Property
Use this property to limit the metric collection queue size (the number of metrics) for a plug-
in.
n sigar.mirror.procnet Property
mirror /proc/net/tcp on Linux.
n sigar.pdh.enableTranslation Property
Use this property to enable translation based on the detected locale of the operating
system.
n snmpTrapReceiver.listenAddress Property
Specifies the port on which the End Point Operations Management agent listens for SNMP
traps
agent.keystore.alias Property
This property configures the name of the user-managed keystore for the agent for agents
configured for unidirectional communication with the vRealize Operations Manager server.
Example: Defining the Name of a Keystore

Given this user-managed keystore for a unidirectional agent
hq self-signed cert), Jul 27, 2011, trustedCertEntry,

Certificate fingerprint (MD5): 98:FF:B8:3D:25:74:23:68:6A:CB:0B:9C:20:88:74:CE
hq-agent, Jul 27, 2011, PrivateKeyEntry,
Certificate fingerprint (MD5): 03:09:C4:BC:20:9E:9A:32:DC:B2:E8:29:C0:3C:FE:38
you define the name of the keystore like this
agent.keystore.alias=hq-agent
If the value of this property does not match the keystore name, agent-server communication
fails.
VMware, Inc. 261

Default
The default behavior of the agent is to look for the hq keystore.
For unidirectional agents with user-managed keystores, you must define the keystore name
using this property.
agent.keystore.password Property
This property configures the password for an End Point Operations Management agent's SSL
keystore.
Define the location of the keystore using the agent.keystore.path Property property.
By default, the first time you start the End Point Operations Management agent following
installation, if agent.keystore.password is uncommented and has a plain text value, the agent
automatically encrypts the property value. You can encrypt this property value yourself, prior to
starting the agent.
It is good practice to specify the same password for the agent keystore as for the agent private
key.
Default
By default, the agent.properties file does not include this property.

agent.keystore.path Property
This property configures the location of a End Point Operations Management agent's SSL
keystore.
Specify the full path to the keystore. Define the password for the keystore using the
agent.keystore.password property. See agent.keystore.password Property.
Specifying the Keystore Path on Windows
On Windows platforms, specify the path to the keystore in this format.
C:/Documents and Settings/Desktop/keystore
Default
AgentHome/data/keystore.
agent.listenPort Property
This property specifies the port where the End Point Operations Management agent listens to
receive communication from the vRealize Operations Manager server.
The property is not required for unidirectional communication.

agent.logDir Property
Point Operations Management agent writes its log file. If you do not specify a fully qualified path,
agent.logDir is evaluated relative to the agent installation directory.
To change the location for the agent log file, enter a path relative to the agent installation
directory, or a fully qualified path.
Note that the name of the agent log file is configured with the agent.logFile property.
VMware, Inc. 262

Default
The default behavior is agent.logDir=log, resulting in the agent log file being written to the
AgentHome/log directory.
agent.logFile Property
The path and name of the agent log file.
Default
In the agent.properties file, the default setting for the agent.LogFile property is made up of a
variable and a string
agent.logFile=${agent.logDir}\agent.log
where
n agent.logDir is a variable that supplies the value of an identically named agent property. By
default, the value of agent.logDir is log, interpreted relative to the agent installation directory.
n agent.log is the name for the agent log file.
By default, the agent log file is named agent.log, and is written to the AgentHome/log directory.
agent.logLevel Property
The level of detail of the messages the agent writes to the log file.
Permitted values are INFO and DEBUG.
Default
INFO
agent.logLevel.SystemErr Property
Redirects System.err to the agent.log file.
Commenting out this setting causes System.err to be directed to agent.log.startup.
Default
ERROR
agent.logLevel.SystemOut Property
Redirects System.out to the agent.log file.
Commenting out this setting causes System.out to be directed to agent.log.startup.
Default
INFO
agent.proxyHost Property
The host name or IP address of the proxy server that the End Point Operations Management
agent must connect to first when establishing a connection to the vRealize Operations Manager
server.
This property is supported for agents configured for unidirectional communication.
VMware, Inc. 263

Use this property in conjunction with agent.proxyPort and agent.setup.unidirectional.
Default
None
agent.proxyPort Property
The port number of the proxy server that the End Point Operations Management agent must
connect to first when establishing a connection to the vRealize Operations Manager server.
This property is supported for agents configured for unidirectional communication.
Use this property in conjunction with agent.proxyPort and agent.setup.unidirectional.
Default
None
agent.setup.acceptUnverifiedCertificate Property
This property controls whether an End Point Operations Management agent issues a warning
when the vRealize Operations Manager server presents an SSL certificate that is not in the
agent's keystore, and is either self-signed or signed by a different certificate authority than the
one that signed the agent's SSL certificate.
When the default is used, the agent issues the warning
The authenticity of host 'localhost' can't be established.

Are you sure you want to continue connecting? [default=no]:
If you respond yes, the agent imports the server's certificate and will continue to trust the
certificate from this point on.
Default
agent.setup.acceptUnverifiedCertificate=no
agent.setup.camIP Property
Use this property to define the IP address of the vRealize Operations Manager server for the
agent. The End Point Operations Management agent reads this value only in the event that it
cannot find connection configuration in its data directory.
You can specify this and other agent.setup.* properties to reduce the user interaction required to
configure an agent to communicate with the server.
The value can be provided as an IP address or a fully qualified domain name. To identify an
server on the same host as the server, set the value to 127.0.0.1.
If there is a firewall between the agent and server, specify the address of the firewall, and
configure the firewall to forward traffic on port 7080, or 7443 if you use the SSL port, to the
vRealize Operations Manager server.
Default
Commented out, localhost.

agent.setup.camLogin Property
VMware, Inc. 264

Management agent user name to use when the agent is registering itself with the server.
The permission required on the server for this initialization is Create, for platforms.
Log in from the agent to the server is only required during the initial configuration of the agent.
The agent reads this value only in the event that it cannot find connection configuration in its
data directory.
Default
Commented our hqadmin.

agent.setup.camPort Property
Management agent server port to use for non-secure communications with the server.
data directory.
Default
Commented out 7080.

agent.setup.camPword Property
Use this property to define the password that the End Point Operations Management agent uses
when connecting to the vRealize Operations Manager server, so that the agent does not prompt
a user to supply the password interactively at first startup.
The password for the user is that specified by agent.setup.camLogin.
data directory.
The first time you start the End Point Operations Management agent after installation, if
agent.keystore.password is uncommented and has a plain text value, the agent automatically
encrypts the property value. You can encrypt these property values prior to starting the agent.
Default
Commented our hqadmin.

agent.setup.camSecure
This property is used when you are registering the End Point Operations Management with the
vRealize Operations Manager server to communicate using encryption.
Use yes=secure, encrypted, or SSL, as appropriate, to encrypt communication.
VMware, Inc. 265

Use no=unencrypted for unencrypted communication.

agent.setup.camSSLPort Property
Management agent server port to use for SSL communications with the server.
data directory.
Default
Commented out 7443.

agent.setup.resetupToken Property
Use this property to configure an End Point Operations Management agent to create a new
token to use for authentication with the server at startup. Regenerating a token is useful if the
agent cannot connect to the server because the token has been deleted or corrupted.
data directory.
Regardless of the value of this property, an agent generates a token the first time it is started
after installation.
Default
Commented out no.

agent.setup.unidirectional Property
Enables unidirectional communications between the End Point Operations Management agent
and vRealize Operations Manager server.
If you configure an agent for unidirectional communication, all communication with the server is
initiated by the agent.
For a unidirectional agent with a user-managed keystore, you must configure the keystore name
in the agent.properties file.
Default
Commented out no.

agent.startupTimeOut Property
The number of seconds that the End Point Operations Management agent startup script waits
before determining that the agent has not started up successfully. If the agent is found to not be
listening for requests within this period, an error is logged, and the startup script times out.
Default
The default behavior of the agent is to timeout after 300 seconds.

autoinventory.defaultScan.interval.millis Property
VMware, Inc. 266

Specifies how frequently the End Point Operations Management agent performs a default
autoinventory scan.
The default scan detects server and platform services objects, typically using the process table
or the Windows registry. Default scans are less resource-intensive than runtime scans.
Default
The agent performs the default scan at startup and every 15 minutes thereafter.
Commented out 86,400,000 milliseconds, or one day.

autoinventory.runtimeScan.interval.millis Property
Specifies how frequently an End Point Operations Management agent performs a runtime scan.
A runtime scan may use more resource-intensive methods to detect services than a default scan.
For example, a runtime scan might involve issuing an SQL query or looking up an MBean.
Default
86,400,000 milliseconds, or one day.

http.useragent Property
Defines the value for the user-agent request header in HTTP requests issued by the End Point
Operations Management agent.
You can use http.useragent to define a user-agent value that is consistent across upgrades.
Default
By default, the user-agent in agent requests includes the End Point Operations Management
agent version, so changes when the agent is upgraded. If a target HTTP server is configured to
block requests with an unknown user-agent, agent requests fail after an agent upgrade.
Hyperic-HQ-Agent/Version, for example, Hyperic-HQ-Agent/4.1.2-EE.

log4j Properties
The log4j properties for the End Point Operations Management agent are described here.
log4j.rootLogger=${agent.logLevel}, R
log4j.appender.R.File=${agent.logFile}
log4j.appender.R.MaxBackupIndex=1
log4j.appender.R.MaxFileSize=5000KB
log4j.appender.R.layout.ConversionPattern=%d{dd-MM-yyyy HH:mm:ss,SSS z} %-5p [%t] [%c{1}@%L] %m%n
log4j.appender.R.layout=org.apache.log4j.PatternLayout
log4j.appender.R=org.apache.log4j.RollingFileAppender
##
## Disable overly verbose logging
##
log4j.logger.org.apache.http=ERROR
log4j.logger.org.springframework.web.client.RestTemplate=ERROR
log4j.logger.org.hyperic.hq.measurement.agent.server.SenderThread=INFO
log4j.logger.org.hyperic.hq.agent.server.AgentDListProvider=INFO
log4j.logger.org.hyperic.hq.agent.server.MeasurementSchedule=INFO
VMware, Inc. 267

log4j.logger.org.hyperic.util.units=INFO
log4j.logger.org.hyperic.hq.product.pluginxml=INFO
# Only log errors from naming context

log4j.category.org.jnp.interfaces.NamingContext=ERROR
log4j.category.org.apache.axis=ERROR
#Agent Subsystems: Uncomment individual subsystems to see debug messages.

#-----------------------------------------------------------------------
#log4j.logger.org.hyperic.hq.autoinventory=DEBUG
#log4j.logger.org.hyperic.hq.livedata=DEBUG
#log4j.logger.org.hyperic.hq.measurement=DEBUG
#log4j.logger.org.hyperic.hq.control=DEBUG
#Agent Plugin Implementations

#log4j.logger.org.hyperic.hq.product=DEBUG
#Server Communication
#log4j.logger.org.hyperic.hq.bizapp.client.AgentCallbackClient=DEBUG
#Server Realtime commands dispatcher

#log4j.logger.org.hyperic.hq.agent.server.CommandDispatcher=DEBUG
#Agent Configuration parser

#log4j.logger.org.hyperic.hq.agent.AgentConfig=DEBUG
#Agent plugins loader

#log4j.logger.org.hyperic.util.PluginLoader=DEBUG
#Agent Metrics Scheduler (Scheduling tasks definitions & executions)

#log4j.logger.org.hyperic.hq.agent.server.session.AgentSynchronizer.SchedulerThread=DEBUG
#Agent Plugin Managers

#log4j.logger.org.hyperic.hq.product.MeasurementPluginManager=DEBUG
#log4j.logger.org.hyperic.hq.product.AutoinventoryPluginManager=DEBUG
#log4j.logger.org.hyperic.hq.product.ConfigTrackPluginManager=DEBUG
#log4j.logger.org.hyperic.hq.product.LogTrackPluginManager=DEBUG
#log4j.logger.org.hyperic.hq.product.LiveDataPluginManager=DEBUG
#log4j.logger.org.hyperic.hq.product.ControlPluginManager=DEBUG
platform.log_track.eventfmt Property
Specifies the content and format of the Windows event attributes that an End Point Operations
Management agent includes when logging a Windows event as an event in vRealize Operations
Manager.
Default
When Windows log tracking is enabled, an entry in the form [Timestamp] Log Message
(EventLogName):EventLogName:EventAttributes is logged for events that match the criteria you
specified on the resource's Configuration Properties page.
VMware, Inc. 268

Attribute Description
Timestamp When the event occurred
Log Message A text string
EventLogName The Windows event log type System, Security, or Application
EventAttributes A colon delimited string made of the Windows event Source and Message attributes
For example, the log entry: 04/19/2010 06:06 AM Log Message (SYSTEM): SYSTEM: Print: Printer HP
LaserJet 6P was paused. is for a Windows event written to the Windows System event log at 6:06
AM on 04/19/2010. The Windows event Source and Message attributes, are "Print" and "Printer
HP LaserJet 6P was paused.", respectively.
Configuration
Use the following parameters to configure the Windows event attributes that the agent writes for
a Windows event. Each parameter maps to Windows event attribute of the same name.
Parameter Description
%user% The name of the user on whose behalf the event occurred.
%computer% The name of the computer on which the event occurred.
%source% The software that logged the Windows event.
%event% A number identifying the particular event type.
%message% The event message.
%category% An application-specific value used for grouping events.
For example, with the property setting platform.log_track.eventfmt=%user%@%computer% %source

%:%event%:%message%, the End Point Operations Management agent writes the following data when
logging the Windows event 04/19/2010 06:06 AM Log Message (SYSTEM): SYSTEM:
HP_Admistrator@Office Print:7:Printer HP LaserJet 6P was paused.. This entry is for a Windows
event written to the Windows system event log at 6:06 AM on 04/19/2010. The software
associated with the event was running as "HP_Administrator" on the host "Office". The Windows
event's Source, Event, and Message attributes, are "Print", "7", and "Printer HP LaserJet 6P was
paused.", respectively.
plugins.exclude Property
Specifies plug-ins that the End Point Operations Management agent does not load at startup.
This is useful for reducing an agent's memory footprint.
Usage
Supply a comma-separated list of plug-ins to exclude. For example,
plugins.exclude=jboss,apache,mysql
plugins.include Property
Specifies plug-ins that the End Point Operations Management agent loads at startup. This is
useful for reducing the agent's memory footprint.
VMware, Inc. 269

Usage
Supply a comma-separated list of plug-ins to include. For example,
plugins.include=weblogic,apache
postgresql.database.name.format Property
discovered PostgreSQL Database and vPostgreSQL Database database types.
By default, the name of a PostgreSQL or vPostgreSQL database is Database DatabaseName, where

DatabaseName is the auto-discovered name of the database.
To use a different naming convention, define postgresql.database.name.format. The variable data

you use must be available from the PostgreSQL plug-in.
Use the following syntax to specify the default table name assigned by the plug-in,
Database ${db}
where
postgresql.db is the auto-discovered name of the PostgreSQL or vPostgreSQL database.
Default

postgresql.index.name.format Property
discovered PostgreSQL Index and vPostgreSQL Index index types.
By default, the name of a PostgreSQL or vPostgreSQL index is Index DatabaseName.Schema.Index,

comprising the following variables
Variable Description
DatabaseName The auto-discovered name of the database.
Schema The auto-discovered schema for the database.
Index The auto-discovered name of the index.
To use a different naming convention, define postgresql.index.name.format. The variable data you
use must be available from the PostgreSQL plug-in.
Use the following syntax to specify the default index name assigned by the plug-in,
Index ${db}.${schema}.${index}
where
VMware, Inc. 270

db Identifies the platform that hosts the PostgreSQL or vPostgreSQL server.
schema Identifies the schema associated with the table.
index The index name in PostgreSQL.
Default

postgresql.server.name.format Property
discovered PostgreSQL and vPostgreSQL server types.
By default, the name of a PostgreSQL or vPostgreSQL server is Host:Port, comprising the

following variables
Host The FQDN of the platform that hosts the server.
Port The PostgreSQL listen port.
To use a different naming convention, define postgresql.server.name.format. The variable data

you use must be available from the PostgreSQL plug-in.
Use the following syntax to specify the default server name assigned by the plug-in,
${postgresql.host}:${postgresql.port}
where
postgresql.host Identifies the FQDN of the hosting platform.
postgresql.port Identifies the database listen port.
Default

postgresql.table.name.format Property
discovered PostgreSQL Table and vPostgreSQL Table table types.
By default, the name of a PostgreSQL or vPostgreSQL table is Table DatabaseName.Schema.Table,

comprising the following variables
DatabaseName The auto-discovered name of the database.
Schema The auto-discovered schema for the database.
Table The auto-discovered name of the table.
VMware, Inc. 271

To use a different naming convention, define postgresql.table.name.format. The variable data you
use must be available from the PostgreSQL plug-in.
Use the following syntax to specify the default table name assigned by the plug-in,
Table ${db}.${schema}.${table}
where
db Identifies the platform that hosts the PostgreSQL or vPostgreSQL server.
schema Identifies the schema associated with the table.
table The table name in PostgreSQL.
Default

scheduleThread.cancelTimeout Property
This property specifies the maximum time, in milliseconds, that the ScheduleThread allows a metric
collection process to run before attempting to interrupt it.
When the timeout is exceeded, collection of the metric is interrupted, if it is in a wait(), sleep() or
non-blocking read() state.
Usage
scheduleThread.cancelTimeout=5000
Default
5000 milliseconds.
scheduleThread.fetchLogTimeout Property
This property controls when a warning message is issued for a long-running metric collection
process.
If a metric collection process exceeds the value of this property, which is measured in
milliseconds, the agent writes a warning message to the agent.log file.
Usage
scheduleThread.fetchLogTimeout=2000
Default
2000 milliseconds.
scheduleThread.poolsize Property
This property enables a plug-in to use multiple threads for metric collection. The property can
increase metric throughput for plug-ins known to be thread-safe.
Usage
Specify the plug-in by name and the number of threads to allocate for metric collection
scheduleThread.poolsize.PluginName=2
VMware, Inc. 272

where PluginName is the name of the plug-in to which you are allocating threads. For example,
scheduleThread.poolsize.vsphere=2
Default
1
scheduleThread.queuesize Property
Use this property to limit the metric collection queue size (the number of metrics) for a plug-in.
Usage
Specify the plug-in by name and the maximum metric queue length number:
scheduleThread.queuesize.PluginName=15000
where PluginName is the name of the plug-in on which you are imposing a metric limit.
For example,
scheduleThread.queuesize.vsphere=15000
Default
1000
sigar.mirror.procnet Property
mirror /proc/net/tcp on Linux.
Default
true
sigar.pdh.enableTranslation Property
Use this property to enable translation based on the detected locale of the operating system.
snmpTrapReceiver.listenAddress Property
Specifies the port on which the End Point Operations Management agent listens for SNMP traps
Typically SNMP uses the UDP port 162 for trap messages. This port is in the privileged range, so
an agent listening for trap messages on it must run as root, or as an administrative user on
Windows.
You can run the agent in the context of a non-administrative user, by configuring the agent to
listen for trap messages on an unprivileged port.
Usage
Specify an IP address (or 0.0.0.0 to specify all interfaces on the platform) and the port for UDP
communications in the format
snmpTrapReceiver.listenAddress=udp:IP_address/port
VMware, Inc. 273

To enable the End Point Operations Management agent to receive SNMP traps on an
unprivileged port, specify port 1024 or higher. The following setting allows the agent to receive
traps on any interface on the platform, on UDP port 1620.
snmpTrapReceiver.listenAddress=udp:0.0.0.0/1620
Managing Agent Registration on vRealize Operations Manager Servers

The End Point Operations Management agents identify themselves to the server using client
certificates. The agent registration process generates the client certificate.
The client certificate includes a token that is used as the unique identifier. If you suspect that a
client certificate was stolen or compromised, you must replace the certificate.
You must have AgentManager credentials to perform the agent registration process. On a freshly
deployed instance of vRealize Operations Manager, before you register the End Point Operations
Management agent, you must also manually activate the management pack from Administration
> Solutions > Repository > Operating Systems/Remote Service Monitoring.
If you remove and reinstall an agent by removing the data directory, the agent token is retained
to enable data continuity. See Understanding Agent Uninstallation and Reinstallation Implications.
Regenerate an Agent Client Certificate
An End Point Operations Management agent client certificate might expire and need to be
replaced. For example, you might replace a certificate that you suspected was corrupt or
compromised.
Prerequisites
Verify that you have sufficient privileges to deploy an End Point Operations Management agent.
You must have vRealize Operations Manager user credentials that include a role that allows you
to install End Point Operations Management agents. See Roles and Privileges in vRealize
Operations Manager.
Procedure
u Start the registration process by running the setup command that is appropriate for the
operating system on which the agent is running.
Operating System Run Command
Linux ep-agent.sh setup
Windows ep-agent.bat setup
Results
The agent installer runs the setup, requests a new certificate from the server, and imports the
new certificate to the keystore.
VMware, Inc. 274

Securing Communications with the Server

Communication from an End Point Operations Management agent to the vRealize Operations
Manager server is unidirectional, however both parties must be authenticated. Communication is
always secured using transport layer security (TLS).
The first time an agent initiates a connection to the vRealize Operations Manager server following
installation, the server presents its SSL certificate to the agent.
If the agent trusts the certificate that the server presented, the agent imports the server's
certificate to its own keystore.
The agent trusts a server certificate if that certificate, or one of its issuers (CA) already exists in
the agent's keystore.
By default, if the agent does not trust the certificate that the server presents, the agent issues a
warning. You can choose to trust the certificate, or to terminate the configuration process. The
vRealize Operations Manager server and the agent do not import untrusted certificates unless
you respond yes to the warning prompt.
You can configure the agent to accept a specific thumb print without warning by specifying the
thumb print of the certificate for the vRealize Operations Manager server.
By default, the vRealize Operations Manager server generates a self-signed CA certificate that is
used to sign the certificate of all the nodes in the cluster. In this case, the thumbprint must be the
thumbprint of the issuer, to allow for the agent to communicate with all nodes.
As a vRealize Operations Manager administrator, you can import a custom certificate instead of
using the default. In this instance, you must specify a thumbprint corresponding to that certificate
as the value of this property.
Either the SHA1 or SHA256 algorithm can be used for the thumbprint.
Launching Agents from a Command Line

You can launch agents from a command line on both Linux and Windows operating systems.
Use the appropriate process for your operating system.
If you are deleting the data directory, do not use Windows Services to stop and start an End
Point Operations Management agent. Stop the agent using epops-agent.bat stop. Delete the data
directory, then start the agent using epops-agent.bat start.
Run the Agent Launcher from a Linux Command Line
You can initiate the agent launcher and agent lifecycle commands with the epops-agent.sh script
in the AgentHome/bin directory.
Procedure
1 Open a command shell or terminal window.
VMware, Inc. 275

2 Enter the required command, using the format sh epops-agent.sh command, where command is
one of the following.
Option Description
start Starts the agent as a daemon process.
stop Stops the agent's JVM process.
restart Stops and then starts the agent's JVM process.
status Queries the status of the agent's JVM process.
dump Runs a thread dump for the agent process, and writes the result to the
agent.log file in AgentHome/log.
ping Pings the agent process.
setup Re-registers the certificate using the existing token.
Run the Agent Launcher from a Windows Command Line

You can initiate the agent launcher and agent lifecycle commands with the epops-agent.bat script
in the AgentHome/bin directory.
Procedure
1 Open a terminal window.
2 Enter the required command, using the format epops-agent.bat command, where command is one
of the following.
Option Description
install Installs the agent NT service. You must run start after running install.
start Starts the agent as an NT service.
stop Stops the agent as an NT service.
remove Removes the agent's service from the NT service table.
query Queries the current status of the agent NT service (status).
dump Runs a thread dump for the agent process, and writes the result to the
agent.log file in AgentHome/log.
ping Pings the agent process.
setup Re-registers the certificate using the existing token.
Managing an End Point Operations Management Agent on a Cloned Virtual Machine

When you clone a virtual machine that is running an End Point Operations Management agent
that is collecting data, there are processes that you must complete related to data continuity to
ensure data continuity.
VMware, Inc. 276

Cloning a Virtual Machine to Delete the Original Virtual Machine

If you are cloning the virtual machine so that you can delete the original virtual machine, you
need to verify that the original machine is deleted from thevCenter Server and from vRealize
Operations Manager so that the new operating system to virtual machine relationship can be
created.
Cloning a Virtual Machine to Run Independently of the Original Machine
If you are cloning the virtual machine so that you can run the two machines independently of the
other, the cloned machine requires a new agent because an agent can only monitor a single
machine.
Procedure
u On the cloned machine, delete the End Point Operations Management token and the data
folder, according to the operating system of the machine.
Operating System Process
Linux Stop the End Point Operations Management services and

delete the End Point Operations Management token and
the data folder.
Windows 1 Run epops-agent remove.

2 Remove the agent token and the data folder.
3 Run epops-agent install.
4 Run epops-agent start.
Moving Virtual Machines between vCenter Server Instances

When you move a virtual machine from one vCenter Server to another, vRealize Operations
Manager preserves the unique object ID, identifiers, and historical data without creating any
duplicate resources. This enables the new operating system to create a relationship with the
migrated virtual machine.
Understanding Agent Uninstallation and Reinstallation Implications

When you uninstall or reinstall an End Point Operations Management agent, various elements are
affected, including existing metrics that the agent has collected, and the identification token that
enables a reinstalled agent to report on the previously discovered objects on the server. To
ensure that you maintain data continuity, it is important that you aware of the implications of
uninstalling and reinstalling an agent.
There are two key locations related to the agent that are preserved when you uninstall an agent.
Before reinstalling the agent, you must decide whether to retain or delete the files.
n The /data folder is created during agent installation. It contains the keystore, unless you
chose a different location for it, and other data related to the currently installed agent.
n The epops-token platform token file is created before agent registration and is stored as
follows:
n Linux: /etc/vmware/epops-token
VMware, Inc. 277

n Windows: %PROGRAMDATA%/VMware/EP Ops Agent/epops-token
When you uninstall an agent, you must delete the /data folder. This does not affect data
continuity.
However, to enable data continuity it is important that you do not delete the epops-token file.
This file contains the identity token for the platform object. Following agent reinstallation, the
token enables the agent to be synchronized with the previously discovered objects on the
server.
When you reinstall the agent, the system notifies you whether it found an existing token, and
provides its identifier. If a token is found, the system uses that token. If a token in not found, the
system creates a new one. In the case of an error, the system prompts you to provide either a
location and file name for the existing token file, or a location and file name for a new one.
The method that you use to uninstall an agent depends on how it was installed.
n Uninstall an Agent that was Installed from an Archive

You can use this procedure to uninstall agents that you installed on virtual machines in your
environment from an archive.
n Uninstall an Agent that was Installed Using an RPM Package

environment using an RPM package.
n Uninstall an Agent that was Installed Using a Windows Executable

environment from a Windows EXE file.
n Reinstall an Agent
If you change the IP address, hostname or port number of the vRealize Operations Manager
server, you need to uninstall and reinstall your agents.
Uninstall an Agent that was Installed from an Archive

environment from an archive.
Prerequisites
Verify that the agent is stopped.
Procedure
1 (Optional) If you have a Windows operating system, run ep-agent.bat remove to remove the
agent service.
2 Select the uninstall option that is appropriate to your situation.
n If you do not intend to reinstall the agent after you have uninstalled it, delete the agent
directory.
The default name of the directory is epops-agent-version.
VMware, Inc. 278

n If you are reinstalling the agent after you have uninstalled it, delete the /data directory.
3 (Optional) If you do not intend to reinstall the agent after you have uninstalled it, or you do
not need to maintain data continuity, delete the epops-token platform token file.
Depending on your operating system, the file to delete is one of the following, unless
otherwise defined in the properties file.
n Linux: /etc/epops/epops-token
n Windows: %PROGRAMDATA%/VMware/EP Ops Agent/epops-token

Uninstall an Agent that was Installed Using an RPM Package
environment using an RPM package.
When you are uninstalling an End Point Operations Management agent, it is good practice to
stop the agent running, to reduce unnecessary load on the server.
Procedure
u On the virtual machine from which you are removing the agent, open a command line and run
rpm -e epops-agent.
Results
The agent is uninstalled from the virtual machine.

Uninstall an Agent that was Installed Using a Windows Executable
environment from a Windows EXE file.
When you are uninstalling an End Point Operations Management agent, it is good practice to
stop the agent running, to reduce unnecessary load on the server.
Procedure
u Double-click unins000.exe in the installation destination directory for the agent.
Results
The agent is uninstalled from the virtual machine.

Reinstall an Agent
If you change the IP address, hostname or port number of the vRealize Operations Manager
server, you need to uninstall and reinstall your agents.
Prerequisites
To maintain data continuity, you must have retained the epops-token platform token file when you
uninstalled your agent. See Uninstall an Agent that was Installed from an Archive.
When you reinstall an End Point Operations Management agent on a virtual machine, objects that
had previously been detected are no longer monitored. To avoid this situation, do not restart the
End Point Operations Management agent until the plug-in synchronization is complete.
VMware, Inc. 279

Procedure
u Run the agent install procedure that is relevant to your operating system.
See Selecting an Agent Installer Package.
What to do next
After you reinstall an agent, MSSQL resources might stop receiving data. If this happens, edit the
problematic resources and click OK.
Install Multiple End Point Operations Management Agents Simultaneously

If you have multiple End Point Operations Management agents to install at one time, you can
create a single standardized agent.properties file that all the agents can use.
Installing multiple agents entails a number of steps. Perform the steps in the order listed.
Prerequisites
Verify that the following prerequisites are satisfied.
1 Set up an installation server.
An installation server is a server that can access the target platforms from which to perform
remote installation.
The server must be configured with a user account that has permissions to SSH to each
target platform without requiring a password.
2 Verify that each target platform on which an End Point Operations Management agent will be
installed has the following items.
n A user account that is identical to that created on the installation server.
n An identically named installation directory, for example /home/epomagent.
n A trusted keystore, if required.
Procedure
1 Create a Standard End Point Operations Management Agent Properties File

You can create a single properties file that contains property values that multiple agents
use.
2 Deploy and Start Multiple Agents One-By-One

You can perform remote installations to deploy multiple agents that use a single
agent.properties file one-by-one.
3 Deploy and Start Multiple Agents Simultaneously

You can perform remote installations to simultaneously deploy agents that use a single
Create a Standard End Point Operations Management Agent Properties File

You can create a single properties file that contains property values that multiple agents use.
VMware, Inc. 280

To enable multiple agent deployment, you create an agent.properties file that defines the
agent properties required for the agent to start up and connect with the vRealize Operations
Manager server. If you supply the necessary information in the properties file, each agent locates
its setup configuration at startup, rather than prompting you for the location. You can copy the
agent properties file to the agent installation directory, or to a location available to the installed
agent.
Prerequisites
Verify that the prerequisites in Install Multiple End Point Operations Management Agents
Simultaneously are satisfied.
Procedure
1 Create an agent.properties file in a directory.
You will copy this file later to other machines.
2 Configure the properties as required.
The minimum configuration is the IP address, user name, password, thumb print, and port of
the vRealize Operations Manager installation server.
3 Save your configurations.
Results
The first time that the agents are started, they read the agent.properties file to identify the
server connection information. The agents connect to the server and register themselves.
What to do next
Perform remote agent installations. See Deploy and Start Multiple Agents One-By-One or Deploy
and Start Multiple Agents Simultaneously.
Deploy and Start Multiple Agents One-By-One
You can perform remote installations to deploy multiple agents that use a single
agent.properties file one-by-one.
Prerequisites
n Verify that the prerequisites in Install Multiple End Point Operations Management Agents
n Verify that you configured a standard agent properties file and copied it to the agent
installation, or to a location available to the agent installation.
Procedure
1 Log in to the installation server user account that you configured with permissions to use SSH
to connect to each target platform without requiring a password.
2 Use SSH to connect to the remote platform.
VMware, Inc. 281

3 Copy the agent archive to the agent host.
4 Unpack the agent archive.
5 Copy the agent.properties file to the AgentHome/conf directory of the unpacked agent
archive on the remote platform.
6 Start the new agent.
Results
The agent registers with the vRealize Operations Manager server and the agent runs an
autodiscovery scan to discover its host platform and supported managed products that are
running on the platform.
Deploy and Start Multiple Agents Simultaneously
You can perform remote installations to simultaneously deploy agents that use a single
Prerequisites
n Verify that the prerequisites in Install Multiple End Point Operations Management Agents
n Verify that you configured a standard agent properties file and copied it to the agent
installation, or to a location available to the agent installation. See Create a Standard End
Point Operations Management Agent Properties File.
Procedure
1 Create a hosts.txt file on your installation server that maps the hostname to the IP address
of each platform on which you are installing an agent.
2 Open a command-line shell on the installation server.
3 Type the following command in the shell, supplying the correct name for the agent package
in the export command.
$ export AGENT=epops-agent-x86-64-linux-1.0.0.tar.gz
$ export PATH_TO_AGENT_INSTALL=</path/to/agent/install>
$ for host in `cat hosts.txt`; do scp $AGENT $host:$PATH_TO_AGENT_INSTALL && ssh $host "cd
$PATH_TO_AGENT_INSTALL; tar zxfp $AGENT &&
./epops-agent-1.0.0/ep-agent.sh start"; done
4 (Optional) If the target hosts have sequential names, for example host001, host002, host003,
and so on, you can skip the hosts.txt file and use the seq command.
$ export AGENT=epops-agent-x86-64-linux-1.0.0.tar.gz
$ for i in `seq 1 9`; do scp $AGENT host$i: && ssh host$i "tar zxfp $AGENT &&
./epops-agent-1.0.0/ep-agent.sh start"; done
VMware, Inc. 282

Results
The agents register with the vRealize Operations Manager server and the agents run an
autodiscovery scan to discover their host platform and supported managed products that are
running on the platform.
Upgrade the End Point Operations Management Agent

You can upgrade the 6.3 or 6.4 version of an End Point Operations Management agent to a 6.5
version or later, from the vRealize Operations Manager administration interface.
Prerequisites
n Download the End Point Operations Management PAK file.
the-box content.
Procedure
1 Log into the vRealize Operations Manager administration interface of your cluster at
https://IP-address/admin.
2 Click Software Update in the left panel.
3 Click Install a Software Update in the main panel.
4 From the Add Software Update dialog box, click Browse to select the PAK file.
5 Click Upload and follow the steps in the wizard to install your PAK file.
6 After Step 4 of the install is complete, you return to the Software Update page of the End
Point Operations Management administration interface.
7 A message that indicates that the software update completed successfully appears in the
main pane.
If any of the agents have not installed successfully, rerun the upgrade steps and ensure that
you have selected Install the PAK file even if it is already installed in the Add Software
Update - Select Software Update page.
What to do next
You can view the log files from the vRealize Operations Manager administration interface >
Support page.
Access and View the Log Files
You can access and view the log files to troubleshoot agent upgrade failure. You can verify the
status of the agents during and after the upgrade process to find out if the agents have
upgraded successfully.
VMware, Inc. 283

You can view the status of the agents during the upgrade from the epops-agent-upgrade-
status.txt file. You can view a final report of the number of agents that have successfully
upgraded or failed upgrade from the epops-agent-bundle-upgrade-summary.txt file.
Procedure
1 Log into the vRealize Operations Manager administration interface of your cluster at
https://IP-address/admin.
2 Click Support in the left panel.
3 Click the Logs tab in the right pane and double-click EPOPS.
4 Double-click the log file to view the contents.
Roles and Privileges in vRealize Operations Manager

vRealize Operations Manager provides several predefined roles to assign privileges to users. You
can also create your own roles.
You must have privileges to access specific features in the vRealize Operations Manager user
interface. The roles associated with your user account determine the features you can access
and the actions you can perform.
Each predefined role includes a set of privileges for users to perform, create, read, update, or
delete actions on components such as dashboards, reports, administration, capacity, policies,
problems, symptoms, alerts, user account management, and adapters. For information about
roles and associated permissions, see KB 59484.
Administrator
Includes privileges to all features, objects, and actions in vRealize Operations Manager.
PowerUser
Users have privileges to perform the actions of the Administrator role except for privileges to
user management and cluster management. vRealize Operations Manager maps vCenter
Server users to this role.
PowerUserMinusRemediation
user management, cluster management, and remediation actions.
ContentAdmin
Users can manage all content, including views, reports, dashboards, and custom groups in
AgentManager
Users can deploy and configure End Point Operations Management agents.
GeneralUser-1 through GeneralUser-4
VMware, Inc. 284

These predefined template roles are initially defined as ReadOnly roles. vCenter Server
administrators can configure these roles to create combinations of roles to give users
multiple types of privileges. Roles are synchronized to vCenter Server once during
registration.
ReadOnly
Users have read-only access and can perform read operations, but cannot perform write
actions such as create, update, or delete.
Registering Agents on Clusters

You can streamline the process of registering agents on clusters by defining a DNS name for a
cluster and configuring that cluster so that the metrics are shared sequentially in a loop.
You only need to register the agent on the DNS, not on the IP address of each individual machine
in the cluster. If you do register the agent on each node in the cluster, it affects the scale of your
environment.
When you have configured the cluster so that the received metrics are shared in a sequential
loop, each time that the agent queries the DNS server for an IP address, the returned address is
for one of the virtual machines in the cluster. The next time the agent queries the DNS, it
sequentially supplies the IP address of the next virtual machine in the cluster, and so on. The
clustered machines are set up in a loop configuration so that each machine receives metrics in
turn, ensuring a balanced load.
After you configure the DNS, it is important to maintain it, ensuring that when machines are
added or removed from the cluster, their IP address information is updated accordingly.
Manually Create Operating System Objects

The agent discovers some of the objects to monitor. You can manually add other objects, such as
files, scripts or processes, and specify the details so that the agent can monitor them.
The Monitor OS Object action only appears in the Actions menu of an object that can be a
parent object.
Procedure
1 In the left pane of vRealize Operations Manager, select the agent adapter object that is to be
the parent under which you are creating an OS object.
2 Select Actions > Monitor OS Object.
A list of parent object context-sensitive objects appear in the menu.
3 Choose one of the following options.
n Click an object type from the list to open the Monitor OS Object dialog box for that object
type.
The three most popularly selected object types appear in the list.
VMware, Inc. 285

n If the object type that you want to select is not in the list, click More to open the Monitor
OS Object dialog box. Select the object type from the complete list of objects that are
available for selection in the Object Type menu.
4 Specify a display name for the OS object.
5 Enter the appropriate values in the other text boxes.
The options in the menu are filtered according to the OS object type that you select.
Some text boxes might display default values, which you can overwrite if necessary. Note the
following information about default values.
Option Value
Process Supply the PTQL query in the form: Class.Attribute.operator=value.

For example, Pid.PidFile.eq=/var/run/sshd.pid.
Where:
n Class is the name of the Sigar class without the Proc prefix.
n Attribute is an attribute of the given Class, index into an array or key in a Map class.
n operator is one of the following (for String values):
n eq Equal to value
n ne Not Equal to value
n ew Ends with value
n sw Starts with value
n ct Contains value (substring)
n re Regular expression value matches
Delimit queries with a comma.
Windows Monitor an application that runs as a service under Windows.

Service To configure it, you supply its Service Name in Windows.
To determine the Service Name:
1 Select Run from the Windows Start menu.
2 Type services.msc in the run dialog box and click OK.
3 In the list of services displayed, right-click the service to monitor and choose Properties.
4 Locate the Service Name on the General tab.
Script Configure vRealize Operations Manager to periodically run a script that collects a system or
application metric.
6 Click OK.
You cannot click OK until you enter values for all the mandatory text boxes.
Results
The OS object appears under its parent object and monitoring begins.
Caution If you enter invalid details when you create an OS object, the object is created but the
agent cannot discover it, and metrics are not collected.
VMware, Inc. 286

Managing Objects with Missing Configuration Parameters

Sometimes when an object is discovered by vRealize Operations Manager for the first time, the
absence of values for some mandatory configuration parameters is detected. You can edit the
object's parameters to supply the missing values.
If you select Custom Groups > Objects with Missing Configuration (EP Ops) in the Environment
Overview view of vRealize Operations Manager, you can see the list of all objects that have
missing mandatory configuration parameters. In addition, objects with such missing parameters
return an error in the Collection Status data.
If you select an object in the vRealize Operations Manager user interface that has missing
configuration parameters, the red Missing Configuration State icon appears on the menu bar.
When you point to the icon, details about the specific issue appear.
You can add the missing parameter values through the Action > Edit Object menu.
Mapping Virtual Machines to Operating Systems

You can map your virtual machines to an operating system to provide additional information to
assist you to determine the root cause of why an alert was triggered for a virtual machine.
vRealize Operations Manager monitors your ESXi hosts and the virtual machines located on them.
When you deploy an End Point Operations Management agent, it discovers the virtual machines
and the objects that are running on them. By correlating the virtual machines discovered by the
End Point Operations Management agent with the operating systems monitored by vRealize
Operations Manager you have more details to determine the exact cause of an alert being
triggered.
Verify that you have the vCenter Adapter configured with the vCenter Server that manages the
virtual machines. You also need to ensure that you have VMware Tools that are compatible with
the vCenter Server installed on each of the virtual machines.
User Scenario
vRealize Operations Manager is running but you have not yet deployed the End Point Operations
Management agent in your environment. You configured vRealize Operations Manager to send
you alerts when CPU problems occur. You see an alert on your dashboard because insufficient
CPU capacity is available on one of your virtual machines that is running a Linux operating
system. You deploy another two virtual CPUs but the alert remains. You struggle to determine
what is causing the problem.
In the same situation, if you deployed the End Point Operations Management agent, you can see
the objects on your virtual machines, and determine that an application-type object is using all
available CPU capacity. When you add more CPU capacity, it also uses that. You disable the
object and your CPU availability is no longer a problem.
Viewing Objects on Virtual Machines

After you deploy an End Point Operations Management agent on a virtual machine, the machine
is mapped to the operating system and you can see the objects on that machine.
VMware, Inc. 287

All the actions and the views that are available to other objects in your vRealize Operations
Manager environment are also available for newly discovered server, service, and application
objects, and for the deployed agent.
You can see the objects on a virtual machine in the inventory when you select the machine by
clicking Environment from the menu, and then from the left pane click vSphere Environment >
vSphere Hosts and Clusters. You can see the objects and the deployed agent under the
operating system.
When you select an object, the center pane of the user interface displays data relevant to that
objects.
Customizing How End Point Operations Management Monitors Operating

Systems
End Point Operations Management gathers operating system metrics through agent-based
collections. In addition to the features available after initial configuration of End Point Operations
Management, you can enable remote monitoring, enable or disable plug-ins for additional
monitoring, and customize End Point Operations Management logging.
Configuring Remote Monitoring

With remote monitoring you can monitor the state of an object from a remote location by
configuring a remote check.
You can configure remote monitoring using HTTP, ICMP TCP methods.
When you configure a remote HTTP, ICMP or TCP check, it is created as a child object of the
tested object that you are monitoring and of the monitoring agent.
If the object that you select to remotely monitor does not already have an alert configured, one
is created automatically in the format Remote check type failed on a object type. If the object
has an existing alert, that is used.
Configure Remote Monitoring of an Object
Use this procedure to configure remote monitoring of an object.
Configuration options are defined in HTTP Configuration Options, ICMP Configuration Optionsand
TCP Configuration Options. You might need to refer to this information when you are completing
this procedure.
Procedure
1 In the vRealize Operations Manager user interface, select the remote object to monitor.
2 On the details page for the object, select Monitor this Object Remotely from the Actions
menu.
3 In the Monitor Remote Object dialog, select the End Point Operations Management agent that
will remotely monitor the object from the Monitored From menu.
VMware, Inc. 288

4 Select the method with which the remote object will be monitored from the Check Method
menu.
The relevant parameters for the selected object type appear.
5 Enter values for all of the configuration options and click OK.
HTTP Configuration Options

Here are the options in the configuration schema for the HTTP resource.
For the HTTP resource, the netservices plug-in descriptor default values are:
n port: 80
n sslport: 443
HTTP Configuration Options
Table 4-40. ssl Option

Option Information Value
Description Use ssl
Default false
Optional true
Type boolean
Notes N/A
Parent Schema ssl
Table 4-41. hostname Option

Description Hostname
Default localhost
Optional false
Type N/A
Notes The hostname of system that hosts the service to monitor.

For example: mysite.com
Parent Schema sockaddr
Table 4-42. port Option

Description Port
Default A default value for port is set for each type of network
service by properties in the netservices plug-in descriptor.
Optional false
Type N/A
VMware, Inc. 289

Table 4-42. port Option (continued)

Notes The port on which the service listens.
Table 4-43. sotimeout Option

Description Socket Timeout (in seconds)
Default 10
Optional true
Type int
Notes The maximum length of time the agent waits for a response
to a request to the remote service.
Table 4-44. path Option

Description Path
Default /
Optional false
Type N/A
Notes Enter a value to monitor a specific page or file on the site.

for example: /Support.html.
Parent Schema url
Table 4-45. method Option

Description Request Method
Default HEAD
Optional false
Type enum
Notes Method for checking availability.

Permitted values: HEAD, GET
HEAD results in less network traffic.
Use GET to return the body of the request response to
specify a pattern to match in the response.
Parent Schema http
VMware, Inc. 290

Table 4-46. hostheader Option

Description Host Header
Default none
Optional true
Type N/A
Notes Use this option to set a Host HTTP header in the request.
This is useful if you use name-based virtual hosting. Specify
the host name of the Vhost's host, for example,
blog.mypost.com.
Parent Schema http
Table 4-47. follow Option

Description Follow Redirects
Default enabled
Optional true
Type boolean
Notes Enable if the HTTP request that is generated will be

redirected. This is important, because an HTTP server
returns a different code for a redirect and vRealize
Operations Manager determines that the HTTP service
check is unavailable if it is a redirect, unless this redirect
configuration is set.
Parent Schema http
Table 4-48. pattern Option

Description Response Match (substring or regex)
Default none
Optional true
Type N/A
Notes Specify a pattern or substring for vRealize Operations

Manager to attempt to match against the content in the
HTTP response. This enables you to check that in addition
to being available, the resource is serving the content you
expect.
Parent Schema http
VMware, Inc. 291

Table 4-49. proxy Option

Description Proxy Connection
Default none
Optional true
Type N/A
Notes If the connection to the HTTP service goes through a proxy

server, supply the hostname and port for the proxy server.
For example, proxy.myco.com:3128.
Parent Schema http
Table 4-50. requestparams Option

Description Request arguments. For example, arg0=val0, arg1=val1, and

so on.
Default N/A
Optional true
Type string
Notes Request parameters added to the URL to be tested.
Parent Schema http
Table 4-51. Credential Option

Description Username
Default N/A
Optional true
Type N/A
Notes Supply the user name if the target site is password-

protected.
Parent Schema credentials
ICMP Configuration Options

Here are the options in the configuration schema for the ICMP resource.
ICMP configuration is not supported in Windows environments. When attempting to run an ICMP
check for remote monitoring from an Agent running on a Windows platform, no data is returned.

Default localhost
VMware, Inc. 292

Table 4-52. hostname Option (continued)

Optional N/A
Type N/A
Notes The hostname of system that hosts the object to monitor.

Parent Schema netservices plug-in descriptor

Default 10
Optional N/A
Type int
Notes The maximum time period the agent waits for a response
to a request to the remote service.
TCP Configuration Options

Here are the options in the configuration schema to enable TCP checking.
Table 4-54. port Option

Description Port
Default A default value for port is set for each type of network
service by properties in the netservices plug-in descriptor.
Optional false
Type N/A
Notes The port on which the service listens.

Default localhost
Optional N/A
Type N/A
Notes The hostname of system that hosts the object to monitor.

VMware, Inc. 293

Make sure that you use the IP address of the machine on which the remote check is to run, not
the host name.

Default 10
Optional N/A
Type int
Notes The maximum amount of time the agent waits for a

response to a request to the remote service.
Agent Management
You can add, edit, and delete End Point Operations Management agents and enable or disable
the End Point Operations Management plug-ins from the tabs in the Agent Management page.
Where You Find the Agent Management Page
In the menu, click Administration, and then in the left pane click Configuration > End Point
Operations.
Agents Tab
You can view the End Point Operations Management agents that are installed and deployed in
your environment.
Where You Find the Agents Tab
In the menu, click Administration, and then in the left pane click Configuration > End Point
Operations.
How the Agents Tab Works
You can view all the agents that are installed, the virtual machines on which they are installed,
their operating system and the agent bundle version. You can also view the collection details of
each agent. You can filter the list of agents based on the name of the agent. You add a filter from
the upper-right corner of the toolbar. You can sort the Agent Token, Agent Name, Collection
State, and Collection Status columns by clicking the column name.
Plug-ins Tab
End Point Operations Management agents include plug-ins that determine which objects to
monitor, how they should be monitored, which metrics to collect, and so on. Some plug-ins are
included in the default End Point Operations Management agent installation, and other plug-ins
might be added as part of any management pack solution that you install to extend the vRealize
Operations Manager monitoring process.
VMware, Inc. 294

You can use the Plug-ins tab from the Agents Management page to disable or enable the agent
plug-ins that are deployed in your environment as part of a solution installation. For example, you
might want to temporarily disable a plug-in so that you can analyze the implication of that plug-in
on a monitored virtual machine. To access the Plug-ins tab, in the menu, click Administration,
and then in the left pane click Configuration > End Point Operations. You can sort all the
columns in the tab by clicking the column name.
All the default plug-ins and the plug-ins that are deployed when you installed one or more
solutions are listed alphabetically on the tab.
You must have Manage Plug-ins permissions to enable and disable plug-ins.
When you disable a plug-in, it is removed from all the agents on which it has existed, and the
agent no longer collects the metrics and other data related to that plug-in. The plug-in is marked
as disabled on the vRealize Operations Manager server.
You cannot disable the default plug-ins that are installed during the vRealize Operations Manager
installation.
You use the action menu that appears when you click the gear wheel icon to disable or enable
plug-ins.
Before you deploy a new version of a plug-in, you must implement a shutdown method. If you do
not implement a shutdown method, the existing plug-in version does not shut down so that a
new instance is created and allocated resources such as static threads are not released.
Implement a shutdown method for these plug-ins.
n Plug-ins that use third-party libraries
n Plug-ins that use native libraries
n Plug-ins that use connection pools
n Plug-ins that might lock files, which cause issues on Windows operating systems
It is good practice that plug-ins do not use threads, third-party libraries, or static collection.
Configuring Plug-in Loading
At startup, an End Point Operations Management agent loads all the plug-ins in the AgentHome/
bundles/agent-x.y.z-nnnn/pdk/plugins directory. You can configure properties in the
agent.properties file to reduce an agent's memory footprint by configuring it to load only the
plug-ins that you use.
Plug-ins are deployed to all agents when a solution is installed. You might want to use the
properties described here in a situation in which you need to remove one or more plug-ins from a
specific machine. You can either specify a list of plug-ins to exclude, or configure a list of plug-ins
to load.
plugins.exclude
Use this property to specify the plug-ins that the End Point Operations Management agent must
not load at startup.
VMware, Inc. 295

You supply a comma-separated list of plugins to exclude. For example,

plugins.exclude=jboss,apache,mysql.
plugins.include
Use this property to specify the plug-ins that the End Point Operations Management agent must
load at startup.
You supply a comma-separated list of plugins to include. For example,

plugins.include=weblogic,apache.
Understanding the Unsynchronized Agents Group
An unsynchronized agent is an agent that is not synchronized with the vRealize Operations
Manager server in terms of its plug-ins. The agent might be missing plug-ins that are registered
on the server, include plug-ins that are not registered on the server, or include plug-ins that have
a different version to that registered on the server.
Each agent must be synchronized with the vRealize Operations Manager server. During the time
that an agent is not synchronized with the server, it appears in the Unsynchronized Agents list.
The list is located in the vRealize Operations Manager user interface on the Groups tab in the
Environment view.
The first time an agent is started, a status message is sent to the server. The server compares
the status sent by the agent with that on the server. The server sends commands to the agent to
synchronize, download or delete plug-ins, as required by the differences that it detects.
When a plug-in is deployed, disabled, or enabled as part of a management pack solution update,
the vRealize Operations Manager server detects that change and sends a new command to the
agents so that synchronization occurs.
Commonly, multiple agents are affected at the same time when a plug-in is deployed, disabled or
enabled. All agents have an equal need to be updated so, to avoid overloading the server and
creating performance issues that might occur if many agents were all synchronized at the same
time, synchronization is performed in batches and is staggered in one-minute periods. You will
notice that the list of unsynchronized agents decrements over time.
Configuring Agent Logging

You can configure the name, location, and logging level for End Point Operations Management
agent logs. You can also redirect system messages to the agent log, and configure the debug log
level for an agent subsystem.
Agent Log Files
The End Point Operations Management agent log files are stored in the AgentHome/log directory.
Agent log files include the following:
agent.log
agent.operations.log
This log is applicable to Windows-based agents only.
VMware, Inc. 296

This is an audit log that records the commands that were run on the agent, together with the
parameters that the agent used to action them.
wrapper.log
The Java service wrapper-based agent launcher writes messages to the wrapper.log file. For
a non-JRE agent, this file is located in agentHome/wrapper/sbin.
In the event that the value was changed ifr the agent.logDir property, the file is also located
in agentHome/wrapper/sbin.
Configuring the Agent Log Name or Location
Use these properties to change the name or location of the agent log file.
agent.logDir
Point Operations Management agent will write its log file. If you do not specify a fully qualified
path, agent.logDir is evaluated relative to the agent installation directory.
This property does not exist in the agent.properties file unless you explicitly add it. The default
behavior is equivalent to the agent.logDir=log setting, resulting in the agent log file being written
to the AgentHome/log directory.
To change the location for the agent log file, add agent.logDir to the agent.properties file and
enter a path relative to the agent installation directory, or a fully qualified path.
The name of the agent log file is configured with the agent.logFile property.
agent.logFile
This property specifies the path and name of the agent log file.
In the agent.properties file, the default setting for the agent.LogFile property is made up of a
variable and a string, agent.logFile=${agent.logDir}\agent.logDir.
n agent.logDir is a variable that supplies the value of an identically named agent property. By
default, the value of agent.logDir is log, interpreted relative to the agent installation directory.
n agent.log is the name for the agent log file.
By default, the agent log file is named agent.log and is written to the AgentHome/log directory.
To configure the agent to log to a different directory, you must explicitly add the agent.logDir
property to the agent.properties file.
Configuring the Agent Logging Level

Use this property to control the severity level of messages that the End Point Operations
Management agent writes to the agent log file.
agent.logLevel
This property specifies the level of detail of the messages that the End Point Operations
Management agent writes to the log file.
VMware, Inc. 297

Setting the agent.logLevel property value to DEBUG level is not advised. This level of logging
across all subsystems imposes overhead, and can also cause the log file to roll over so frequently
that log messages of interest are lost. It is preferable to configure debug level logging only at the
subsystem level.
The changes that you make to this property become effective approximately five minutes after
you save the properties file. It is not necessary to restart the agent to initiate the change.
Redirecting System Messages to the Agent Log
You can use these properties to redirect system-generated messages to the End Point
Operations Management agent log file.
agent.logLevel.SystemErr
This property redirects System.err to agent.log. Commenting out this setting causes System.err
to be directed to agent.log.startup.
The default value is ERROR.
agent.logLevel.SystemOut
This property redirects System.out to agent.log. Commenting out this setting causes System.out
to be directed to agent.log.startup.
The default value is INFO.

Configuring the Debug Level for an Agent Subsystem
For troubleshooting purposes, you can increase the logging level for an individual agent
subsystem.
To increase the logging level for an individual agent subsystem, uncomment the appropriate line
in the section of the agent.properties file that is labeled Agent Subsystems: Uncomment individual
subsystems to see debug messages.
Agent log4j Properties
This is the log4j properties in the agent.properties file.
log4j.rootLogger=${agent.logLevel}, R
log4j.appender.R.File=${agent.logFile}
log4j.appender.R.MaxBackupIndex=1
log4j.appender.R.MaxFileSize=5000KB
log4j.appender.R.layout.ConversionPattern=%d{dd-MM-yyyy HH:mm:ss,SSS z} %-5p [%t] [%c{1}@%L] %m%n
log4j.appender.R.layout=org.apache.log4j.PatternLayout
log4j.appender.R=org.apache.log4j.RollingFileAppender
##
## Disable overly verbose logging
##
log4j.logger.org.apache.http=ERROR
log4j.logger.org.springframework.web.client.RestTemplate=ERROR
log4j.logger.org.hyperic.hq.measurement.agent.server.SenderThread=INFO
log4j.logger.org.hyperic.hq.agent.server.AgentDListProvider=INFO
log4j.logger.org.hyperic.hq.agent.server.MeasurementSchedule=INFO
log4j.logger.org.hyperic.util.units=INFO
VMware, Inc. 298

log4j.logger.org.hyperic.hq.product.pluginxml=INFO
# Only log errors from naming context

log4j.category.org.jnp.interfaces.NamingContext=ERROR
log4j.category.org.apache.axis=ERROR
#Agent Subsystems: Uncomment individual subsystems to see debug messages.

#-----------------------------------------------------------------------
#log4j.logger.org.hyperic.hq.autoinventory=DEBUG
#log4j.logger.org.hyperic.hq.livedata=DEBUG
#log4j.logger.org.hyperic.hq.measurement=DEBUG
#log4j.logger.org.hyperic.hq.control=DEBUG
#Agent Plugin Implementations

#log4j.logger.org.hyperic.hq.product=DEBUG
#Server Communication
#log4j.logger.org.hyperic.hq.bizapp.client.AgentCallbackClient=DEBUG
#Server Realtime commands dispatcher

#log4j.logger.org.hyperic.hq.agent.server.CommandDispatcher=DEBUG
#Agent Configuration parser

#log4j.logger.org.hyperic.hq.agent.AgentConfig=DEBUG
#Agent plugins loader

#log4j.logger.org.hyperic.util.PluginLoader=DEBUG
#Agent Metrics Scheduler (Scheduling tasks definitions & executions)

#log4j.logger.org.hyperic.hq.agent.server.session.AgentSynchronizer.SchedulerThread=DEBUG
#Agent Plugin Managers

#log4j.logger.org.hyperic.hq.product.MeasurementPluginManager=DEBUG
#log4j.logger.org.hyperic.hq.product.AutoinventoryPluginManager=DEBUG
#log4j.logger.org.hyperic.hq.product.ConfigTrackPluginManager=DEBUG
#log4j.logger.org.hyperic.hq.product.LogTrackPluginManager=DEBUG
#log4j.logger.org.hyperic.hq.product.LiveDataPluginManager=DEBUG
#log4j.logger.org.hyperic.hq.product.ControlPluginManager=DEBUG
Installing Optional Solutions in vRealize Operations Manager

You can extend the monitoring capabilities of vRealize Operations Manager by installing optional
solutions from VMware or third parties.
VMware solutions include adapters for Storage Devices, Log Insight, NSX for vSphere, Network
Devices, and VCM. Third-party solutions include AWS, SCOM, EMC Smarts, and many others. To
download software and documentation for optional solutions, visit the VMware Solution
Exchange at https://marketplace.vmware.com/vsx/.
VMware, Inc. 299

Solutions can include dashboards, reports, alerts and other content, and adapters. Adapters are
how vRealize Operations Manager manages communication and integration with other products,
applications, and functions. When a management pack is installed and the solution adapters are
configured, you can use the vRealize Operations Manager analytics and alerting tools to manage
the objects in your environment.
If you upgrade from an earlier version of vRealize Operations Manager, your management pack
files are copied to the /usr/lib/vmware-vcops/user/plugins/.backup file in a folder with the
date and time as the folder name. Before migrating your data to your new vRealize Operations
Manager instance, you must configure the adapter instances again. If you have customized the
adapter, your adapter customizations are not included in the migration, and you must
reconfigure the customizations.
If you update a management pack in vRealize Operations Manager to a newer version, and you
have customized the adapter, your adapter customizations are not included in the upgrade, and
you must reconfigure them.
Solutions in vRealize Operations Manager

You can view and configure solutions that are already installed and configure adapter instances
from the Solutions page.
How Solutions Work

Solutions can include content and adapters. vRealize Operations Manager uses adapters to
manage communication and integration with other products, applications, and functions.
Where You Find Solutions

In the menu, click Administration and in the left pane click Solutions> Configuration to view and
configure solutions that are already installed.
Note The VMware vSphere solution is pre-installed and cannot be deactivated.
Data Collection Notifications

The Data Collection bell icon on the menu provides quick access to status and critical
notifications related to data collections. The icon indicates whether notifications exist, and
whether any of them are critical.
The list displays notifications about the data collections that are in progress, and indicates
whether any of them have critical issues. The list groups the data collection notifications that are
in progress into a single entry at the bottom of the list. To view the details about a collection,
expand the notification.
Each notification displays the status of the last or current data collection, the associated adapter
instance, and the time since the collection completed or an issue was identified. You can click a
notification to open the Solutions page, where you can see further details, and manage adapter
instances.
VMware, Inc. 300

If problems occur with the data collections, vRealize Operations Manager identifies those
problems during each 5-minute collection cycle.
Failed Solution Installation

If a solution installation fails, plug-ins related to the solution might appear in the Plug-ins page of
vRealize Operations Manager, even though the solution is not installed and does not appear on
the Solutions page. When the solution installation fails, reinstall the solution.
Solutions Options
The Solutions page includes a toolbar of options.
Click Show to filter the list of solutions to show configured, unconfigured, or all solutions.
The solutions data grid is a list of solutions that were added. You must configure solution
components so that vRealize Operations Manager can collect data.
Table 4-57. Solutions Data Grid Options

Option Description
Name Name that the vendor or manufacturer gave to the

solution.
Description Typically, an indication of what the solution monitors or

what data source its adapter connects to.
Version Version and build number identifiers of the solution.
Provided By Vendor or manufacturer that created the solution.
Licensing Indicates that the solution requires a license.
Adapter Status Indicates the status of the solution. Data receiving shows
that the solution is collecting data.
The details area includes a toolbar of options.
Table 4-58. Solution Details Toolbar Options

Option Description
Configure Open a window in which you control settings such as

network addresses or credentials that allow the solution to
connect to data. Configuration varies by solution.
Start Collecting Turn on data collection through the selected adapter.
Stop Collecting Do not collect data through the selected adapter.
Reload Refresh the list of details.
The details data grid displays additional information for the selected solution.
VMware, Inc. 301

Table 4-59. Solution Details Data Grid Options

Option Description
Adapter Type Name that the vendor or manufacturer gave to the

adapter.
Adapter Instance Name Name that the installing user gave to this unique installation
of the adapter.
Credential Name Name that the installing user gave to the set of login
credentials used to connect to the data source.
Collector Indicates where vRealize Operations Manager is receiving

the collected data. Typically, the name combines the
adapter and the vRealize Operations Manager node names.
Collection State Indicates whether the adapter is enabled for data

collection.
Collection Status Indicates whether the adapter has collected any data.
Install Native Management Packs and Add Management Packs

You can install native management packs and add management packs from the Repository page.
Where You Find the Repository Page
In the menu, click Administration. From the left pane, select Solutions > Repository.
Table 4-60. Repository Page Options

Options Descriptions
VMware Native Management Packs
Activate Installs the native management pack. You can configure the
management pack after activation from Solutions >
Configuration.
Deactivate Uninstalls the management pack.
Activated The management pack has been installed.
Other Management Packs
Add a Management Pack You can add a management pack. For more details, see the
topic called Add Solutions Wizard.
Add Solutions Wizard

Solutions are delivered as PAK files that you upload, license, and install.
How Added Solutions Work

When you add solutions, you configure adapters that manage communication and integration
between vRealize Operations Manager and other products, applications, and functionality.
VMware, Inc. 302

Where You Add Solutions

On the menu, select Administration and in the left pane select Solutions> Repository. Click the
Add a Management Pack to install other management packs.
Add Solutions Wizard Options

The wizard includes three pages where you locate and upload a PAK file, accept the EULA and
install, and review the installation.
Before you install the PAK file, or upgrade your vRealize Operations Manager instance, clone any
customized content to preserve it. Customized content can include alert definitions, symptom
definitions, recommendations, and views. Then, during the software update, you select the
options named Install the PAK file even if it is already installed and Reset out-of-the-box
content.
Table 4-61. Wizard Options

Option Description
Page 1
Browse a Solution Navigate to your copy of a management pack PAK file.
Upload To prepare for installation, copy the PAK file to vRealize Operations Manager.
Install the PAK file even if it If the PAK file was already uploaded, reload the PAK file using the current file, but leave
is already installed user customizations in place. Do not overwrite or update the solution alerts, symptoms,
recommendations, and policies.
Reset out-of-the-box If the PAK file was already uploaded, reload the PAK file using the current file, and
content overwrite the solution default alerts, symptoms, recommendations, and policies with newer
versions provided with the current PAK file.
Note A reset overwrites customized content. If you are upgrading vRealize Operations
Manager, the best practice is to clone your customized content before you upgrade.
The PAK file is unsigned Warning appears if the PAK file is not signed with a digital signature that VMware provides.
The digital signature indicates the original developer or publisher and provides the
authenticity of the management pack. If installing a PAK file from an untrusted source is a
concern, check with the management pack distributor before proceeding with the
installation.
Page 2
I accept the terms of the Read and agree to the end-user license agreement.
agreement
Note Clicking Next installs the solution.
Page 3
Installation Details Review the installation progress, including the vRealize Operations Manager nodes where
the adapter was installed.
Manage Solutions Workspace

Solutions include adapters that you must configure so that vRealize Operations Manager can
collect data from or send data to the target system.
VMware, Inc. 303

You can configure adapters associated with solutions that are provided with or that you add to
vRealize Operations Manager. After you have configured the adapter, vRealize Operations
Manager can communicate with the target system. You can access the Manage Solutions
workspace at any time to modify your adapter configurations.
Where You Manage Solutions

On the menu, click Administration and in the left pane click Solutions> Configuration. Select the
solution you want to manage.
The options available depend on the selected solution.
Manage the vSphere Solution

To view the manage solution workspace options of the vSphere solution, see Manage Solution -
VMware vSphere Solution Workspace Options.
Managing Solution Credentials

Credentials are the user accounts that vRealize Operations Manager uses to enable one or more
solutions and associated adapters, and to establish communication with the target data sources.
The credentials are supplied when you configure each adapter. You can add or modify the
credential settings outside the adapter configuration process to accommodate changes to your
environment.
For example, if you are modifying credentials to accommodate changes based on your password
policy, the adapters configured with these credentials begin using the new user name and
password to communicate between vRealize Operations Manager and the target system.
Another use of credential management is to remove misconfigured credentials. If you delete valid
credentials that were in active use by an adapter, you disable the communication between the
two systems.
If you need to change the configured credential to accommodate changes in your environment,
you can edit the credential settings without being required to configure a new adapter instance
for the target system. To edit credential settings, click Administration on the menu, and in the
left pane, click Management> Credentials.
Any adapter credential you add is shared with other adapter administrators and vRealize
Operations Manager collector hosts. Other administrators might use these credentials to
Credentials
The credentials are the collection configuration settings, for example, user names and passwords,
that the adapters use to authenticate the connection on the external data sources. Other
credentials can include values such as domain names, pass phrases, or proxy credentials. You
can configure for one or more solutions to connect to data sources as you manage your
changing environment.
VMware, Inc. 304

Where You Find Credentials

On the menu, click Administration and in the left pane click Management > Credentials.
Table 4-62. Credentials Options

Option Description
Toolbar options Manages the selected credential.

n Add New Credentials. Add new credentials for an
adapter type that you can later apply when configuring
an adapter.
n Edit Selected Credentials. Modify the selected
credentials, usually when the user name and password
require a change. The change is applied to the current
adapter credentials and the data source continues to
communicate with vRealize Operations Manager.
n Delete Selected Credential. Deletes the selected
credentials from vRealize Operations Manager. If you
have an adapter that uses these credentials, the
communication fails and you cease monitoring the
objects that the adapter was configured to manage.
Commonly used to delete misconfigured credentials.
Filtering options Limits the displayed credentials based on the adapter or

credential types.
Credential name Description of user defined name that you provide to

manage the credentials. Not the account user name.
Adapter Type Adapter type for which the credentials are configured.
Credential Type Type of credentials associated with the adapter. Some

adapters support multiple types of credentials. For
example, one type might define a user name and
password, and another might define a pass code and key
phrase.
Manage Credentials
To configure or reconfigure credentials that you use to enable an adapter instance, you must
provide the collection configuration settings, for example, user name and password, that are
valid on the target system. You can also modify the connection settings for an existing credential
instance.
Where You Manage Credentials
On the menu, click Administration and in the left pane click Management > Credentials.
VMware, Inc. 305

Manage Credentials Options

The Manage Credentials dialog box is used to add new or modifies existing adapter credentials.
The dialog box varies depending on the type of adapter and whether you are adding or editing.
The following options describe the basic options. Depending on the solution, the options other
than the basic ones vary.
Caution Any adapter credentials you add are shared with other adapter administrators and
vRealize Operations Manager collector hosts. Other administrators might use these credentials to
Table 4-63. Manage Credential Add or Edit Options

Option Description
Adapter Type Adapter type for which you are configuring the credentials.
Credential Kind Credentials associated with the adapter. The combination

of adapter and credential type affects the additional
configuration options.
Credential Name Descriptive name by which you are managing the

credentials.
User Name User account credentials that are used in the adapter
configuration to connect vRealize Operations Manager to
the target system.
Password Password for the provided credentials.
Managing Collector Groups

vRealize Operations Manager uses collectors to manage adapter processes such as gathering
metrics from objects. You can select a collector or a collector group when configuring an adapter
instance.
If there are remote collectors in your environment, you can create a collector group, and add
remote collectors to the group. When you assign an adapter to a collector group, the adapter
can use any collector in the group. Use collector groups to achieve adapter resiliency in cases
where the collector experiences network interruption or becomes unavailable. If this occurs, and
the collector is part of a group, the total workload is redistributed among all the collectors in the
group, reducing the workload on each collector.
Collector Group Workspace

You can add, edit, or remove collector groups in vRealize Operations Manager, and rebalance
your adapter instances.
VMware, Inc. 306

Rebalancing an Adapter Instance

Rebalancing of your adapter instances is not intended to provide equally distributed adapter
instances across each collector in the collector group. The rebalancing action considers the
number of resources that each adapter instance collects to determine the rebalancing placement.
The rebalancing happens at the adapter instance, which can result in several small adapter
instances on a single collector, and a single huge adapter instance on another collector, in your
vRealize Operations Manager instance.
Rebalancing your collector groups can add a significant load on the entire cluster. Moving
adapter instances from one collector to another collector requires that vRealize Operations
Manager stops the adapter instance and all its resources on the source collector, then starts
them on the target collector.
If a collector fails to respond or loses connectivity to the cluster, vRealize Operations Manager
starts automated rebalancing in the collector group. All other user-initiated manual operations on
the collector, such as to stop or restart the collector manually, do not result in automated
rebalancing.
If one of the collectors fails to respond, or if it loses network connectivity, vRealize Operations
Manager performs automated rebalancing. In cases of automated rebalancing, to properly
rebalance the collector group, you must have spare capacity on the collectors in the collector
group.
Where You Manage Collector Groups
On the menu, click Administration and in the left pane click Management > Collector Groups.
Table 4-64. Collector Group Summary Grid

Options Description
Collector Group toolbar To manage collector groups, use the toolbar icons.
n Add. Add a collector group
n Edit. Modify the collector group by adding or removing remote collectors.
n Delete. Remove the selected collector group.
n Rebalance collector group. If you have permissions to manage clusters, you can
rebalance the workload across the collectors and the remote collectors in the
collector group. You can only rebalance one collector group at a time. The rebalance
action moves objects from one collector group to another to rebalance the number
of objects on each collector in the collector group. If a disk rebalance is already in
progress, the collector rebalance does not run.
Collector Group Name The name given to the collector group when the collector group is created.
Description Description given to the collector group when the collector group is created.
All Filters Displays the list of collector groups in the summary grid by collector group name,
description, collector name, or IP address.
Quick Filter Name Filters the list of collector groups according to the name of the collector group entered.
VMware, Inc. 307

Table 4-65. Collector Group Details Grid

Detail Grid Options Description
Members Remote collectors that are assigned to the collector group.
Name Name given to the remote collector when the collector was
created.
IP Address IP address of the remote collector.
Status Status of the remote collector: online or offline
Adding a Collector Group

Create a new collector group from the available remote collectors in your environment. A
collector can only be added to one group at a time.
Where You Add New Collector Groups
Click the Add icon on the Collector Groups toolbar.
Add New Collector Group Workspace
Option Description
Name Name of the collector group.
Description Description of the collector group.
Members Displays a list of the available remote collectors in your

vRealize Operations Manager environment together with
their IP address and status. Collectors that have already
been added to a collector group are not displayed in this
list.
All Filters Enables you to search the list of collectors according to the
following criteria:
n Collector Name
n IP address
n Status
Editing Collector Groups

Edit a collector group by adding remote collectors to the group, or removing the collectors that
you no longer require be part of the group.
Where You Edit a Collector Group
Click the Edit icon on the Collector Groups toolbar.
VMware, Inc. 308

Edit Collector Group Options

Option Description
Name Name given to the collector group when the collector

group is created.
Description Description given to the collector group when the collector

group is created.
Members Displays a list of the available remote collectors in your

vRealize Operations Manager environment together with
their IP address and status. Collectors that have been
added to another collector group are not displayed in this
list. Collectors that are assigned to this collector group
appear with a selected check box next to the collector
name.
All Filters Enables you to filter the list of collectors according to the
following criteria:
n Collector Name
n IP Address
n Status
Configuring Alerts and Actions

In VMware vRealize Operations Manager, alerts and actions play key roles in monitoring the
objects.
All Alerts
The All Alerts page is a list of all the alerts generated in vRealize Operations Manager. Use the
alert list to determine the state of your environment and to begin resolving problems.
How the All Alerts Page Works

By default, only active alerts are initially listed, and the alerts are grouped by Time. Review and
manage the alerts in the list using the toolbar options. Select multiple rows in the list using Shift
+click, Control+click.
To filter the columns in the data grid, click the small box on the lower left of the alert list.
To see the alert details, click the alert name. The alert details appear on the right, including the
symptoms triggered by the alert. The system offers recommendations for addressing the alert
and links to additional information. A Run Action button may appear in the details. Hover over
the button to learn what recommendation is performed if you click the button. Click the X at the
top right of the alert details to return to the list view. Alternatively, you can view the Run button
and the Suggested Fix in the Alerts data grid. You can filter by alerts that have the Run option
enabled and perform the recommended task to address the alert from the Alerts data grid. Click
the small box on the lower left of the alert list to include the Suggested Fix and Run columns in
the data grid.
VMware, Inc. 309

Click the name of the object on which the alert was generated to see the object details, and
access additional information relating to metrics and events.
If you migrated alerts from a previous version of vRealize Operations Manager, the alerts are
listed with a cancelled status and alert details are not available.
Where You Find the All Alerts Page

In the menu, click Alerts.
All Alerts Options

The alert options include toolbar and data grid options. Use the toolbar options to sort the alert
list and to cancel, suspend, or manage ownership. Use the data grid to view the alerts and alert
details.
Select an alert from the list to enable the Actions menu:
Table 4-66. Actions Menu

Option Description
Cancel Alert Cancels the selected alerts. If you configure the alert list to
display only active alerts, the canceled alert is removed
from the list.
Cancel alerts when you do not need to address them.
Canceling an alert does not cancel the underlying condition
that generated it. Canceling alerts is effective if the alert is
triggered by fault and event symptoms, because these
symptoms are triggered again only if subsequent faults or
events occur on the monitored objects. If the alert was
generated based on metric or property symptoms, the
alert is canceled only until the next collection and analysis
cycle. If the violating values are still present, the alert is
generated again.
Delete Canceled Alerts Delete cancelled (inactive) alerts by doing a group

selection or by individually selecting alerts. The option is
disabled for active alerts.
Suspend Suspend an alert for a specified number of minutes.

You suspend alerts when you are investigating an alert and
do not want the alert to affect the health, risk, or efficiency
of the object while you are working. If the problem persists
after the elapsed time, the alert is reactivated and it will
again affect the health, risk, or efficiency of the object.
The user who suspends the alert becomes the assigned
owner.
Take Ownership As the current user, you make yourself the owner of the
alert.
You can only take ownership of an alert, you cannot assign
ownership.
Release Ownership Alert is released from all ownership.
VMware, Inc. 310

Table 4-66. Actions Menu (continued)

Option Description
Go to Alert Definition Switches to the Alert Definitions page, with the definition
for the previously selected alert displayed.
Disable... Offers two options for disabling the alert:

Disable the alert in all policies: this disables the alert for all
objects for all the policies.
Disable Alert in Selected Policies: this disables the alert for
objects having the selected policy. Note that this method
works only for objects with alerts.
Open an external application Actions you can run on the selected object.
For example, Open Virtual Machine in vSphere Client.
Table 4-67. Group By Options

Option Description
None Alerts are not sorted into specific groupings.
Time Group alerts by time triggered. This is the default option.

You can also group by 1 hour, 4 hours, Today and
Yesterday, days of current week, Last week and Older.
Criticality Group alerts by criticality. Values are, from the least critical:
Info/Warning/Immediate/Critical. See also Criticality in the
"All Alerts Data Grid Options" table, below.
Definition Group alerts by definition, that is, group like alerts

together.
Object Type Group alerts by the type of object that triggered the alert.
For example, group alerts on hosts together.
Table 4-68. All Filters

All Filters Descriptions
Filtering options Limit the list of alerts to those matching the filters you
choose.
For example, you might have chosen the Time option in the
Group By menu. Now you can choose Status -> Active in
the all Filters menu, and the All Alerts page displays only
the active alerts, ordered by the time they were triggered.
Selected Options (see also the Group By and All Alerts Data Grid tables for more filter definitions:)
Owner Name of operator who owns the alert.
Impact Alert badge affected by the alert. The affected badge,

health, risk, or efficiency, indicates the level of urgency for
the identified problem.
VMware, Inc. 311

Table 4-68. All Filters (continued)

Control State State of user interaction with the alert. Possible values
include:
n Open. The alert is available for action and has not been
assigned to a user.
n Assigned. The alert is assigned to the user who is
logged in when that user clicks Take Ownership.
n Suspended. The alert was suspended for a specified
amount of time. The alert is temporarily excluded from
affecting the health, risk, and efficiency of the object.
This state is useful when a system administrator is
working on a problem and does not want the alert to
affect the health status of the object.
Object Type Type of object on which the alert was generated.
Updated On Date and time when the alert was last modified.
An alert is updated whenever one of the following changes
occurs:
n Another symptom in the alert definition is triggered.
n Triggering symptom that contributed to the alert is
canceled.
Canceled On Date and time when the alert canceled for one of the
following reasons:
n Symptoms that triggered the alert are no longer active.
Alert is canceled by the system.
n Symptoms that triggered the alert are canceled
because the corresponding symptom definitions are
disabled in the policy that is applied to the object.
because the corresponding symptom definitions were
deleted.
n Alert definition for this alert is disabled in the policy that
is applied to the object.
n Alert definition is deleted.
n User canceled the alert.
Action Choose Yes to filter based on alerts that have the Run
option enabled. Choose No to filter based on alerts that
have the Run option disabled.
The Alerts data grid provides the list of generated alerts used to resolve problems in your
environment. An arrow in each column heading orders the list in ascending or descending order.
VMware, Inc. 312

Table 4-69. All Alerts Data Grid

Option Description
Criticality Criticality is the level of importance of the alert in your

environment.
The level is based on the level assigned when the alert
definition was created, or on the highest symptom
criticality, if the assigned level was Symptom Based.
The possible values include:
n Critical
n Immediate
n Warning
n Information
Alert Name of the alert definition that generated the alert.

Click the alert name to display the alert details to the right.
Triggered On Name of the object for which the alert was generated, and
the object type, which appears in a tooltip when you hover
the mouse over the object name.
Click the object name to view the object details tabs where
you can begin to investigate any additional problems with
the object.
Created On Date and time when the alert was generated.
Status Current state of the alert.

Possible values include Active or Canceled.
Alert Type Describes the type of alert that triggered on the selected
object, and helps you categorize the alerts so that you can
assign certain types of alerts to specific system
administrators. For example, Application, Virtualization/
Hypervisor, Hardware, Storage, and Network.
Alert Subtype Describes additional information about the type of alert

that triggered on the selected object, and helps you
categorize the alerts to a more detailed level than Alert
Type, so that you can assign certain types of alerts to
specific system administrators. For example, Availability,
Performance, Capacity, Compliance, and Configuration.
Suggested Fix Displays the recommendation to address the alert.
Action Click this button to perform the recommendation to

address the alert.
Types of Alerts
Different types of alerts are triggered on a certain object.
The alerts are of three types:
n Health Alerts
n Risk Alerts
VMware, Inc. 313

n Efficiency Alerts
Health Alerts
The health alert list is all the generated alerts that are configured to affect the health of your
environment and require immediate attention. You use the health alert list to evaluate, prioritize,
and immediately begin resolving the problems.
How Health Alerts Work

All the health alerts generated for you managed objects appear in the list.
You can manage the alerts in the list using the toolbar options, click the alert name to see the
alert details for the affected object, or click the name of the object on which the alert was
generated to see the object details.
Health Alerts Options

The alert options include toolbar and data grid options. Use the toolbar options to cancel,
suspend, or manage ownership. You can select multiple rows in the list using Shift+click, Control
+click. Use the data grid to view the alerts. You can click the alert name to view the alert details
or object name to view the object details.
Table 4-70. Health Alerts Toolbar Options

Option Description
Open in external application Actions you can run on the selected object.
from the list.
You cancel alerts when you do not need to address them.
Canceling the alert does not cancel the underlying
condition that generated the alert. Canceling alerts is
effective if the alert is generated by triggered fault and
event symptoms because these symptoms are triggered
again only when subsequent faults or events occur on the
monitored objects. If the alert is generated based on metric
or property symptoms, the alert is canceled only until the
next collection and analysis cycle. If the violating values are
still present, the alert is generated again.

owner.
VMware, Inc. 314

Table 4-70. Health Alerts Toolbar Options (continued)

Option Description
alert.
ownership.
Filtering options Limits the list of alerts to those matching the filter you
create.
You can also sort on the columns in the data grid.
The Health Alerts data grid provides a list of generated alerts that you use to resolve problems in
your environment.
Table 4-71. Health Alerts Data Grid Options

Option Description

environment. The alert criticality appears in a tooltip when
you hover the mouse over the criticality icon.
n Critical
n Immediate
n Warning
n Information
By default, alerts are sorted by criticality. Presorting the
alerts list by criticality displays critical alerts at the top of
the list. If you change the sort order, the sort is saved with
your preferences in the global alerts list, and the Health,
Risk, and Efficiency alerts lists.

Click the alert name to view the alert details tabs where
you can begin troubleshooting the alert.

VMware, Inc. 315

Table 4-71. Health Alerts Data Grid Options (continued)

Option Description

the object.
include:
assigned to a user.
Owner Name of the user who owns the alert.
occurs:
canceled.
following reasons:
deleted.
VMware, Inc. 316

Risk Alerts
The risk alerts list is all the generated alerts that are configured to indicate risk in your
environment. Address risk alerts in the near future, before the triggering symptoms that
generated the alert negatively affect the health of your environment.
How Risk Alerts Work

All the risk alerts generated for your managed objects appear in the list.
Risk Alerts Options

Table 4-72. Risk Alerts Toolbar Options

Option Description
from the list.

owner.
alert.
ownership.
VMware, Inc. 317

Table 4-72. Risk Alerts Toolbar Options (continued)

Option Description
create.
The Risk Alerts data grid provides a list of generated alerts that you use to resolve problems in
your environment.
Table 4-73. Risk Alerts Data Grid Options

Option Description

n Critical
n Immediate
n Warning
n Information



VMware, Inc. 318

Table 4-73. Risk Alerts Data Grid Options (continued)

Option Description
the object.
include:
assigned to a user.
occurs:
canceled.
following reasons:
deleted.
VMware, Inc. 319

Efficiency Alerts
The efficiency alerts list is all the generated alerts that are configured to indicate problems with
the efficient use of your monitored objects in your environment. Address efficiency alerts to
reclaim wasted space or to improve the performance of objects in your environment.
How Efficiency Alerts Work

All the efficiency alerts generated for you managed objects appear in the list.
Efficiency Alerts Options

Table 4-74. Efficiency Alerts Toolbar Options

Option Description
from the list.

owner.
alert.
ownership.
VMware, Inc. 320

Table 4-74. Efficiency Alerts Toolbar Options (continued)

Option Description
create.
The Efficiency Alerts data grid provides a list of generated alerts that you use to resolve
problems in your environment.
Table 4-75. Efficiency Alerts Data Grid Options

Option Description

n Critical
n Immediate
n Warning
n Information



VMware, Inc. 321

Table 4-75. Efficiency Alerts Data Grid Options (continued)

Option Description
the object.
include:
assigned to a user.
occurs:
canceled.
following reasons:
deleted.
VMware, Inc. 322

Configuring Alerts
Whenever there is a problem in the environment, the alerts are generated. You can create the
alert definitions so that the generated alerts tell you about the problems in the monitored
environment.
Defining Alerts in vRealize Operations Manager

An alert definition comprises one or more symptom definitions, and the alert definition is
associated with a set of recommendations and actions that help you resolve the problem. Alert
definitions include triggering symptom definitions and actionable recommendations. You create
the alert definitions so that the generated alerts tell you about problems in the monitored
environment. You can then respond to the alerts with effective solutions that are provided in the
recommendations.
Predefined alerts are provided in vRealize Operations Manager as part of your configured
adapters. You can add or modify alert definitions to reflect the needs of your environment.
Symptoms in Alert Definitions

Symptom definitions evaluate conditions in your environment that, if the conditions become true,
trigger a symptom and can result in a generated alert. You can add symptom definitions that are
based on metrics or super metrics, properties, message events, fault events, or metric events.
You can create a symptom definition as you create an alert definition or as an individual item in
the appropriate symptom definition list.
When you add a symptom definition to an alert definition, it becomes a part of a symptom set. A
symptom set is the combination of the defined symptom with the argument that determines
when the symptom condition becomes true.
A symptom set combines one or more symptom definitions by applying an Any or All condition,
and allows you to choose the presence or absence of a particular symptom. If the symptom set
pertains to related objects rather than to Self, you can apply a population clause to identify a
percentage or a specific count of related objects that exhibit the included symptom definitions.
An alert definition comprises one or more symptom sets. If an alert definition requires all of the
symptom sets to be triggered before generating an alert, and only one symptom set is triggered,
an alert is not generated. If the alert definition requires only one of several symptom sets to be
triggered, then the alert is generated even though the other symptom sets were not triggered.
Recommendations in Alert Definitions

Recommendations are the remediation options that you provide to your users to resolve the
problems that the generated alert indicates.
When you add an alert definition that indicates a problem with objects in your monitored
environment, add a relevant recommendation. Recommendations can be instructions to your
users, links to other information or instruction sources, or vRealize Operations Manager actions
that run on the target systems.
VMware, Inc. 323

Modifying Alert Definitions

If you modify the alert impact type of an alert definition, any alerts that are already generated will
have the previous impact level. Any new alerts will be at the new impact level. If you want to
reset all the generated alerts to the new level, cancel the old alerts. If they are generated after
cancellation, they will have the new impact level.
Defining Symptoms for Alerts

Symptoms are conditions that indicate problems in your environment. You define symptoms that
you add to alert definitions so that you know when a problem occurs with your monitored
objects.
As data is collected from your monitored objects, the data is compared to the defined symptom
condition. If the condition is true, then the symptom is triggered.
You can define symptoms based on metrics and super metrics, properties, message events, fault
events, and metric events.
Defined symptoms in your environment are managed in the Symptom Definitions. When the
symptoms that are added to an alert definition are triggered, they contribute to a generated
alert.
Define Symptoms to Cover All Possible Severities and Conditions

Use a series of symptoms to describe incremental levels of concern. For example, Volume
nearing capacity limit might have a severity value of Warning while Volume reached
capacity limit might have a severity level of Critical. The first symptom is not an immediate
threat. The second symptom is an immediate threat.
About Metrics and Super Metrics Symptoms

Metric and super metric symptoms are based on the operational or performance values that
vRealize Operations Manager collects from target objects in your environment. You can configure
the symptoms to evaluate static thresholds or dynamic thresholds.
You define symptoms based on metrics so that you can create alert definitions that let you know
when the performance of an object in your environment is adversely affected.
Static Thresholds
Metric symptoms that are based on a static threshold compare the currently collected metric
value against the fixed value you configure in the symptom definition.
For example, you can configure a static metric symptom where, when the virtual machine CPU
workload is greater than 90, a critical symptom is triggered.
Dynamic Thresholds
Metric symptoms that are based on dynamic thresholds compare the currently collected metric
value against the trend identified by vRealize Operations Manager, evaluating whether the
current value is above, below, or generally outside the trend.
VMware, Inc. 324

For example, you can configure a dynamic metric symptom where, when the virtual machine CPU
workload is above the trended normal value, a critical symptom is triggered.
Metric / Super Metric Symptom Definitions
The Metric / Super Metric Symptom Definitions is a list of the metric-based symptoms defined in
your vRealize Operations Manager environment. You use the information in the list to evaluate
the defined metric threshold triggering states and determine if you want to add, edit, or clone
symptoms.
Where You Find Metric / Super Metric Symptoms
To manage symptoms based on metrics and super metrics, in the menu, click Alerts and then in
the left pane, click Alert Settings > Symptom Definitions > Metric/Property.
You can also define symptoms as you are defining alerts in the Alert Definition Workspace.
Table 4-76. Metric / Super Metric Symptoms Options

Option Description
Toolbar options Use the toolbar options to manage your symptoms. You
can select multiple symptoms using Ctrl+click or Shift+click.
n Add. Add a symptom definition.
n Edit. Modify the selected symptom definition. Any
changes you make affect the alert definitions that
include this symptom. You cannot edit a symptom that
manages a badge.
n Delete. Remove the selected symptom definition. You
cannot delete an alert that is used in an alert definition.
To delete a symptom, you must first remove it from the
alert definitions in which it is used. You cannot delete a
symptom that manages a badge.
n Clone. Create a copy of the selected symptom
definition.
n Export and Import. Export the file as xml from one
vRealize Operations Manager so that you can import
the file on another instance. When you import the file, if
you encounter a conflict, you can override the existing
file or not import the new file.
All Filters Limits the list to symptoms matching the filter.

Quick Filter (Name) Limits the list based on the text you type.
Symptom Descriptive name of the symptom.
Adapter Type Adapter type for which the symptom is configured.
Object Type Base object type against which the symptom is defined.
Metric Key Text string that is used as a reference key for the metric.
You can use the metric key to locate additional information
about how the system statistics are derived from the
metric.
Operator Operator used to compare the current value to the

threshold value, and trigger the symptom.
VMware, Inc. 325

Table 4-76. Metric / Super Metric Symptoms Options (continued)

Option Description
Threshold Triggering threshold for the symptom. The threshold and

the operator combine to set the point at which the
symptom is triggered.
Defined By Indicates whether the symptom was created by a user or

provided with a solution adapter.
Metric and Supermetric Symptoms Definition Workspace

You define metric and super metric symptoms, which are based on collected operational or
performance values, so that you can create one or more of the symptoms that you can add to an
alert definition in vRealize Operations Manager. When a symptom is triggered, you use the
symptoms to evaluate alerts or troubleshoot other problems.
How Metric Symptom Definitions Work
A metric or super metric symptom is triggered when a metric is compared to the configured
static or dynamic thresholds, and the symptom condition is evaluated as true. If the symptom is
based on a static threshold, the metric is compared based on the configured operator and the
provided numeric value. If the symptom is based on a dynamic threshold, the metric is compared
based on whether the current value is above, below, or abnormal compared to the calculated
trend value.
Where You Find the Metric Symptom Definition Workspace
To define symptoms based on metrics or super metrics, in the menu, click Alerts and then in the
left pane, click Alert Settings > Symptom Definitions > Metric / Property. Click the plus sign to
define a metric-based symptom in the workspace.
Table 4-77. Symptoms Workspace Options for Metrics and Super Metrics
Option Description
Metric Explorer Components that you use to locate your metrics or super
metrics for which you are creating symptoms.
Base Object Type Object against which the symptom is evaluated.

Based on the select object type, the list of available metrics
displays only the metrics applicable to the object type.
Select Resource If a metric or supermetric is not listed in the common metric

or supermetric list, based on the selected based object
type, use Select Resource to inspect the metrics or
supermetrics of a selected object so that you can locate the
property that you must use to create the symptom. Even
though you select a metric or supermetric for a specific
object, the symptom definition is applicable to all objects
with that metric or supermetric in your environment.
Search Use a word search to limit the number of items that appear
in the list.
Metric list List of metrics for the selected base object type.
VMware, Inc. 326

Table 4-77. Symptoms Workspace Options for Metrics and Super Metrics (continued)
Option Description
Symptom definition workspace Click and drag the metric to the right pane.
You can define symptoms based on static or dynamic
thresholds.
Threshold Determines if the symptom is static or dynamic.

n Static thresholds are fixed values that trigger symptoms
as true. You can configure one threshold for each
symptom. You can also create multiple symptoms for
multiple thresholds.
For example, configure one symptom where the CPU

use is greater than 90 percent and another where the
CPU usage is less than 40 percent. Each is a separate
symptom and can be added individually to an alert
definition.
n Dynamic thresholds are based on vRealize Operations
Manager trended data where the triggering value is
determined through the analytics. If the current value of
the metric or super metric does not fall in the trended
range, the symptom is triggered.
VMware, Inc. 327

Option Description
Static Threshold configuration options If you select Static Threshold, configure the options for this
threshold type.
n Operator. Determines how the value you specify in the
value text box is compared to the current value of the
metric or super metric when the symptom is evaluated.
n Value. Value that is the triggering threshold.
n Criticality level. Severity of the symptom when it is
triggered.
n Symptom name. Name of the symptom as it appears in
the symptom list when configuring an alert definition, as
it appears when the alert is generated, and when
viewing triggered symptoms.
n Wait Cycle. The trigger condition should remain true for
this number of collection cycles before the symptom is
triggered. The default value is 1, which means that the
symptom is triggered in the same collection cycle when
the condition became true.
n Cancel Cycle. The symptom is canceled after the trigger
condition is false for this number of collection cycles
after which the symptom is cancelled. The default value
is 1, which means that the symptom is canceled in the
same cycle when the condition becomes false.
n Evaluate on instanced metrics. Select this check box so
that the system evaluates the object level symptom as
well as the instance level symptom. For example, for
CPU usage, when the check box is not selected, the
symptom is triggered based on the object's CPU usage.
However, if you select the check box, the system also
evaluates CPU usage of each of the cores. If any of the
cores is found to be crossing the threshold, the
n Exclude the following instances of the metric. To
exclude specific instanced metrics from the symptom,
drag the metric instances from the left pane. If you
cannot locate the metric instance you want to exclude,
you can search for it in another object that uses the
metric by clicking Select Object next to the Metrics text
box.
Dynamic Threshold configuration options If you select Dynamic Threshold, configure the options for
this threshold type.
n Threshold trend. Relationship of the current value to
trended range based on the following options:
n Above. If current value is above trended range, the
n Below. If the current value is below the trended
range, the symptom is triggered.
n Abnormal. If the current value is either above or
below the trended range, the symptom is triggered.
VMware, Inc. 328

Option Description

triggered.
n Symtom name. Name of the symptom as it appears in
it appears when the alert is generated, and viewing
triggered symptoms.
n Evaluate on instanced metrics. Select this check box so
that the system evaluates the object level symptom as
well as the instance level symptom. For example, for
CPU usage, when the check box is not selected, the
symptom is triggered based on the object's CPU usage.
However, if you select the check box, the system also
evaluates CPU usage of each of the cores. If any of the
cores is found to be crossing the threshold, the
n Exclude the following instances of the metric. To
exclude specific instanced metrics from the symptom,
drag the metric instances from the left pane. If you
cannot locate the metric instance you want to exclude,
you can search for it in another object that uses the
metric by clicking Select Object next to the Metrics
field.
Property Symptoms
Property symptoms are based on the configuration properties that vRealize Operations Manager
collects from the target objects in your environment.
You define symptoms based on properties so that you can create alert definitions that let you
know when changes to properties on your monitored objects can affect the behavior of the
Property Symptoms Definitions
The Property Symptom Definitions is a list of the property-based symptoms in your vRealize
Operations Manager environment. You use the information in the list to evaluate the defined
property triggering states and determine whether to add, edit, or clone symptoms.
Where You Find Property Symptoms
To manage symptoms based on properties, in the menu, click Alerts and then in the left pane,
click Alert Settings > Symptom Definitions > Metric/Property.
VMware, Inc. 329

Table 4-78. Property Symptoms Definitions Options

Option Description
manages a badge.
definition.
All Filters Limits the list to symptoms matching the filter.

Quick Filter (Name) Limits the list based on the text you type.
Property Text string that is used as a reference key for the property.
You can use the property to locate additional information
about the property.
Operator Operator used to compare the threshold value to the

current value.
Value Text string that is the compared value for the property.

Property Symptoms Definition Workspace

You define property symptoms, which are based on collected configuration properties, so that
you can add one or more symptoms to an alert definition in vRealize Operations Manager. You
use the triggered symptoms to resolve alerts or troubleshoot other problems.
How Property Symptom Definitions Work
A property symptom is triggered when the defined threshold is compared with the current
property value and the comparison is evaluated as true.
Where You Find the Property Symptom Definition Workspace
VMware, Inc. 330

To define symptoms based on metrics or super metrics, in the menu, click Alerts and then in the
left pane, click Alert Settings > Symptom Definitions. Click Add to define a property-based
symptom in the workspace.
Table 4-79. Symptoms Workspace Options for Properties

Option Description
Property Selector Components that you use to locate the properties for which
you are creating symptoms.
Based Object Type Object against which the symptom is evaluated.

Based on the selected object type, the list of available
properties displays only the properties applicable to the
object type.
Select Resource If a property is not listed in the common properties list,

based on the selected based object type, use Select
Resource to inspect the properties of a selected object so
that you can locate the property that you must use to
create the symptom. Even though you select a property for
a specific object, the symptom definition is applicable to all
objects with that property in your environment.
in the list.
Property list List of properties for the selected base object type.
VMware, Inc. 331

Table 4-79. Symptoms Workspace Options for Properties (continued)

Option Description
Symptom definition workspace Drag the property to the right pane.
Property The properties are configured values that are compared to

the value you specify. You can configure a single property
symptom or add multiple symptoms.
For example, if you need an alert when a particular
property, such as Memory Hot Add, is no longer at the
value required, you can configure a symptom and add it to
an alert definition.
Configure the options:
n Operator. Determines how the value you specify in the
value text box is compared to the current value of the
property for an object when the symptom definition is
evaluated.
n Value. Value that the operator evaluates.
triggered.
Message Event Symptoms

Message event symptoms are based on events received as messages from a component of
vRealize Operations Manager or from an external monitored system through the system's REST
API. You define symptoms based on message events to include in alert definitions that use these
symptoms. When the configured symptom condition is true, the symptom is triggered.
The adapters for the external monitored systems and the REST API are inbound channels for
collecting events from external sources. Adapters and the REST server both run in the vRealize
Operations Manager system. The external system sends the messages, and vRealize Operations
Manager collects them.
VMware, Inc. 332

You can create message event symptoms for the supported event types. The following list is of
supported event types with example events.
n System Performance Degradation. This message event type corresponds to the

EVENT_CLASS_SYSTEM and EVENT_SUBCLASS_PERFORM_DEGRADATION type and
subtype in the vRealize Operations Manager API SDK.
n Change. The VMware adapter sends a change event when the CPU limit for a virtual machine
is changed from unlimited to 2 GHz. You can create a symptom to detect CPU contention
issues as a result of this configuration change. This message event type corresponds to the
EVENT_CLASS_CHANGE and EVENT_SUBCLASS_CHANGE type and subtype in the vRealize
Operations Manager API SDK.
n Environment Down. The vRealize Operations Manager adapter sends an environment down
event when the collector component is not communicating with the other components. You
can create a symptom that is used for internal health monitoring. This message event type
corresponds to the EVENT_CLASS_ENVIRONMENT and EVENT_SUBCLASS_DOWN type and
subtype in the vRealize Operations Manager API SDK.
n Notification. This message event type corresponds to the EVENT_CLASS_NOTIFICATION and

EVENT_SUBCLASS_EXTEVENT type and subtype in the vRealize Operations Manager API
SDK.
Message Event Symptom Definitions
The Message Event Symptom Definitions is a list of the message event-based symptoms defined
in your vRealize Operations Manager environment. You use the information in the list to evaluate
the defined message events and to determine if you want to add, edit, or clone symptoms.
Where You Find Message Event Symptoms
To manage symptoms based on message events, in the menu, click Alerts and then in the left
pane, click Alert Settings > Symptom Definitions. Select the Message Event tab.
VMware, Inc. 333

Table 4-80. Message Event Symptoms Options

Option Description
manages a badge.
definition.
Filter options Limits the list to symptoms matching the filter.
Event Type Defined event classification type.
Operator Operator used to compare the message from the incoming

event against the event message specified in the symptom.
Event Message Text string that is compared to the message in the

incoming event using the specified operator.

Message Event Symptoms Definition Workspace

Message event symptoms are based on message events received from a component of vRealize
Operations Manager or from an external monitored system through the system's REST API. You
define message event systems so that you can create one or more of the symptoms that you
can add to an alert definition.
How Message Event Symptom Definitions Work
A message event symptom is triggered when a message in an incoming event matches the text
string in the symptom based on the specified operator.
Where You Find the Message Event Symptom Definition Workspace
VMware, Inc. 334

To define symptoms based on message events, in the menu, click Alerts and then in the left
pane, click Alert Settings > Symptom Definitions. Click Add to define a property-based
symptom in the workspace.
Table 4-81. Symptoms Workspace Options for Message Events

Option Description
Message Event Selector Components that you use to create symptoms.
Select the Type of Event Select the type of incoming event against which you are
matching the events as they arrive. The incoming event
must contain the following type and subtype combinations.
n System Performance Degradation.
n Change.
n Environment Down.
n Notifications.
Symptom definition workspace Drag the event type to the right pane.
Message Event The Message Event text string is compared to the message
in the incoming event by using the specified operator. You
can configure a single message event symptom or add
multiple symptoms.
For example, the VMware adapter sends a change event
when the CPU limit for a virtual machine was changed from
unlimited to 2 GHz. You can create a symptom to detect
CPU contention issues as a result of this configuration
change.
n Operator. Determines how the string that you specify in
the event message text box is evaluated against the
message in the event when the symptom definition is
evaluated.
n Event message. String that the operator evaluates.
triggered.
VMware, Inc. 335

Fault Symptoms
Fault symptoms are based on events published by monitored systems. vRealize Operations
Manager correlates a subset of these events and delivers them as faults. Faults are intended to
signify events in the monitored systems that affect the availability of objects in your environment.
You define symptoms based on faults to include in alert definitions that use these symptoms.
When the configured symptom condition is true, the symptom is triggered.
You can create fault symptoms for the supported published faults. Some object types have
multiple fault definitions from which to choose, while others have no fault definitions.
If the adapter published fault definitions for an object type, you can select one or more fault
events for a given fault while you define the symptom. The symptom is triggered if the fault is
active because of any of the chosen events. If you do not select a fault event, the symptom is
triggered if the fault is active because of a fault event.
Fault Symptom Definitions
The Fault Symptom Definitions is a list of the fault-based symptoms defined in your vRealize
Operations Manager environment. You use the information in the list to evaluate the defined fault
message events and to determine whether to add, edit, or clone symptoms.
Where You Find Fault Symptoms
To manage symptoms based on fault message events, in the menu, click Alerts and then in the
left pane, click Alert Settings > Symptom Definitions. Select the Fault tab.
Table 4-82. Fault Symptoms Definitions Options

Option Description
manages a badge.
definition.
VMware, Inc. 336

Table 4-82. Fault Symptoms Definitions Options (continued)

Option Description
Fault Selected fault based on object type.

Fault Symptoms Definition Workspace

You define fault symptoms, which are based on events published by the monitored systems, so
that you can add one or more symptoms to an alert definition. You use the triggered symptoms
to resolve alerts or troubleshoot other problems in vRealize Operations Manager.
How Fault Symptom Definitions Work
A fault symptom is triggered when a fault is active on the base object because of the occurrence
of any of the fault events selected in the symptom definition.
Where You Find the Fault Symptom Definition Workspace
To define symptoms based on fault message events, in the menu, click Alerts and then in the left
pane, click Alert Settings > Symptom Definitions. Click the Fault tab and Fault Symptom
Definitions click Add to define a property-based symptom in the workspace.
Table 4-83. Symptoms Workspace Options for Faults

Option Description
Fault Selector Components that you use to create symptoms.
Fault definitions Select the fault definition for the selected base object
type.
Some object types do not have fault definitions, and other
types have multiple definitions.
VMware, Inc. 337

Table 4-83. Symptoms Workspace Options for Faults (continued)

Option Description
Symptom definition workspace Drag the fault definition to the right pane.
Fault symptom definition The fault events are published events from monitored
systems. You can configure a single fault event symptom
or add multiple symptoms.
For example, if your base object is host and you drag the
Hardware sensor fault for unknown type fault definition,
you then select one of two text strings indicating a fault.
n Fault event. Select one or more fault events that
activate the fault. If you do not select a string, then
any of the provided strings are evaluated.
triggered.
n Symptom name. Name of the symptom as it appears
in the symptom list when configuring an alert
definition, as it appears when the alert is generated,
and when viewing triggered symptoms.
n Wait Cycle. The trigger condition should remain true
for this number of collection cycles before the
symptom is triggered. The default value is 1, which
means that the symptom is triggered in the same
collection cycle when the condition became true.
n Cancel Cycle. The symptom is canceled after the
trigger condition is false for this number of collection
cycles after which the symptom is cancelled. The
default value is 1, which means that the symptom is
canceled in the same cycle when the condition
becomes false.
Metric Event Symptoms

Metric event symptoms are based on events communicated from a monitored system where the
selected metric violates a threshold in a specified manner. The external system manages the
threshold, not vRealize Operations Manager.
Metric event symptoms are based on conditions reported for selected metrics by an external
monitored system, as compared to metric symptoms, which are based on thresholds that
vRealize Operations Manager is actively monitoring.
The metric event thresholds, which determine whether the metric is above, below, equal to, or
not equal to the threshold set on the monitored system, represent the type and subtype
combination that is specified in the incoming metric event.
n Above Threshold. Corresponds to type and subtype constants EVENT_CLASS_HT and

EVENT_SUBCLASS_ABOVE defined in the vRealize Operations Manager API SDK.
n Below Threshold. Corresponds to type and subtype constants EVENT_CLASS_HT and

EVENT_SUBCLASS_BELOW defined in the vRealize Operations Manager API SDK.
VMware, Inc. 338

n Equal Threshold. Corresponds to type and subtype constants EVENT_CLASS_HT and

EVENT_SUBCLASS_EQUAL defined in the vRealize Operations Manager API SDK.
n Not Equal Threshold. Corresponds to type and subtype constants EVENT_CLASS_HT and
EVENT_SUBCLASS_NOT_EQUAL defined in the vRealize Operations Manager API SDK.
Metric Event Symptom Definitions
The Metric Event Symptom Definitions is a list of the metric event-based symptoms defined in
your vRealize Operations Manager environment. You use the information in the list to evaluate
the defined threshold triggering states for the metric events and to determine if you want to add,
edit, or clone symptoms.
Where You Find Metric Event Symptoms
To manage symptoms based on metric events, in the menu, click Alerts and then in the left pane,
click Alert Settings > Symptom Definitions. Click the Metric Event tab.
Table 4-84. Metric Event Symptom Definitions Options

Option Description
manages a badge.
definition.
Event Metric Selected event metric based on object type.
Event Type Specifies whether the metric was above, below, equal to,
or not equal to the threshold set by the monitoring system.

VMware, Inc. 339

Metric Event Symptoms Definition Workspace

You define metric event symptoms, which are based on reported violations of metric thresholds
from monitored systems, so that you can create one or more of the symptoms that you can add
to an alert definition in vRealize Operations Manager.
How Metric Event Symptom Definitions Work
A metric event symptom is triggered when vRealize Operations Manager receives a metric event
for the metric and event type defined in the symptom. The event type specifies whether the
metric is above, below, equal to, or not equal to the threshold set on the monitored system.
Where You Find the Metric Event Symptom Definition Workspace
To define symptoms based on metric events, in the left pane, in the menu, click Alerts and then
in the left pane, click Alert Settings > Symptom Definitions. Select the Metric Event tab and click
Add to define a property-based symptom in the workspace.
Table 4-85. Symptoms Workspace Options for Metric Events

Option Description
Metric Explorer Components that you use to create symptoms.

Based on the select object type, the list of available metrics
displays only the metrics applicable to the object type.
Select Resource If a property is not listed in the common properties list,

based on the selected based object type, use Select
Resource to inspect the properties of a selected object so
that you can locate the property that you must use to
create the symptom. Even though you select a property for
a specific object, the symptom definition is applicable to all
objects with that property in your environment.
in the list.
Metric Event list List of the metric events for the selected base object type.
VMware, Inc. 340

Table 4-85. Symptoms Workspace Options for Metric Events (continued)

Option Description
Symptom definition workspace Click and drag the metric to the right pane.
Metric Event You can configure a single threshold or add multiple

thresholds.
For example, configure a symptom where, when the virtual
machine CPU usage is above the threshold defined in the
monitored system, the metric event is above the threshold
on the system.
n Event type. Select whether the metric is above, below,
equal to, or not equal to the threshold set on the
monitored system.
triggered.
Understanding Negative Symptoms for vRealize Operations Manager Alerts

Alert symptoms are conditions that indicate problems in your environment. When you define an
alert, you include symptoms that generate the alert when they become true in your environment.
Negative symptoms are based on the absence of the symptom condition. If the symptom is not
true, the symptom is triggered.
To use the absence of the symptom condition in an alert definition, you negate the symptom in
the symptom set.
All defined symptoms have a configured criticality. However, if you negate a symptom in an alert
definition, it does not have an associated criticality when the alert is generated.
All symptom definitions have a configured criticality. If the symptom is triggered because the
condition is true, the symptom criticality will be the same as the configured criticality. However, if
you negate a symptom in an alert definition and the negation is true, it does not have an
associated criticality.
When negative symptoms are triggered and an alert is generated, the effect on the criticality of
the alert depends on how the alert definition is configured.
VMware, Inc. 341

The following table provides examples of the effect negative symptoms have on generated
alerts.
Table 4-86. Negative Symptoms Effect on Generated Alert Criticality

Negative Symptom Standard Symptom Configured Alert Criticality When
Alert Definition Criticality Configured Criticality Criticality Triggered
Warning One Critical Symptom One Immediate Symptom Warning. The alert
criticality is based on the
defined alert criticality.
Symptom Based One Critical Symptom One Warning Symptom Warning. The negative
symptom has no
associated criticality and
the criticality of the
standard symptom
determines the criticality
of the generated alert.
Symptom Based One Critical Symptom No standard symptom included Info. Because an alert
must have a criticality and
the negative alert does
not have an associated
criticality, the generated
alert has a criticality of
Info, which is the lowest
possible criticality level.
Defining Recommendations for Alert Definitions

Recommendations are instructions to your users who are responsible for responding to alerts.
You add recommendations to vRealize Operations Manager alerts so that your users can
maintain the objects in your environment at the required levels of performance.
Recommendations provide your network engineers or virtual infrastructure administrators with

information to resolve alerts.
Depending on the knowledge level of your users, you can provide more or less information,
including the following options, in any combination.
n One line of instruction.
n Steps to resolve the alert on the target object.
n Hyperlink to a Web site, runbook, wiki, or other source.
n Action that makes a change on the target object.
When you define an alert, provide as many relevant action recommendations as possible. If more
than one recommendation is available, arrange them in priority order so that the solution with the
lowest effect and highest effectiveness is listed first. If no action recommendation is available,
add text recommendations. Be as precise as possible when describing what the administrator
should do to fix the alert.
VMware, Inc. 342

Recommendations
Recommendations are probable solutions for an alert generated in vRealize Operations Manager.
You can create a library of recommendations that include instructions to your environment
administrators or actions that they can run to resolve an alert.
Where You Find Recommendations
To define recommendations, in the menu, click Alerts and then in the left pane, click Alert
Settings > Recommendations.
You can also define recommendations when you create an alert definition.
Table 4-87. Recommendations Overview Options

Option Description
Toolbar options Use the toolbar options to manage your

recommendations.
n Add. Add a recommendation.
n Edit. Modify the selected recommendation.
n Delete. Remove the selected recommendation.
n Clone. Create a copy of the selected recommendation
so that you can create a new recommendation that
uses the current one.
n Export and Import. Export the file as XML from one
the file on another instance. When you import the file,
if you encounter a conflict, you can override the
existing file or not import the new file.
Filter options Limits the list to recommendations matching the filter.
Description Recommendation text as it appears when the alert is

generated and the recommendation is presented.
Action If the recommendation includes running an action, the

name of the actions.
Recommendation Workspace
You create recommendations that are solutions to alerts generated in vRealize Operations
Manager. The recommendations are intended to ensure that your network operations engineers
and virtual infrastructure administrators can respond to alerts as quickly and accurately as
possible.
How the Recommendations Workspace Works
A recommendation is instructions to your users or actions that your users can perform to resolve
an alert. The instructions can be links to useful Web sites or local runbooks, instructions as text,
or actions that you can initiate from vRealize Operations Manager.
Where You Find Recommendations Workspace
To define recommendations, click Alerts and select Recommendations from the Alert Settings
drop-down menu in the left pane. Click Add to create a recommendation.
You can also define recommendations when you define alerts.
VMware, Inc. 343

Table 4-88. Define Recommendation Options

Option Description
Create a hyperlink Enter text in the text box, select the text, and click the
button to make the text a hyperlink to a Web site or local
wiki page.
You cannot modify a hyperlink. To change the link, delete
the hyperlinked word and create a new link.
Enter text Enter the description of what must be done to resolve the
triggered alert.
The description can include steps a user must take to
resolve the alert or it might be instructions to notify a
virtual infrastructure administrator.
This is a text field.
Adapter Type Select an adapter type from the drop-down list to narrow
down the list of actions displayed in the Actions field.
Action You can add an action as a method to resolve a triggered

symptom or a generated alert. Actions must already be
configured in vRealize Operations Manager.
You must provide text in the text box to describe the
action before you can save the recommendation.
These actions, named Delete Unused Snapshots for Datastore Express and Delete Unused
Snapshots for VM Express appear. However, they can only be run in the user interface from an
alert whose first recommendation is associated with this action. You can use the REST API to run
these actions.
The following actions are also not visible except in the alert recommendations:
n Set Memory for VM Power Off Allowed
n Set CPU Count for VM Power Off Allowed
n Set CPU Count and Memory for VM Power Off Allowed
These actions are intended to be used to automate the actions with the Power Off Allowed flag
set to true.
Alert Definitions
Alert definitions are a combination of symptoms and recommendations that you combine to
identify problem areas in your environment and generate alerts on which you can act for those
areas. You use the Alert Definitions to manage your vRealize Operations Manager alert library,
and to add or modify the definitions.
Where You Find Alert Definitions

To manage your alert definitions, in the menu, click Alerts and then in the left pane, click Alert
Settings > Alert Definitions.
VMware, Inc. 344

Table 4-89. Alert Definition Options

Option Description
Toolbar options Use the toolbar options to manage your alert definitions.
n Add. Add an alert definition.
n Edit. Modify the selected definition.
n Delete. Remove the selected definition.
n Clone. Create a copy of the selected definition so that
you can customize it for your needs.
n Export or Import. Export the selected definition so that
you can import it on another vRealize Operations
Manager instance.
create.
Name Name of the alert definition, which is also the name of the
alert that appears when the symptoms are triggered.
Adapter Type Adapter that manages the selected base object type.
Object Type Base object type against which the alert is defined.
Alert Type Metadata that is used to classify the alert when it is

generated.
You define the value on the Alert Impact page of the
workspace.
Alert Subtype Subcategory of the alert type and is the metadata that is
used to classify the alert when it is generated.
You define the value on the Alert Impact page of the
workspace.
Criticality Severity of the alert when it is generated. The criticality

includes the following possible values:
n Symptom. Alert is configured to display symptom
based criticality.
n Critical
n Immediate
n Warning
n Info
Impact Alert is configured to affect the Health, Risk, or Efficiency

badge.
Defined by Indicates who added the alert definition. The alert can be
added by an adapter, a user, or the vRealize Operations
Manager system.
Alert Definition Workspace

The alert definition process includes adding symptoms that trigger an alert and
recommendations that help you resolve the alert. The alert definitions you create with this
process are saved to your vRealize Operations Manager Alert Definition Overview list and
actively evaluated in your environment based on your configured policies.
VMware, Inc. 345

How the Alert Definition Workspace Works

You use the workspace to build alert definitions. As you create the definition, the name,
description, base object, and the alert impact. You can create or reuse existing symptoms and
recommendations as part of the alert definition. If you create symptoms and recommendations,
you add them to the definition, and they are added to the symptom and recommendations
content libraries for future use.
Where You Create an Alert Definition
To create or edit your alert definitions, in the menu, click Alerts and then in the left pane, click
Alert Settings > Alert Definitions. Click the plus sign to add a definition, or click the pencil to edit
the selected definition.
Alert Definition Workspace Options
An alert definition is identified by a name and description. The definition comprises a target
object type that is monitored for the alert, the badge that the alert affects, the set symptoms that
trigger the alert, and the recommendations that might resolve the alert.
n Alert Definition Workspace Name and Description

The name and description of the alert definition. This is the information that identifies the
alert when it is generated in vRealize Operations Manager.
n Alert Definition Workspace Base Object Type

The base object type is the object type on which the alert is generated in vRealize
Operations Manager when a symptom condition is found to be true.
n Alert Definition Workspace Alert Impact

The alert impact specifies the urgency of the alert, determines which badge the alert affects,
how critical the alert is to the functioning of your environment, and how it is classified when
you or the system processes a generated alert.
n Alert Definition Workspace Add Symptom Definitions

The add symptom definitions options are the mechanisms you use to add existing
symptoms or to create new symptoms for the alert definition. If the symptom that you need
for an alert definition does not exist, you can create it from this workspace.
n Alert Definition Workspace Add Recommendations

Recommendations are instructions you provide to your user so that they can resolve
generated alerts. The recommendations might include actions.
Alert Definition Workspace Name and Description

The name and description of the alert definition. This is the information that identifies the alert
when it is generated in vRealize Operations Manager.
Where You Define Name and Description
To create or edit your alert definitions, in the menu, click Alerts and then in the left pane,
clickAlert Settings > Alert Definitions. Click the plus sign to add a definition, or click the pencil to
edit the selected definition. In the workspace, on the left, click Name and Description.
VMware, Inc. 346

Table 4-90. Alert Definition Name and Description Options

Option Description
Name Name of the alert as it appears when the alert is

generated.
Description Description of the alert as it appears when the alert is

generated. Provide a useful description for your users.
Alert Definition Workspace Base Object Type

The base object type is the object type on which the alert is generated in vRealize Operations
Manager when a symptom condition is found to be true.
Where You Define the Base Object Type
the selected definition. In the workspace, on the left, click Base Object Type.
Alert Details
Notes
Table 4-91. Base Object Type Options

Option Description
Base Object Type The object type against which the alert definition is
evaluated and the alert is generated.
The drop-down menu includes all of the object types in
your environment. You can define an alert definition
based on one object type.
Alert Definition Workspace Alert Impact

The alert impact specifies the urgency of the alert, determines which badge the alert affects, how
critical the alert is to the functioning of your environment, and how it is classified when you or the
system processes a generated alert.
Where You Define the Alert Impact
clickAlert Settings > Alert Definitions. Click the plus sign to add a definition, or click the pencil to
edit the selected definition. In the workspace, on the left, click Alert Impact.
VMware, Inc. 347

Table 4-92. Alert Impact Options

Option Description
Impact Select the badge that is affected if the alert is generated.

You can select a badge based on the urgency of the
alert.
n Health. Alert requires immediate attention.
n Risk. Alert should be addressed soon after it is
triggered, either in days or weeks.
n Efficiency. Alert should be addressed in the long term
to optimize your environment.
Criticality Severity of the alert that is communicated as part of the

alert notification.
Select one of the following values.
n Info. Informational purposes only. Does not affect
badge color.
n Warning. Lowest level. Displays yellow.
n Immediate. Medium level. Displays orange.
n Critical. Highest level. Displays red.
n Symptom Based. In addition to alert criticality, each
symptom includes a defined criticality. Criticality of
the alert is determined by the most critical of all of
the triggered symptoms. The color is dynamically
determined accordingly. It you negate symptoms, the
negative symptoms to not contribute to the criticality
of a symptom-based alert.
Alert Type and Subtype Select the type and subtype of alert.
This value is metadata that is used to classify the alert
when it is generated, and the information is carried to the
alert, including the alert notification.
You can use the type and subtype information to route
the alert to the appropriate personnel and department in
your organization.
VMware, Inc. 348

Table 4-92. Alert Impact Options (continued)

Option Description
Wait Cycle The symptoms included in the alert definition remain

triggered for this number of collection cycles before the
alert is generated.
The value must be 1 or greater.
This setting helps you adjust for sensitivity in your
environment. The wait cycle for the alert definition is
added to the wait cycle for the symptom definitions. In
most definitions you configure the sensitivity at the level
of symptom level and configure the wait cycle of alert
definition to 1. This configuration ensures that after all of
the symptoms are triggered at the desired symptom
sensitivity level, the alert is immediately triggered.
Cancel Cycle The symptoms are cancelled for this number of collection
cycles after which the alert is cancelled.
The value must be 1 or greater.
This setting helps you adjust for sensitivity in your
environment. The cancel cycle for the alert definition is
added to the cancel cycle for the symptom definitions. In
most definitions you configure the sensitivity at the level
of symptom level and configure the wait cycle of the
alert definition to 1. This configuration ensures that after
all of the symptom conditions disappear after the desired
symptom cancel cycle, the alert is immediately canceled.
Alert Definition Workspace Add Symptom Definitions

The add symptom definitions options are the mechanisms you use to add existing symptoms or
to create new symptoms for the alert definition. If the symptom that you need for an alert
definition does not exist, you can create it from this workspace.
How the Add Symptom Definitions Options Work
You can select and add symptoms defined for the base object type, and you can add symptoms
for related object types. As you add one or more symptoms, you create a symptom expression.
If this expression is evaluated as true, then the alert is generated.
Where You Define the Symptom Definitions
the selected definition. In the workspace, on the left, click Add Symptom Definitions.
Add Symptoms Definitions Options
To add symptom definitions, you use the left pane to select your symptoms. You use the
workspace on the right to define the point at which the symptoms or symptom sets are true. You
also use the workspace to specify whether all or any of the symptoms or symptom sets must be
true to generate an alert.
VMware, Inc. 349

Table 4-93. Add Symptoms Selection Options

Option Description
Defined On Object that the symptom evaluates.

As you create alert definitions, you can select or define symptoms for the base object
type and for related object types, based on the object relationship hierarchy. The
following relationships are object types as they relate to the alert definition base object
type.
n Self. A base object type for the alert definition. For example, host system.
n Descendant. An object type that is at any level below the base object type, either a
direct or indirect child object. For example, a virtual machine is a descendant of a
host system.
n Ancestor. An object type that is one or more levels higher than the base object
type, either a direct or indirect parent. For example, a datacenter and a vCenter
Server are ancestors of a host system.
n Parent. An object type that is in an immediately higher level in the hierarchy from
the base object type. For example, a datacenter is a parent of a host system.
n Child. An object type that is one level below the base object type. For example, a
virtual machine is a child of a host system.
Filter by Object Type Available only when you select a Defined On value other than Self.
Limits the symptoms to those that are configured for the selected object type based
on the selected Defined On relationship.
VMware, Inc. 350

Table 4-93. Add Symptoms Selection Options (continued)

Option Description
Symptom Definition Type Select the type of symptom definition that you are adding for the current Defined On
object type.
n Metric / Supermetric. Add symptoms that use metric and super metric symptoms.
These metrics are based on the operational or performance values that vRealize
Operations Managercollects from target objects in your environment.
n Property. Add symptoms that use property symptoms. These symptoms are based
on the configuration properties that vRealize Operations Manager collects from the
target objects in your environment.
n Message Event. Add symptoms that use message event symptoms. These
symptoms are based on events received as messages from a component of
vRealize Operations Manager or from an external monitored system through the
system's REST API.
n Fault Event. Add symptoms that use fault symptoms. These symptoms are based
on events that monitored systems publish. vRealize Operations Manager correlates
a subset of these events and delivers them as faults. Faults are intended to signify
events in the monitored systems that affect the availability of objects in your
environment.
n Metric Event. Add symptoms that use metric event symptoms. These symptoms
are based on events communicated from a monitored system where the selected
metric violates a threshold in a specified manner. The external system manages the
threshold, not vRealize Operations Manager. These symptoms are based on
conditions reported for selected metrics by an external monitored system, as
compared to metric symptoms, which are based on thresholds that vRealize
Operations Manager is actively monitoring.
n Smart Early Warning. Add a symptom that uses a defined condition that is
triggered when the number of anomalies on an object is over the trending
threshold. This symptom represents the overall anomalous behavior of the object.
Anomalies are based on vRealize Operations Manager analysis of the number of
applicable metrics that violate the dynamic threshold that determines the normal
operating behavior of the object. This symptom is not configurable. You either use
it or you do not use it.
Add symptom button If symptoms that you need for your alert do not exist, you can create them.
Opens the symptoms definition dialog box.
Not available for Smart Early Warning symptoms, which are predefined in the system.
All Filters Filter the list of symptom definitions. This selection is available when Defined On is set
to Self, or when it is set to another relationship and you select an object from the Filter
by Object Type drop-down menu.
n Symptom. Type text to search on the name of the symptom definitions. For
example, to display all symptom definitions that have efficiency in their name, type
Efficiency.
n Defined By. Type text to search for the name of the adapter that defined the
symptom definitions. For example, to display all symptom definitions provided by
the vCenter Adapter, type vCenter. To display only user-defined symptom
definitions, type the search term User.
To clear a filter, click the double arrow icon and the red x that appears next to the filter
name.
VMware, Inc. 351

Table 4-93. Add Symptoms Selection Options (continued)

Option Description
Quick filter (Name) Search the list based on the symptom name.
Symptoms list List of existing symptoms for the selected object type. To configure a symptom, drag it
into the workspace.
To combine symptoms that are based on multiple levels in the hierarchy, select the
new Defined On level and Filter by Object Type before you select and drag the new
symptom to the workspace.
Use the workspace to configure the interaction of the symptoms and symptom sets.
Table 4-94. Symptom Sets in the Alert Definition Workspace

Option Description
Alert Definition Summary The currently configured information for the alert definition. Use the information
as reference when you create alert definitions.
Symptoms The symptom sets comprise an expression that is evaluated to determine if an

alert should be triggered.
To add one or more symptoms from the symptom list to an existing symptom
set, drag the symptom from the list to the symptom set. To create a new
symptom set for the alert definition, drag a symptom to the landing area
outlined with a dotted line.
VMware, Inc. 352

Table 4-94. Symptom Sets in the Alert Definition Workspace (continued)

Option Description
Match {operator} of the following Select the operator for all of the added symptom sets. Available only when you
symptom sets add more than one symptom set.
n All. All of the symptom sets must be true before the alert is generated.
Operates as a Boolean AND.
n Any. One or more of the symptom sets must be true before the alert is
generated. Operates as a Boolean OR.
Symptom sets Add one or more symptoms to the workspace, define the points at which the
symptom sets are true, and specify whether all or any of the symptoms in the
symptom set must be true to generate the alert.
A symptom set can include one or more symptoms, and an alert definition can
include one or more symptom sets.
If you create a symptom set where the Defined On object is Self, you can set
the operator for multiple symptoms in the symptom set.
If you create a symptom set where the Defined On object is a relationship other
than Self, you can set the operator and modify the triggering threshold. To
configure the symptom set criteria, you set the options.
n Value operator. Specifies how the value you provide in the value text box is
compared to a number of related objects to evaluate the symptom set as
true.
n Value text box. Number of objects of the specified relationship, based on
the value type, that are required to evaluate the symptom set as true.
n Value type. Possible types include the following items:
n Count. Exact number of related objects meet the symptom set criteria.
n Percent. Percentage of total related objects meet the symptom set
criteria.
n Any. One or more of the related objects meet the symptom set criteria.
n All. All of the related objects meet the symptom set criteria.
n Symptom set operator. Operator applied between symptoms in the
symptom set.
n All. All of the symptoms must be true before the alert is generated.
Operates as a Boolean AND.
n Any. One or more of the symptoms must be true before the alert is
generated. Operates as a Boolean OR.
When you include a symptom in a symptom set, the condition must become
true to trigger the symptom set. However, you might want to configure a
symptom set where the absence of a symptom condition triggers a symptom.
To use the absence of the symptom condition, click the Negate This Symptom
Condition icon to the left of the symptom name.
Although you can configure symptom criticality, if you negate a symptom, it
does not have an associated criticality that affects the criticality of generated
alerts.
Alert Definition Workspace Add Recommendations

Recommendations are instructions you provide to your user so that they can resolve generated
alerts. The recommendations might include actions.
How Add Recommendations Works
VMware, Inc. 353

Recommendations are information provided to users to resolve a problem when an alert is

generated. You use the recommendation options to add existing information or to create
solutions to alerts. If the recommendation that you need for an alert definition does not exist, you
can create it from this workspace.
Where You Find the Add Recommendation Options
clickAlert Settings > Alert Definitions. Click the plus sign to add a definition or click the pencil to
edit the selected definition..In the workspace, on the left, click Add Recommendations.
Table 4-95. Add Recommendations Options in the Alert Definition Workspace

Option Description
Add recommendation If recommendations that you need to resolve the

symptoms in the problem do not exist, you can create
them.
Quick filter (Name) Limits the list based on the text you type.
List of available recommendations. List of existing recommendations that you can drag to
the workspace.
Recommendations are instructions and, where possible,
actions that assist you with resolving alerts when they
are triggered.
Recommendation workspace Add one or more recommendations to the workspace.

If you add more than one recommendation, you can drag
the recommendations to change the priority order in the
table.
Create a New Alert Definition

Based on the root cause of the problem, and the solutions that you used to fix the problem, you
can create a new alert definition for vRealize Operations Manager to alert you. When the alert is
triggered on your host system, vRealize Operations Manager alerts you and provides
recommendations on how to solve the problem.
To alert you before your host systems experience critical capacity problems, and have vRealize
Operations Manager notify you of problems in advance, you create alert definitions, and add
symptom definitions to the alert definition.
Procedure
1 In the menu, click Alerts and then in the left pane, select Alert Settings > Alert Definitions.
2 Enter capacity in the search text box.
Review the available list of capacity alert definitions. If a capacity alert definition does not
exist for host systems, you can create one.
VMware, Inc. 354

3 Click the plus sign to create a new capacity alert definition for your host systems.
a In the alert definition workspace, for the Name and Description, enter
Hosts - Alert on Capacity Exceeded.
b For the Base Object Type, select vCenter Adapter > Host System
c For the Alert Impact, select the following options.
Option Selection
Impact Select Risk.
Criticality Select Immediate.
Alert Type and Subtype Select Application : Capacity.
Wait Cycle Select 1.
Cancel Cycle Select 1.
d For Add Symptom Definitions, select the following options.
Option Selection
Defined On Select Self.
Symptom Definition Type Select Metric / Supermetric.
Quick filter (Name) Enter capacity.
e From the Symptom Definition list, click Host System Capacity Remaining is moderately
low and drag it to the right pane.
In the Symptoms pane, make sure that the Base object exhibits criteria is set to All by
default.
f For Add Recommendations, enter virtual machine in the quick filter text box.
g Click Review the symptoms listed and remove the number of vCPUs from the virtual
machine as recommended by the system, and drag it to the recommendations area in
the right pane.
This recommendation is set to Priority 1.
4 Click Save to save the alert definition.
Your new alert appears in the list of alert definitions.
Results
You have added an alert definition to have vRealize Operations Manager alert you when the
capacity of your host systems begins to run out.
Alert Definition Best Practices

As you create alert definitions for your environment, apply consistent best practices so that you
optimize alert behavior for your monitored objects.
VMware, Inc. 355

Alert Definitions Naming and Description

The alert definition name is the short name that appears in the following places:
n In data grids when alerts are generated
n In outbound alert notifications, including the email notifications that are sent when outbound
alerts and notifications are configured in your environment
Ensure that you provide an informative name that clearly states the reported problem. Your
users can evaluate alerts based on the alert definition name.
The alert definition description is the text that appears in the alert definition details and the
outbound alerts. Ensure that you provide a useful description that helps your users understand
the problem that generated the alert.
Wait and Cancel Cycle

The wait cycle setting helps you adjust for sensitivity in your environment. The wait cycle for the
alert definition goes into effect after the wait cycle for the symptom definition results in a
triggered symptom. In most alert definitions you configure the sensitivity at the symptom level
and configure the wait cycle of alert definition to 1. This configuration ensures that the alert is
immediately generated after all of the symptoms are triggered at the desired symptom sensitivity
level.
The cancel cycle setting helps you adjust for sensitivity in your environment. The cancel cycle for
the alert definition goes into affect after the cancel cycle for the symptom definition results in a
cancelled symptom. In most definitions you configure the sensitivity at the symptom level and
configure the cancel cycle of alert definition to 1. This configuration ensures that the alert is
immediately cancelled after all of the symptoms conditions disappear after the desired symptom
cancel cycle.
Create Alert Definitions to Generate the Fewest Alerts

You can control the size of your alert list and make it easier to manage. When an alert is about a
general problem that can be triggered on a large number of objects, configure its definition so
that the alert is generated on a higher level object in the hierarchy rather than on individual
objects.
As you add symptoms to your alert definition, do not overcrowd a single alert definition with
secondary symptoms. Keep the combination of symptoms as simple and straightforward as
possible.
You can also use a series of symptom definitions to describe incremental levels of concern. For
example, Volume nearing capacity limit might have a severity value of Warning while Volume
reached capacity limit might have a severity level of Critical. The first symptom is not an
immediate threat, but the second one is an immediate threat. You can then include the Warning
and Critical symptom definitions in a single alert definition with an Any condition and set the alert
criticality to be Symptom Based. These settings cause the alert to be generated with the right
criticality if either of the symptoms is triggered.
VMware, Inc. 356

Avoid Overlapping and Gaps Between Alerts

Overlaps result in two or more alerts being generated for the same underlying condition. Gaps
occur when an unresolved alert with lower severity is canceled, but a related alert with a higher
severity cannot be triggered.
A gap occurs in a situation where the value is <=50% in one alert definition and >=75% in a
second alert definition. The gap occurs because when the percentage of volumes with high use
falls between 50 percent and 75 percent, the first problem cancels but the second does not
generate an alert. This situation is problematic because no alert definitions are active to cover the
gap.
Actionable Recommendations
If you provide text instructions to your users that help them resolve a problem identified by an
alert definition, precisely describe how the engineer or administrator should fix the problem to
resolve the alert.
To support the instructions, add a link to a wiki, runbook, or other sources of information, and
add actions that you run from vRealize Operations Manageron the target systems.
Creating and Managing vRealize Operations Manager Alert Notifications

When alerts are generated in vRealize Operations Manager, they appear in the alert details and
object details, but you can also configure vRealize Operations Manager to send your alerts to
outside applications using one or more outbound alert options.
You configure notification options to specify which alerts are sent out for the Standard Email,
REST, SNMP, and Log File outbound alert plug-ins. For the other plug-in types, all the alerts are
sent when the target outbound alert plug-in is enabled.
The most common outbound alert plug-in is the Standard Email plug-in. You configure the
Standard Email plug-in to send notifications to one or more users when an alert is generated that
meets the criteria you specify in the notification settings.
List of Outbound Plug-Ins in vRealize Operations Manager

vRealize Operations Manager provides outbound plug-ins. This list includes the name of the plug-
in and whether you can filter the outbound data based on your notification settings.
If the plug-in supports configuring notification rules, then you can filter the messages before they
are sent to the target system. If the plug-in does not support notifications, all messages are sent
to the target system, and you can process them in that application.
If you installed other solutions that include other plug-in options, they appear as a plug-in option
with the other plug-ins.
Messages and alerts are sent only when the plug-in is enabled.
VMware, Inc. 357

Table 4-96. Notification Support for Outbound Plug-Ins

Outbound Plug-In Configure Notification Rules
Automated Action Plug-in No

The Automated Action plug-in is enabled by default. If automated actions stop working,
select the Automated Action plug-in and enable it if necessary. If you edit the Automated
Action plug-in, you only have to provide the instance name.
Log File Plug-In Yes

To filter the log file alerts, you can either configure the file named TextFilter.xml or
configure the notification rules.
Smarts SAM Notification No

Plug-In
REST Notification Plug-In Yes
Network Share Plug-In No
Standard Email Plug-In Yes
SNMP Trap Plug-In Yes
Service-Now Notification Yes

Plugin
Add Outbound Notification Plug-Ins in vRealize Operations Manager

You add outbound plug-in instances so that you can notify users about alerts or capture alert
data outside of vRealize Operations Manager.
You can configure one or more instances of the same plug-in type if you need to direct alert
information to multiple target systems.
The Automated Action plug-in is enabled by default. If automated actions stop working, check
the Automated Action plug-in and enable it if necessary. If you edit the Automated Action plug-
in, you only need to provide the instance name.
n Add a Standard Email Plug-In for vRealize Operations Manager Outbound Alerts
You add a Standard Email Plug-In so that you can use Simple Mail Transfer Protocol (SMTP)
to email vRealize Operations Manager alert notifications to your virtual infrastructure
administrators, network operations engineers, and other interested individuals.
n Add a REST Plug-In for vRealize Operations Manager Outbound Alerts

You add a REST Plug-In so that you can send vRealize Operations Manager alerts to another
REST-enabled application where you built a REST Web service to accept these messages.
n Add a Log File Plug-In for vRealize Operations Manager Outbound Alerts
You add a Log File plug-in when you want to configure vRealize Operations Manager to log
alerts to a file on each of your vRealize Operations Manager nodes. If you installed vRealize
Operations Manager as a multiple node cluster, each node processes and logs the alerts for
the objects that it monitors. Each node logs the alerts for the objects it processes.
VMware, Inc. 358

n Add a Network Share Plug-In for vRealize Operations Manager Reports

You add a Network Share plug-in when you want to configure vRealize Operations Manager
to send reports to a shared location. The Network Share plug-in supports only SMB version
2.1. Note that SMB version 1.0 is not supported.
n Add an SNMP Trap Plug-In for vRealize Operations Manager Outbound Alerts
You add an SNMP Trap plug-in when you want to configure vRealize Operations Manager to
log alerts on an existing SNMP Trap server in your environment.
n Add a Smarts Service Assurance Manager Notification Plug-In for vRealize Operations
Manager Outbound Alerts
You add a Smarts SAM Notification plug-in when you want to configure vRealize Operations
Manager to send alert notifications to EMC Smarts Server Assurance Manager.
n Add a Service-Now Notification Plug-In for Outbound Alerts

You add a Service-Now Notification plug-in when you want to integrate Service Now
ticketing system with vRealize Operations Manager. Service Now creates an incident
whenever an alert is triggered in vRealize Operations Manager.
Add a Standard Email Plug-In for vRealize Operations Manager Outbound Alerts
You add a Standard Email Plug-In so that you can use Simple Mail Transfer Protocol (SMTP) to
email vRealize Operations Manager alert notifications to your virtual infrastructure administrators,
network operations engineers, and other interested individuals.
Prerequisites
Ensure that you have an email user account that you can use as the connection account for the
alert notifications. If you choose to require authentication, you must also know the password for
this account.
Procedure
1 In the menu, click Administration and then in the left pane, click Management.
2 Click Outbound Settings and click the plus sign to add a plug-in.
3 From the Plug-In Type drop-down menu, select Standard Email Plugin.
The dialog box expands to include your SMTP settings.
4 Enter an Instance Name.
This is the name that identifies this instance that you select when you later configure
notification rules.
VMware, Inc. 359

5 Configure the SMTP options appropriate for your environment.
Option Description
Use Secure Connection Enables secure communication encryption using SSL/TLS. If you select this
option, you must select a method in the Secure Connection Type drop-
down menu.
Requires Authentication Enables authentication on the email user account that you use to configure
this SMTP instance. If you select this option, you must provide a password
for the user account.
SMTP Host URL or IP address of your email host server.
SMTP Port Default port SMTP uses to connect with the server.
Secure Connection Type Select either SSL/TLS as the communication encryption method used in your
environment from the drop-down menu. You must select a connection type
if you select Use Secure Connection.
User Name Email user account that is used to connect to the email server.
Password Password for the connection user account. A password is required if you
select Requires Authentication.
Sender Email Address Email address that appears on the notification message
Sender Name Displayed name for the sender email address.
6 Click Save.
7 To start the outbound alert service for this plug-in, select the instance in the list and click
Enable on the toolbar.
Results
This instance of the standard email plug-in for outbound SMTP alerts is configured and running.
What to do next
Create notification rules that use the standard email plug-in to send a message to your users
about alerts requiring their attention. See User Scenario: Create a vRealize Operations Manager
Email Alert Notification .
Add a REST Plug-In for vRealize Operations Manager Outbound Alerts
You add a REST Plug-In so that you can send vRealize Operations Manager alerts to another
REST-enabled application where you built a REST Web service to accept these messages.
The REST Plug-In supports enabling an integration, it does not provide an integration. Depending
on your target application, you might need an intermediary REST service or some other
mechanism that will correlate the alert and object identifiers included in the REST alert output
with the identifiers in your target application.
VMware, Inc. 360

Determine which content type you are delivering to your target application. If you select
application/json, the body of the POST or PUT calls that are sent have the following format.
Sample data is included.
{
"startDate":1369757346267,
"criticality":"ALERT_CRITICALITY_LEVEL_WARNING",
"Risk":4.0,
"resourceId":"sample-object-uuid",
"alertId":"sample-alert-uuid",
"status":"ACTIVE",
"subType":"ALERT_SUBTYPE_AVAILABILITY_PROBLEM",
"cancelDate":1369757346267,
"resourceKind":"sample-object-type",
"alertName":"Invalid IP Address for connected Leaf Switch",
"attributeKeyID":5325,
"Efficiency":1.0,
"adapterKind":"sample-adapter-type",
"Health":1.0,
"type":"ALERT_TYPE_APPLICATION_PROBLEM",
"resourceName":"sample-object-name",
"updateDate":1369757346267,
"info":"sample-info"
}
If you select application/xml, the body of the POST or PUT calls that are sent have the following
format:
<alert>
<startDate>1369757346267</startDate>
<criticality>ALERT_CRITICALITY_LEVEL_WARNING</criticality>
<Risk>4.0</Risk>
<resourceId>sample-object-uuid</resourceId>
<alertId>sample-alert-uuid</alertId>
<status>ACTIVE</status>
<subType>ALERT_SUBTYPE_AVAILABILITY_PROBLEM</subType>
<cancelDate>1369757346267</cancelDate>
<resourceKind>sample-object-type</resourceKind>
<alertName>Invalid IP Address for connected Leaf Switch</alertName>
<attributeKeyId>5325</attributeKeyId>
<Efficiency>1.0</Efficiency>
<adapterKind>sample-adapter-type</adapterKind>
<Health>1.0</Health>
<type>ALERT_TYPE_APPLICATION_PROBLEM</type>
<resourceName>sample-object-name</resourceName>
<updateDate>1369757346267</updateDate>
<info>sample-info</info>
</alert>
Note If the alert is triggered by a non-metric violation, the attributeKeyID is omitted from the
REST output and is not sent.
VMware, Inc. 361

If the request is processed as POST, for either JSON or XML, the Web service returns an HTTP
status code of 201, which indicates the alert was successfully created at the target. If the request
is processed as PUT, the HTTP status code of 202, which indicates the alert was successfully
accepted at the target.
Prerequisites
Ensure that you know how and where the alerts sent using the REST plug-in are consumed and
processed in your environment, and that you have the appropriate connection information
available.
Procedure
1 In the left pane of vRealize Operations Manager, click the Administration icon.
3 From the Plug-In Type drop-down menu, select Rest Notification Plugin.
The dialog box expands to include your REST settings.
notification rules.
5 Configure the Rest options appropriate for your environment.
Option Description
URL URL to which you are sending the alerts. The URL must support HTTPS.
When an alert is sent to the REST Web server, the plug-in appends /
{alertID} to the POST or PUT call.
User Name User account on the target REST system.
Password User account password.
Content Type Specify the format for the alert output.

n application/json. Alert data is transmitted using JavaScript Object
Notation as human-readable text.
n application/xml. Alert data is transmitted using XML that is human-
readable and machine-readable content.
Certificate thumbprint Thumbprint for the public certificate for your HTTPS service. Either the SHA1
or SHA256 algorithm can be used.
Connection count Limits the number of simultaneous alerts that are sent to the target REST
server. Use this number to ensure that your REST server is not overwhelmed
with requests.
6 Click Save.
VMware, Inc. 362

Results
This instance of the REST plug-in for outbound alerts is configured and running.
What to do next
Create notification rules that use the REST plug-in to send alerts to a REST-enabled application or
service in your environment. See User Scenario: Create a vRealize Operations Manager REST
Alert Notification.
Add a Log File Plug-In for vRealize Operations Manager Outbound Alerts
You add a Log File plug-in when you want to configure vRealize Operations Manager to log alerts
to a file on each of your vRealize Operations Manager nodes. If you installed vRealize Operations
Manager as a multiple node cluster, each node processes and logs the alerts for the objects that
it monitors. Each node logs the alerts for the objects it processes.
All alerts are added to the log file. You can use other applications to filter and manage the logs.
Prerequisites
Ensure that you have write access to the file system path on the target vRealize Operations
Manager nodes.
Procedure
3 From the Plug-In Type drop-down menu, select Log File.
The dialog box expands to include your log file settings.
4 In the Alert Output Folder text box, enter the folder name.
If the folder does not exist in the target location, the plug-in creates the folder in the target
location. The default target location is: /usr/lib/vmware-vcops/common/bin/.
5 Click Save.
Results
This instance of the log file plug-in is configured and running.
What to do next
When the plug-in is started, the alerts are logged in the file. Verify that the log files are created in
the target directory as the alerts are generated, updated, or canceled.
Add a Network Share Plug-In for vRealize Operations Manager Reports
You add a Network Share plug-in when you want to configure vRealize Operations Manager to
send reports to a shared location. The Network Share plug-in supports only SMB version 2.1. Note
that SMB version 1.0 is not supported.
VMware, Inc. 363

Prerequisites
Verify that you have read, write, and delete permissions to the network share location.
Procedure
1 In the menu, click Administration and then in the left pane, click Management > Outbound
Settings.
2 From the toolbar, click the Add icon.
3 From the Plug-In Type drop-down menu, select Network Share Plug-in.
The dialog box expands to include your plug-in instance settings.
notification rules.
5 Configure the Network Share options appropriate for your environment.
Option Description
Domain Your shared network domain address.
User Name The domain user account that is used to connect to the network.
Password The password for the domain user account.
Network share root The path to the root folder where you want to save the reports. You can
specify subfolders for each report when you configure the schedule
publication.
You must enter an IP address. For example, \\IP_address\ShareRoot. You
can use the host name instead of the IP address if the host name is resolved
to an IPv4 when accessed from the vRealize Operations Manager host.
Note Verify that the root destination folder exists. If the folder is missing,
the Network Share plug-in logs an error after 5 unsuccessful attempts.
6 Click Test to verify the specified paths, credentials, and permissions.
The test might take up to a minute.
7 Click Save.
The outbound service for this plug-in starts automatically.
8 (Optional) To stop an outbound service, select an instance and click Disable on the toolbar.
Results
This instance of the Network Share plug-in is configured and running.
What to do next
Create a report schedule and configure it to send reports to your shared folder. See Schedule
Reports Overview.
VMware, Inc. 364

Add an SNMP Trap Plug-In for vRealize Operations Manager Outbound Alerts
You add an SNMP Trap plug-in when you want to configure vRealize Operations Manager to log
alerts on an existing SNMP Trap server in your environment.
You can provide filtering when you define a Notification using an SNMP Trap destination.
Prerequisites
Ensure that you have an SNMP Trap server configured in your environment, and that you know
the IP address or host name, port number, and community that it uses.
Procedure
3 From the Plug-In Type drop-down menu, select SNMP Trap.
The dialog box expands to include your SNMP trap settings.
4 Type an Instance Name.
5 Configure the SNMP trap settings appropriate to your environment.
Option Description
Destination Host IP address or fully qualified domain name of the SNMP management system
to which you are sending alerts.
Port Port used to connect to the SNMP management system. Default port is 162.
Community Text string that allows access to the statistics. SNMP Community strings are
used only by devices that support SNMPv3 protocol.
Username Username to configure SNMP trap settings in your environment. If the

username is specified, SNMPv3 is considered as the protocol by the plugin.
If left blank, SNMPv2c is considered as the protocol by the plugin.
Authentication Protocol Authentication algorithms available are SHA-224, SHA-256, SHA-384,

SHA-512.
Authentication Password Authentication password.
Privacy Protocol Privacy algorithms available are AES192, AES2564.
Privacy Password Privacy password.
6 Click Save.
Results
This instance of the SNMP Trap plug-in is configured and running.
What to do next
When the plug-in is added, Configuring Notifications for receiving the SNMP traps.
VMware, Inc. 365

Add a Smarts Service Assurance Manager Notification Plug-In for vRealize Operations Manager
Outbound Alerts
You add a Smarts SAM Notification plug-in when you want to configure vRealize Operations
Manager to send alert notifications to EMC Smarts Server Assurance Manager.
This outbound alert option is useful when you manage the same objects in Server Assurance
Manager and in vRealize Operations Manager, and you added the EMC Smarts management pack
and configured the solution in vRealize Operations Manager. Although you cannot filter the alerts
sent to Service Assurance Manager in vRealize Operations Manager, you can configure the
Smarts plug-in to send the alerts to the Smarts Open Integration server. You then configure the
Open Integration server to filter the alerts from vRealize Operations Manager, and send only
those that pass the filter test to the Smarts Service Assurance Manager service.
Prerequisites
n Verify that you configured the EMC Smarts solution. For documentation regarding EMC
Smarts integration, see https://solutionexchange.vmware.com/store.
n Ensure that you have the EMC Smarts Broker and Server Assurance Manager instance host
name or IP address, user name, and password.
Procedure
3 From the Plug-In Type drop-down menu, select Smarts SAM Notification.
The dialog box expands to include your Smarts settings.
notification rules.
5 Configure the Smarts SAM notification settings appropriate for your environment.
Option Description
Broker Type the host name or IP address of the EMC Smarts Broker that manages
registry for the Server Assurance Manager instance to which you want the
notifications sent.
Broker Username If the Smarts broker is configured as Secure Broker, type the user name for
the Broker account.
Broker Password If the Smarts broker is configured as Secure Broker, type the password for
the Broker user account.
SAM Server Type the host name or IP address of the Server Assurance Manager server
to which you are sending the notifications.
VMware, Inc. 366

Option Description
User Name Type the user name for the Server Assurance Manager server instance. This
account must have read and write permissions for the notifications on the
Smarts server as specified in the SAM Server.
Password Type the password for the Server Assurance Manager server account.
6 Click Save.
7 Modify the Smarts SAM plug-in properties file.
a Open the properties file at: /usr/lib/vmware-vcops/user/plugins/outbound/vcops-

smartsalert-plugin/conf/plugin.properties
b Add the following string to the properties file: #

sendByType=APPLICATION::AVAILABILITY,APPLICATION::PERFORMANCE,APPLICATION::CAPACITY,AP
PLICATION::COMPLIANCE,VIRTUALIZATION::AVAILABILITY,VIRTUALIZATION::PERFORMANCE,VIRTUAL
IZATION::CAPACITY,VIRTUALIZATION::COMPLIANCE,HARDWARE::AVAILABILITY,HARDWARE::PERFORMA
NCE,HARDWARE::CAPACITY,HARDWARE::COMPLIANCE,STORAGE::AVAILABILITY,STORAGE::PERFORMANCE
,STORAGE::CAPACITY,STORAGE::COMPLIANCE,NETWORK::AVAILABILITY,NETWORK::PERFORMANCE,NETW
ORK::CAPACITY,NETWORK::COMPLIANCE
c Save the properties file.
Results
This instance of the Smarts SAM Notifications plug-in is configured and running.
What to do next
In Smarts Service Assurance Manager, configure your Notification Log Console to filter the alerts
from vRealize Operations Manager. To configure the filtering for Service Assurance Manager, see
the EMC Smarts Service Assurance Manager documentation.
Add a Service-Now Notification Plug-In for Outbound Alerts
You add a Service-Now Notification plug-in when you want to integrate Service Now ticketing
system with vRealize Operations Manager. Service Now creates an incident whenever an alert is
triggered in vRealize Operations Manager.
Using Service-Now Notification Plug-In you can send alert notifications to the Service Now
ticketing system to create incidents. The incident includes information like the Caller, Category,
Subcategory, Business Service, and other attributes related to alerts.
Prerequisites
Ensure that you have log in credentials for Service-Now.
Ensure that you are assigned with IT Infrastructure Library (ITIL) role in Service Now.
VMware, Inc. 367

Procedure
Settings.
3 From the Plug-In Type drop-down menu, select Service-Now Notification Plug-in.
5 Enter the Service Now URL.
https://dev22418.service-now.com/
6 Enter the user name and password for Service Now.
7 Enter a value for the Connection Count.
The connection count represents the maximum number of open connections allowed per
node in vRealize Operations Manager.
8 To verify the specified paths, credentials, and permissions, click Test.
9 Click Save.
Results
This instance of the Service-Now Notifications plug-in is configured and running.
What to do next
When the plug-in is added, Configuring Notifications for creating incidents in Service-Now
ticketing system.
Outbound Settings
You use the Outbound Settings to manage your communication settings so that you can send
information to users or applications outside of vRealize Operations Manager.
How Outbound Settings Work
You manage your outbound options from this page, including adding or editing outbound plug-
ins, and turning the configured plug-ins on or off. When enabled, the plug-in sends a message to
users as email notifications, or sends a message to other applications.
Where You Find Outbound Settings
To manage your outbound settings, select Administration in the left pane, and click Outbound
Settings.
VMware, Inc. 368

Table 4-97. Outbound Settings Options

Option Description
Toolbar options Use the toolbar options to manage your Outbound Plug-
Ins.
n Add or Edit. Opens the Outbound Plug-In dialog box
where you configure the connection options for the
instance.
n Delete. Removes the selected plug-in instance.
n Enable or Disable. Starts or stops the plug-in instance.
Disabling an instance allows you to stop sending the
messages configured for the plug-in without removing
the configuration from your environment.
Instance Name Name that you assigned when you created the plug-in
instance.
Plug-In Type Type of configured plug-in for the plug-in instance. The
types of plug-ins vary depending on the solutions you
added to your environment.
The most common plug-in types include standard email,
SNMP trap, log file, and REST.
Status Specifies whether the plug-in is currently running.
Outbound Plug-Ins
Outbound plug-in settings determine how the supported external notification systems connect to
their target systems. You configure one or more instances of one or more plug-in types so that
you can send data about generated notifications outside of vRealize Operations Manager.
How Outbound Plug-Ins Work
You configure each plug-in with the required information, including destination locations, hosts,
ports, user names, passwords, instance name, or other information that is required to send
notifications to those target systems. The target systems can include email recipients, log files, or
other management products.
Some plug-ins are included with vRealize Operations Manager, and others might be added when
you add a management pack as a solution.
Where You Configure Outbound Settings
To add or edit an outbound plug-in, select Administration in the top pane, and click Outbound
Settings under Management. On the toolbar, click the plus sign to add a plug-in instance, or
select a plug-in from the list and click the pencil to edit the existing plug-in.
Outbound Plug-In Configuration Options
The configuration options vary depending on which plug-in you select from the Plug-In Type
drop-down menu.
VMware, Inc. 369

Configuring Notifications
Notifications are alert notifications that meet the filter criteria in the notification rules before they
are sent outside vRealize Operations Manager. You configure notification rules for the supported
outbound alerts so that you can filter the alerts that are sent to the selected external system.
You use the notifications list to manage your rules. You then use the notification rules to limit the
alerts that are sent to the external system. To use notifications, the supported outbound alert
plug-ins must be added and running.
With notification rules, you can limit the data that is sent to the following external systems.
n Standard Email. You can create multiple notification rules for various email recipients based
on one or more of the filter selections. If you add recipients but do not add filter selections, all
the generated alerts are sent to the recipients.
n REST. You can create a rule to limit alerts that are sent to the target REST system so that you
do not need to implement filtering on that target system.
n SNMP Trap. You can configure vRealize Operations Manager to log alerts on an existing
SNMP Trap server in your environment.
n Log File. You can configure vRealize Operations Manager to log alerts to a file on each of
your vRealize Operations Manager nodes.
User Scenario: Create a vRealize Operations Manager Email Alert Notification
As a virtual infrastructure administrator, you need vRealize Operations Manager to send email
notifications to your advanced network engineers when critical alerts are generated for mmbhost
object, the host for many virtual machines that run transactional applications, where no one has
yet taken ownership of the alert.
Prerequisites
n Ensure that you have at least one alert definition for which you are sending a notification. For
an example of an alert definition, see Create an Alert Definition for Department Objects.
n Ensure that at least one instance of the standard email plug-in is configured and running. See
Add a Standard Email Plug-In for vRealize Operations Manager Outbound Alerts.
Procedure
1 In the menu, click Alerts and then in the left pane, click Alert Settings.
2 Click Notification Settings and click the plus sign to add a notification rule.
3 In the Name text box type a name similar to Unclaimed Critical Alerts for mmbhost.
4 In the Method area, select Standard Email Plug-In from the drop-down menu, and select the
configured instance of the email plug-in.
VMware, Inc. 370

5 Configure the email options.
a In the Recipients text box, type the email addresses of the members of your advance
engineering team, separating the addresses with a semi-colon (;).
b To send a second notification if the alert is still active after a specified amount of time,
type the number of minutes in the Notify again text box.
c Type number of notifications that are sent to users in the Max Notifications text box.
6 Configure the scope of filtering criteria.
a From the Scope drop-down menu, select Object.
b Click Click to select Object and type the name of the object.
In this example, type mmbhost.
c Locate and select the object in the list, and click Select.
7 Configure the Notification Trigger.
a From the Notification Trigger drop-down menu, select Impact.
b From the adjacent drop-down menu, select Health.
8 In the Criticality area, click Critical.
9 Expand the Advanced Filters and from the Alert States drop-down menu, select Open.
The Open state indicates that no engineer or administrator has taken ownership of the alert.
10 Click Save.
Results
You created a notification rule that sends an email message to the members of your advance
network engineering team when any critical alerts are generated for the mmbhost object and the
alert is not claimed by an engineer. This email reminds them to look at the alert, take ownership
of it, and work to resolve the triggering symptoms.
What to do next
Respond to alert email notifications. See User Scenario: An Alert Arrives in Your Inbox.
User Scenario: Create a vRealize Operations Manager REST Alert Notification
As a virtual infrastructure administrator, you need vRealize Operations Manager to send alerts in
JSON or XML to a REST-enabled application that has REST Web service that accepts these
messages. You want only alerts where the virtualization alerts that affect availability alert types
go to this outside application. You can then use the provided information to initiate a remediation
process in that application to address the problem indicated by the alert.
The notification configuration limits the alerts sent to the outbound alert instance to those
matching the notification criteria.
VMware, Inc. 371

Prerequisites
n Verify that you have at least one alert definition for which you are sending a notification. For
an example of an alert definition, see Create an Alert Definition for Department Objects.
n Verify that at least one instance of the REST plug-in is configured and running. See Add a
REST Plug-In for vRealize Operations Manager Outbound Alerts.
Procedure
2 Click Notifications and click the plus sign to add a notification rule.
3 In the Name text box type a name similar to Virtualization Alerts for Availability.
4 In the Method area, select REST Plug-In from the drop-down menu, and select the configured
instance of the email plug-in.
5 Configure the Notification Trigger.
a From the Notification Trigger drop-down menu, select Alert Type.
b Click Click to select Alert type/subtype and select Virtualization/Hypervisor Alerts

Availability.
6 In the Criticality area, click Warning.
7 Expand the Advanced Filters and from the Alert Status drop-down menu, select New.
The New status indicates that the alert is new to the system and not updated.
8 Click Save.
Results
You created a notification rule that sends the alert text to the target REST-enabled system. Only
the alerts where the configured alert impact is Virtualization/Hypervisor Availability and where
the alert is configured as a warning are sent to the target instance using the REST plug-in.
Notifications
You use the Notifications page to manage your individual alert notification rules. The rules
determine which vRealize Operations Manager alerts are sent to the supported target systems.
How Notifications Work
You add, manage, and edit your notification rules from this page. To send notifications to a
supported system, you must configure and enable the settings for outbound alerts. The
supported outbound notification plug-ins include the Standard Email plug-in, REST plug-in, SNMP
Trap plug-in, and the Log File plug-in.
Before you can create and manage your notification rules, you must configure the outbound alert
plug-in instances.
Where You Find Notifications
VMware, Inc. 372

To manage your notifications, select Alerts in the menu, and click Notifications Settings from the
left pane.
Table 4-98. Notifications Options

Option Description
Toolbar options Use the toolbar options to manage your notification rules.
n Add or Edit. Opens the Rule dialog box where you configure the filtering options for the
notification rule.
n Delete. Removes the selected rule.
Rule Name Name you assigned when you created the notification rule.
Instance Name of the configured outbound alert instance for the notification rule.
Instances are configured as part of the outbound alerts and can indicate different email servers
or sender addresses for alert notifications.
Email Address If the rule is for standard email notifications, the alert recipient email addresses are listed.
Object Name If the rule specifies a notification for a particular object, the object name is listed.
Children If the rule specifies a notification for a particular object and selected child objects, the child
object types are listed.
Notification Rule
Notification rules determine which alerts are sent to the target systems. You configure one or
more notification rules to limit the data that vRealize Operations Manager sends to systems or
recipients.
How Notification Rules Work
Notification rules are filters that limit the data sent to external systems by using outbound alert
plug-ins that are supported, configured, and running. Rather than sending all alerts to all your
email recipients, you can use notification rules to send specific alerts. For example, you can send
health alerts for virtual machines to one or more of your network operations engineers. You can
send critical alerts for selected hosts and clusters to the virtual infrastructure administrator for
those objects.
Before you can create and manage notification rules, you must configure the outbound alert
plug-in instances.
You can configure one filtering selection, or you can configure as many selections as you need so
that vRealize Operations Manager sends only the required data to the target external system.
Where You Find Notification Rules
To manage your notifications, in the menu, click Alerts and then in the left pane, click Alert
Settings > Notification Settings. On the toolbar, click the Add icon to add a rule, or select a rule
and click the Edit icon to edit the exiting rule.
VMware, Inc. 373

Table 4-99. Notification Rule Configuration Selections

Selections Description
Name Name of the rule that you use to manage the rule instance.
Method Includes plug-in type and the plug-in instance. If you are configuring notifications for standard
email, you can add recipients and associated information.
n Type of plug-in. Select one of the configured outbound alert plug-in types: Standard Email,
REST, SNMP Trap, Log File and Service-Now.
n Instance. Select the configured instance for the type of plug-in.
Method -Standard Includes plug-in type and the plug-in instance. If you are configuring notifications for standard
Email Plugin email, you can add recipients and associated information.
n Recipients. Enter the email addresses of the individuals to whom you are sending email
messages that contain alert notifications. If you are sending to more than one recipient, use a
semicolon (;) between addresses.
n Notify again. Number of minutes between notifications messages for active alerts. Leave the
text box empty to send only one message per alert.
n Max Notifications. Number of times to send the notification for the active alert. Leave the text
box empty to send only one message per alert.
n Delay to notify. Number of minutes to delay before sending a notification when a new alert is
generated. For example, if the delay is 10 minutes and a new alert is generated, the
notification is not sent for 10 minutes. If the alert is canceled in those 10 minutes, the
notification is not sent. The notification delay reduces the number of notifications for alerts
that are canceled during that time.
n Description. Enter the text to include in the email message. For example, Attention Host
Management team.
VMware, Inc. 374

Table 4-99. Notification Rule Configuration Selections (continued)

Selections Description
Method - Service- If you are configuring notifications for Service-Now notification plug-in, you can add instances
Now Notification and associated information.
Plugin n Caller. Enter the name of the person who reported the incident or who is affected by the
incident.
n Category. Specify the category to which the incident belongs.
n Sub Category. Specify the sub category to which the incident belongs
n Business Service. Specify the business service of the incident.
n Contact Type. Enter the contact type.
n State. Enter the incident state in digits.
n Resolution Code. Enter the resolution code for the incident.
n Resolution notes. Enter the resolution notes for the incident.
n On hold reason. Enter the reason as to why the incident is on hold.
n Impact. Set the incident impact in digits. Impact measures the business criticality of the
affected service.
n Urgency. Set urgency for the incident in digits. Urgency defines the number of days taken to
resolve an incident.
n Priority. Enter the priority for the incident. Priority defines the sequece in which the incident
must be resolved.
n Assignment Group. Enter the assignment group for the incident.
n Assigned To. Enter the details of the person to whom the incident is assigned.
n Severity. Set the severity for the incident in digits.
n Upon Approval. Specify the next steps to be taken upon incident approval.
n Problem. Enter the details of the related problem if it exists.
n Cause by change. Enter the change request which triggered the incident.
n Change Request. Enter the details for the related chage list if it exists.
Filtering Criteria Note The Filtering Criteria and Advanced Filter sections are same for all the plugins.
Scope General object type for which you are filtering the alert notifications.
After you select the type, you select the specific instance. For example, if you select Object, you
then select the specific object by name and determine whether to include any child objects.
Notification Trigger Alert type and subtypes, impact, or definition that triggers the alert.
After you select the trigger type, you configure the specific selections associated with the trigger
type. For example, if you select Alert Definition, you then select the alert definition that limits the
data to alerts with this definition.
Criticality Defined criticality of the alert that results in the data being sent to an external system. For
example, if you select Critical, then the data that is sent to the external system must also be
labeled as critical.
Advanced Filters
Alert States Managed state of the alert, either opened, assigned, or suspended.
Alert Status Current state of the alert, either canceled, updated, or new.
Collectors Configured collectors in your environment. For example, in an environment where you manage
multiple vCenter Server instances, you can select a collector for one instance. If you want to
distribute email alert notifications between various groups which use different remote collectors,
select Default collector group. This option filters alerts by the target collector group.
VMware, Inc. 375

Create an Alert Definition for Department Objects

As a virtual infrastructure administrator, you are responsible for the virtual machines and hosts
that the accounting department uses. You can create alerts to manage the accounting
department objects.
You received several complaints from your users about delays when they are using their
accounting applications. Using vRealize Operations Manager, you identified the problem as
related to CPU allocations and workloads. To better manage the problem, you create an alert
definition with tighter symptom parameters so that you can track the alerts and identify problems
before your users encounter further problems.
Using this scenario, you create a monitoring system that monitors your accounting objects and
provides timely notifications when problems occur.
Add Description and Base Object to Alert Definition

To create an alert to monitor the CPUs for the accounting department virtual machines and
monitor host memory for the hosts on which they operate, you begin by describing the alert.
When you name the alert definition and define alert impact information, you specify how the
information about the alert appears in vRealize Operations Manager. The base object is the
object around which the alert definition is created. The symptoms can be for the base object and
for related objects.
Procedure
1 In the menu, click Alerts and then in the left pane, click Alert Settings > Alert Definitions.
2 Click the plus sign to add a definition.
3 Type a name and description.
In this scenario, type Acct VM CPU early warning as the alert name, which is a quick
overview of the problem. The description, which is a detailed overview. should provide
information that is as useful as possible. When the alert is generated, this name and
description appears in the alert list and in the notification.
4 Click Base Object Type.
5 From the drop-down menu, expand vCenter Adapter and select Host System.
This alert is based on host systems because you want an alert that acts as an early warning
to possible CPU stress on the virtual machines used in the accounting department. By using
host systems as the based object type, you can respond to the alert symptom for the virtual
machines with bulk actions rather than responding to an alert for each virtual machine.
VMware, Inc. 376

6 Click Alert Impact and configure the metadata for this alert definition.
a From the Impact drop-down menu, select Risk.
This alert indicates a potential problem and requires attention in the near future.
b From the Criticality drop-down menu, select Immediate.
As a Risk alert, which is indicative of a future problem, you still want to give it a high
criticality so that it is ranked for correct processing. Because it is designed as an early
warning, this configuration provides a built-in buffer that makes it an immediate risk rather
than a critical risk.
c From the Alert Type and Subtype drop-down menu, expand Virtualization/Hypervisor
and select Performance.
d To ensure that the alert is generated during the first collection cycle after the symptoms
become true, set the Wait Cycle to 1.
e To ensure that the an alert is removed as soon as the symptoms are no longer triggered,
set the Cancel Cycle to 1.
The alert is canceled in the next collection cycle if the symptoms are no long true.
These alert impact options help you identify and prioritize alerts as they are generated.
Results
You started an alert definition where you provided the name and description, selected host
system as the base object type, and defined the data that appears when the alert generated.
What to do next
Continue in the workspace, adding symptoms to your alert definition. See Add a Virtual Machine
CPU Usage Symptom to the Alert Definition.
Add a Virtual Machine CPU Usage Symptom to the Alert Definition

To generate alerts related to CPU usage on your accounting virtual machines, you add symptoms
to your vRealize Operations Manager alert definition after you provide the basic descriptive
information for the alert. The first symptom you add is related to CPU usage on virtual machines.
You later use a policy and group to apply alert to the accounting virtual machines.
This scenario has two symptoms, one for the accounting virtual machines and one to monitor the
hosts on which the virtual machines operate.
Prerequisites
Begin configuring the alert definition. See Add Description and Base Object to Alert Definition.
Procedure
1 In the Alert Definition Workspace window, after you configure the Name and Description,
Base Object Type, and Alert Impact, click Add Symptom Definitions and configure the
symptoms.
VMware, Inc. 377

2 Begin configuring the symptom set related to virtual machines CPU usage.
a From the Defined On drop-down menu, select Child.
b From the Filter by Object Type drop-down menu, select Virtual Machine.
c From the Symptom Definition Type drop-down menu, select Metric / Supermetric.
d Click the Add button to open the Add Symptom Definition workspace window.
3 Configure the virtual machine CPU usage symptom in the Add Symptom Definition
workspace window.
a From the Base Object Type drop-down menu, expand vCenter Adapter and select
Virtual Machine.
The collected metrics for virtual machines appears in the list.
b In the metrics list Search text box, which searches the metric names, type usage.
c In the list, expand CPU and drag Usage (%) to the workspace on the right.
d From the threshold drop-down menu, select Dynamic Threshold.
Dynamic thresholds use vRealize Operations Manager analytics to identify the trend
metric values for objects.
e In the Symptom Definition Name text box, type a name similar to

VM CPU Usage above trend.
f From the criticality drop-down menu, select Warning.
g From the threshold drop-down menu, select Above Threshold.
h Leave the Wait Cycle and Cancel Cycle at the default values of 3.
This Wait Cycle setting requires the symptom condition to be true for 3 collection cycles
before the symptom is triggered. This wait avoids triggering the symptom when there is a
short spike in CPU usage.
i Click Save.
The dynamic symptom, which identifies when the usage is above the tracked trend, is added
to the symptom list.
4 In the Alert Definition Workspace window, drag VM CPU Usage above trend from the
symptom definition list to the symptom workspace on the right.
The Child-Virtual Machine symptom set is added to the symptom workspace.
VMware, Inc. 378

5 In the symptoms set, configure the triggering condition so that when the symptom is true on
half of the virtual machines in the group to which this alert definition is applied, the symptom
set is true.
a From the value operator drop-down menu, select >.
b In the value text box, enter 50.
c From the value type drop-down menu, select Percent.
Results
You defined the first symptom set for the alert definition.
What to do next
Add the host memory usage symptom to the alert definition. See Add a Host Memory Usage
Symptom to the Alert Definition.
Add a Host Memory Usage Symptom to the Alert Definition

To generate alerts related to CPU usage on your accounting virtual machines, you add a second
symptom to your vRealize Operations Manager alert definition after you add the first symptom.
The second symptom is related to host memory usage for the hosts on which the accounting
virtual machines operate.
Prerequisites
Add the virtual machine CPU usage symptom. See Add a Virtual Machine CPU Usage Symptom
to the Alert Definition.
Procedure
Base Object Type, and Alert Impact, click Add Symptom Definitions.
2 Configure the symptom related to host systems for the virtual machines.
a From the Defined On drop-down menu, select Self.
b From the Symptom Definition Type drop-down menu, select Metric / Supermetric.
c Click the Add button to configure the new symptom.
3 Configure the host system symptom in the Add Symptom Definition workspace window.
a From the Base Object Type drop-down menu, expand vCenter Adapters and select Host
System.
b In the metrics list, expand Memory and drag Usage (%) to the workspace on the right.
c From the threshold drop-down menu, select Dynamic Threshold.
Dynamic thresholds use vRealize Operations Manager analytics to identify the trend
metric values for objects.
VMware, Inc. 379

d In the Symptom Definition Name text box, enter a name similar to

Host memory usage above trend.
e From the criticality drop-down menu, select Warning.
f From the threshold drop-down menu, select Above Threshold.
g Leave the Wait Cycle and Cancel Cycle at the default values of 3.
This Wait Cycle setting requires the symptom condition to be true for three collection
cycles before the symptom is triggered. This wait avoids triggering the symptom when a
short spike occurs in host memory usage.
h Click Save.
The dynamic symptom identifies when the hosts on which the accounting virtual machines
run are operating above the tracked trend for memory usage.
The dynamic symptom is added to the symptom list.
4 In the Alert Definition Workspace window, drag Host memory usage above trend from the
symptoms list to the symptom workspace on the right.
The Self-Host System symptom set is added to the symptom workspace.
5 On the Self-Host System symptom set, from the value type drop-down menu for This
Symptom set is true when, select Any.
With this configuration, when any of the hosts running accounting virtual machines exhibit
memory usage that is above the analyzed trend, the symptom condition is true.
6 At the top of the symptom set list, from the Match {operator} of the following symptoms
drop-down menu, select Any.
With this configuration, if either of the two symptom sets, virtual machine CPU usage or the
host memory, are triggered, an alert is generated for the host.
Results
You defined the second symptom set for the alert definition and configured how the two
symptom sets are evaluated to determine when the alert is generated.
What to do next
Add recommendations to your alert definition so that you and your engineers know how to
resolve the alert when it is generated. See Add Recommendations to the Alert Definition.
Add Recommendations to the Alert Definition

To resolve a generated alert for the accounting department's virtual machines, you provide
recommendations so that you or other engineers have the information you need to resolve the
alert before your users encounter performance problems.
VMware, Inc. 380

As part of the alert definition, you add recommendations that include actions that you run from
vRealize Operations Manager and instructions for making changes in vCenter Server that resolve
the generated alert.
Prerequisites
Add symptoms to your alert definition. See Add a Host Memory Usage Symptom to the Alert
Definition.
Procedure
Base Object Type, Alert Impact, and Add Symptom Definitions, click Add
Recommendations and add the recommended actions and instructions.
2 Click Add and select an action recommendation to resolve the virtual machine alerts.
a In the New Recommendation text box, enter a description of the action similar to
Add CPUs to virtual machines.
b From the Actions drop-down menu, select Set CPU Count for VM.
c Click Save.
3 Click Add and provide an instructive recommendation to resolve host memory problems
similar to this example.
If this host is part of a DRS cluster, check the DRS settings to verify that the
load balancing setting are configured correctly. If necessary, manually vMotion
the virtual machines.
4 Click Add and provide an instructive recommendation to resolve host memory alerts.
a Enter a description of the recommendation similar to this example.
If this is a standalone host, add more memory to the host.
b To make the URL a hyperlink in the instructions, copy the URL, for example, https://
www.vmware.com/support/pubs/vsphere-esxi-vcenter-server-pubs.html, to your
clipboard.
c Highlight the text in the text box and click Create a hyperlink.
d Paste the URL in the Create a hyperlink text box and click OK.
e Click Save.
5 In the Alert Definition Workspace, drag Add CPUs to virtual machines, If this host is part of
a DRS cluster, and the If this is a standalone host recommendations from the list to the
recommendation workspace in the order presented.
6 Click Save.
VMware, Inc. 381

Results
You provided the recommended actions and instructions to resolve the alert when it is
generated. One of the recommendations resolves the virtual machine CPU usage problem and
the other resolves the host memory problem.
What to do next
Create a group of objects to use to manage your accounting objects. See Create a Custom
Accounting Department Group.
Create a Custom Accounting Department Group

To manage, monitor, and apply policies to the accounting objects as a group, you create a
custom object group.
Prerequisites
Verify that you completed the alert definition for this scenario. See Add Recommendations to the
Alert Definition.
Procedure
1 In the menu, click Environment and click the Custom Groups tab.
2 Click the New Custom Group icon to create a new custom group.
3 Type a name similar to Accounting VMs and Hosts.
4 From the Group Type drop-down menu, select Department.
5 From the Policy drop-down menu, select Default Policy.
When you create a policy, you apply the new policy to the accounting group.
6 In the Define membership criteria area, from the Select the Object Type that matches the
following criteria drop-down menu, expand vCenter Adapter, select Host System, and
configure the dynamic group criteria.
a From the criteria drop-down menu, select Relationship.
b From the relationships options drop-down menu, select Parent of.
c From the operator drop-down menu, select contains.
d In the Object name text box, enter acct.
e From the navigation tree drop-down list, select vSphere Hosts and Clusters.
You created a dynamic group where host objects that are the host for virtual machines with
acct in the virtual machine name are included in the group. If a virtual machine with acct in the
object name is added or moved to a host, the host object is added to the group.
7 Click Preview in the lower-left corner of the workspace, and verify that the hosts on which
your virtual machines that include acct in the object name appear in the Preview Group
window.
VMware, Inc. 382

8 Click Close.
9 Click Add another criteria set.
A new criteria set is added with the OR operator between the two criteria sets.
10 From the Select the Object Type that matches the following criteria drop-down menu,
expand vCenter Adapter, select Virtual Machine, and configure the dynamic group criteria.
a From the criteria drop-down menu, select Properties.
b From the Pick a property drop-down menu, expand Configuration and double-click
Name.
c From the operator drop-down menu, select contains.
d In the Property value text box, enter acct.
You created a dynamic group where virtual machine objects with acct in the object name are
included in the group that depends on the presence of those virtual machines. If a virtual
machine with acct in the name is added to your environment, it is added to the group.
11 Click Preview in the lower-left corner of the workspace, and verify that the virtual machines
with acct in the object name are added to the list that also includes the host systems.
12 Click Close.
13 Click OK.
The Accounting VMs and Hosts group is added to the Groups list.
Results
You created a dynamic object group that changes as virtual machines with acct in their names
are added, removed, and moved in your environment.
What to do next
Create a policy that determines how vRealize Operations Manager uses the alert definition to
monitor your environment. See Create a Policy for the Accounting Alert.
Create a Policy for the Accounting Alert

To configure how vRealize Operations Manager evaluates the accounting alert definition in your
environment, you configure a policy that determines behavior so that you can apply the policy to
an object group. The policy limits the application of the alert definition to only the members of
the selected object group.
When an alert definition is created, it is added to the default policy and enabled, ensuring that
any alert definitions that you create are active in your environment. This alert definition is
intended to meet the needs of the accounting department, so you disable it in the default policy
and create a new policy to govern how the alert definition is evaluated in your environment,
including which accounting virtual machines and related hosts to monitor.
VMware, Inc. 383

Prerequisites
n Verify that you completed the alert definition for this scenario. See Add Recommendations to
the Alert Definition.
n Verify that you created a group of objects that you use to manage you accounting objects.
See Create a Custom Accounting Department Group.
Procedure
1 In the menu, click Administration and then in the left pane, click Policies.
2 Click the Policy Library tab.
3 Click Add New Policy.
4 Type a name similar to Accounting Objects Alerts Policy and provide a useful description
similar to the following example.
This policy is configured to generate alerts when

Accounting VMs and Hosts group objects are above trended
CPU or memory usage.
5 Select Default Policy from the Start with drop-down menu.
6 On the left, click Customize Alert / Symptom Definitions and disable all the alert definitions
except the new Acct VM CPU early warning alert.
a In the Alert Definitions area, click Actions and select Select All.
The alerts on the current page are selected.
b Click Actions and select Disable.
The alerts indicate Disabled in the State column.
c Repeat the process on each page of the alerts list.
d Select Acct VM CPU early warning in the list, click Actions and select Enable.
The Acct VM CPU early warning alert is now enabled.
7 On the left, click Apply Policy to Groups and select Accounting VMs and Hosts.
8 Click Save.
Results
You created a policy where the accounting alert definition exists in a custom policy that is applied
only to the virtual machines and hosts for the accounting department.
What to do next
Create an email notification so that you learn about alerts even you when you are not actively
monitoring vRealize Operations Manager. See Configure Notifications for the Department Alert.
VMware, Inc. 384

Configure Notifications for the Department Alert

To receive an email notification when the accounting alert is generated, rather than relying on
your ability to generally monitor the accounting department objects in vRealize Operations
Manager, you create notification rules.
Creating an email notification when accounting alerts are triggered is an optional process, but it
provides you with the alert even when you are not currently working in vRealize Operations
Manager.
Prerequisites
n Verify that you completed the alert definition for this scenario. See Add Recommendations to
the Alert Definition.
n Verify that standard email outbound alerts are configured in your system. See Add a
Standard Email Plug-In for vRealize Operations Manager Outbound Alerts.
Procedure
2 Click Notification Settings and click the plus sign to add a notification rule.
3 Configure the communication options.
a In the Name text box, type a name similar to Acct Dept VMs or Hosts Alerts.
b From the Select Plug-In Type drop-down menu, select StandardEmailPlugin.
c From the Select Instance drop-down menu, select the standard email instance that is
configured to send messages.
d In the Recipients text box, type your email address and the addresses of other recipients
responsible for the accounting department alerts. Use a semicolon between recipients.
e Leave the Notify again text box blank.
If you do not provide a value, the email notice is sent only once. This alert is a Risk alert
and is intended as an early warning rather than requiring an immediate response.
You configured the name of the notification when it is sent to you and the method that is
used to send the message.
4 In the Filtering Criteria area, configure the accounting alert notification trigger.
a From the Notification Trigger drop-down menu, select Alert Definition.
b Click Click to select Alert Definition.
c Select Acct VM CPU early warning and click Select.
5 Click Save.
VMware, Inc. 385

Results
You created a notification rule that sends you and your designated engineers an email message
when this alert is generated for your accounting department alert definition.
What to do next
Create a dashboard with alert-related widgets so that you can monitor alerts for the accounting
object group. See Create a Dashboard to Monitor Department Objects.
Create a Dashboard to Monitor Department Objects

To monitor all the alerts related to the accounting department object group, you create a
dashboard that includes the alert list and other widgets. The dashboard provides the alert data in
a single location for all related objects.
Creating a dashboard to monitor the accounting virtual machines and related hosts is an optional
process, but it provides you with a focused view of the accounting object group alerts and
objects.
Prerequisites
Create an object group for the accounting department virtual machines and related objects. See
Create a Custom Accounting Department Group.
Procedure
1 In the menu, click Dashboards > Actions > Create Dashboard.
2 In the Dashboard Configuration definition area, type a tab name similar to

Accounting VMs and Hosts and configure the layout options.
3 Click Widget List and drag the following widgets to the workspace.
n Alert List
n Efficiency
n Health
n Risk
n Top Alerts
n Alert Volume
The blank widgets are added to the workspace. To change the order in which they appear,
you can drag them to a different location in the workspace.
4 On the Alert List widget title bar, click Edit Widget and configure the settings.
a In the Title text box, change the title to Acct Dept Alert List.
b For the Refresh Content option, select On.
VMware, Inc. 386

c Type Accounting in the Search text box and click Search.
The Accounting value corresponds to the name of the object group for the accounting
department virtual machines and related hosts.
d In the filtered resource list, select the Accounting VMs and Hosts group.
The Accounting VMs and Hosts group is identified in the Selected Resource text box.
e Click OK.
The Acct Dept Alert List is now configured to display alerts for the Accounting VMs and
Hosts group objects.
5 Click Widget Interactions and configure the following interactions.
a For Acct Dept Alert List, leave the selected resources blank.
b For Top Alerts, Health, Risk, Efficiency, and Alert Volume select Acct Dept Alert List from
the Selected Resources drop-down menu.
c Click Apply Interactions.
With the widget interaction configured in this way, the select alert in the Acct Dept Alert List
is the source for the data in the other widgets. When you select an alert in the alert list, the
Health, Risk, and Efficiency widgets display alerts for that object, Top Alerts displays the topic
issues affecting the health of the object, and Alert Volume displays an alert trend chart.
6 Click Save.
Results
You created a dashboard that displays the alerts related to the accounting virtual machines and
hosts group, including the Risk alert you created.
Alerts Group
For easy and better management of alerts, you can arrange them as a group as per your
requirement.
It is complicated to identify a problem in large environments as you receive different kind of

alerts. To manage alerts easily, group them by their definitions.
For example, there are 1000 alerts in your system. To identify different types of alerts, group
them based on their alert definitions. It is also easy to detect the alert having the highest severity
in the group.
When you group alerts, you can see the number of times the alerts having the same alert
definition are triggered. By grouping alerts, you can perform the following tasks easily and
quickly:
n Find the noisiest alert: The alert that has triggered maximum number of times is known as the
noisiest alert. Once you find it, you can disable it to avoid further noise.
VMware, Inc. 387

n Filter alerts: You can filter alerts based on a substring in alert definitions. The result shows the
group of alerts that contain the substring.
Note
n If you cancel or disable an alert group, the alerts are not canceled instantly. It might take
some time if the group is large.
n Only one group can be expanded at a time.
n The number next to the group denotes the number of alerts in that particular group.
n The criticality sign indicates the highest level of severity of an alert in a group.
Grouping Alerts
You can group alerts by time, criticality, definition, and object type.
To group alerts:
Procedure
1 In the menu, click Alerts.
2 Select from the various options available from the Group By drop-down menu.
Disable Alerts
In an alerts group, you can disable an alert by a single click.
To disable an alert, in the menu, click Alerts and then in the left pane, click All Alerts. Select the
alert name from the data grid, and click Actions > Disable.
The alerts can be disabled by two methods:
n Disable Alert in All Policies: You disable the alert for all the objects for all the policies.
n Disable Alert in Selected Policies: You disable the alert for the objects having the selected
policy. Note that this method will work only for objects with alerts.
Configuring Actions
Actions are the ability to update objects or read data about objects in monitored systems, and
are commonly provided in vRealize Operations Manager as part of a solution. The actions added
by solutions are available from the object Actions menu, list and view menus, including some
dashboard widgets, and can be added to alert definition recommendations.
The possible actions include read actions and update actions.
The read actions retrieve data from the target objects.
VMware, Inc. 388

The update actions modifies the target objects. For example, you can configure an alert
definition to notify you when a virtual machine is experiencing memory issues. Add an action in
the recommendations that runs the Set Memory for Virtual Machine action. This action increases
the memory and resolves the likely cause of the alert.
To see or use the actions for your vCenter Server objects, you must enable actions in the vCenter
Adapter for each monitored vCenter Server instance. Actions can only be viewed and accessed if
you have the required permissions.
List of vRealize Operations Manager Actions

The list of actions includes the name of the action, the objects that each one modifies, and the
object levels at which you can run the action. You use this information to ensure that you
correctly apply the actions as alert recommendations and when the actions are available in the
Actions menu.
Actions and Modified Objects

vRealize Operations Manager actions make changes to objects in your managed vCenter Server
instances.
When you grant a user access to actions in vRealize Operations Manager, that user can take the
granted action on any object that vRealize Operations Manager manages.
Action Object Levels

The actions are available when you work with different object levels, but they modify only the
specified object. If you are working at the cluster level and select Power On VM, all the virtual
machines in the cluster for which you have access permission are available for you to run the
action. If you are working at the virtual machine level, only the selected virtual machine is
available.
Table 4-100. vRealize Operations Manager Actions Affected Objects

Action Modified Object Object Levels
Rebalance Container Virtual Machines n Data Center

n Custom Data Center
Delete Idle VM Virtual Machines n Clusters

n Host Systems
n Virtual Machines
Set DRS Automation Cluster n Clusters
Move VM Virtual Machine n Virtual Machines
Power Off VM Virtual Machine n Clusters

n Host Systems
n Virtual Machines
Shut Down Guest OS for VM Virtual Machine n Clusters

VMware Tools must be installed and running on n Host Systems
the target virtual machines to run this action. n Virtual Machines
VMware, Inc. 389

Table 4-100. vRealize Operations Manager Actions Affected Objects (continued)

Action Modified Object Object Levels
Power On VM Virtual Machine n Clusters

n Host Systems
n Virtual Machines
Delete Powered Off VM Virtual Machine n Clusters

n Host Systems
n Virtual Machines
Set Memory for VM Virtual Machine n Clusters

and n Host Systems
Set Memory for VM Power Off n Virtual Machines
Allowed
Set Memory Resources for VM Virtual Machine n Clusters

n Host Systems
n Virtual Machines
Set CPU Count for VM Virtual Machine n Clusters

and n Host Systems
Set CPU Count for VM Power Off n Virtual Machines
Allowed
Set CPU Resources for VM Virtual Machine n Clusters

n Host Systems
n Virtual Machines
Set CPU Count and Memory for Virtual Machine n Clusters

VM n Host Systems
and n Virtual Machines
Set CPU Count and Memory for
VM Power Off Allowed
Delete Unused Snapshots for VM Snapshot n Clusters

n Host Systems
n Virtual Machines
Delete Unused Snapshots for Snapshot n Clusters

Datastore n Datastores
n Host Systems
Actions Overview List in vRealize Operations Manager

Actions are the method you use to configuration changes on managed objects that you initiate
from vRealize Operations Manager. These actions are available to add to alert recommendations.
How the Actions Overview List Works

Actions are defined to run on the target object from different object levels, allowing you to add
actions as recommendations for alert definitions that are configured for different base objects.
The Actions overview is a list of actions available in your environment.
VMware, Inc. 390

Where You Find the Actions Overview List

To view the available actions, in the menu, click Alerts and then in the left pane, click Alert
Settings > Actions.
Table 4-101. Actions Overview Options

Option Description
Filter options Limits the list to actions matching the filter.
Action Name Name of the action. Duplicate names indicate that the action name is provided by more than one
adapter or has more than one associated object.
Action Type Type of action that the action performs, either read or update.
n Update actions make changes to the target objects.
n Read actions retrieve data from the target objects.
Adapter Type Name of the configured adapter that provides the action.
Resource Adapter Adapter that provides the action.

Type
Associated Object Indicates the object level at which the action instance runs.
Types
Recommendations Indicates whether the action is used in at least one recommendation.
these actions.
set to true.
Actions Supported for Automation

Recommendations can identify ways to remediate problems indicated by an alert. Some of these
remediations can be associated with actions defined in your vRealize Operations Manager
instance. You can automate several of these remediation actions for an alert when that
recommendation is the first priority for that alert.
You enable actionable alerts in your policies. By default, automation is disabled in policies. To
configure automation for your policy, in the menu, click Administration > Policies > Policy
Library. Then, you edit a policy, access the Alert / Symptom Definitions workspace, and select
Local for the Automate setting in the Alert / Symptom Definitions pane.
VMware, Inc. 391

When an action is automated, you can use the Automated and Alert columns in Administration >
History > Recent Tasks to identify the automated action and view the results of the action.
n vRealize Operations Manager uses the automationAdmin user account to trigger automated
actions. For these automated actions that are triggered by alerts, the Submitted By column
displays the automationAdmin user.
n The Alert column displays the alert that triggered the action. When an alert is triggered that is
associated to the recommendation, it triggers the action without any user intervention.
The following actions are supported for automation:
n Delete Powered Off VM
n Delete Idle VM
n Move VM
n Power Off VM
n Power On VM
n Set CPU Count And Memory for VM
n Set CPU Count And Memory for VM Power Off Allowed
n Set CPU Count for VM
n Set CPU Resources for VM
n Set Memory for VM
n Set Memory Resources for VM
n Shut Down Guest OS for VM
Roles Needed to Automate Actions

To automate actions, your role must have the following permissions:
n Create, edit, and import policies in Administration > Policies > Policy Library.
n Create, clone, edit, and import alert definitions in Alerts > Alert Settings > Alert Definitions.
n Create, edit, and import recommendation definitions in Alerts > Alert Settings >
Recommendations.
Important You set the permissions used to run the actions separately from the alert and
recommendation definition. Anyone who can modify alerts, recommendations, and policies can
also automate the action, even if they do not have permission to run the action.
VMware, Inc. 392

For example, if you do not have access to the Power Off VM action, but you can create and
modify alerts and recommendations, you can see the Power Off VM action and assign it to an
alert recommendation. Then, if you automate the action in your policy, vRealize Operations
Manager uses the automationAdmin user to run the action.
Example Action Supported for Automation

For the Alert Definition named Virtual machine has chronic high CPU workload leading to
CPU stress, you can automate the action named Set CPU Count for VM.
When CPU stress on your virtual machines exceeds a critical, immediate, or warning level, the
alert triggers the recommended action without user intervention.
Integration of Actions with vRealize Automation

vRealize Operations Manager restricts actions on objects that vRealize Automation manages, so
that the actions do not violate any constraints set forth by vRealize Automation.
When objects in your environment are managed by vRealize Automation, actions in vRealize
Operations Manager are not available on those objects. For example, if a host or parent object is
being managed by vRealize Automation, actions are not available on that object.
This behavior is true for all actions, including Power Off VM, Move VM, Rebalance Container, and
so on.
You cannot turn on or turn off the exclusion of actions on vRealize Automation managed objects.
Actions Determine Whether Objects Are Managed

Actions check the objects in the vRealize Automation managed resource container to determine
which objects are being managed by vRealize Automation.
n Actions such as Rebalance Container check the child objects of the data center container or
custom data center container to determine whether the objects are managed by vRealize
Automation. If the objects are being managed, the action does not appear on those objects.
n The Move VM action checks whether the virtual machine to be moved is being managed by
vRealize Automation.
Is the Virtual
Machine
Managed? Result of Move VM Action
Yes The Move VM action does not appear in the vRealize Operations Manager user interface for that
virtual machine.
No The Move VM action moves the virtual machine to a new host, datastore, or new host and
datastore. The Move VM action does not check whether the new host or datastore is being
managed by vRealize Automation.
n The Delete Snapshots action checks whether the virtual machine or datastore is being
managed by vRealize Automation.
VMware, Inc. 393

Actions on Objects that vRealize Automation Does Not Manage

For a host or parent object that is not managed by vRealize Automation, only the virtual
machines that are not being managed by vRealize Automation appear in the action dialog, and
you can only take action on the virtual machines that are not being managed by vRealize
Automation. If all child objects are being managed by vRealize Automation, the user interface
displays the message No objects are eligible for the selected action.
If You Attempt to Run an Action on Multiple Objects

If you select multiple objects and attempt to run an action, such as Power Off VM, only the
objects that are not being managed by vRealize Automation, which might include a subset of the
virtual machines, appear in the Power Off VM action dialog box.
Working with Actions That Use Power Off Allowed

Some of the actions provided with vRealize Operations Manager require the virtual machines to
shut down or power off, depending on the configuration of the target machines, to run the
actions. You should understand the impact of the Power Off Allowed option before running the
actions so that you select the best options for your target virtual machines.
Power Off and Shut Down

The actions that you can run on your vCenter Server instances include actions that shut down
virtual machines and actions that power off virtual machines. It also includes actions where the
virtual machine must be in a powered off state to complete the action. Whether the VM is shut
down or powered off depends on how it is configured and what options you select when you run
the action.
The shut-down action shuts down the guest operating system and then powers off the virtual
machine. To shut down a virtual machine from vRealize Operations Manager, the VMware Tools
must be installed and running on the target objects.
The power off action turns off the VM without regard for the state of the guest operating system.
In this case, if the VM is running applications, your user might lose data. After the action is
finished, for example, modifying the CPU count, the virtual machine is returned to the power
state it was in when the action began.
Power Off Allowed and VMware Tools
For the actions where you are increasing the CPU count or the amount of memory on a VM,
some operating systems support the actions if the Hot Plug is configured on the VM. For other
operating systems, the virtual machine must be in a powered off state to change the
configuration. To accommodate this need where the VMware Tools is not running, the Set CPU
Count, Set Memory, and Set CPU Count and Memory actions include the Power Off Allowed
option.
VMware, Inc. 394

If you select Power Off Allowed, and the machine is running, the action verifies whether VMware
Tools is installed and running.
n If VMware Tools is installed and running, the virtual machine is shut down before completing
the action.
n If VMware Tools is not running or not installed, the virtual machine is powered off without
regard for the state of the operating system.
If you do not select Power Off Allowed and you are decreasing the CPU count or memory, or the
hot plug is not enabled for increasing the CPU count or memory, the action does not run and the
failure is reported in Recent Tasks.
Power Off Allowed When Changing CPU Count or Memory

When you run the actions that change the CPU count and the amount of memory, you must
consider several factors to determine if you want to use the Power Off Allowed option. These
factors include whether you are increasing or decreasing the CPU or memory and whether the
target virtual machines are powered on. If you increase the CPU or memory values, whether hot
plug is enabled also affects how you apply the option when you run the action.
How you use Power Off Allowed when you are decreasing the CPU count or the amount of
memory depends on the power state of the target virtual machines.
Table 4-102. Decreasing CPU Count and Memory Behavior Based On Options
Virtual Machine Power State Power Off Allowed Selected Results
On Yes If VMware Tools is installed and

running, the action shuts down the
virtual machine, decreases the CPU or
memory, and powers the machine
back on.
If VMware Tools is not installed, the
action powers off the virtual machine,
decreases the CPU or memory, and
powers the machine back on.
On No The action does not run on the virtual

machine.
Off Not applicable. The virtual machine is The action decreases the value and
powered off. leaves the virtual machine in a
powered off state.
How you use Power Off Allowed when you are increasing the CPU count or the amount of
memory depends on several factors, including the state of the target virtual machine and
whether hot plug is enabled. Use the following information to determine which scenario applies
to your target objects.
If you are increasing the CPU count, you must consider the power state of the virtual machine
and whether CPU Hot Plug is enabled when determining whether to apply Power Off Allowed.
VMware, Inc. 395

Table 4-103. Increasing CPU Count Behavior.

Power Off Allowed
Virtual Machine Power State CPU Hot Plug Enabled Selected Results
On Yes No The action increases the

CPU count to the specified
amount.
On No Yes If VMware Tools is installed

and running, the action shuts
down the virtual machine,
increases the CPU count,
and powers the machine
back on.
If VMware Tools is not
installed, the action powers
off the virtual machine,
increases the CPU count,
and powers the machine
back on.
Off Not applicable. The virtual Not required. The action increases the
machine is powered off. CPU count to the specified
amount.
If you are increasing the memory, you must consider the power state of the virtual machine,
whether Memory Hot Plug is enabled, and whether there is a Hot Memory Limit when
determining how to apply Power Off Allowed.
Table 4-104. Increasing Memory Amount Behavior

Virtual Machine Memory Hot Plug Power Off Allowed
Power State Enabled Hot Memory Limit Selected Results
On Yes New memory value ≤ No The action increases

hot memory limit the memory the
specified amount.
On Yes New memory value > Yes If VMware Tools is

hot memory limit installed and running,
the action shuts down
the virtual machine,
increases the memory,
and powers the
machine back on.
installed, the action
powers off the virtual
machine, increases the
memory, and powers
the machine back on.
VMware, Inc. 396

Table 4-104. Increasing Memory Amount Behavior (continued)

Virtual Machine Memory Hot Plug Power Off Allowed
Power State Enabled Hot Memory Limit Selected Results
On No Not applicable. The Yes If VMware Tools is

hot plug is not installed and running,
enabled. the action shuts down
the virtual machine,
increases the memory,
and powers the
machine back on.
installed, the action
powers off the virtual
machine, increases the
memory, and powers
the machine back on.
Off Not applicable. The Not applicable. Not required The action increases
virtual machine is the memory the
powered off. specified amount.
Configuring Policies
To create a policy, you can inherit the settings from an existing policy, and you can modify the
settings in existing policies if you have adequate permissions. After you create a policy, or edit an
existing policy, you can apply the policy to one or more groups of objects.
Policies
A policy is a set of rules that you define for vRealize Operations Manager to use to analyze and
display information about the objects in your environment. You can create, modify, and
administer policies to determine how vRealize Operations Manager displays data in dashboards,
views, and reports.
How Policies Relate to Your Environment

vRealize Operations Manager policies support the operational decisions established for your IT
infrastructure and business units. With policies, you control what data vRealize Operations
Manager collects and reports on for specific objects in your environment. Each policy can inherit
settings from other policies, and you can customize and override various analysis settings, alert
definitions, and symptom definitions for specific object types, to support the service Level
agreements and business priorities established for your environment.
When you manage policies, you must understand the operational priorities for your environment,
and the tolerances for alerts and symptoms to meet the requirements for your business critical
applications. Then, you can configure the policies so that you apply the correct policy and
threshold settings for your production and test environments.
VMware, Inc. 397

Policies define the settings that vRealize Operations Manager applies to your objects when it
collects data from your environment. vRealize Operations Manager applies policies to newly
discovered objects, such as the objects in an object group. For example, you have an existing
VMware adapter instance, and you apply a specific policy to the group named World. When a
user adds a new virtual machine to the vCenter Server instance, the VMware adapter reports the
virtual machine object to vRealize Operations Manager. The VMware adapter applies the same
policy to that object, because it is a member of the World object group.
To implement capacity policy settings, you must understand the requirements and tolerances for
your environment, such as CPU use. Then, you can configure your object groups and policies
according to your environment.
n For a production environment policy, a good practice is to configure higher performance

settings, and to account for peak use times.
n For a test environment policy, a good practice is to configure higher utilization settings.
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 configured settings 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 bottom 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 different policy to each object group,
vRealize Operations Manager associates the highest ranking policy with that object.
Table 4-105. Configurable Policy Rule Elements

Policy Rule Elements Thresholds, Settings, Definitions
Workload Configure symptom thresholds for Workload.
Time Remaining Configure thresholds for the Time Remaining.
Capacity Remaining Configure thresholds for the Capacity Remaining.
Maintenance Schedule Sets a time to perform maintenance tasks.
Attributes An attribute is a collectible data component. You can enable or disable metric, property, and
super metric attributes for collection, and set attributes as key performance indicators
(KPIs). A KPI is the designation of an attribute that indicates that the attribute is important in
your own environment.
Alert Definitions Enable or disable combinations of symptoms and recommendations to identify a condition
that classifies as a problem.
Symptom Definitions Enable or disable test conditions on properties, metrics, or events.
Privileges to Create, Modify, and Prioritize Policies

VMware, Inc. 398

To set the policy priority, on the Active Policies tab, click the policy row and drag it to place it at
the desired priority in the list. The priority for the Default Policy is always designated with the
letter D.
How Upgrades Affect Your Policies

After you upgrade vRealize Operations Manager from a previous version, you might find newly
added or updated default settings of policies such as, new alerts and symptoms. Hence, you
must analyze the settings and modify these settings to optimize them for your current
environment. If you apply the policies used with a previous version of vRealize Operations
Manager, the manually modified policy settings remain unaltered.
Policy Decisions and Objectives

Implementing policy decisions in vRealize Operations Manager is typically the responsibility of the
Infrastructure Administrator or the Virtual Infrastructure Administrator, but users who have
privileges can also create and modify policies.
You must be aware of the policies established to analyze and monitor the resources in your IT
infrastructure.
n If you are a Network Operations engineer, you must understand how policies affect the data
that vRealize Operations Manager reports on objects, and which policies assigned to objects
report alerts and issues.
n If you are the person whose role is to recommend an initial setup for policies, you typically
edit and configure the policies in vRealize Operations Manager.
n If your primary role is to assess problems that occur in your environment, but you do not
have the responsibility to change the policies, you must still understand how the policies
applied to objects affect the data that appears in vRealize Operations Manager. For example,
you might need to know which policies apply to objects that are associated with particular
alerts.
n If you are a typical application user who receives reports from vRealize Operations Manager,
you must have a high-level understanding of the operational policies so that you can
understand the reported data values.
Active Policies Tab for Policies

The Active Policies tab displays the policies associated with groups of objects. You can manage
the active policies for the objects in your environment so that you can have vRealize Operations
Manager analyze and display specific data about those objects in dashboards, views, and
reports.
How the Active Policies Tab Works

Use the Active Policies tab to associate a policy with one or more object groups, and to set the
default policy. You can view the locally defined settings for a policy, and the complete list of
settings, which includes those that are inherited from the base policies that you select in the Add
or Edit Policy workspace. You can assign any policy to be the default policy.
VMware, Inc. 399

To display the details for a selected policy, click the split bar to expand the pane. The Details and
Related Items tabs and options for the policy appear in the lower pane. On the Related Items tab,
you can also apply the selected policy to object groups.
You can use the far right column of the Active Policies tab to reorder and therefore reprioritize
the policies by dragging them to a new position. However, even though it seems like you can
drag a custom policy below the default policy, you cannot. The default policy is always the last
policy in the list after the view is refreshed.
How to Prioritize Policies

To set the policy priority, on the Active Policies tab, click the policy row and drag it to place it at
the desired priority in the list. The priority for the Default Policy is always designated with the
letter D.
Where You Manage the Active Policies

To manage the active policies, in the menu, click Administration, and then in the left pane click
Policies. The Active Policies tab appears and lists the policies that are active for the objects in
your environment.
VMware, Inc. 400

Table 4-106. Active Policies Tab Options

Option Description
Toolbar Use the toolbar selections to take action on the active policies.
n Show Association. Opens the Related Items tab so that you can associate the
policy with groups.
n Set Default Policy. You can set any policy to be the default policy, which applies
the settings in that policy to all objects that do not have a policy applied. When
you set a policy to be the default policy, the priority is set to D, which gives that
policy the highest priority.
Active Policies Tab data grid vRealize Operations Manager displays the priority and high-level details for the active
policies.
n Priority. Ranking of the priority of the policy. The default policy is marked with a
check mark in the Is Default column.
n Name. Name of the policy as it appears in the Add or Edit Monitoring Policy wizard,
and in areas where the policy applies to objects, such as in Custom Groups.
n Description. Meaningful description of the policy, such as which policy is inherited,
and any specific information users need to understand the relationship of the
policy to one or more groups of objects.
n Groups. Indicates the number of object groups to which the policy is assigned.
n Affected Objects. Displays the object name, type, and adapter to which the active
policy is assigned, and the direct parent group, when applicable.
n Last Modified. Date and time that the policy was last modified.
n Modified By. User who last modified the policy settings.
VMware, Inc. 401

Table 4-106. Active Policies Tab Options (continued)

Option Description
Active Policies Tab > Details The Details tab displays the name and description of the policy from which the settings
Tab are inherited, the policy priority, who last modified the policy, and the number of
object groups associated with the policy. From the Details tab, you can view the
settings that are locally defined in your policy, and the complete group of settings that
include both customized settings and the settings inherited from the base policies
selected when the policy was created.
n Locally Defined Settings. Displays the locally changed policy element settings for
each object type in the policy.
n Complete Settings Including Inherited. Displays all of the policy element settings for
each object type in the policy, including locally changed settings and settings that
are inherited. A summary of the enabled and disabled alert definitions, symptom
definitions, and attributes appear indicate the number of changes in the policy. The
policy element settings include symptom thresholds, and indicate changes made to
the Workload, Capacity Remaining, and Time Remaining settings.
Active Policies Tab > Related Summarizes the related groups and objects, and details about the selected object
Objects Tab group and objects.
n Groups. Displays the groups of objects associated with the selected active policy,
and provides options to add and release an association.
n Add Association. Opens the Apply the policy to groups dialog box where you
select object groups to associate with the selected policy.
n Release Association. Opens a confirmation dialog box to confirm the release of
the object group that is associated with the selected policy.
n Data grid. Displays the groups assigned to this policy, the object types
associated with the group, and the number of objects in the group.
n Details for the selected object group. Displays the object group name, type,
and number of members associated with the selected policy, and the type of
association with the policy. An object group can have a direct association with
a policy, and inherited policy associations based on the base policies that you
selected when you created a local policy. For example, if the Base Settings
policy appears in the list, with an inherited association, the Base Settings policy
was included in the base policies selected when this policy was created.
n Affected Objects. Displays the names of the objects in your environment, their
object types, and associated adapters. When a parent group exists for an object, it
appears in this data grid.
Policy Library Tab for Policies

The Policy Library tab displays the base settings, default policy, and other best practice policies
that vRealize Operations Manager includes. You can use the library policies to create your own
policies. The policy library includes all the configurable settings for the policy elements, such as
workload, capacity and time remaining, and so on.
How the Policy Library Works

Use the options on the Policy Library tab to create your own policy from an existing policy, or to
override the settings from an existing policy so that you can apply the new settings to groups of
objects. You can also import and export a policy.
VMware, Inc. 402

To display the details for a selected policy, click the split bar to expand the pane. The Details and
Related Items tabs and options for the policy appear in the lower pane. On the Related Items tab,
you can also apply the selected policy to object groups.
When you add or edit a policy, you access the policy workspace where you select the base
policies and override the settings for analysis, metrics, properties, alert definitions, and symptom
definitions. In this workspace, you can also apply the policy to object groups. To update the
policy association with an object group, the role assigned to your user account must have the
Manage Association permission enabled for policy management.
Where You Manage the Policy Library

To manage the policy library, in the menu, click Administration, and then in the left pane click
Policies. The Policy Library tab appears and lists the policies available to use for your
environment.
Table 4-107. Policy Library Tab Options

Option Description
Toolbar Use the toolbar selections to take action in the policy library.
n Add New Policy. Create a policy from an existing policy.
n Edit Selected Policy. Customize the policy so that you can override settings for
vRealize Operations Manager to analyze and report data about the associated
objects.
n Set Default Policy. You can set any policy to be the default policy, which applies
the settings in that policy to all objects that do not have a policy applied. When
you set a policy to be the default policy, the priority is set to D, which gives that
policy the highest priority.
n Import Policy and Export Policy. You can import or export a policy in XML format.
To import or export a policy, the role assigned to your user account must have the
Import or Export permissions enabled for policy management.
n Delete Selected Policy. Remove a policy from the list.
Policy Library Tab data grid vRealize Operations Manager displays the high-level details for the policies.
n Name. Name of the policy as it appears in the Add or Edit Monitoring Policy wizard,
and in areas where the policy applies to objects, such as in Custom Groups.
n Description. Meaningful description of the policy, such as which policy is inherited,
and any specific information users need to understand the relationship of the
policy to one or more groups of objects.
n Last Modified. Date and time that the policy was last modified.
n Modified By. User who last modified the policy settings.
VMware, Inc. 403

Table 4-107. Policy Library Tab Options (continued)

Option Description
Policy Library Tab > Details Tab The Details tab displays the name and description of the policy from which the settings
are inherited, the policy priority, who last modified the policy, and the number of
object groups associated with the policy. From the Details tab, you can view the
settings that are locally defined in your policy, and the complete group of settings that
include both customized settings and the settings inherited from the base policies
selected when the policy was created.
n Locally Defined Settings. Displays the locally changed policy element settings for
each object type in the policy.
n Complete Settings Including Inherited. Displays all of the policy element settings for
each object type in the policy, including locally changed settings and settings that
are inherited. A summary of the enabled and disabled alert definitions, symptom
definitions, and attributes appear indicate the number of changes in the policy. The
policy element settings include symptom thresholds, and indicate changes made to
the Workload, Capacity Remaining, and Time Remaining settings.
Related Objects Tab Summarizes the related groups and objects, and details about the selected object
group and objects.
n Groups. Displays the groups of objects associated with the selected active policy,
and provides options to add and release an association.
n Add Association. Opens the Apply the policy to groups dialog box where you
select object groups to associate with the selected policy.
n Release Association. Opens a confirmation dialog box to confirm the release of
the object group that is associated with the selected policy.
n Data grid. Displays the groups assigned to this policy, the object types
associated with the group, and the number of objects in the group.
n Details for the selected object group. Displays the object group name, type,
and number of members associated with the selected policy, and the type of
association with the policy. An object group can have a direct association with
a policy, and inherited policy associations based on the base policies that you
selected when you created a local policy. For example, if the Base Settings
policy appears in the list, with an inherited association, the Base Settings policy
was included in the base policies selected when this policy was created.
n Affected Objects. Displays the names of the objects in your environment, their
object types, and associated adapters. When a parent group exists for an object, it
appears in this data grid.
Operational Policies
Determine how to have vRealize Operations Manager monitor your objects, and how to notify
you about problems that occur with those objects.
vRealize Operations Manager Administrators assign policies to object groups and applications to
support Service Level Agreements (SLAs) and business priorities. When you use policies with
object groups, you ensure that the rules defined in the policies are quickly put into effect for the
With policies, you can:
n Enable and disable alerts.
VMware, Inc. 404

n Control data collections by persisting or not persisting metrics on the objects in your
environment.
n Configure the product analytics and thresholds.
n Monitor objects and applications at different service levels.
n Prioritize policies so that the most important rules override the defaults.
n Understand the rules that affect the analytics.
n Understand which policies apply to object groups.
vRealize Operations Manager includes a library of built-in active policies that are already defined
for your use. vRealize Operations Manager applies these policies in priority order.
When you apply a policy to an object group, vRealize Operations Manager collects data from the
objects in the object group based on the thresholds, metrics, super metrics, attributes,
properties, alert definitions, and problem definitions that are enabled in the policy.
The following examples of policies might exist for a typical IT environment.
n Maintenance: Optimized for ongoing monitoring, with no thresholds or alerts.
n Critical Production: Production environment ready, optimized for performance with sensitive
alerting.
n Important Production: Production environment ready, optimized for performance with

medium alerting.
n Batch Workloads: Optimized to process jobs.
n Test, Staging, and QA: Less critical settings, fewer alerts.
n Development: Less critical settings, no alerts.
n Low Priority: Ensures efficient use of resources.
n Default Policy: Default system settings.
Types of Policies
There are three types of policies such as default policies, custom policies, and policies that are
offered with vRealize Operations Manager.
Custom Policies
You can customize the default policy and base policies included with vRealize Operations
Manager for your own environment. You can then apply your custom policy to groups of objects,
such as the objects in a cluster, or virtual machines and hosts, or to a group that you create to
include unique objects and specific criteria.
You must be familiar with the policies so that you can understand the data that appears in the
user interface, because policies drive the results that appear in the vRealize Operations Manager
dashboards, views, and reports.
VMware, Inc. 405

To determine how to customize operational policies and apply them to your environment, you
must plan ahead. For example:
n Must you track CPU allocation? If you overallocate CPU, what percentage must you apply to
your production and test objects?
n Will you overallocate memory or storage? If you use High Availability, what buffers must you
use?
n How do you classify your logically defined 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 settings, then override
specific settings 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 settings on all object types to have vRealize Operations
Manager report on workload, and so on.
n Enable specific attributes for collection, including metrics, properties, and super metrics.
n Enable or disable alert definitions and symptom definitions in your custom policy settings.
n Apply the custom policy to object groups.
When you use an existing policy to create a custom policy, you override the policy settings 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 buffers. To allocate and configure 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.
VMware, Inc. 406

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 settings to fine-tune them until
vRealize Operations Manager displays the results that are meaningful and that affect for your
environment. For example, you can adjust the capacity buffer settings in your policy, and then
view the data that appears in the dashboards to see the effect of the policy settings.
Default Policy in vRealize Operations Manager

The default policy is a set of rules that applies to the majority of your objects.
The Default policy appears on the Active Policies tab, and is marked with the letter D in the
Priority column. The Default policy can apply to any number of objects.
The Default policy always appears at the bottom in the list of policies, even if that policy is not
associated with an object group. When an object group does not have a policy applied, vRealize
Operations Manager associates the Default policy with that group.
A policy can inherit the Default policy settings, and those settings can apply to various objects
under several conditions.
The policy that is set to Default always takes the lowest priority. If you attempt to set two
policies as the Default policy, the first policy that you set to Default is initially set to the lowest
priority. When you set the second policy to Default, that policy then takes the lowest priority,
and the earlier policy that you set to Default is set to the second lowest priority.
You can use the Default policy as the base policy to create your own custom policy. You modify
the default policy settings to create a policy that meets your analysis and monitoring needs.
When you start with the Default policy, your new policy inherits all of the settings from the
Default base policy. You can then customize your new policy and override these settings.
The data adapters and solutions installed in vRealize Operations Manager provide a collective
group of base settings that apply to all objects. In the policy navigation tree on the Policy Library
tab, these settings are called Base Settings. The Default policy inherits all of the base settings by
default.
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 settings in new policies that you
create.
Where You Find the Policies Provided with vRealize Operations Manager Policies
In the menu, click Administration, and then in the left pane click Policies. Click the Policy Library
tab. To see the policies provided with vRealize Operations Manager, expand the Base Settings
policy.
VMware, Inc. 407

Policies That vRealize Operations Manager Includes

All policies exist under the Base Settings, because the data adapters and solutions installed in
your vRealize Operations Manager instance provide a collective group of base settings that apply
to all objects. In the policy navigation tree on the Policy Library tab, these settings are called
Base Settings.
The Base Settings 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 Settings, because
the data adapters and solutions installed in your vRealize Operations Manager instance provide a
collective group of base settings that apply to all objects.
The Config Wizard Based Policy set includes policies provided with vRealize Operations Manager
that you use for specific settings on objects to report on your objects. The Config Wizard Based
Policy set includes several types of policies:
n Efficiency alerts policies for infrastructure objects and virtual machines
n Health alerts policies for infrastructure objects
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.
Using the Monitoring Policy Workspace to Create and Modify

Operational Policies
You can use the workflow in the monitoring policy workspace to create local policies quickly, and
update the settings in existing policies. Select a base policy to use as the source for your local
policy settings, and modify the thresholds and settings used for analysis and collection of data
from groups of objects in your environment. A policy that has no local settings defined inherits
the settings from its base policy to apply to the associated object groups.
Prerequisites
Verify that objects groups exist for vRealize Operations Manager to analyze and collect data, and
if they do not exist, create them. See Managing Custom Object Groups in VMware vRealize
Operations Manager.
Procedure
1 In the menu, click Administration, and then in the left pane click Policies.
2 Click Policy Library, and click the Add New Policy icon to add a policy, or select the policy
and click the Edit Selected Policy icon to edit an existing policy.
You can add and edit policies on the Policy Library tab, and remove certain policies. You can
use the Base Settings policy or the Default Policy as the root policy for the settings in other
policies that you create. You can set any policy to be the default policy.
VMware, Inc. 408

3 In the Getting Started workspace, assign a name and description to the policy.
Give the policy a meaningful name and description so that all users know the purpose of the
policy.
4 Click Select Base Policies, and in the workspace, select one or more policies to use as a
baseline to define the settings for your new local policy.
When you create a policy, you can use any of the policies provided with vRealize Operations
Manager as a baseline source for your new policy settings.
5 Click Override Settings, and in the workspace, filter the object types to customize your policy
for the objects to associate with this policy.
Filter the object types, and modify the settings for those object types so that vRealize
Operations Manager collects and displays the data that you expect in the dashboards and
views.
6 Click Override Attributes, and in the workspace, select the metric, property, or super metric
attributes to include in your policy.
vRealize Operations Manager collects data from the objects in your environment based on
the metric, property, or super metric attributes that you include in the policy.
7 Click Override Alert / Symptom Definitions, and in the workspace, enable or disable the alert
definitions and symptom definitions for your policy.
vRealize Operations Manager identifies problems on objects in your environment and triggers
alerts when conditions occur that qualify as problems.
8 Click Apply Policy to Groups, and in the workspace, select one or more groups to which the
policy applies.
VMware vRealize Operations Manager monitors the objects according to the settings in the
policy that is applied to the object group, triggers alerts when thresholds are violated, and
reports the results in the dashboards, views, and reports. If you do not assign a policy to one
or more object groups, VMware vRealize Operations Manager does not assign the settings in
that policy to any objects, and the policy is not active. For an object group that dos not have
a policy assigned, VMware vRealize Operations Manager associates the object group with the
Default Policy.
9 Click Save to retain the settings defined for your local policy.
What to do next
After vRealize Operations Manager analyzes and collects data from the objects in your
environment, review the data in the dashboards and views. If the data is not what you expected,
edit your local policy to customize and override the settings until the dashboards display the data
that you need.
VMware, Inc. 409

Policy Workspace in vRealize Operations Manager

The policy workspace allows you to quickly create and modify policies. To create a policy, you
can inherit the settings from an existing policy, and you can modify the settings in existing
policies if you have adequate permissions. After you create a policy, or edit an existing policy,
you can apply the policy to one or more groups of objects.
How the Policy Workspace Works

Every policy includes a set of packages, and uses the defined problems, symptoms, metrics, and
properties in those packages to apply to specific object groups in your environment. You can
view details for the settings inherited from the base policy, and display specific settings for
certain object types. You can override the settings of other policies, and include additional policy
settings to apply to object types.
Use the Add and Edit options to create policies and edit existing policies.
Where You Create and Modify a Policy

To create and modify policies, in the menu, click Administration, and then in the left pane click
Policies. Click the Policy Library tab, and click the Add New Policy icon to add a policy or click
the Edit Selected Policy icon to edit a policy. The policy workspace is where you select the base
policies, and customize and override the settings for analysis, metrics, properties, alert
definitions, and symptom definitions. In this workspace, you can apply the policy to object
groups.
To remove a policy from the list, select the policy and click the red X.
Policy Workspace Options

The policy workspace includes a step-by-step workflow to create and edit a policy, and apply the
policy to custom object groups.
n Getting Started Details

When you create a policy, you must give the policy a meaningful name and description so
that users know the purpose of the policy.
n Select Base Policy Details

You can use any of the policies provided with vRealize Operations Manager as a baseline
source for your policy settings when you create a new policy. In the policy content area, you
can view the packages and elements for the base policy and additional policies that you
selected to override the settings, and compare the differences in settings highlighted
between these policies. You select the settings and objects types to display.
n Analysis Settings Details

You can filter the object types, and modify the settings for those object types so that
vRealize Operations Manager applies these settings. The data that you expect then appears
in the dashboards and views.
VMware, Inc. 410

n Workload Automation Details

You can set the workload automation options for your policy, so that vRealize Operations
Manager can optimize the workload in your environment per your definition.
n Collect Metrics and Properties Details

You can select the attribute type to include in your policy so that vRealize Operations
Manager can collect data from the objects in your environment. Attribute types include
metrics, properties, and super metrics. You enable or disable each metric, and determine
whether to inherit the metrics from base policies that you selected in the workspace.
n Alert and Symptom Definitions Details

You can enable or disable alert and symptom definitions to have vRealize Operations
Manager identify problems on objects in your environment and trigger alerts when
conditions occur that qualify as problems. You can automate alerts.
n Apply Policy to Groups Details

You can assign your local policy to one or more groups of objects to have VMware vRealize
Operations Manager analyze those objects according to the settings in your policy, trigger
alerts when the defined threshold levels are violated, and display the results in your
dashboards, views, and reports.
Getting Started Details

When you create a policy, you must give the policy a meaningful name and description so that
users know the purpose of the policy.
Where You Assign the Policy Name and Description
To add a name and description to a policy, in the menu, click Administration, and then in the left
pane click Policies. Click the Policy Library tab, and click the Add New Policy icon to add a policy
or click the Edit Selected Policy icon to edit a policy. In the Add or Edit Monitoring policy
workspace, on the left click Getting Started. The name and description appear in the workspace.
Table 4-108. Name and Description Options in the Add or Edit Monitoring Policy Workspace
Option Description
Name Name of the policy as it appears in the Add or Edit Monitoring Policy wizard, and in
areas where the policy applies to objects, such as Custom Groups.
Description Meaningful description of the policy. For example, use the description to indicate which
policy is inherited, and any specific information that users need to understand the
relationship of the policy to one or more groups of objects.
Start with The base policy that will be used as a starting point. All settings from the base policy
will be inherited as default settings in your new policy. You can override these settings
to customize the new policy.
Select a base policy to inherit the base policy settings as a starting point for your new
policy.
VMware, Inc. 411

Select Base Policy Details

You can use any of the policies provided with vRealize Operations Manager as a baseline source
for your policy settings when you create a new policy. In the policy content area, you can view
the packages and elements for the base policy and additional policies that you selected to
override the settings, and compare the differences in settings highlighted between these policies.
You select the settings and objects types to display.
How the Select Base Policies Workspace Works
To create a policy, select a base policy from which your new custom policy inherits settings. To
override some of the settings in the base policy according to the requirements for the service
level agreement for your environment, you can select and apply a separate policy for a
management pack solution. The override policy includes specific settings defined for the types of
objects to override, either manually or that an adapter provides when it is integrated with
vRealize Operations Manager. The settings in the override policy overwrite the settings in the
base policy that you selected.
When you select and apply a policy in the left pane to use to overwrite the settings that your
policy inherits from the base policy, the policy that you select appears in the applied policy
history list in the right pane.
The right pane displays tabs for the inherited policy configuration, and your policy, and displays a
preview of the selected policy tab in the Policy Preview pane. When you select one of the policy
tabs, you can view the number of enabled and disabled alert definitions, symptom definitions,
metrics and properties, and the number of enabled and disabled changes.
In the right pane, you select the objects to view so that you can see which policy elements apply
to the object type. For example, when you select the StorageArray object type, and you click the
tab to display the configuration settings for your policy, the Policy Preview pane displays the
local packages for the policy and the object group types with the number of policy elements in
each group.
You can preview the policy settings for all object types, only the object types that have settings
changed locally, or settings for new object types that you add to the list, such as Storage Array
storage devices.
Where You Select and Override Base Policies Settings
To select a base policy to use as a starting point for your own policy, and to select a policy to
override one or more settings that your policy inherits from the base policy, in the menu, select
Administration, and then in the left pane click Policies. Click the Policy Library tab, and click the
Add New Policy icon to add a policy or click the Edit Selected Policy icon to edit a policy. In the
Add or Edit Monitoring policy workspace, on the left add a name for the policy and click Select
Base Policy. The policy configuration, objects, and preview appear in the workspace.
VMware, Inc. 412

Table 4-109. Base Policy and Override Settings in the Add or Edit Monitoring Policy Workspace
Option Description
Show changes for Select the objects to view changes.

n All object types. Displays the number of enabled and disabled alert definitions,
symptom definitions, and metrics and properties, the number of enabled and
disabled changes, and the object type groups and the number of local policy
elements for each group.
n All object types with overrides. Displays the object types that have changes
applied, with the objects types selected for override. Use the drop-down menu to
select object types. Click the filter button to add the selected object type to the list
so that you can preview and configure the settings.
n Add settings for new set of objects. Provides a list of the object types so that you
can select an object type, such as Storage Devices > SAN, and add the selected
object to the Object types list.
Override settings from Select and apply one or more policies to override the settings that your policy inherits
additional policies from the base policy.
Apply Applies the override policy to your policy, and lists the override policy in the applied
policy history.
Applied policy template history Displays the policies that you selected to override the settings in your policy.
Configuration inherited from When selected, displays a preview of the inherited policy configuration in the Policy
base policy Preview pane.
Configuration settings defined When selected, displays a preview of your policy configuration in the Policy Preview
in this policy pane.
Policy Preview Displays summary information about the local packages and object group types.
n Packages (Local). Displays the number of enabled and disabled alert definitions,
symptom definitions, metrics and properties, and the number of policy elements
for each object group.
n Object Type groups. Displays the associated object groups.
n Drop down arrows on packages and settings. Displays the packages and settings
for the displayed policies.
Analysis Settings Details

You can filter the object types, and modify the settings for those object types so that vRealize
Operations Manager applies these settings. The data that you expect then appears in the
dashboards and views.
How the Analysis Settings Workspace Works
When you turn on and configure the analysis settings for a policy, you can override the settings
for the policy elements that vRealize Operations Manager uses to trigger alerts and display data.
These types of settings include symptom thresholds based on alerts, situational settings such as
committed projects to calculate capacity and time remaining, and other detailed settings.
You expand a policy element setting and configure the values to make your policy specific. For
example, to reclaim capacity, you can set percentages to have vRealize Operations Manager
indicate when a resource is oversized, idle, or powered off.
VMware, Inc. 413

Policies focus on objects and object groups. When you configure policy element settings for your
local policy, you must consider the object type and the results that you expect to see in the
dashboards and views. If you do not make any changes to the settings, your local policy retains
the settings that your policy inherited from the base policy that you selected.
Where You Set the Policy Analysis Settings
To set the analysis settings for your policy, in the menu, click Administration, and then in the left
pane click Policies. Click the Policy Library tab, and click the Add New Policy icon to add a policy
or click the Edit Selected Policy icon to edit a policy. In the Add or Edit Monitoring policy
workspace, on the left click Analysis Settings. The analysis settings for host systems, virtual
machines, and other object types that you select appear in the workspace.
Table 4-110. Analysis Settings in the Add or Edit Monitoring Policy Workspace
Option Description
Show changes for Select the objects to view changes.

n All object types. Displays the number of enabled and disabled alert definitions,
symptom definitions, and metrics and properties, the number of enabled and
disabled changes, and the object type groups and the number of local policy
elements for each group.
n All object types with overrides. Displays the object types that have changes
applied, with the objects types selected for override. Use the drop-down menu to
select object types. Click the filter button to add the selected object type to the list
so that you can preview and configure the settings.
n Add settings for new set of objects. Provides a list of the object types so that you
can select an object type, such as Storage Devices > SAN, and add the selected
object to the Object types list.
Right pane - Analysis Settings The right pane displays a list of the object types that you selected in the left pane.
for object types Expand a view of the policy elements and settings for the object type so that you can
have vRealize Operations Manager analyze the object type.
Expand the view for the object type so that you can view and modify the threshold
settings for the following policy elements:
n Workload
n Time Remaining
n Capacity Remaining
n Compliance
n Maintenance Schedule
Click the lock icon on the right of each element to override the settings and change the
thresholds for your policy.
Time Remaining Calculations You can set the risk level for the time that is remaining when the forecasted total need
of a metric reaches usable capacity.
n Conservative. Select this option for production and mission critical workloads.
n Aggressive. Select this option for non-critical workloads.
Policy Workload Element

Workload is a measurement of the demand for resources on an object. You can turn on and
configure the settings for the Workload element for the object types in your policy.
How the Workload Element Works
VMware, Inc. 414

The Workload element determines how vRealize Operations Manager reports on the resources
that the selected object group uses. The resources available to the object group depend on the
amount of configured and usable resources.
n A specific amount of physical memory is a configured resource for a host system, and a
specific number of CPUs is a configured resource for a virtual machine.
n The usable resource for an object or an object group is a subset of, or equal to, the
configured amount.
n The configured and usable amount of a resource can vary depending on the type of resource
and the amount of virtualization overhead required, such as the memory that an ESX host
machine requires to run the host system. When accounting for overhead, the resources
required for overhead are not considered to be usable, because of the reservations required
for virtual machines or for the high availability buffer.
Where You Override the Policy Workload Element
To view and override the policy workload analysis setting, in the menu, click Administration, and
then in the left pane click Policies. Click the Policy Library tab. Click the Add New Policy icon to
add a policy or click the Edit Selected Policy icon to edit a policy. In the Add or Edit Monitoring
policy workspace, click Analysis Settings, then select one or more objects in the left pane. The
workload settings for the object types that you selected appear in the right pane.
View the Workload policy element, and configure the settings for your policy.
If you do not configure the policy element, your policy inherits the settings from the selected
base policy.
Table 4-111. Policy Workload Element Settings in the Add or Edit Monitoring Policy Workspace
Option Description
Lock icon Enables you to override the policy element settings so that you can customize the
policy to monitor the objects in your environment.
Workload Score Threshold Allows you to set the number of collection cycles it takes to trigger or clear an alert.
Policy Time Remaining Element

The Time remaining element is a measure of the amount of time left before your objects run out
of capacity.
How the Time Remaining Element Works
The Time Remaining element determines how vRealize Operations Manager reports on the
available time until capacity runs out for a specific object type group.
n The time remaining indicates the amount of time that remains before the object group
consumes the capacity available. vRealize Operations Manager calculates the time remaining
as the number of days remaining until all the capacity is consumed.
n To keep the Time Remaining more than the critical threshold setting or to keep it green, your
objects must have more days of capacity available.
Where You Override the Policy Time Remaining Element
VMware, Inc. 415

To view and override the policy Time Remaining analysis setting, in the menu, click
Administration, and then in the left pane click Policies. Click the Policy Library tab. Click the Add
New Policy icon to add a policy or click the Edit Selected Policy icon to edit a policy. In the Add
or Edit Monitoring policy workspace, click Analysis Settings, then select one or more objects in
the left pane. The time remaining settings for the object types that you selected in the workspace
appear in the right pane.
View the Time Remaining policy element and configure the settings for your policy.
base policy.
Table 4-112. Policy Time Remaining Element Settings in the Add or Edit Monitoring Policy
Workspace
Option Description
Time Remaining Score Allows you to set the number of days until capacity is projected to run out based on
Threshold your current consumption trend.
Policy Capacity Remaining Element

Capacity is a measurement of the amount of memory, CPU, and disk space for an object. You can
turn on and configure the settings for the Capacity Remaining element for the object types in
your policy.
How the Capacity Remaining Element Works
The Capacity Remaining element determines how vRealize Operations Manager reports on the
available capacity until resources run out for a specific object type group.
n The capacity remaining indicates the capability of your environment to accommodate

workload.
n Usable capacity is a measurement of the percentage of capacity available, minus the capacity
affected when you use high availability.
Where You Override the Policy Capacity Remaining Element
To view and override the policy Capacity Remaining analysis setting, in the menu, click
Administration, and then in the left pane click Policies. Click the Policy Library tab. Click the Add
the left pane. The capacity remaining settings for the object types that you selected in the
workspace appear in the right pane.
View the Capacity Remaining policy element and configure the settings for your policy.
base policy.
VMware, Inc. 416

Table 4-113. Policy Capacity Remaining Element Settings in the Add or Edit Monitoring Policy
Workspace
Option Description
Capacity Remaining Score Allows you to set the percentage at which the capacity remaining alerts must be
Threshold triggered.
Policy Compliance Element

Compliance is a measurement that ensures that the objects in your environment meet industrial,
governmental, regulatory, or internal standards. You can unlock and configure the settings for
the Compliance element for the object types in your policy.
Where You Override the Policy Compliance Element
To view and override the policy Compliance analysis setting, in the menu, click Administration,
and then in the left pane click Policies. Click the Policy Library tab. Click the Add New Policy icon
to add a policy or click the Edit Selected Policy icon to edit a policy. In the Add or Edit
Monitoring policy workspace, click Analysis Settings, then select one or more objects in the left
pane. The compliance settings for the object types that you selected appear in the right pane.
View the Compliance policy element and configure the settings for your policy.
base policy.
Table 4-114. Policy Compliance Element Settings in the Add or Edit Monitoring Policy Workspace
Option Description
Compliance Score Threshold Allows you to set the compliance score threshold based on the number of violations
against those standards.
Policy Maintenance Schedule Element

You can set a time to perform maintenance tasks for each policy.
Where You Override the Policy Maintenance Schedule Element
To view and override the policy Maintenance Schedule analysis setting, in the menu, click
Administration, and then in the left pane, click Policies. Click the Policy Library tab. Click the Add
the left pane. The maintenance schedule settings for the object types that you selected appear in
the right pane.
View the maintenance schedule policy element.
base policy.
VMware, Inc. 417

Table 4-115. Policy Maintenance Schedule Element Settings in the Add or Edit Monitoring Policy
Workspace
Option Description
Maintenance Schedule Sets a time to perform maintenance tasks. During maintenance, vRealize Operations
Manager does not calculate analytics.
Policy Allocation Model Element

Allocation model defines how much CPU, memory, or disk space is allocated to objects in a
cluster or datastore cluster. In the policy, you can turn on the Allocation Model element and
configure the resource allocation for the objects.
How the Allocation Model Element Works
The Allocation Model element determines how vRealize Operations Manager calculates capacity
when you allocate a specific amount of CPU, memory, and disk space resource to clusters or
data store clusters. You can specify the allocation ratio for either one, or all of the resource
containers of the cluster. Unlike the demand model, the allocation model is used for capacity
calculations only when you turn it on in the policy.
The allocation model element also affects the reclaimable resources for memory and storage in
Reclaim page. When you turn on the Allocation Model element in the policy, the tabular
representation of the VMs and snapshots in the selected data center from which resources can
be reclaimed displays reclaimable memory and disk space based on the overcommit values.
Where You Override the Allocation Model Element
To view and override the policy workload analysis setting, in the menu, click Administration, and
then in the left pane click Policies. Click the Policy Library tab. Click the Add New Policy icon to
add a policy or click the Edit Selected Policy icon to edit a policy. In the Add or Edit Monitoring
policy workspace, click Analysis Settings and click All object types. The analysis settings for the
object types appear in the right pane.
Click the unlock icon next to Allocation Model to set the overcommit ratios.
Table 4-116. Policy Allocation Model Element Settings

Option Description
Set overcommit ratio, to enable Allows you to set the overcommit ratio for CPU, memory, or disk space. Select the
Allocation Model check box next to the resource container you want to edit and change the overcommit
ratio value.
Policy Custom Profile Element

The custom profile element lets you apply a custom profile which shows how many more of a
specified object can fit in your environment depending on the available capacity and object
configuration.
Where You Define the Custom Profiles
To define a custom profile, in the menu click Administration, and then in the left pane click
Configuration. Click Custom Profiles and click the Add icon to define a new custom profile.
VMware, Inc. 418

Where You Select the Custom Profile Element
To view and override the policy Custom Profile analysis setting, in the menu, click Administration,
and then in the left pane click Policies. Click the Policy Library tab. Click the Add New Policy icon
to add a policy or click the Edit Selected Policy icon to edit a policy. In the Add or Edit
Monitoring policy workspace, click Analysis Settings, select Cluster or Datastore Cluster in the
left pane and click Show Object Type. The custom profile element for the object types that you
selected in the workspace appear in the right pane. Click the lock icon to unlock the section and
make changes.
Workload Automation Details

You can set the workload automation options for your policy, so that vRealize Operations
Manager can optimize the workload in your environment per your definition.
How the Workload Automation Workspace Works
You click the lock icon to unlock and configure the workload automation options specific for your
policy. When you click the lock icon to lock the option, your policy inherits the parent policy
settings.
Where You Set the Policy Workload Automation
To set the workload automation for your policy, in the menu, click Administration, and then in
the left pane click Policies. Click the Policy Library tab, and click the Add New Policy icon to add
a policy or click the Edit Selected Policy icon to edit a policy. In the Add or Edit Monitoring policy
workspace, on the left click Workload Automation.
Table 4-117. Workload Automation in the Add or Edit Monitoring Policy Workspace
Option Description
Workload Optimization Select a goal for workload optimization.

Select Balance when workload performance is your first goal. This approach
proactively moves workloads so that the resource utilization is balanced, leading to
maximum headroom for all resources.
Select Moderate when you want to minimize the workload contention.
Select Consolidate to proactively minimize the number of clusters used by workloads.
You might be able to repurpose resources that are freed up. This approach is good for
cost optimization, while making sure that performance goals are met. This approach
might reduce licensing and power costs.
Cluster Headroom Headroom establishes a required capacity buffer, for example, 20 percent. It provides
you with an extra level of control and ensures that you have extra space for growth
inside the cluster when required. Defining a large headroom setting limits the systems
opportunities for optimization.
Advanced Settings Click Advanced Settings to select what type of virtual machines vRealize Operations
Manager moves first to address workload. You can set Storage vMotion on or off. The
default is ON.
Collect Metrics and Properties Details

You can select the attribute type to include in your policy so that vRealize Operations Manager
can collect data from the objects in your environment. Attribute types include metrics, properties,
VMware, Inc. 419

and super metrics. You enable or disable each metric, and determine whether to inherit the
metrics from base policies that you selected in the workspace.
How the Collect Metrics and Properties Workspace Works
When you create or customize a policy, you can override the base policy settings to have
vRealize Operations Manager collect the data that you intend to use to generate alerts, and
report the results in the dashboards.
To define the metric and super metric symptoms, metric event symptoms, and property
symptoms, in the menu, click Alerts and then in the left pane click Alert Settings > Symptom
Definitions.
Where You Override the Policy Attributes
To override the attributes and properties settings for your policy, in the menu, click
Add or Edit Monitoring policy workspace, on the left click Collect Metrics and Properties. The
attributes and properties settings for the selected object types appear in the workspace.
Table 4-118. Collect Metrics and Properties Options

Option Description
Actions Select one or more attributes and select enable, disable, or inherit to change the state and KPI for
this policy.
Filter options Deselect the options in the Attribute Type, State, KPI, and DT drop-down menus, to narrow the
list of attributes.
n Enabled. Indicates that an attribute will be calculated.
n Enabled (Force). Indicates state change due to a dependency.
n Disabled. Indicates that an attribute will not be calculated.
n Inherited. Indicates that the state of this attribute is inherited from the base policy and will
be calculated.
n Inherited. Indicates that the state of this attribute is inherited from the base policy and will
not be calculated.
The KPI determines whether the metric, property, or super metric attribute is considered to be a
key performance indicator (KPI) when vRealize Operations Manager reports the collected data in
the dashboards. Filter the KPI states to display attributes with KPI enabled, disabled, or inherited
for the policy.
Object Type Filters the attributes list by object type.
VMware, Inc. 420

Table 4-118. Collect Metrics and Properties Options (continued)

Option Description
Page Size The number of attributes to list per page.
Attributes data grid Display the attributes for a specific object type.
n Name. Identifies the name of the metric or property for the selected object type.
n Type. Distinguishes the type of attribute to be either a metric, property, or super metric.
n Adapter Type. Identifies the adapter used based on the object type selected, such as Storage
Devices.
n Object Type. Identifies the type of object in your environment, such as StorageArray.
n State. Indicates whether the metric, property, or super metric is inherited from the base
policy.
n KPI. Indicates whether the key performance indicator is inherited from the base policy. If a
violation against a KPI occurs, vRealize Operations Manager generates an alert.
n DT. Indicates whether the dynamic threshold (DT) is inherited from the base policy.
Alert and Symptom Definitions Details

You can enable or disable alert and symptom definitions to have vRealize Operations Manager
identify problems on objects in your environment and trigger alerts when conditions occur that
qualify as problems. You can automate alerts.
How the Alert and Symptom Definitions Workspace Works
vRealize Operations Manager collects data for objects and compares the collected data to the
alert definitions and symptom definitions defined for that object type. Alert definitions include
associated symptom definitions, which identify conditions on attributes, properties, metrics, and
events.
You can configure your local policy to inherit alert definitions from the base policies that you
select, or you can override the alert definitions and symptom definitions for your local policy.
Before you add or override the alert definitions and symptom definitions for a policy, familiarize
yourself on the available alerts and symptoms.
n To view the available alert definitions, in the menu, click Alerts and then in the left pane click
Alert Settings > Alert Definitions.
n To view the available symptom definitions, in the menu, click Alerts and then in the left pane
click Alert Settings > Symptom Definitions. Symptom definitions are available for metrics,
properties, messages, faults, smart early warnings, and external events.
A summary of the number of problem and symptoms that are enabled and disabled, and the
difference in changes of the problem and symptoms as compared to the base policy, appear in
the Analysis Settings pane of the policies workspace.
VMware, Inc. 421

Where You Override the Alert Definitions and Symptom Definitions

To override the alert definitions and symptom definitions for your policy, in the menu, click
Add or Edit Monitoring policy workspace, on the left click Alert / Symptom Definitions. The
definitions appear in the workspace.
Policy Alert Definitions and Symptom Definitions

You can override the alert definitions and symptom definitions for each policy.
n Policy Alert Definitions

Each policy includes alert definitions. Each alert uses a combination of symptoms and
recommendations to identify a condition that classifies as a problem, such as failures or high
stress. You can enable or disable the alert definitions in your policy, and you can set actions
to be automated when an alert triggers.
n Policy Symptom Definitions

Each policy includes a package of symptom definitions. Each symptom represents a distinct
test condition on a property, metric, or event. You can enable or disable the symptom
definitions in your policy.
Policy Alert Definitions

Each policy includes alert definitions. Each alert uses a combination of symptoms and
recommendations to identify a condition that classifies as a problem, such as failures or high
stress. You can enable or disable the alert definitions in your policy, and you can set actions to be
automated when an alert triggers.
How the Policy Alert Definitions Work
vRealize Operations Manager uses problems to trigger alerts. A problem manifests when a set of
symptoms exists for an object, and requires you to take action on the problem. Alerts indicate
problems in your environment. vRealize Operations Manager generates alerts when the collected
data for an object is compared to alert definitions for that object type and the defined symptoms
are true. When an alert occurs, vRealize Operations Manager presents the triggering symptoms
for you to take action.
Some of the alert definitions include predefined symptoms. When you include symptoms in an
alert definition, and enable the alert, an alert is generated when the symptoms are true.
The Alert Definitions pane displays the name of the alert, the number of symptoms defined, the
adapter, object types such as host or cluster, and whether the alert is enabled as indicated by
Local, disabled as indicated by not Local, or inherited. Alerts are inherited with a green
checkmark by default, which means that they are enabled.
You can automate an alert definition in a policy when the highest priority recommendation for the
alert has an associated action.
VMware, Inc. 422

To view a specific set of alerts, you can select the badge type, criticality type, and the state of
the alert to filter the view. For example, you can set the policy to send fault alerts for virtual
machines.
Where You Modify the Policy Alert Definitions
To modify the alerts associated with policies, in the menu, click Administration, and then in the
left pane click Policies. Click the Policy Library tab, and click the Add New Policy icon to add a
policy or click the Edit Selected Policy icon to edit a policy. In the Add or Edit Monitoring policy
workspace, on the left click Alert / Symptom Definitions. The alert definitions and symptom
definitions for the selected object types appear in the workspace.
Table 4-119. Alert Definitions in the Add or Edit Monitoring Policy Workspace
Option Description
Actions Select one or more alert definitions and select enable, disable, or inherit to change the
state for this policy.
Filter options Deselect the options in the Type and State drop-down menus, to narrow the list of
symptom definitions.
Impact indicates the health, risk, and efficiency badges to which the alerts apply.
Criticality indicates the information, critical, immediate, warning, or automatic criticality
types to which the alert definition applies.
Automate indicates the actions that are enabled for automation when an alert triggers,
or actions that are disabled or inherited. Actions that are enabled for automation might
appear as inherited with a green checkmark, because policies can inherit settings from
each other. For example, if the Automate setting in the base policy is set to Local with
a green checkmark, other policies that inherit this setting will display the setting as
inherited with a green checkmark.
Object Type Filters the alert definitions list by object type.
Page Size The number of alert definitions to list per page.
Filter Locates data in the alert definition list.
Alert Definitions data grid Displays information about the alert definitions for the object types. The full name for
Alert definition and the criticality icon appear in a tooltip when you hover the mouse
over the Alert Definition name.
n Name. Meaningful name for the alert definition.
n Symptom Definitions. Number of symptoms defined for the alert.
n Actionable Recommendations. Only recommendations with actions in the first
priority, as they are the only ones you can automate.
n Automate. When the action is set to Local, the action is enabled for automation
when an alert triggers. Actions that are enabled for automation might appear as
inherited with a green checkmark, because policies can inherit settings from each
other. For example, if the Automate setting in the base policy is set to Local with a
green checkmark, other policies that inherit this setting will display the setting as
inherited with a green checkmark.
n Adapter. Data source type for which the alert is defined.
n Object Type. Type of object to which the alert applies.
n State. Alert definition state, either enabled as indicated by Local, disabled as
indicated by not Local, or inherited from the base policy.
VMware, Inc. 423

If you do not configure the package, the policy inherits the settings from the selected base
policy.
Policy Symptom Definitions
Each policy includes a package of symptom definitions. Each symptom represents a distinct test
condition on a property, metric, or event. You can enable or disable the symptom definitions in
your policy.
How the Policy Symptom Definitions Work
vRealize Operations Manager uses symptoms that are enabled to generate alerts. When the
symptoms used in an alert definition are true, and the alert is enabled, an alert is generated.
When a symptom exists for an object, the problem exists and requires that you take action to
solve it. When an alert occurs, vRealize Operations Manager presents the triggering symptoms,
so that you can evaluate the object in your environment, and with recommendations for how to
resolve the alert.
To assess objects for symptoms, you can include symptoms packages in your policy for metrics
and super metrics, properties, message events, and faults. You can enable or disable the
symptoms to determine the criteria that the policy uses to assess and evaluate the data collected
from the objects to which the policy applies. You can also override the threshold, criticality, wait
cycles, and cancel cycles.
The Symptoms pane displays the name of the symptom, the associated management pack
adapter, object type, metric or property type, a definition of the trigger such as for CPU usage,
the state of the symptom, and the trigger condition. To view a specific set of symptoms in the
package, you can select the adapter type, object type, metric or property type, and the state of
the symptom.
When a symptom is required by an alert, the state of the symptom is enabled, but is dimmed so
that you cannot modify it. The state of a required symptom includes an information icon that you
can hover over to identify the alert that required this symptom.
Where You Modify the Policy Symptom Definitions
To modify the policy package of symptoms, in the menu, click Administration, and then in the
left pane click Policies. Click the Policy Library tab, and click the Add New Policy icon to add a
policy or click the Edit Selected Policy icon to edit a policy. In the Add or Edit Monitoring policy
workspace, on the left, click Alert / Symptom Definitions. The alert definitions and symptom
definitions for the selected object types appear in the workspace.
VMware, Inc. 424

Table 4-120. Symptom Definitions in the Add or Edit Monitoring Policy Workspace
Option Description
Actions Select one or more symptom definitions and select enable, disable, or inherit to
change the state for this policy.
Filter options Deselect the options in the Type and State drop-down menus, to narrow the list of
symptom definitions.
n Enabled. Indicates that a symptom definition will be included.
n Enabled (Force). Indicates state change due to a dependency.
n Disabled. Indicates that a symptom definition not be included.
n Inherited. Indicates that the state of this symptom definition is inherited from the
base policy and will be included.
n Inherited. Indicates that the state of this symptom definition is inherited from the
base policy and will not be included.
Type determines whether symptom definitions that apply to HT and DT metrics,
properties, events such as message, fault, and metric, and smart early warnings
appear in the list.
State determines whether enabled, disabled, and inherited symptom definitions appear
in the symptom definition list.
Object Type Filters the symptom definitions list by object type
Page Size The number of symptom definitions to list per page.
Filter Locate data in the symptom definition list.
Symptom Definitions data grid Displays information about the symptom definitions for the object types. The full name
for Symptom Definition appears in a tooltip when you hover the mouse over the
Symptom Definition name.
n Name. Symptom definition name as defined in the list of symptom definitions in the
Content area.
n Adapter. Data source type for which the alert is defined.
n Object Type. Type of object to which the alert applies.
n Type. Object type on which the symptom definition must be evaluated.
n Trigger. Static or dynamic threshold, based on the number of symptom definitions,
the object type and metrics selected, the numeric value assigned to the symptom
definition, the criticality of the symptom, and the number of wait and cancel cycles
applied to the symptom definition.
n State. Symptom definition state, either enabled, disabled, or inherited from the
base policy.
n Condition. Enables action on the threshold. When set to Override, you can change
the threshold. Otherwise set to default.
n Threshold. To change the threshold, you must set the State to Enabled, set the
condition to Override, and set the new threshold in the Override Symptom
Definition Threshold dialog box.
If you do not configure the package, the policy inherits the settings from the selected base
policy.
VMware, Inc. 425

Apply Policy to Groups Details

You can assign your local policy to one or more groups of objects to have VMware vRealize
Operations Manager analyze those objects according to the settings in your policy, trigger alerts
when the defined threshold levels are violated, and display the results in your dashboards, views,
and reports.
How the Apply Policy to Groups Workspace Works
When you create a policy, or modify the settings in an existing policy, you apply the policy to
one or more object groups. VMware vRealize Operations Manager uses the settings in the policy
to analyze and collect data from the associated objects, and displays the data in dashboards,
views, and reports.
Where You Apply a Policy to Groups
To apply the policy to object groups, in the menu, click Administration, and then in the left pane
click Policies. Click the Policy Library tab, and click the Add New Policy icon to add a policy or
click the Edit Selected Policy icon to edit a policy. In the Add or Edit Monitoring policy
workspace, on the left click Apply Policy to Groups.
Apply Policy to Groups Options

To apply the policy to groups of objects, select the check box for the object group in the
workspace.
You can then view the details about each object group associated with the policy. In the menu,
click Administration, and then in the left pane click Policies. Click Active Policies > Related
Objects. Click an object group in the list of groups, and view the summary in the Details pane.
For more information about how to create an object group, see the topic called Custom Object
Groups Workspace to Create a New Group.
For more information about how to create a policy, see Policy Workspace in vRealize Operations
Manager.
Define Monitoring Goals for vRealize Operations Manager Solutions

The Manage Solution configuration for the vSphere solution provides a set of questions for you
to answer to help you define the default policy settings associated with your vCenter Adapter.
You can create a policy for a management pack solution that you add to vRealize Operations
Manager.
How Define Monitoring Goals Works in vRealize Operations Manager

The Manage Solution workspace includes an option to define monitoring goals for the solution.
The selections you make determine the default policy settings that vRealize Operations Manager
uses to analyze and monitor the objects associated with the solution.
VMware, Inc. 426

For example, you might have a production environment that is composed of four separate
production areas, each of which includes specific object groups. To monitor the objects in each
production area, you must set the default policy settings according to the monitoring
requirements for each area. You can have vRealize Operations Manager set the default settings
based on your infrastructure or virtual machines, alert you on individual objects or object groups,
and so on.
Where You Define the Monitoring Goals for a Solution

To define the monitoring goals for a solution and establish the default settings for monitoring
goals in the default policy, in the menu, click Administration, and then in the left pane, click
Solutions > Configuration, and select a solution. Click Configure, and click Define Monitoring
Goals. In the Define Monitoring Goals dialog box that appears, select answers to the questions
about your objects, alerts, memory capacity, and compliance settings according to the vSphere
Hardening Guide.
When you select an option, vRealize Operations Manager saves your setting. If you display the
Define Monitoring Goals dialog box later, and the user interface did not appear to retain your
selection, the selection is still active. As a double-check, select the option again, and click Save.
To adjust advanced settings of the policy, in the menu, click Administration, and then in the left
pane, click Policies.
Table 4-121. Define Monitoring Goals Questions

Option Description
Which objects do you want to Select the type of objects to receive alerts. You can have vRealize Operations Manager
be alerted on in your alert on all infrastructure objects except for virtual machines, only virtual machines, or
environment? all.
Which type of alerts do you You can enable vRealize Operations Manager to trigger Health, Risk, and Efficiency
want to enable? alerts on your objects.
Configure Memory Capacity Set the memory capacity model based on the type of environment to monitor. For
based on? example, to monitor a production environment, select the vSphere Default model to
use moderate settings to ensure performance. Use Most Aggressive for test and
development environments. Use Most Conservative to use all allocated memory for
capacity calculations.
Enable vSphere Hardening Use the vSphere Hardening Guide to continuously and securely assess and operate
Guide Alerts? your vSphere objects. When you enable these alerts, vRealize Operations Manager
assesses your objects against the vSphere Hardening Guide rules.
vSphere 6.0 objects are assessed against vSphere 6.0 hardening rules, and vSphere
5.5 objects are assessed against vSphere 5.5 hardening rules.
Learn More links To display more information about a monitoring goal selection, click Learn More.

guides.html.
VMware, Inc. 427

Configuring Compliance
You can set compliance on your objects to meet the defined standards and determine the
compliance of your objects against the configuration standards.
Defining Compliance Standards

Compliance is used to monitor the vCenter Server instances, hosts, virtual machines, distributed
port groups, and distributed switches in your environment to ensure that the settings on your
objects meet the defined standards.
vRealize Operations Manager includes alerts for VMware vSphere Hardening Guide versions 6.5,
6.0 and 5.5. Hardening guides for regulatory standards are delivered as management packs (PAK
files) that you upload, license, and install.
You can install management packs for the following regulatory standards:
n Health Insurance Portability and Accountability Act (HIPAA)
n Payment Card Industry Data Security Standard (PCI DSS) compliance standards
n CIS Security Standards
n Defense Information Systems Agency (DISA) Security Standards
n The Federal Information Security Management Act (FISMA) Security Standards
n International Organization for Standardization Security Standards
You can also define your own compliance score cards. Use compliance alerts or define your own
alerts to monitor. You can define up to five score cards.
vRealize Operations Manager generates compliance alerts when symptoms trigger on your
vCenter Server instances, hosts, virtual machines, distributed port groups, and distributed
switches. After vRealize Operations Manager collects the compliance data from your objects, you
resolve any rule violations that occurred, and create a report of the compliance results.
To enforce vSphere Security Configuration Guide compliance on virtual machines, vRealize

Operations Manager includes several compliance risk profiles. You apply the risk profiles to
groups of virtual machines based on whether you must ensure a high, medium, or low level of
security in your environment.
n Risk Profile 1 includes all available compliance rules as symptoms, and enforces the highest
level of security for your virtual machines. This profile is enabled by default.
n Risk Profile 2 enforces a medium level of security for your environment, and includes fewer
symptoms than Risk Profile 1. This profile is disabled by default.
n Risk Profile 3 enforces a low level of security, and includes fewer symptoms than Risk Profile
2. This profile is disabled by default.
VMware, Inc. 428

All the compliance standards in vRealize Operations Manager, including any standards that you
define, are based on alert definitions. Alert definition of any type, but of the Compliance sub-type
are counted. Custom score cards can monitor user defined alerts. You can view score cards of
each available hardening guide in the Home > Troubleshoot > vSphere Compliance page and the
Environment > Object > Compliance tab. A score card is a compliance visualization term.
In the Home > Troubleshoot > vSphere Compliance summary page, vRealize Operations
Manager displays score cards for vSphere Security Configuration Guide, HIPAA Hardening Guide,
PCI DSS Hardening Guide, CIS Security Standards, DISA Security Standards, FISMA Security
Standards, ISO Security Standards based on resources. The score cards display the number of
compliant resources, number of non-compliant resources, and the total number of resources
affected by the each hardening guide. In addition, you can see the breakdown of total number of
objects that are compliant and non-compliant.
In the Environment > Object > Compliance tab, vRealize Operations Manager displays score
cards for vSphere Security Configuration Guide, HIPAA Hardening Guide, PCI DSS Hardening
Guide, CIS Security Standards, DISA Security Standards, FISMA Security Standards, ISO Security
Standards based on the number of symptoms. The score cards display the total number of rules
and the number non-compliant rules based on symptoms for each hardening guide.

guides.html.
vRealize Operations Manager Compliance for vSphere Objects

To ensure compliance of your vSphere objects, vRealize Operations Manager includes
compliance alerts for VMware vSphere Security Configuration Guide versions. These Security
Configuration guide alerts are now based on object type. To meet industry standard regulatory
requirements, you can also install management packs.
When you customize a policy to enable the vSphere Security Configuration Guide alerts, you can
enable vSphere alerts for the following object types and versions:
n ESXi host is violating vSphere Security Configuration Guide
n vCenter Server is violating vSphere Security Configuration Guide
n Virtual machine is violating Risk Profile 1 in vSphere Security Configuration Guide
n vSphere Distributed Port Group is violating vSphere Security Configuration Guide
n vSphere Distributed Virtual Switch is violating vSphere Security Configuration Guide
By default, the alert named Virtual machine is violating Risk Profile 1 is the only active
alert among the risk profiles. You can configure this profile later, and choose one of the other risk
profiles.

guides.html.
VMware, Inc. 429

To determine whether an alert triggered against vSphere Security Configuration Guide 6.5, 6.0 or
5.5, you must examine the underlying symptoms. For example, for the alert named ESXi Host is
violating vSphere Security Configuration Guide, the following underlying symptoms for the
alert include:
n ESXi.set-account-lockout - The count failed login attempts before the account is locked out
exceeded maximum (vSphere Security Configuration Guide)
n DCUI service is running (vSphere Security Configuration Guide)
When you customize a policy to enable the HIPAA Hardening Guide alerts, you can enable
vSphere alerts for the following object types:
n ESXi host is violating HIPAA Hardening Guide for vSphere
n vCenter is violating HIPAA Hardening Guide for vSphere
n Virtual Machine is violating HIPAA Hardening Guide for vSphere
n vSphere Distributed Port Group is violating HIPAA Hardening Guide for vSphere
n vSphere Distributed Virtual Switch is violating HIPAA Hardening Guide for vSphere
When you customize a policy to enable the PCI DSS Hardening Guide alerts, you can enable
vSphere alerts for the following object types:
n ESXi host is violating PCI DSS 3.2 Hardening Guide for vSphere
n vCenter is violating PCI DSS 3.2 Hardening Guide for vSphere
n Virtual Machine is violating PCI DSS 3.2 Hardening Guide for vSphere
n vSphere Distributed Port Group is violating PCI DSS 3.2 Hardening Guide for vSphere
n vSphere Distributed Virtual Switch is violating PCI DSS 3.2 Hardening Guide for vSphere
When you customize a policy to enable the DISA Hardening Guide for vSphere alerts, you can
enable vSphere alerts for the following object types:
n vCenter is violating DISA Hardening Guide for vSphere
n vSphere Distributed Port Group is violating DISA Hardening Guide for vSphere
n vSphere Distributed Virtual Switch is violating DISA Hardening Guide for vSphere
n ESXi Host is violating DISA Hardening Guide for vSphere
n Virtual Machine is violating DISA Hardening Guide for vSphere
When you customize a policy to enable the CIS Hardening Guide for vSphere alerts, you can
n Virtual Machine is violating CIS Hardening Guide for vSphere
n ESXi Host is violating CIS Hardening Guide for vSphere
VMware, Inc. 430

When you customize a policy to enable the FISMA Hardening Guide for vSphere alerts, you can
n vSphere Distributed Virtual Switch is violating FISMA Hardening Guide for vSphere
n Virtual Machine is violating FISMA Hardening Guide for vSphere
n vSphere Distributed Port Group is violating FISMA Hardening Guide for vSphere
n ESXi Host is violating FISMA Hardening Guide for vSphere
n vCenter is violating FISMA Hardening Guide for vSphere
When you customize a policy to enable the ISO Hardening Guide for vSphere alerts, you can
n vCenter is violating ISO Hardening Guide for vSphere
n Virtual Machine is violating ISO Hardening Guide for vSphere
n ESXi Host is violating ISO Hardening Guide for vSphere
n vSphere Distributed Port Group is violating ISO Hardening Guide for vSphere
n vSphere Distributed Virtual Switch is violating ISO Hardening Guide for vSphere
Reset Default Content to Ensure Current Compliance Standards for vSphere Objects
Alert definitions and symptom definitions now include the compliance standards for both
vSphere. When you upgrade your current version of vRealize Operations Manager, you must
select the option to overwrite alert definitions and symptom definitions.
When the configured policy is applied to objects, it becomes active. When the configured
symptom definitions become true for your vCenter Server instances, hosts, virtual machines,
distributed port groups, and distributed switches, vRealize Operations Manager generates
compliance related alerts. vRealize Operations Manager displays score cards in the vSphere
Compliance page and Compliance tab in the object page.
If you do not overwrite your alert definitions and symptom definitions with the new content
provided with this release, some compliance rules will include the new alert and symptom
definitions, while other compliance rules will continue to use outdated alert and symptom
definitions.
Configure Security Configuration Guide Compliance

As the virtual infrastructure administrator for your company, you must ensure that your vSphere
objects comply with the compliance rules in the vSphere Security Configuration Guide. You use
the compliance alerts in vRealize Operations Manager to monitor your objects for violations to
your compliance standards. When a compliance alert triggers on your vCenter Server instance,
hosts, virtual machines, distributed port groups, or distributed switches, you investigate the
compliance violation.
VMware, Inc. 431

To enforce and report on the compliance of your vSphere objects, you enable the compliance
rules in the vSphere Security Configuration Guide. Then, you enable the appropriate alerts, and
apply a risk profile to your virtual machines.
The Alert definitions provided with vRealize Operations Manager are based on object types
instead of the specific versions of the Security Configuration guides. To use these alerts, you no
longer must create a custom group and apply the policy to that group.
Prerequisites
Verify that the current version of vRealize Operations Manager is installed and running.
Procedure
1 In vRealize Operations Manager, enable the compliance rules.
a Click Administration, and click Solutions.
b Click the VMware vSphere solution, and click Configure.
c In the Manage Solution dialog box, click Define Monitoring Goals.
d Under Enable vSphere Hardening Guide Alerts, click Yes and click Save.
e When vRealize Operations Manager reports that the default policy is configured to collect
compliance data on your objects, click OK, Save Settings and then click Close.
vRealize Operations Manager modifies the current default policy and enables the alert
definitions. By default, the Virtual Machine is violating Risk Profile 1 in vSphere Security
Configuration Guide alert definition is enabled.
2 Verify or change the compliance alert definitions in the default policy.
a In the menu, click Administration, and then on the left pane click Policies and then click
the Active Policies tab. Note the name of the current default policy.
b In the Policy Library tab, select the current default policy and click Edit Selected Policy.
c To edit the alert definitions for the vSphere Security Configuration Guide, do the
following:
n In the Edit Monitoring Policy workspace on the left, click Alert / Symptom Definitions.
n In the Alert Definitions pane, enter Security Configuration in the Filter search box.
Several alert definitions appear, which you use to enforce compliance on your
objects. Each alert displays the number of symptoms and the object type to which the
alert applies. You can see the alert definitions for risk profiles 1, 2, and 3, which you
use to ensure high, medium, or low security on your virtual machines.
n Select an alert.
n In the State column, click the down arrow, and select Local for either one of the base
security configuration policy, or for any one of the risk profiles. Do not enable more
than one risk profile.
VMware, Inc. 432

d To enable vSphere Security Configuration Guide alerts by specifying the base policy, do
the following:
n In the Edit Monitoring Policy workspace on the left, click Select Base Policy.
n From the Select drop down list, select the vSphere Security Configuration Guide
policy.
n Click Apply.
e To enable compliance alerts on your virtual machines, distributed port groups, and
distributed switches, enable the other alert definitions, and click Save.
3 View the symptom set in the alert definition.
a In the menu, click Alerts and then in the left pane, click Alert Definitions.
b In the filter text box, enter Security Configuration.
c In the lower pane, locate the alert impact, criticality, and symptom set.
d Scroll through the symptom set and examine the symptoms, which can trigger an alert,
for the host.
e Below the symptom set, examine the recommendation to fix the problem if this alert
triggers on your host.
f Click the link to the vSphere Security Configuration Guide.
The Web page opens a link to VMware Security Hardening Guides.
Results
You have ensured that the compliance rules, are enforced on the objects in your vCenter Server
instances, according to the VMware vSphere Security Configuration Guide.
What to do next
Analyze compliance rule violations in the Object summary page in the Compliance tab.
Configure Compliance Management Packs

Solutions for industry standard regulatory compliance requirements are delivered as
management packs. You download PAK files from VMware Solutions Exchange and then upload,
license, and install them in vRealize Operations Manager.
To enforce and report on the compliance of your vSphere objects, you install the PAK file that
contains the policies for the regulatory standard. Then, you enable the appropriate alerts for your
virtual machines. You can install compliance packs for the following regulatory standards:
n Health Insurance Portability and Accountability Act (HIPAA)
n Payment Card Industry Data Security Standard (PCI DSS) compliance standards
n CIS Security Standards
n Defense Information Systems Agency (DISA) Security Standards
VMware, Inc. 433

n The Federal Information Security Management Act (FISMA) Security Standards
n International Organization for Standardization Security Standards
Prerequisites
You must download the PAK files from the VMware Solutions Exchange website. After you log in
to an instance of vRealize Operations Manager, go to the vSphere Compliance page from the
Quick Start page. Click Download below the regulatory standard that you want to configure. You
must provide your login credentials before you can download the PAK files from the VMware
Solutions Exchange website.
VMware, Inc. 434

Procedure
1 In the menu, select Administration and in the left pane select Solutions > Repository. From
the Other Management Packs section in the Repository page, click Add a Management Pack
and select the PAK file you want to install.
a The wizard includes three pages where you locate and upload a PAK file, accept the
EULA and install, and review the installation.
b In the wizard, follow the options on each page to install the PAK file for HIPAA and PCI
DSS.
Table 4-122. Wizard Options

Option Description
Page 1
Browse Navigate to your copy of a management pack PAK file.
Upload To prepare for installation, copy the PAK file to vRealize Operations Manager.
Install the PAK file even if If the PAK file was already uploaded, reload the PAK file using the current file, but
it is already installed leave user customization in place. Do not overwrite or update the solution alerts,
symptoms, recommendations, and policies.
Reset Default Content, If the PAK file was already uploaded, reload the PAK file using the current file, and
overwriting to a newer overwrite the solution default alerts, symptoms, recommendations, and policies with
version provided by this newer versions provided with the current PAK file.
update. User
Note A reset overwrites customized content. If you are upgrading vRealize
modifications to
Operations Manager, the best practice is to clone your customized content before
DEFAULT Alert
you upgrade.
Definitions, Symptoms,
Recommendations,
Policy Definitions, Views,
Dashboards, Widgets,
and Reports are
overwritten. If you are
installing a product
software update, clone
or backup the content
before you proceed.
The PAK file is unsigned Warning appears if the PAK file is not signed with a digital signature that VMware
provides. The digital signature indicates the original developer or publisher and
provides the authenticity of the management pack. If installing a PAK file from an
untrusted source is a concern, check with the management pack distributor before
proceeding with the installation.
Page 2
End User License Read and agree to the end-user license agreement. Click the I accept the terms of
Agreement this agreement check-box.
Note Clicking Next installs the solution.
Page 3
Installation Details Review the installation progress. Click Finish after the installation is complete.
VMware, Inc. 435

2 Enable the compliance alert definitions in the default policy.
a In the menu, click Administration, and then in the left pane click Policies > Policy Library.
b Click the Default Policy, and click Edit Selected Policy.
c To edit the alert definitions, do the following:
n In the Edit Monitoring Policy workspace on the left, click Alert / Symptom Definitions.
n In the Alert Definitions pane, enter hardening in the Filter search box. Several alert
definitions appear, which you use to enforce compliance on your objects. Each alert
displays the number of symptoms and the object type to which the alert applies.
n Select one or more alert definitions.
n From the Actions menu, click Enable under State.
d To enable alerts by specifying the base policy, do the following:
n In the Edit Monitoring Policy workspace on the left, click Select Base Policy.
n From the Select drop-down menu, select the hardening guide policy.
n Click Apply.
e To enable compliance alerts on your virtual machines, distributed port groups, and
3 View the symptom set in the alert definition.
b In the filter text box, enter hardening.
c In the lower pane, locate the alert impact, criticality, and symptom set.
d Scroll through the symptom set and examine the symptoms, which can trigger an alert,
for the host.
e Below the symptom set, examine the recommendation to fix the problem if this alert
f Click the link to the regulatory standard.
What to do next
Analyze compliance rule violations in the Object summary page in the Compliance tab.
Configure Custom Compliance Score Cards

You can create a custom compliance benchmark to ensure that objects comply with compliance
alerts available in vRealize Operations Manager, or custom compliance alert definitions . When a
compliance alert triggers on your vCenter Server instance, hosts, virtual machines, distributed
port groups, or distributed switches, you investigate the compliance violation. You can add up to
five custom compliance score cards.
VMware, Inc. 436

Procedure
1 Click Actions > Create in the Home > Troubleshoot > Compliance page.
The Add Custom Compliance wizard opens.
2 Provide a name and description to your custom compliance score card and click Next.
3 Select the compliance alerts that you want to add to the custom compliance score card.
Optionally, you can use the Defined By filter to narrow down the list of compliance alerts
displayed in the wizard.
4 Click Finish.
Results
vRealize Operations Manager displays the custom compliance score card in the Compliance page
and monitors the objects based on the alerts that you configured. You can view the object break
down and triggered alerts by selecting the custom compliance score card and clicking View
Alerts.
Analyzing Compliance Standards

Analyze compliance standards using the Compliance tab in the object summary page. vRealize
Operations Manager displays symptom-based alerts for the compliance standards that you have
configured.
Viewing the Compliance Alerts

The Compliance tab provides analysis based on the vRealize Operations Manager vSphere,
HIPAA and PCI standards alerts that are configured with the alert subtype of Compliance. You
use the compliance value as an investigative tool when you evaluate the state of objects in your
environment, or when you research the root cause of a problem.
You can use the alert-based compliance that vRealize Operations Manager provides to ensure
compliance of your vCenter Server instances, hosts, virtual machines, distributed port groups,
and distributed switches. If you also use vRealize Configuration Manager in your environment,
you can add the vRealize Configuration Manager adapter to vRealize Operations Manager. The
vRealize Configuration Manager adapter provides vRealize Configuration Manager compliance
information in place of the alert-based compliance.
The compliance alerts, which have the subtype named Compliance, include one or more
symptoms that represent the compliance rules. Compliance alerts that trigger appear on the
Compliance tab as a violations to the standard, and the triggered symptoms appear as violated
rules. The rules are the alert symptoms, and the symptom configuration identifies the incorrect
value or configuration. If a rule symptom triggers for any of the alerts in the standard, the
triggered rule violates the standard and affects the score that appears on the Compliance tab.
The Compliance Score Card

The compliance score card of a resource is counted as smallest rounded off integer (100*(total
number of symptoms enabled on objects/all the triggered symptoms on objects)).
VMware, Inc. 437

To enable alert-based compliance, you must customize a policy. If the compliance alerts are not
enabled, the score card value is 100 and is green, and no violations exist in the list of violated
standards. For example, the VMware vSphere solutions provide the alerts for the ESXi host and
virtual machine sections of the vSphere Hardening Guide.
Where You Find Compliance Summary Based on vRealize Operations Manager Alerts
n In the menu, click Environment, then select a group, custom data center, application or
inventory object. Click the Compliance tab.
n Alternatively, click Environment, then use the hierarchies in the left pane to quickly drill down
to the object you want.
n Go the Quick Start page and open the vSphere Compliance page. Click View Alerts to view
the active compliance alerts.
Table 4-123. Compliance Based on vRealize Operations Manager Alerts Options

Item Description
Score card for the configured Displays the score card value, total number of rules, and number of non-compliance rules
hardening guides for the vSphere Security Configuration Guide, HIPAA Compliance and PCI Security
Standards depending on which of compliance standards you have configured.
Active Compliance Alerts Violated rules are based on the symptoms defined in the compliance alert.
If you click the standard, the rules for the standard appear. If a symptom triggered, the
rule is considered to be violated. View the list of rules in the following tabs:
n Violated Rules. Displays only the triggered symptoms. Click a symptom to view more
information.
n All Rules. Displays triggered and untriggered symptoms.
User Scenario: Ensure Host Objects Comply with Alert-Based Compliance Rules
As a virtual infrastructure administrator, you use vRealize Operations Manager to monitor the
objects in your environment, including vCenter Server instances and ESXi hosts, on which run
your virtual machines. You review the Compliance tab for your hosts and discover that one of
your hosts is violating the VMware vSphere Hardening Guide standard. You must identify and fix
the problems.
vRealize Operations Manager includes alert-based compliance from the VMware vSphere
Hardening Guide.
In this scenario, you resolve a violated rule on your host, and another violated rule on one of your
virtual machines. In your own scenario, you might repeat this procedure for any other violated
rules.
vRealize Operations Manager assesses vSphere 6.0 objects against 6.0 rules, and vSphere 5.5
objects against 5.5 rules.
Prerequisites
n Verify that you can open an XLSX file on the machine that you are using to access vRealize
Operations Manager.
VMware, Inc. 438

n Enable the vSphere Hardening Guide alerts so that the alert-based compliance is active in
your environment. See Configure Security Configuration Guide Compliance.
Procedure
1 In the menu, click Environment.
2 Browse to a host object.
If you had created an object group to manage your hosts, you can select a host in the group.
3 With the host as the focus, click the Compliance tab.
The Compliance score displays a value other than 100.
4 Click the violated rule named ESXi Host is violating vSphere Hardening Guide in the Active
Compliance Alerts area.
See the violated rules, including violations for vSphere 6.0 objects and 5.5 objects.
5 In the Recommendations area, click the link to the vSphere Hardening Guides at: http://
www.vmware.com/security/hardening-guides.html, and click the link to the version you need.
The vSphere Hardening Guide downloads as an Excel spreadsheet to the machine you are
using to access vRealize Operations Manager.
6 You see that vRealize Operations Manager identified that one of the virtual machines is
violating a DCUI rule, so you locate the compliance rule and the remediation method.
n For vSphere 6.0 objects, in the 6.0 version of the vSphere Hardening Guide, locate the
rule named Set DCUI.Access to allow trusted users to override lockdown mode.
n For vSphere 5.5 objects, in the 5.5 version of the vSphere Hardening Guide, click the ESXi
tab and locate the rule named Disable DCUI to prevent local administrative
control.
7 Review information about the rule in the vSphere Hardening Guide, and implement the
remediation method.
Results
You identified and resolved violated compliance rules that triggered on your host and virtual
machine. After you remediate the violated rules, as described in the vSphere Hardening Guide,
wait for vRealize Operations Manager to run several collection cycles. After several collection
cycles, the violated rules no longer appear in the list of violated standards.
User Scenario: Monitor Compliance for Your vSphere Objects

You manage and monitor the security of your production, test, and development environments.
Your objects consist of multiple vCenter Server instances, with hosts, virtual machines, distributed
port groups, and distributed switches in each instance. You must resolve the violation so that the
violated object continues to meet industry security standards. Your CIO requires that you run
SSH on all vCenter Server instances and host machines in your production and test environments.
You monitor all hosts to ensure that they comply with the SSH requirement. You produce a
VMware, Inc. 439

compliance report each week to prove to your manager and the compliance team that your
objects comply with the implemented security standards.
To enforce and report on the compliance of your vSphere objects, you enable the compliance
rules in the vSphere Security Configuration Guide. Then, you enable the appropriate alerts, and
apply a risk profile to your virtual machines. After vRealize Operations Manager collects the
compliance data from your objects, you resolve any rule violations that occurred, and create a
report of the compliance results for your manager and the compliance team.
Prerequisites
Verify that the current version of vRealize Operations Manager is installed and running.
Procedure
1 In vRealize Operations Manager, enable the compliance rules.
a Click Administration, and click Solutions.
b Click the VMware vSphere solution, and click Configure.
c In the Manage Solution dialog box, click Define Monitoring Goals.
d Under Enable vSphere Hardening Guide Alerts, click Yes and click Save.
e When vRealize Operations Manager reports that the default policy is configured to collect
compliance data on your objects, click OK, Save Settings and then click Close.
2 Enable the compliance alert definitions in the default policy.
a In the menu, click Administration, and then on the left pane click Policies and then click
the Policy Library tab.
b Click the Default Policy, and click Edit Selected Policy.
c In the Edit Monitoring Policy workspace on the left, click Alert / Symptom Definitions.
d In the filter text box in the Alert Definitions pane, enter Security Configuration.
Several alert definitions appear, which you use to enforce compliance on your objects.
Each alert displays the number of symptoms and the object type to which the alert
applies. You can see the alert definitions for risk profiles 1, 2, and 3, which you use to
ensure high, medium, or low security on your virtual machines.
e Click the alert named vCenter is violating vSphere Hardening Guide.
f In the State column, click the down arrow, and select Local.
g To enable compliance alerts on your virtual machines, distributed port groups, and
3 View the symptom set in the alert definition for the ESXi host.
VMware, Inc. 440

c Click the alert named vCenter is violating vSphere Hardening Guide.
d In the lower pane, locate the alert impact, criticality, and symptom set.
e Scroll through the symptom set and examine the symptoms, which can trigger an alert,
for the host.
f Below the symptom set, examine the recommendation to fix the problem if this alert
g Click the link to the VMware vSphere Security Configuration Guide.
The Web page opens to the list of VMware vSphere Security Hardening Guides at http://
www.vmware.com/security/hardening-guides.html.
4 Focus in on the alerts for the host in your production vCenter Server instance.
a In the menu, click Alerts and then in the left pane, click All Alerts.
b Click the link in the compliance alert named ESXi Host is violating vSphere Hardening
Guide.
c Examine the symptoms, which display the hosts that violated the rules in the vSphere
Security Configuration Guide.
d For the first host listed, click the host name, and examine the violations on the Summary
tab.
5 Run a report for your compliance team.
a In the menu, click Dashboards, and then in the left pane click Reports.
The report named VMware vSphere Security Configuration Guide - Non-compliance

Report appears.
c On the Report Templates tab, click Run Template, and in the Select an Object dialog box,
navigate to a virtual machine and click OK.
d Wait for vRealize Operations Manager to generate the report. Click Generated Reports.
The report appears, and provides PDF and CSV versions for you to download.
e In the Download column, click the PDF icon and examine the content in the report.
The non-compliance report appears for the host, and includes the date and time that you
ran the report. It also identifies you as the user who ran the report. The report displays
the noncompliant rules that ran on the object and its descendants. In the report, you can
see the criticality and status of the alert, the object name, and the type on which the alert
triggered.
f In the Download column, click the CSV icon, and examine the content of the spreadsheet.
The spreadsheet provides an easy way to see a summary of the results, and allows you
to import the data into another application.
VMware, Inc. 441

Results
You have ensured that the compliance rules, are enforced on the objects in your vCenter Server
instances, according to the VMware vSphere Security Configuration Guide.
What to do next
To examine the compliance alert definitions for your other objects, click Alerts > Alert
Definitions.
Configuring Super Metrics

The super metric is a mathematical formula that contains one or more metrics or properties. It is a
custom metric that you design to help track combinations of metrics or properties, either from a
single object or from multiple objects. If a single metric does not inform you about the behavior
of your environment, you can define a super metric.
After you define it, you assign the super metric to one or more object types. This action
calculates the super metric for the objects in that object type and simplifies the metrics display.
For example, you define a super metric that calculates the average CPU usage on all virtual
machines, and you assign it to a cluster. The average CPU usage on all virtual machines in that
cluster is reported as a super metric for the cluster.
When the super metric attribute is enabled in a policy, you can also collect super metrics from a
group of objects associated with a policy.
Because super metric formulas can be complex, plan your super metric before you build it. The
key to creating a super metric that alerts you to the expected behavior of your objects is
knowing your own enterprise and data. Use this checklist to help identify the most important
aspects of your environment before you begin to configure a super metric.
Table 4-124. Designing a Super Metric Checklist
When you define the metrics to use, you can select either
Determine the objects that are involved in the behavior
specific objects or object types. For example, you can
to track.
select the specific objects VM001 and VM002, or you can
select the object type virtual machine.
If you are tracking the transfer of packets along a network,

Determine the metrics to include in the super metric.
use metrics that refer to packets in and packets out. In
another common use of super metrics, the metrics might
be the average CPU usage or average memory usage of
the object type you select.
For example, to find the ratio of packets in to packets out,

Decide how to combine or compare the metrics.
you must divide the two metrics. If you are tracking CPU
usage for an object type, you might want to determine the
average use. You might also want to determine what the
highest or lowest use is for any object of that type. In more
complex scenarios, you might need a formula that uses
constants or trigonometric functions.
VMware, Inc. 442

Table 4-124. Designing a Super Metric Checklist (continued)
You define the objects to track in the super metric, then

Decide where to assign the super metric.
assign the super metric to the object type that contains the
objects being tracked. To monitor all the objects in a group,
enable the super metric in the policy, and apply the policy
to the object group.
After you create the super metric, you add it to a policy.

Determine the policy to which you add the super
For more information, refer to Policy Workspace in vRealize
metric.
Operations Manager.
What Else Can You Do with Super Metrics

n To see the super metrics in your environment, generate a system audit report. For more
information, refer to System Audit for vRealize Operations Manager.
n To create alert definitions to notify you of the performance of objects in your environment,
define symptoms based on super metrics. For more information, refer to About Metrics and
Super Metrics Symptoms.
n Learn about the use of super metrics in policies. For more information, refer to Policy
Workspace in vRealize Operations Manager.
n Use OPS CLI commands to import, export, configure, and delete super metrics. For more
information, refer to the OPS CLI documentation.
n To display metric-related widgets, create a custom set of metrics. You can configure one or
more files that define different sets of metrics for a particular adapter and object types. This
ensures that the supported widgets are populated based on the configured metrics and
selected object type. For more information, refer to Manage Metric Configuration.
Create a Super Metric

Create a super metric when you want to check the health of your environment, but cannot find a
suitable metric to perform the analysis.
Procedure
1 On the menu, click Administration and in the left pane click Configuration > Super Metrics.
2 Click the Add icon.
The Manage Super Metric wizard opens.
3 Enter a meaningful name for the super metric such as Worst VM CPU Usage (%) in the Name
text box.
Note It is important that you have an intuitive name as it appears in dashboards, alerts, and
reports. For meaningful names, always use space between words so that it is easier to read.
Use title case for consistency with the out of the box metrics and add the unit at the end.
VMware, Inc. 443

4 Provide a brief summary of the super metric in the Description text box and click Next.
Note Information regarding the super metric, like why it was created and by whom can
provide clarity and help you track your super metrics with ease.
The Create a formula screen appears.
5 Create the formula for the super metric.
For example, to add a super metric that captures the average CPU usage across all virtual
machines in a cluster, perform the following steps.
a Select the function or operator. This selection helps combine the metric expression with
operators and/or functions. In the super metric editor, enter avg and select the avg
function.
You can manually enter functions, operators, objects, object types, metrics, metrics types,
property, and properties types in the text box and use the suggestive text to complete
your super metric formula.
Alternatively, select the function or operator from the Functions and Operators drop-
down menus.
b To create a metric expression, enter Virtual and select Virtual Machine from the object
type list.
c Add the metric type, enter usage, and select the CPU|Usage (%) metric from the metric
type list.
Note The expression ends with depth=1 by default. If the expression ends with depth=1,
that means that the metric is assigned to an object that is one level above virtual
machines in the relationship chain. However, since this super metric is for a cluster which
is two levels above virtual machine in the relationship chain, change the depth to 2.
The depth can also be negative, this happens when you need to aggregate the parents of
a child object. For example, when aggregating all the VMs in a datastore, the metric
expression ends with depth=-1, because VM is a parent object of datastore. But, if you
want to aggregate all the VMs at a Datastore Cluster level, you need to implement 2
super metrics. You cannot directly aggregate from VM to Datastore Cluster, because
both are parents of a datastore. For a super metric to be valid, depth cannot be 0
(-1+1=0). Hence, you need to create the first super metric (with depth=-1) for the
aggregate at the datastore level, and then build the second super metric based on the
first (with depth = 1).
The metric expression is created.
VMware, Inc. 444

d To calculate the average CPU usage of powered on virtual machines in a cluster, you can
add the where clause. Enter where=””.
Note The where clause cannot point to another object, but can point to a different metric
in the same object. For example, you cannot count the number of VMs in a cluster with
the CPU contention metric > SLA of that cluster. The phrase "SLA of that cluster " belongs
to the cluster object, and not to the VM object. The right operand must also be a number
and cannot be another super metric or variable. The where clause cannot be combined
using AND, OR, NOT, which means you cannot have where="VM CPU>4 and VM RAM>16" in
your super metric formula.
e Position the pointer between the quotation marks, enter Virtual, and select the Virtual
Machine object type and the System|Powered ON metric type.
f To add the numeric value for the metric, enter ==1.
g To view hints and suggestions, click ctrl+space and select the adapter type, objects,
object types, metrics, metrics types, property, and properties types to build your super
metric formula.
h Click the This object icon.
If the This object icon is selected during the creation of a metric expression, it means that
the metric expression is associated to the object for which the super metric is created.
6 You can also use the Legacy template to create a super metric formula without the
suggestive text.
To view the super metric formula in a human-readable format, click the Show Formula
Description icon. If the formula syntax is wrong, an error message appears.
Note If you are using Internet Explorer, you are automatically directed to the legacy
template.
7 Verify that the super metric formula has been created correctly.
a Expand the Preview section.
b In the Objects text box, enter and select a Cluster.
A metric graph is displayed showing values of the metric collected for the object. Verify
that the graph shows values over time.
c Click the Snapshots icon.
You can save a snapshot, or download the metric chart in a .csv format.
d Click the Monitoring Objects icon.
If enabled, only the objects that are being monitored are used in the formula calculation.
e Click Next.
The Assign to Object Types screen appears.
VMware, Inc. 445

8 Associate the super metric with an object type. vRealize Operations Manager calculates the
super metric for the target objects and displays it as a metric for the object type.
a In the Assign to an Object Type text box, enter Cluster and select the Cluster Compute
Resource object type.
After one collection cycle, the super metric appears on each instance of the specified
object type. For example, if you define a super metric to calculate the average CPU usage
across all virtual machines and assign it to the cluster object type, the super metric
appears as a super metric on each cluster.
b Click Next.
The Enable in a Policy screen appears.
9 Enable the super metric in a policy, wait for at least one collection cycle till the super metric
begins collecting and processing data, and then review your super metric on the All Metrics
tab.
a In the Enable in a Policy section, you can view the policies related to the object types you
assigned your super metric to. Select the policy in which you want to enable the super
metric. For example, select the Default Policy for Cluster.
10 Click Finish.
You can now view the super metric you created and the associated object type and policy on
the Super Metrics page.
Enhancing Your Super Metrics

You can enhance your super metrics by using clauses and resource entry aliasing.
Where Clause
The where clause verifies whether a particular metric value can be used in the super metric. Use
this clause to point to a different metric of the same object, such as
where = "metric_group|my_metric > 0.
For example:
count(${objecttype = ExampleAdapter, adaptertype = ExampleObject, metric =
ExampleGroup|Rating, depth=2, where = "==1"})
Resource Entry Aliasing

Resource entries are used to retrieve metric data from vRealize Operations Manager for
computing super metrics. A resource entry is the part of an expression which begins with $
followed by a {..} block. When computing a super metric, you might have to use the same
resource entry multiple times. If you have to change your computation, you must change every
resource entry, which might lead to errors. You can use resource entry aliasing to rewrite the
expression.
The following example, shows a resource entry that has been used twice.
VMware, Inc. 446

(min(${adaptertype=VMWARE, objecttype=HostSystem, attribute= cpu|demand|

active_longterm_load, depth=5, where=”>=0”}) + 0.0001)/(max(${adaptertype=VMWARE,
objecttype=HostSystem, attribute=cpu|demand|active_longterm_load, depth=5,
where=”>=0”}) + 0.0001)"
The following example shows how to write the expressing using resource entry aliasing. The
output of both expressions is the same.
(min(${adaptertype=VMWARE, objecttype=HostSystem, attribute= cpu|demand|

active_longterm_load, depth=5, where=”>=0”} as cpuload) + 0.0001)/(max(cpuload) +
0.0001)"
Follow these guidelines when you use resource entry aliasing:
n When you create an alias, make sure that after the resource entry you write as and then
alias:name. For example: ${…} as alias_name.
n The alias cannot contain the ()[]+-*/%|&!=<>,.?:$ special characters, and cannot begin with a
digit.
n An alias name, like all names in super metric expressions, is case-insensitive.
n Use of an alias name is optional. You can define the alias, and not use it in an expression.
n Each alias name can be used only once. For example:

${resource1,…} as r1 + ${resource2,…} as R1.
n You can specify multiple aliases for the same resource entry. For example: ${…} as a1 as a2.
Conditional Expression ?: Ternary Operators

You can use a ternary operator in an expression to run conditional expressions.
For example: expression_condition ? expression_if_true : expression_if_false.
The result of the conditional expression is converted to a number. If the value is not 0, then the
condition is assumed as true.
For example: -0.7 ? 10 : 20 equals 10. 2 + 2 / 2 - 3 ? 4 + 5 / 6 : 7 + 8 equals 15 (7 + 8).
Depending on the condition, either expression_if_true or expression_if_false is run, but not

both of them. In this way, you can write expressions such as,
${this, metric=cpu|demandmhz} as a != 0 ? 1/a : -1. A ternary operator can contain other
operators in all its expressions, including other ternary operators.
For example: !1 ? 2 ? 3 : 4 : 5 equals 5.
Exporting and Importing a Super Metric

You can export a super metric from one vRealize Operations Manager instance and import it to
another vRealize Operations Manager instance. For example, after developing a super metric in a
test environment, you can export it from the test environment and import it use in a production
environment.
VMware, Inc. 447

If the super metric to import contains a reference to an object that does not exist in the target
instance, the import fails. vRealize Operations Manager returns a brief error message and writes
detailed information to the log file.
Procedure
1 Export a super metric.
a On the menu, select Administration and in the left pane select Configuration > Super
Metrics.
b Select the super metric to export, click the Actions icon and select Export Selected Super
Metric icon.
vRealize Operations Manager creates a super metric file, for example, SuperMetric.json.
c Download the super metric file to your computer.
2 Import a super metric.
a On the menu, select Administration and in the left pane select Configuration > Super
Metrics.
b Click the Actions icon and select Import Super Metric.
c (Optional). If the target instance has a super metric with the same name as the super
metric you are importing, you can either overwrite the existing super metric or skip the
import, which is the default.
Super Metrics Tab

A super metric is a mathematical formula that contains a combination of one or more metrics for
one or more objects. With super metrics you can assess information more quickly when you are
observing fewer metrics.
Where You Configure Super Metrics

Click Administration and in the left pane click Configuration > Super Metrics.
VMware, Inc. 448

Table 4-125. Configuration Options for Super Metrics

Option Description
Toolbar Use the toolbar selections to manage super metric options.

n Add New Super Metric. Starts the Manage Super Metric
workspace. See Manage Super Metric Workspace.
n Edit Selected Super Metric. Starts the Manage Super
Metric workspace.
n Clone Selected Super Metric. Duplicates the super
metric. Edit the clone or associate it with a different
object type.
n Delete Selected Super Metric.
n Export Selected Super Metric. Exports a super metric to
use in another vRealize Operations Manager instance.
See Exporting and Importing a Super Metric.
n Import Super Metric. Imports a super metric to this
vRealize Operations Manager instance. See Exporting
and Importing a Super Metric.
Super Metrics list Configured super metrics listed by name and formula
description.
Policies Tab Policies in which the super metric attribute is enabled for
collection. When enabled in a policy, vRealize Operations
Manager collects super metrics from the objects associated
with the policy. See Collect Metrics and Properties Details.
Object Types Tab Object types for the super metric display. vRealize
Operations Manager calculates the super metric for the
objects associated with the object type and displays the
value with the object type. Use the toolbar selections to
add or delete an object type association.
Manage Super Metric Workspace

You use the Manage Super Metric workspace to create or edit a super metric. The toolbar helps
you to build the mathematical formula with the objects and metrics you select.
Where You Configure Super Metrics

On the menu, click Administration and in the left pane click Configuration > Super Metrics.
VMware, Inc. 449

Table 4-126. Super Metrics Workspace Options

Option Description
Super Metric Use the toolbar selections to build and display your super
metric formula.
n Functions. Mathematical functions that operate on a
single object or group of objects. See Super Metric
Functions and Operators.
n Operators. Mathematical symbols to enclose or insert
between functions. See Enhancing Your Super Metrics.
n This Object. Assigns the super metric to the object
selected in the Object pane and displays this in the
formula instead of a long description for the object.
n Show Formula Description. Shows the formula in a
textual format.
n Visualize Super Metric. Shows the super metric in a
graph. Look at the graph so that you can verify that
vRealize Operations Manager is calculating the super
metric for the target objects that you selected.
n Name. The name you give to the super metric.
Objects Pane Displays the list of objects collecting metrics. Use this list to
select the object with the metrics to measure. If an object
type is selected, only objects of the selected type are
listed. Column headings help you to identify the object.
Object Types Pane Use this list to select the object type with the metrics to
measure. The object type selection affects the list of
objects, metrics, and attribute types displayed.
n Adapter Type. Shows the object types for the adapter
selected.
n Filter. Shows the object types with the filter words.
Metrics Pane Displays the list of available metrics for the object or object
type selection. Use this list to select the metrics to add to
the formula.
Attribute Types Pane Displays the list of attribute types for the object or object
type selection. Use this list to select the metrics for the
attribute type to add to the formula.
Super Metric Functions and Operators

vRealize Operations Manager includes functions and operators that you can use in super metric
formulas. The functions are either looping functions or single functions.
Looping Functions
Looping functions work on more than one value.
VMware, Inc. 450

Table 4-127. Looping Functions

Function Description
avg Average of the collected values.
combine Combines all the values of the metrics of the included

objects in a single metric timeline.
count Number of values collected.
max Maximum value of the collected values.
min Minimum value of the collected values.
sum Total of the collected values.
Note vRealize Operations Manager 5.x included two sum functions: sum (expr) and sumN
(expr, depth). vRealize Operations Manager 6.x includes one sum function: sum (expr). Depth
is set at depth=1 by default. For more information about setting depth, refer to Create a Super
Metric.
Looping Function Arguments

The looping function returns an attribute or metric value for an object or object type. An attribute
is metadata that describes the metric for the adapter to collect from the object. A metric is an
instance of an attribute. The argument syntax defines the desired result.
For example, CPU usage is an attribute of a virtual machine object. If a virtual machine has
multiple CPUs, the CPU usage for each CPU is a metric instance. If a virtual machine has one CPU,
then the function for the attribute or the metric return the same result.
Table 4-128. Looping Function Formats

Argument syntax example Description
funct(${this, metric =a|b:optional_instance|c}) Returns a single data point of a particular metric for the object to
which the super metric is assigned. This super metric does not take
values from the children or parents of the object.
funct(${this, attribute=a|b:optional_instance|c}) Returns a set of data points for attributes of the object to which the
super metric is assigned. This super metric does not take values
from the child or parent of the object.
funct(${adaptertype=adaptkind, Returns a single data point of a particular metric for the resname
objecttype=reskind, resourcename=resname, specified in the argument. This super metric does not take values
identifiers={id1=val1id2=val2,…}, metric=a| from the children or parents of the object.
b:instance|c})
funct(${adaptertype=adaptkind, Returns a set of data points. This function iterates attributes of the
objecttype=reskind, resourcename=resname, resname specified in the argument. This super metric does not take
identifiers={id1=val1, id2=val2,…}, attribute=a| values from the child or parent of the object.
b:optional_instance|c})
VMware, Inc. 451

Table 4-128. Looping Function Formats (continued)

Argument syntax example Description
funct(${adaptertype=adaptkind, Returns a set of data points. This function iterates metrics of the
objecttype=reskind, depth=dep}, metric=a| reskind specified in the argument. This super metric takes values
b:optional_instance|c}) from the child (depth > 0) or parent (depth < 0) objects, where
depth describes the object location in the relationship chain.
For example, a typical relationship chain includes a data center,
cluster, host, and virtual machines. The data center is at the top
and the virtual machines at the bottom. If the super metric is
assigned to the cluster and the function definition includes depth =
2, the super metric takes values from the virtual machines. If the
function definition includes depth = -1, the super metric takes
values from the data center.
funct(${adaptertype=adaptkind, Returns a set of data points. This function iterates attributes of the
objecttype=reskind, depth=dep}, attribute=a| reskind specified in the argument. This super metric takes values
b:optional_instance|c}) from the child (depth > 0) or parent (depth < 0) objects.
For example, avg(${adaptertype=VMWARE, objecttype=VirtualMachine, attribute=cpu|

usage_average, depth=1}) averages the value of all metric instances with the cpu|
usage_average attribute for all objects of type VirtualMachine that the vCenter adapter finds.
vRealize Operations Manager searches for objects one level below the object type where you
assign the super metric.
Single Functions
Single functions work on only a single value or a single pair of values.
Table 4-129. Single Functions

Function Format Description
abs abs(x) Absolute value of x. x can be any floating point number.
acos acos(x) Arccosine of x.
asin asin(x) Arcsine of x.
atan atan(x) Arctangent of x.
ceil ceil(x) The smallest integer that is greater than or equal to x.
cos cos(x) Cosine of x.
cosh cosh(x) Hyperbolic cosine of x.
exp exp(x) e raised to the power of x.
floor floor(x) The largest integer that is less than or equal to x.
log log(x) Natural logarithm (base x) of x.
log10 log10(x) Common logarithm (base 10) of x.
pow pow(x,y) Raises x to the y power.
rand rand() Generates a pseudo random floating number greater than or equal to 0.0 and
less than 1.0.
sin sin(x) Sine of x.
VMware, Inc. 452

Table 4-129. Single Functions (continued)

Function Format Description
sinh sinh(x) Hyperbolic sine of x.
sqrt sqrt(x) Square root of x.
tan tan(x) Tangent of x.
tanh tanh(x) Hyperbolic tangent of x.
Operators
Operators are mathematical symbols and text to enclose or insert between functions.
Table 4-130. Numeric Operators

Operators Description
+ Plus
- Subtract
* Multiply
/ Divide
% Modulo
== Equal
!= Not equal
< Less than
<= Less than, or equal
> Greater than
>= Greater than, or equal
|| Or
&& And
! Not
?: Ternary operator. If/then/else

For example:
conditional_expression ?
expression_if_condition_is_true :
expression_if_condition_is_false
For more information about ternary operators, see
Enhancing Your Super Metrics.
() Parentheses
[] Use in an array of expressions
[x, y, z] An array containing x, y, z. For example, min([x, y, z])
VMware, Inc. 453

Table 4-131. String Operators

String Operators Description
equals Returns true if metric/property string value is equal to

specified string.
contains Returns true if metric/property string value contains

specified string.
startsWith Returns true if metric/property string value starts with the

specified prefix.
endsWith Returns true if metric/property string value ends with the

specified suffix.
!equals Returns true if metric/property string value is not equal to

specified string.
!contains Returns true if metric/property string value does not

contain specified string.
!startsWith Returns true if metric/property string value does not start

with the specified prefix.
!endsWith Returns true if metric/property string value does not end

with the specified suffix.
Note String operators are valid in 'where' condition only. For example:
${this, metric=summary|runtime|isIdle, where = "System Properties|
resource_kind_type !contains GENERAL"}
Configuring Objects
Using the power of object management - including metrics and alerts - you can monitor objects,
applications, and systems that must stay up and running. Some metrics and alerts are
prepackaged into dashboards and policies; others you combine into custom tools
vRealize Operations Manager discovers objects in your environment and makes them available to
you. With the information that vRealize Operations Manager provides, you can quickly access
and configure any object. For example, you can determine if a datastore is connected or
providing data, or you can power on a virtual machine.
Object Discovery
Its ability to monitor and collect data on objects in your systems environment makes vRealize
Operations Manager a critical tool in maintaining system uptime and ensuring ongoing good
health for all system resources from virtual machines to applications to storage - across physical,
virtual and cloud infrastructures.
Following are examples of objects that can be monitored.
n vCenter Server
n Virtual machines
VMware, Inc. 454

n Servers/hosts
n Compute resources
n Resource pools
n Data centers
n Storage components
n Switches
n Port groups
n Datastores
Adapters – Key to Object Discovery

vRealize Operations Manager collects data and metrics from objects using adapters, the central
components of management packs, which in turn make up vRealize Operations Manager
solutions. When you configure the vSphere Solution, for example, you create adapter instances
customized for your environment with unique names, port numbers, and so on. You must create
an adapter instance for each vCenter Server in your deployment.
Locate existing adapters in the UI as follows: in the menu, click Administration, then click
Solutions in the left pane.
As shown in the screenshot, the Solutions screen lists available solutions at the top of the screen.
When you select a solution, the available adapters appear in the lower half of the screen. Existing
adapter instances related to each adapter are listed in the second column.
For complete information on configuring management packs and adapters, see Connecting
vRealize Operations Manager to Data Sources
When you create a new adapter instance, it begins discovering and collecting data from the
objects designated by the adapter, and notes the relationships between them. Now you can
begin to manage your objects.
About Objects
Objects are the structural components of your mission-critical IT applications: virtual machines,
datastores, virtual switches and port groups are examples of objects.
VMware, Inc. 455

Because downtime equals cost - in unused resources and lost business opportunities - it's crucial
that you successfully identify, monitor and track objects in your environment. The goal is to
proactively isolate, troubleshoot and correct problems even before users are aware that
anything is wrong.
When a user actually reports an issue, the solution should be quick and comprehensive.
For a complete list of objects that can be defined in vRealize Operations Manager refer to Object
Discovery.
vRealize Operations Manager gives you visibility into objects including applications, storage and
networks across physical, virtual and cloud infrastructures through a single interface that relates
performance information to positive or negative events in the environment.
Managing Objects
When you monitor a large infrastructure, the number of objects and corresponding metrics in
vRealize Operations Manager grows rapidly, especially as you add solutions that extend dynamic
monitoring and alerts to more parts of your infrastructure. vRealize Operations Manager gives
you ample tools to stay abreast of events and issues.
Adding Objects and Configuring Object Relationships

vRealize Operations Manager automatically discovers objects and their relationships once you
create an adapter instance. You have the added ability to manually add any objects that you
want monitored and to configure object relationships using abstract concepts rather than the
connections recorded by vRealize Operations Manager. Where vRealize Operations Manager
might discover the classic parent-child relationships between objects, you can create
relationships between objects that might not normally be related. For example, you could
configure all the datastores supporting a company department to be related.
When objects are related, a problem with one object appears as an anomaly on related objects.
So object relationships can help you to identify problems in your environment quickly. The object
relationships that you create are called custom groups.
Custom Groups
To create an automated management system you need some way to organize objects so that
you can quickly gain insights. You can achieve a high level of automation using custom groups.
You have multiple options for tailoring group attributes to support your monitoring strategy.
For example, you can designate a group either to be static or to be updated automatically with
membership criteria that you designate. Consider a non-static group of all virtual machines that
are powered on and have OS type Linux. When you power on a new Linux VM, it is automatically
added to the group and the policy is applied.
For additional flexibility, you can also specify individual objects to be always included or excluded
from a given custom group. Or you can have a different set of alerts and capacity calculations for
your production environment versus your testing environments.
VMware, Inc. 456

Managing Applications
vRealize Operations Manager allows you to create containers or objects that can contain a group
of virtual machines or other objects in different structural tiers. This new application can then be
managed as a single object, and have health badges and alarms aggregated from the child
objects of the group.
For example, the system administrator of an online training system might request that you
monitor components in the Web, application and database tiers of the training environment. You
build an application that groups related training objects together in each tier. If a problem occurs
with one of the objects, it is highlighted in the application display and you can investigate the
source of the problem
The Power of Object Management

Using the power of object management, including metrics and alerts - some prepackaged into
dashboards and policies, others that you combine into custom monitoring tools - you'll keep a
close watch on the objects, applications and systems that must stay up and running.
Managing Objects in Your Environment

An object is the individual managed item in your environment for which vRealize Operations
Manager collects data, such as a router, switch, database, virtual machine, host, and vCenter
Server instances.
The system requires specific information about each object. When you configure an adapter
instance, vRealize Operations Manager performs object discovery to start collecting data from
the objects with which the adapter communicates.
An object can be a single entity, such as a database, or a container that holds other objects. For
example, if you have multiple Web servers, you can define a single object for each Web server
and define a separate container object to hold all of the Web server objects. Groups and
applications are types of containers.
Categorize your objects using tags, so that you can easily find, group, or filter them later. A tag
type can have multiple tag values. You or vRealize Operations Manager assigns objects to tag
values. When you select a tag value, vRealize Operations Manager displays the objects
associated with that tag. For example, if a tag type is Lifecycle and tag values are Development,
Test, Pre-production, and Production, you might assign virtual machine objects VM1, VM2, or
VM3 in your environment to one or more of these tag values, depending on the virtual machine
function.
Adding an Object to Your Environment

You might want to add an object by providing its information to vRealize Operations Manager.
For example, some solutions cannot discover all the objects that might be monitored. For these
solutions, you must either use manual discovery or manually add the object.
When you add an individual object, you provide specific information about it, including the kind
of adapter to use to make the connection and the connection method. For example, a vSAN
adapter does not know the location of the vSAN devices that you want to monitor.
VMware, Inc. 457

Prerequisites
Verify that an adapter is present for the object you plan to add. See Installing Optional Solutions
in vRealize Operations Manager
Procedure
1 In the menu, click Administration, then select Configuration > Inventory from the left pane.
2 On the toolbar, click the plus sign.
3 Use the topic menus to reveal all fields and provide the required information.
Option Description
Display name Enter a name for the object. For example, enter vSAN-Host1.
Description Enter any description. For example, enter

vSAN-Host monitored with vSAN adapter
Adapter type Select an adapter type. For example, select vSAN Adapter.
Adapter instance Select an adapter instance.
Object type Select an object type. For a vSAN adapter, you might select vSAN-Host.
When you select the object type, the dialog box selections change to
include information you provide so that vRealize Operations Manager can
find and connect with the selected object type.
Host IP address Enter the host IP. For example, enter the IP address of vSAN-Host1.
Port number Accept the default port number or enter a new value.
Credential Select the Credential, or click the plus sign to add new login credentials for
the object.
Collection interval Enter the collection interval, in minutes. For example, if you expect the host
to generate performance data every 5 minutes, set the collection interval to
5 minutes.
Dynamic Thresholding. Accept the default, Yes.
4 Click OK to add the object.
Results
vSAN-Host1 appears in the Inventory as a host object type for the vSAN adapter type.
What to do next
When you add an individual object, vRealize Operations Manager does not begin collecting
metrics for the object until you turn on data collection. See Inventory : List of Objects.
For each new object, vRealize Operations Manager assigns tag values for its collector and its
object type. Sometimes, you might want to assign other tags. See Creating and Assigning Tags.
Configuring Object Relationships

vRealize Operations Manager shows the relationship between objects in your environment. Most
relationships are automatically formed when the objects are discovered by an installed adapter.
VMware, Inc. 458

In addition, you can use vRealize Operations Manager to create relationships between objects
that might not normally be related.
Objects are related physically, logically, or structurally.
n Physical relationships represent how objects connect in the physical world. For example,
virtual machines running on a host are physically related.
n Logical relationships represent business silos. For example, all the storage objects in an
environment are related to one another.
n Structural relationships represent a business value. For example, all the virtual machines that
support a database are structurally related.
Solutions use adapters to monitor the objects in your environment so that physical relationship
changes are reflected in vRealize Operations Manager. To maintain logical or structural
relationships, you can use vRealize Operations Manager to define the object relationships. When
objects are related, a problem with one object appears as an influence on related objects. So
object relationships can help you to identify problems in your environment quickly.
Apart from the parent-child relationship, you can also define new relationships in vRealize
Operations Manager. The relationship between objects in your environment can be one-to-many,
many-to-one, or one-one, the relationship can be defined in horizontal , vertical, or diagonal
levels.
Adding an Object Relationship
Parent-child relationships normally occur between interrelated objects in your environment. For
example, a data center object for a vCenter Adapter instance might have datastore, cluster, and
host system child objects.
The most common object relationships gather similar objects into groups. When you define a
custom group with parent objects, a summary of that group shows alerts for that object and for
any of its descendants. You can create relationships between objects that might not normally be
related. For example, you might define a child object for an object in the group. You define these
types of relationships by configuring object relationships.
Procedure
1 At the Home page, select Administration. Then select Configuration > Object Relationships
in the left pane.
2 In the Parent Selection column, expand the object tag and select a tag value that contains the
object to act as the parent object.
The objects for the tag value appear in the top pane of the second column.
3 Select a parent object.
Current child objects appear in the bottom pane of the second column.
4 In the column to the right of the List column, expand the object tag and select a tag value
that contains the child object to relate to the parent.
VMware, Inc. 459

5 (Optional) If the list of objects is long, filter the list to find the child object or objects.
Option Action
Navigate the object tag list for an Expand the object tag in the pane to the right of the List column and select a
object tag value that contains the object. The objects for the tag value appear in
the List column. If you select more than one value for the same tag, the list
contains objects that have either value. If you select values for two or more
different tags, the list includes only objects that have all of the selected
values.
Search for an object by name If you know all or part of the object name, enter it in the Search text box and
press Enter.
6 To make an object a child object of the parent object, select the object from the list and drag
it to the parent object in the top pane of the second column, or click the Add All Objects To
Parent icon to make all of the listed objects children of the parent object.
You can use Ctrl+click to select multiple objects or Shift+click to select a range of objects.
Example: Custom Group with Child Objects

If you want vRealize Operations Manager to monitor objects in your environment to ensure that
service level capacity requirements for your IT department are met, you add the objects to a
custom group, apply a group policy, and define criteria that affect the membership of objects in
the group. If you want to monitor the capacity of an object that does not affect the service level
requirements, you can add the object as a child of a parent object in the group. If a capacity
problem exists for the child object, the summary of the group shows an alert for the parent
object.
Object Relationships Workspace
Objects in an enterprise environment are related to other objects in that environment. Objects
are either part of a larger object, or they contain smaller component objects, or both.
How Object Relationships Works
When you select a parent object, vRealize Operations Manager shows any related child objects.
You can delete a child object or add more child objects from the list of objects in your
environment.
Where You Find Object Relationships
At the Home page, select Administration. Then select Configuration > Object Relationships in
the left pane.
Object Relationships Workspace Options
n Two columns in the center pane display the existing parent-child relationships. You use the
object tag options above the left column to select a parent object.
n Two columns in the right pane list objects in your environment. You use the object tag
options above the right column to select the object to add as a child.
VMware, Inc. 460

Table 4-132. Object Tag Options

Option Description
Collapse all. Closes all the tag group selections.
Deselect All. Tags remain selected until deselected. Use this option to
deselect all tags.
When a parent object has children, the parent selection shows the child objects and the child
object options are active.
Table 4-133. Child Object Options

Option Description
Clear Selections. Clear all child object selections.
Select All. Select all child objects. To remove most child objects from
the relationship, use this option then click the child objects
you do not want to delete.
Remove Selected Children from Relationship. Removes the selected children from the relationship.
Remove All Children from Relationship. Select all children listed on the page and remove them from
the relationship.
Per Page. Number of children to list per page.
Search. Filter options limit the list to objects matching the filter.
Filter options include ID, Name, Description, Maintenance
Schedule, Adapter Type, Object Type, and Identifiers.
Use the list options to manage the objects to add as children.
Table 4-134. List Options

Option Description
Clear Selections. Clear all object selections.
Select All. Select all objects displayed.
Add All Objects to Parent. Select all children listed on the page and add them to the
parent.
Per page. Number of objects to list per page.
Search. Filter options limit the list to objects matching the filter.
Filter options include ID, Name, Description, Maintenance
Schedule, Adapter Type, Object Type, and Identifiers.
Creating and Assigning Tags

A large enterprise can have thousands of objects defined in vRealize Operations Manager.
Creating object tags and tag values makes it easier to find objects and metrics. With object tags,
you select the tag value assigned to an object and view the list of objects that are associated
with that tag value.
VMware, Inc. 461

A tag is a type of information, for example, Adapter Types. Adapter Types is a predefined tag.
Tag values are individual instances of that type of information. For example, when the system
discovers objects using the vCenter Adapter, it assigns all the objects to the vCenter Adapter tag
value under the Adapter Types tag.
You can assign any number of objects to each tag value, and you can assign a single object to
tag values under any number of tags. You typically look for an object by looking under its
adapter type, its object type, and possibly other tags.
If an object tag is locked, you cannot add objects to it. vRealize Operations Manager maintains
locked object tags.
n Predefined Object Tags

vRealize Operations Manager includes several predefined object tags. It creates values for
most of these tags and assigns objects to the values.
n Add an Object Tag and Assign Objects to the Tag

An object tag is a type of information, and a tag value is an individual instance of that type
of information. If the predefined object tags do not meet your needs, you can create your
own object tags to categorize and manage objects in your environment. For example, you
can add a tag for cloud objects and add tag values for different cloud names. Then you can
assign objects to the cloud name.
n Use a Tag to Find an Object

The quickest way to find an object in vRealize Operations Manager is to use tags. Using tags
is more efficient than searching through the entire object list.
Predefined Object Tags

vRealize Operations Manager includes several predefined object tags. It creates values for most
of these tags and assigns objects to the values.
For example, when you add an object, the system assigns it to the tag value for the collector it
uses and the kind of object that it is. vRealize Operations Manager creates tag values if they do
not already exist.
If a predefined tag has no values, there is no object of that tag type. For example, if no
applications are defined, the applications tag has no tag values.
Each tag value appears with the number of objects that have that tag. Tag values that have no
objects appear with the value zero. You cannot delete the predefined tags or tag values.
VMware, Inc. 462

Table 4-135. Predefined Tags

Tag Description
Collectors (Full Set) Each defined collector is a tag value. Each object is
assigned to the tag value for the collector that it uses when
you add the object to vRealize Operations Manager. The
default collector is vRealize Operations Manager Collector-
vRealize.
Applications (Full Set) Each defined application is a tag value. When you add a
tier to an application, or an object to a tier in an application,
the tier is assigned to that tag value.
Maintenance Schedules (Full Set) Each defined maintenance schedule is a tag value, and
objects are assigned to the value when you give them a
schedule by adding or editing them.
Adapter Types Each adapter type is a tag value, and each object that uses
that adapter type is given the tag value.
Adapter Instances Each adapter instance is a tag value, and each object is
assigned the tag value for the adapter instance or
instances through which its metrics are collected.
Object Types Each type of object is a tag value, and each object is
assigned to the tag value for its type when you add the
object.
Recently Added Objects The last day, seven days, 10 days, and 30 days have tag
values. Objects have this tag value as long as the tag value
applies to them.
Object Statuses Tag value assigned to objects that are not receiving data.
Collection States Tag value assigned to indicate the object collection state,
such as collecting or not collecting.
Health Ranges Good (green), Warning (yellow), Immediate (orange),

Critical (red), and Unknown (blue) health statuses have tag
values. Each object is assigned the value for its current
health status.
Entire Enterprise The only tag value is Entire Enterprise Applications. This
tag value is assigned to each application.
Licensing Tag values are License Groups found under Home >
Administration > Mangement > Licensing. Objects are
assigned to the license groups during vRealize Operations
Manager installation.
Untag Drag an object to this tag to delete the tag assignment.
Add an Object Tag and Assign Objects to the Tag

An object tag is a type of information, and a tag value is an individual instance of that type of
information. If the predefined object tags do not meet your needs, you can create your own
object tags to categorize and manage objects in your environment. For example, you can add a
tag for cloud objects and add tag values for different cloud names. Then you can assign objects
to the cloud name.
VMware, Inc. 463

Prerequisites
Become familiar with the predefined object tags.
Procedure
1 Click Administration in the menu, then click Configuration > Inventory in the left pane.
2 Click the Manage Tags icon above the list of tags.
3 Click the Add New Tag icon to add a new row and type the name of the tag in the row.
For example, type Cloud Objects and click Update.
4 With the new tag selected, click the Add New Tag Value icon to add a new row and type the
name of the value in the row.
For example, type Video Cloud and click Update.
5 Click OK to add the tag.
6 Click the tag to which you want to add objects to display the list of object tag values.
For example, click Cloud Objects to display the Video Cloud object tag value.
7 Drag objects from the list in the right pane of the Inventory onto the tag value name.
You can press Ctrl+click to select multiple individual objects or Shift+click to select a range of
objects.
For example, if you want to assign datacenters that are connected through the vCenter
Adapter, type vCenter in the search filter and select the datacenter objects to add.
Use a Tag to Find an Object
The quickest way to find an object in vRealize Operations Manager is to use tags. Using tags is
more efficient than searching through the entire object list.
Tag values that can also be tags are Applications and Object Types. For example, the Object
Types tag has values for each object that is in vRealize Operations Manager, such as Virtual
Machine, which includes all the virtual machine objects in your environment. Each of these virtual
machines is also a tag value for the Virtual Machine tag. You can expand the tag value list to
select the value for which you want to see objects.
Procedure
1 In the menu, click Administration, then click Configuration > Inventory in the left pane.
2 In the tag list in the center pane, click a tag for an object with an assigned value.
When you click a tag, the list of values expands under the tag. The number of objects that is
associated with each value appears next to the tag value.
A plus sign next to a tag value indicates that the value is also a tag and that it contains other
tag values. You can click the plus sign to see the subvalues.
VMware, Inc. 464

3 Select the tag value.
The objects that have that tag value appear in the pane on the right. If you select multiple tag
values, the objects in the list depend on the values that you select.
Tag Value Selection Objects Displayed
More than one value for the The list includes objects that have either value. For example, if you select two values
same tag of the Object Types tag, such as Datacenter and Host System, the list shows objects
that have either value.
Values for two or more The list includes only objects that have all of the selected values. For example, if you
different tags select two values of the Object Types tag, such as Datacenter and Host System, and
you also select an adapter instance such as vC-1 of the vCenter Adapter instance tag,
only Datacenter or Host System objects associated with vC-1 appear in the list.
Datacenter or Host System objects associated with other adapter instances do not
appear in the list, nor do objects that are not Datacenter or Host System objects.
4 Select the object from the list.
Manage Object Tags Workspace

A large enterprise can have thousands of objects. When objects are assigned to a tag, and you
choose to display objects with that tag value, the objects are easier to find on the Inventory list.
Where You Find Manage Object Tags
In the menu, click Administration, then click Configuration > Inventory in the left pane.
Click the Manage Tags icon above the list of tags in the middle pane.
Manage Object Tags Options
The Manage Object Tags screen appears with previously created tags listed. In the left pane, you
add tags. In the right pane, you add tag values.
n Click Add a New Tag and type a new tag name, or select a tag to delete.
n For the selected tag, click Add a New Tag Value and type a new tag value name, or select a
tag value to delete.
n For the GEO Location tag, tag values are identified with a location on a world map. Select the
tag value and click Manage Location to display the Manage Location map and pick a
geographical location. Objects assigned to that tag value appear in that geographical location
on the Inventory : Geographical Map of Objects.
Manage Object Type Tags Workspace

Every object in your environment is of a particular object type. You use Manage Object Type
Tags to control the object type tags displayed.
How Manage Object Type Tags Works
For every adapter instance installed, vRealize Operations Manager discovers objects in your
environment and starts collecting data from those objects.
VMware, Inc. 465

Where You Find Manage Object Type Tags

In the menu, click Administration, then click Configuration > Inventory in the left pane. Click the
Manage Object Type Tags icon above the list of tags.
Manage Object Type Tags Options
Depending on the number of adapters installed , there may be hundreds of object type tags. The
Manage Object Type Tags options allow you to turn on or off the tags listed.
n Type a filter word to show the object type tags with the word.
n Name lists all the object type tags.
n To toggle the display of an object type tag, select the check box in the Show Tag column of
its row.
Inventory : List of Objects

vRealize Operations Manager discovers objects in your environment for each adapter instance
and lists them. From the complete list of all the objects in your environment, you can quickly
access and configure any object. For example, you can check if a datastore is connected or
providing data, or you can power on a virtual machine.
How the List Works
Objects appear in a data grid. To find a particular object, you can sort a column in the grid or
search for a filter word. In addition to sorting and searching, assigning objects to object tags
makes it easier to find objects and metrics.
Where You Find the List
In the menu, click Administration, then click Inventory . The system lists all the objects in your
environment.
Inventory List Options
The center pane includes object tag options. The right pane includes toolbar options for all of the
Table 4-136. Object Tag Options

Option Description
Collapse all Closes all the tag group selections.
Deselect All Tags remain selected until deselected. Use this option to
deselect all tags.
Manage Tags Add a tag or tag value. See Manage Object Tags
Workspace.
Manage Object Type Tags There might be many object type tags. Use this option to
choose the object type tags to display. See Manage Object
Type Tags Workspace.
VMware, Inc. 466

Use the toolbar options to manage objects.
n Filter options limit the list to objects matching the filter. Filter options include ID, Name,
Description, Maintenance Schedule, Adapter Type, Object Type, and Identifiers.
n Select the object to manage from the list. If an object tag is selected, only objects of the
selected tag value are listed. Column headings help you to identify the object. See Object List
Widget.
Table 4-137. Inventory Toolbar Options

Option Description
Action Perform an action on the selected object. Available actions

depend on the object type. For example, Power on VM
applies to the selected virtual machine. See List of vRealize
Operations Manager Actions
Open in external application If an adapter includes the ability to link to another

application for information about the object, click the
button to access a link to the application. For example,
Open Virtual Machine in a vSphere Client or Search for VM
logs in vRealize Log Insight.
Start Collecting Turn on data collection for the selected object.
Stop Collecting Do not collect data for the selected object. When data
collection stops, vRealize Operations Manager retains
metric data for the object in case data collection starts at a
later time.
Perform Multi-Collecting If an object collects metrics through more than one adapter
instance, select the adapter instance or instances for data
collection. Does not apply to objects that do not use the
adapter instance.
Edit object Edit the selected object. For example, add or change the
maintenance schedule for a virtual machine. If multiple
objects of the same type are selected, common identifiers
for the object type are editable. For example, change the
VM entity name of multiple datastores with a single edit.
See Manage Objects Workspace.
Add object vRealize Operations Manager discovers objects for most

adapters. For adapters that do not support autodiscovery
for all objects, the objects are manually added. See Manage
Objects Workspace.
Discover Objects Perform an IP scan to discover objects associated with a

particular adapter. See Discover Objects Workspace.
Delete object Remove the object from the list.
Start maintenance Take the object offline for maintenance. See Manage
Maintenance Schedules for Your Object Workspace.
End maintenance Terminate the maintenance period and put the selected
object back online.
Clear Selections Clear all object selections.
VMware, Inc. 467

Table 4-137. Inventory Toolbar Options (continued)

Option Description
Select All Select all objects displayed.
Show Detail Display the Summary tab of the selected object. See
Summary Tab.
Per page The number of objects to list per page.
Manage Objects Workspace

To collect data from an object, you might need to add an object or edit an existing object in your
environment. For example, you might need to add objects for an adapter that does not support
autodiscovery, or change the maintenance schedule of an existing object.
Where You Find Manage Objects
In the menu, click Administration, then click Configuration > Inventory in the left pane. Click the
plus sign to add an object or the edit icon to edit the selected object.
Items that appear in the window depend on the object that you are editing. Not all options can
be changed.
Table 4-138. Manage Objects Add or Edit Options

Options Description
Display name Name of the object. Use only letters and numbers. Do not
use nonalphanumeric characters or spaces.
Description (Optional) For informational purposes only.
Adapter Type If you are editing an object, you cannot change the adapter
type.
Adapter Instance If you are editing an object, you cannot change the adapter
instance.
Object Type If you are editing an object, you cannot change the object
type. More configuration options might appear, depending
on the object type.
VMware, Inc. 468

Table 4-138. Manage Objects Add or Edit Options (continued)

Options Description
Collection Interval The collection interval for an object influences the

collection status for the object. The collection interval for
the adapter instance determines how often to collect data.
For example, if the collection interval for an adapter
instance is set to five minutes, setting the collection interval
for an object to 30 minutes prevents the object from
having the No Data Receiving collection status after five
collection cycles or 25 minutes.
In cases of adapter instances such as vRealizeOpsMgrAPI
and HttpPost that push data to vRealize Operations
Manager through the REST API, when data is no longer
pushed, the status of the adapter instance is changed to
Down after five collection intervals. For example, if the
process pushes data every ten minutes and is stopped, the
status of the adapter instance is changed to Down after 50
minutes. This behavior is expected for these adapter
instance types.
Dynamic Thresholding On by default, to enable dynamic thresholding and early

warning smart alerts. See vRealize Operations Manager
Dynamic Thresholds
Discover Objects Workspace

If vRealize Operations Manager does not discover objects after an adapter instance is configured,
use manual discovery. Discovering objects is more efficient than adding objects individually.
Note You use discovery to define objects for embedded adapters. vRealize Operations Manager
discovers objects that use external adapters.
Where You Find Discover Objects
In the menu, select Administration, then click Configuration > Inventory in the left pane. Click
Discover Objects in the List tool bar.
Discover Objects
The Discoveries section of the describe.xml file for the adapter might include parameters for
discovery information. The describe.xml file is in the conf subfolder of the adapter, for example
xyz_adapter3/conf/describe.xml.
Options Description
Collector Collector that vRealize Operations Manager uses to

discover objects. Only the vRealize Operations Manager
Collector is added during installation.
Adapter Type Adapter type for the objects to discover.
Adapter Instance Adapter instance of the selected adapter type.
VMware, Inc. 469

Options Description
Discovery Info Selection depends on the adapter type. For example, for a
vCenter adapter, the Discovery Info selection adds an
option to discover objects of a particular object type.
Only New Objects On by default, to omit objects that are already discovered.
Discovery Results List

When you use the Discover Objects feature to manually discover objects in your environment,
vRealize Operations Manager lists the objects of the specified object type. You can choose the
objects to monitor.
Where You Find Discovery Results
Discover Objects in the List tool bar.
After you make selections in the Discover Objects Workspace, click OK. With the default setting,
vRealize Operations Manager displays only newly discovered objects. See Discover Objects
Workspace.
Table 4-139. Object Types

Options Description
Object Type Discovered object types of the Object Type selected on

the Discover Objects Workspace.
Object Count Number of objects of the object type.
Import When selected, imports the object type. Option is active

and selectable for newly discovered object types.
Collect When selected, imports the object type and starts

collecting data. Option is active and selectable for newly
discovered object types.
Credential If the object type requires a login credential to collect data

from the object., the value is True.
Double-click the Object Type to display a list of objects to monitor.
Table 4-140. Objects

Options Description
Object Objects of the selected type that exist in the environment

for the adapter. For example, the vCenter adapter
discovers objects in the vCenter Server system.
Import When selected, imports the object but does not start
collecting data. Option is active and selectable for newly
discovered objects that do not exist in the vRealize
Operations Manager environment .
VMware, Inc. 470

Table 4-140. Objects (continued)

Options Description
Exists Indicates that the object exists in the vRealize Operations

Manager environment.
Collect When selected, imports the object and starts collecting

data. Option is active and selectable for newly discovered
objects that do not exist in the vRealize Operations
Manager environment.
Manage Maintenance Schedules for Your Object Workspace

You use maintenance mode to take an object offline. Many objects in your environment might be
intentionally taken offline. For example, you might deactivate a server to update software. If
vRealize Operations Manager collects metrics when the object is offline, it might generate
incorrect alerts that affect the data for the object's health. When an object is in maintenance
mode, vRealize Operations Manager does not collect metrics from the object and does not
generate alerts for it.
How Maintenance Schedules Work
If an object undergoes maintenance at fixed intervals, you can create a maintenance schedule
and assign it to the object. For example, you can put an object into maintenance mode from
midnight until 3 a.m. every Tuesday night. You can also manually put an object in maintenance
mode, either indefinitely or for a specified period of time. These methods are not mutually
exclusive. You can put an object in maintenance mode or take it out of maintenance mode, even
if it has an assigned maintenance schedule.
Where You Find Manage Maintenance Schedules
Start Maintenance in the List tool bar.
Table 4-141. Manage Maintenance Schedules Options

Options Description
I will come back and end maintenance myself. Maintenance mode starts for the selected object when you
click OK. You must manually end maintenance mode for
this object.
End maintenance in Type the number of minutes that the object is in

maintenance mode.
End maintenance on Click the calendar icon, and select the date that
maintenance mode ends.
Define Custom Property Workspace

In vRealize Operations Manager, you can define custom properties to collect and store
operational data related to different objects. The custom property can be either a string or a
numeric. You can assign custom properties to any subset of objects irrespective of the adapter
kind and resource kind. You can use a mouse click, search filter, or a tag selector to select the
correct object.
Where You Find Add/Edit Custom Property
VMware, Inc. 471

In the menu, select Administration, then click Inventory in the left pane. Click Add/Edit Custom
Property in the List tool bar.
Table 4-142. Add/Edit Custom Property

Options Description
Property Name Select or enter a property name.
Type Select the property type from the drop-down menu.
Value Enter a value for the property.
You can assign the custom properties defined in this page to the Custom Object Groups and New
Groups.
For more information, see Custom Object Groups Workspace to Create a New Group.
Inventory : Geographical Map of Objects

vRealize Operations Manager discovers objects in your environment for each adapter. Objects
that are assigned a GEO Location tag appear on a geographical map. You can use this map to
quickly locate your objects in the world.
How the Geographical Map Works
Objects with the GEO Location tag appear on a map of the world.
n To create a GEO Location tag, see Manage Object Tags Workspace.
n To assign objects to the tag, see Creating and Assigning Tags.

Where You Find the Geographical Map
In the menu, select Administration, then navigate to Configuration > Inventory in the left pane.
Click the Geographical tab.
Geographical Map Options
Use the plus sign to zoom in. Use the minus sign to zoom out. Click and drag to pan the map to
the left or right.
Managing Custom Object Groups in VMware vRealize Operations Manager

A custom object group is a container that includes one or more objects. vRealize Operations
Manager uses custom groups to collect data from the objects in the group, and report on the
data collected.
Why Use Custom Object Groups?

You use groups to categorize your objects and have the system collect data from the groups of
objects and display the results in dashboards and views according to the way you define the
data to appear.
You can create static groups of objects, or dynamic groups with criteria that determine group
membership as vRealize Operations Manager discovers and collects data from new objects
added to the environment.
VMware, Inc. 472

vRealize Operations Manager provides commonly used object group types, such as World,
Environment, and Licensing. The system uses the object group types to categorize groups of
objects. You assign a group type to each group so that you can categorize and organize the
groups of objects that you create.
Types of Custom Object Groups

When you create custom groups, you can use rules to apply dynamic membership of objects to
the group, or you can manually add the objects to the group. When you add an adapter, the
groups associated with the adapter become available in vRealize Operations Manager.
n Dynamic group membership. To dynamically update the membership of objects in a group,

define rules when you create a group. vRealize Operations Manager adds objects to the
group based on the criteria that you define.
n Mixed membership, which includes dynamic and manual.
n Manual group membership. From the inventory of objects, you select objects to add as
members to the group.
n Groups associated with adapters. Each adapter manages the membership of the group. For
example, the vCenter Server adapter adds groups such as datastore, host, and network, for
the container objects in the vSphere inventory. To modify these groups, you must do so in
the adapter.
Administrators of vRealize Operations Manager can set advanced permissions on custom groups.
Users who have privileges to create groups can create custom groups of objects and have
vRealize Operations Manager apply a policy to each group to collect data from the objects and
report the results in dashboards and views.
When you create a custom group, and assign a policy to the group, the system uses the criteria
defined in the applied policy to collect data from and analyze the objects in the group. vRealize
Operations Manager reports on the status, problems, and recommendations for those objects
based on the settings in the policy.
Note Only custom groups defined explicitly by users can be exported from or imported to
vRealize Operations Manager. Users are able to export or import multiple custom groups. Once
an import function has been executed, the user must check to determine if a policy or policies
should be associated with the imported group. Export-import operations are available for user
defined (created explicitly by user) custom groups only.
How Policies Help vRealize Operations Manager Report On Object Groups

When you apply a policy to an object group, vRealize Operations Manager uses threshold
settings, metrics, super metrics, attributes, properties, alert definitions, and problem definitions
that you enabled in the policy to collect data from the objects in the group, and report the results
in dashboards and views.
VMware, Inc. 473

When you create a new object group, you have the option to apply a policy to the group.
n To associate a policy with the custom object group, select the policy in the group creation
wizard.
n To not associate a specific policy with the object group, leave the policy selection blank. The
custom object group will be associated with the default policy. If the default policy changes,
this object group will be associated with the new default policy.
User Scenario: Creating Custom Object Groups

As a system administrator, you must monitor the capacity for your clusters, hosts, and virtual
machines. vRealize Operations Manager monitors them at different service levels to ensure that
these objects adhere to the policies established for your IT department, and discovers and
monitors new objects added to the environment. You have vRealize Operations Manager apply
policies to the object groups to analyze, monitor, and report on the status of their capacity levels.
To have vRealize Operations Manager monitor the capacity levels for your objects to ensure that
they adhere to your policies for your service levels, you categorize your objects into Platinum,
Gold, and Silver object groups to support the service tiers established.
You create a group type, and create dynamic object groups for each service level. You define
membership criteria for each dynamic object group to have vRealize Operations Manager keep
the membership of objects current. For each dynamic object group, you assign the group type,
and add criteria to maintain membership of your objects in the group. To associate a policy with
the custom object group, you can select the policy in the group creation wizard.
Prerequisites
n Know the objects that exist in your environment, and the service levels that they support.
n Understand the policies required to monitor your objects.
n Verify that policies are available to monitor the capacity of your objects.
Procedure
1 To create a group type to identify service level monitoring, click Administration in the menu,
then click Configuration > Group Types.
VMware, Inc. 474

2 On the Group Types toolbar, click the plus sign and type Service Level Capacity for the
group type.
Your group type appears in the list.
3 Click Environment in the menu, then click the Custom Groups tab.
4 To create a new object group, click the plus sign on the Groups toolbar.
The New Group workspace appears where you define the data and membership criteria for
the dynamic group.
a In the Name text box, type a meaningful name for the object group, such as
Platinum_Objects.
b In the Group Type drop-down menu, select Service Level Capacity.
c (Optional) In the Policy drop-down menu, select your service level policy that has
thresholds set to monitor the capacity of your objects.
To associate a policy with the custom object group, select the policy in the group
creation wizard. To not associate a specific policy with the object group, leave the policy
selection blank. The custom object group will be associated with the default policy. If the
default policy changes, this object group will be associated with the new default policy.
d Select the Keep group membership up to date check box so that vRealize Operations
Manager can discover objects that meet the criteria, and add those objects to the group.
5 Define the membership for virtual machines in your new dynamic object group to monitor
them as platinum objects.
a From the Select Object drop-down menu, select vCenter Adapter, and select Virtual
Machine.
b From the empty drop-down menu for the criteria, select Metrics.
c From the Pick a metric drop-down menu, select Disk Space and double-click Current
Size.
d From the conditional value drop-down menu, select is less than.
e From the Metric value drop-down menu, type 10.
6 Define the membership for host systems in your new dynamic object group to monitor them
as platinum objects.
a Click Add another criteria set.
b From the Select Object drop-down menu, select vCenter Adapter, and select Host
System.
c From the empty drop-down menu for the criteria, select Metrics.
d From the Pick a metric drop-down menu, select Disk Space and double-click Current
Size.
VMware, Inc. 475

e From the conditional value drop-down menu, select is less than.
f From the Metric value drop-down menu, type 100.
7 Define the membership for cluster compute resources in your new dynamic object group.
a Click Add another criteria set.
b From the Select Object drop-down menu, select vCenter Adapter, and select Cluster
Compute Resources.
c From the empty drop-down menu for the criteria, select Metrics.
d From the Pick a metric drop-down menu, select Disk Space and double-click
capacityRemaining.
e From the conditional value drop-down menu, select is less than.
f From the Metric value drop-down menu, type 1000.
g Click Preview to determine whether objects already match this criteria.
8 Click OK to save your group.
When you save your new dynamic group, the group appears in the Service Level Capacity
folder, and in the list of groups on the Groups tab.
9 Wait five minutes for vRealize Operations Manager to collect data from the objects in your
environment.
Results
vRealize Operations Manager collects data from the cluster compute resources, host systems,
and virtual machines in your environment, according to the metrics that you defined in the group
and the thresholds defined in the policy that is applied to the group, and displays the results
about your objects in dashboards and views.
What to do next
To monitor the capacity levels for your platinum objects, create a dashboard, and add widgets to
the dashboard. See Dashboards.
Object Group Types in vRealize Operations Manager

An object group type is an identifier that you apply to a specific group of objects in your
environment to categorize them. You can add new group types, and apply them to groups of
objects so that vRealize Operations Manager can collect data from the object group and display
the results in the dashboards and views.
How the Group Types Work
Use group types to categorize your objects so that the system can apply policies to them to
track, and display specific status, such as alerts, workload, faults, risk, and so on.
VMware, Inc. 476

When you create a new group type, vRealize Operations Manager adds it to the existing list of
group types, and creates a new folder with the name of your group type in the Environment
Custom Groups list.
When you create a new group of objects, you assign a group type to that group of objects. You
add objects from the inventory trees to your custom group, then create your dashboard, add
widgets to the dashboard, and configure the widgets to display the data collected from the
objects in the group. You can then monitor and manage the objects.
You can apply a group type to a group of objects that you create manually, or to object groups
that you cannot modify, such those added by adapters. Each adapter that you add to vRealize
Operations Manager adds one or more static groups of objects to group the data received from
the adapter sources.
The list of group types appears in the Content area under Group Types. The custom object
groups appear in the Environment area under Custom Groups.
Where You Create and Modify a Group Type
To create or modify a group type, click Administration in the menu, then Configuration > Group
Types in the left pane.
Group Type Options
You can add, edit, or delete group types. You cannot edit group types that are created by
adapters.
Groups Tab on the Environment Overview Pane

Groups are containers that can contain any number and type of objects in your environment.
vRealize Operations Manager collects data from the objects in the group and displays the results
in dashboards and views that you define.
How Groups Work
Groups are installed with vRealize Operations Manager, created by an adapter, or created by a
user. Based on the group criteria, you can use groups to organize your environment and monitor
all objects in the group together. You can also assign policies to groups and make group
membership dynamic.
For example, if you have a set of vSphere hosts and you do not want to generate alerts when the
host goes into maintenance mode, you can put the vSphere hosts in a group and assign a policy
that includes a maintenance schedule setting. During the maintenance period, vRealize
Operations Manager ignores any metrics for those objects and does not generate any alerts.
After the maintenance period ends, vRealize Operations Manager returns to monitoring the
objects and generates alerts if an outage occurs.
Where You Find Custom Groups
To access Custom Groups that you create, click Environment on the top menu, then click the
Custom Groups tab.
VMware, Inc. 477

Custom Group Options

Click the New Custom Group icon to add a group. You can only edit, clone, or delete a user-
created group. You cannot modify groups installed with vRealize Operations Manager or by an
adapter.
The Groups data grid displays an overview of the state of each group.
Table 4-143. Group Data Grid Options

Option Description
Name Select the group name to display a summary of the group. Select to the right of the name to
edit, clone, or delete the group.
Summary Criticality of the health, risk, and efficiency of any group. Click a group with a red, orange, or
yellow criticality to get more details about potential problems with objects in the group.
Custom Object Groups Workspace

You can create and edit custom groups of objects to have vRealize Operations Manager collect
data from the objects and display the results in the dashboards and views so that you can
monitor your objects and take action on them when problems occur.
How the Custom Groups Workspace Works
When you create a new object group, you define a meaningful group name, and select the group
type. To associate the custom object group with a policy for analysis, you select the policy in the
group creation wizard. You can leave the policy selection blank to not associate a policy with the
object group. When the policy selection is blank, the custom object group is associated with the
policy that is designated as the default policy.
You select the object types, and determine whether membership in the object group is static,
dynamic, or a combination of static and dynamic membership.
n To create a static object group, you add objects to the group. You do not include criteria for
object membership.
n To create a dynamic object group that vRealize Operations Manager updates based on
specific criteria, you select the object type and define membership criteria for the group
based on metrics, relationships, and properties.
When you add objects to a custom object group, a new folder appears in the Custom Groups
navigation pane on the left, and includes the member objects.
Where You Create and Modify Object Groups
To create or modify static or dynamic object groups, or object groups that have a combination of
static and dynamic membership, click Environment > Custom Groups. The Custom Groups tab
displays a list of custom object groups, and the object groups for adapters added to vRealize
Operations Manager.
To edit existing groups, select a group and click the edit icon on the Custom Groups tab.
VMware, Inc. 478

Custom Object Groups Workspace to Create a New Group

You can create a new object group, define custom properties, assign a group type and objects to
the group. When you create the group, you can assign a policy, or leave the policy selection
blank to apply the default policy. vRealize Operations Manager collects data from the objects in
the group based on the settings in the policy that is associated with the group. The results
appear in the dashboards and views.
Where You Assign Custom Group Type, Policy, and Membership
To assign the group type, policy, and membership, click Environment, click Custom Groups, and
click the plus sign to add a new group. In the New Group workspace, you can define the
membership criteria, and select the objects to include or exclude.
To associate a policy with the custom object group, select the policy in the group creation
wizard. To not associate a specific policy with the object group, leave the policy selection blank.
The custom object group will be associated with the default policy. If the default policy changes,
this object group will be associated with the new default policy.
Table 4-144. New Group Workspace

Option Description
Name Meaningful name of the object group.
Group Type Categorization for the object group. New custom groups appear in a dedicated folder
in the Custom Groups navigation pane on the left.
Policy Assigns a policy to one or more groups of objects to have vRealize Operations
Manager analyze the objects according to the settings in your policy, trigger alerts
when the defined thresholds are violated, and display the results in dashboards, views,
and reports. You can assign a policy to the group when you create the group, or you
can assign it later from the edit custom group wizard or from the policies area.
Keep group membership up to For dynamic object groups, vRealize Operations Manager can discover objects that
date match the criteria for the group membership according to the rules that you define,
and update the group members based on the search results.
VMware, Inc. 479

Table 4-144. New Group Workspace (continued)

Option Description
Define Membership Criteria Defines the criteria for a dynamic object group and has vRealize Operations Manager
pane keep the object membership of the group current.
n Object Type drop-down menu. Selects the type of objects to add to the group,
such as virtual machines.
n Metrics, Relationship, and Properties criteria drop-down menu. Defines the criteria
for vRealize Operations Manager to apply to collect data from the selected objects.
n Metrics. An instance of a data type, or attribute, that varies based on the object
type. A metric is used as measurement criteria to collect data from objects. For
example, you can select system attributes as a metric, where an attribute is a type
of data that vRealize Operations Manager collects from objects.
n Relationship. Indicates how the object is related to other objects. For example, you
can require a virtual machine object to be a child object that contains a certain
word in the vSphere Hosts and Clusters navigation tree.
n Properties. Identifies a configuration parameter for the object. For example, you
can require a virtual machine to have a memory limit that is greater than 100KB.
n Add. Includes another metric, relationship, or property for the object type.
n Remove. Deletes the selected object type from the membership criteria, or delete
the selected metric, relationship, or property type from the criteria for the object
type.
n Reset. Resets the criteria for the first metric, relationship, or property that you
define.
n Adds another criteria set. Adds another object type to add to the group. For
example, you might want to create a single object group to track vCenter Server
instances and Host Systems.
n Preview button. After you define the membership criteria, previews the list of
objects in the group to verify that the criteria you defined is applicable to the
group of objects. If the criteria that you defined is valid, the preview displays
applicable objects. If the criteria is not valid, the preview does not display any
objects.
VMware, Inc. 480


Option Description
Objects To Always Include pane Determine which objects to include in the group every time vRealize Operations
Manager collects data from the objects, regardless of the membership criteria. The
objects that you include override the criteria that you define for membership. In
previous versions of vRealize Operations Manager, these objects were called a allow
list.
n Filtered objects pane. Displays the list of available object groups and the objects in
each group. To always include objects in the group, select the check box for a
group or select individual objects in a group, and click the Add button.
n Add button. Adds the selected objects to the right pane for permanent inclusion in
the object group.
n Selected objects only. Adds only the selected objects to the object group
permanently.
n Selected objects and descendants. Adds the selected object and the
descendants of the selected objects to the object group permanently.
n Objects to always include (n) pane. Lists the objects that you add to the include list.
You must select the check box in the right pane to confirm inclusion of the objects.
The number of objects selected for inclusion is reflected by the (n) variable in the
title of the pane.
n Remove button. Removes the objects selected in the right pane from the list of
objects to always include.
n Selected objects only. Removes only the selected objects from the list of
objects to always include.
n Selected objects and direct children. Removes the selected objects and the
children of the selected objects from the list of objects to always include.
n Selected objects and all descendants. Removes the selected objects and the
descendants of the selected objects from the list of objects to always include.
VMware, Inc. 481


Option Description
Objects To Always Exclude Determine which objects to exclude from the group every time vRealize Operations
pane Manager collects data from the objects, regardless of the membership criteria. The
objects that you include override the criteria that you define for membership. In
previous versions of vRealize Operations Manager, these objects were called a
denylist.
n Filtered objects pane. Displays the list of available object groups and the objects in
each group. To always exclude objects from the group, select the check box for a
group or select individual objects in a group, and click the Add button.
n Add button. Adds the selected objects to the right pane for permanent exclusion
from the object group.
n Selected objects only. Adds only the selected objects to be permanently
excluded from the object group.
n Selected objects and descendants. Adds the selected objects and the
descendants of the selected objects for permanent exclusion from the object
group.
n Objects to always exclude (n) pane. Lists the objects that you add to the exclude
list. You must select the check box in the right pane to confirm exclusion of the
objects. The number of objects selected for exclusion is reflected by the (n)
variable in the title of the pane.
n Remove button. Removes the objects selected in the right pane from the list of
objects to always exclude.
n Selected objects only. Removes only the selected objects from the list of
objects to always exclude.
n Selected objects and direct children. Removes the selected objects and the
children of the selected objects from the list of objects to always exclude.
n Selected objects and all descendants. Removes the selected object and the
descendants of the selected objects from the list of objects to always exclude.
Assign Custom Properties In vRealize Operations Manager, you can define custom properties to collect and store
operational data related to different objects. The custom property can be either a
string or a numeric. You can assign the newly defined custom properties to new
groups or existing groups.
n Property Name. Select or specify a name for the custom property.
n Type. Select the type of custom property from the drop-down menu.
The custom property can either be a string or a numeric.

n Inclusion Value. Specify a custom property value, which should be assigned to this
custom property when an object is added to the group.
n Exclusion Value. Specify a custom property value, which should be assigned to this
custom property when an object leaves the group.
n Reset. Resets the custom property to a non-zero value.
n Remove. Removes the custom property from the group.
n Add Another Custom Property. Adds another custom property to the group.
Managing Application Groups

An application is a container construct that represents a collection of interdependent hardware
and software components that deliver a specific capability to support your business. vRealize
Operations Manager builds an application to determine how your environment is affected when
VMware, Inc. 482

one or more components in an application experiences problems, and to monitor the overall
health and performance of the application. Object membership in an application is not dynamic.
To change the application, you manually modify the objects in the container.
Reasons to Use Applications

vRealize Operations Manager collects data from components in the application and displays the
results in a summary dashboard for each application with a real-time analysis for any of the
components. If a component experiences problems, you can see where in the application the
problems arise, and determine how problems spread to other objects.
Note vRealize Operations Manager provides for calendar periodicity. If your application includes
work performed on a specific day of the month, for example, the 15th of the month or the last
day of the month, this calendar function identifies the pattern after six cycles of the application.
Once the pattern is recognized, the system can forecast accurately into the future. Because the
system acquires its information from the input data, you do not have to give any details about
how you schedule periodical work.
Applications Tab on the Environment Overview Pane

Applications are groups of related objects in your environment that mimic an application in your
business. Use the summary to track the health of objects in the application and help troubleshoot
performance issues.
How Applications Work
In vRealize Operations Manager, each application contains one or more tiers and each tier
contains one or more objects. The tier is a convenient way to organize objects that perform a
specific task in an application. For example, you can group all of your database servers together
in a tier.
The objects in a tier are static. If the set of objects in a tier changes, you must manually edit the
application.
Construct an application to view a particular segment of your business. The application shows
how the performance of one object affects other objects in the same application, and helps you
to locate the source of a problem. For example, if you have an application that includes all the
database, Web, and network servers that process sales data for your business, you see a yellow,
orange, or red status if the application health is degrading. Starting with the application summary
dashboard, you can investigate which server is causing or exhibiting the problem.
Where You Find Applications
In the menu, click Environment, then click the Applications tab.
Applications defined in a previous release of vRealize Operations Manager appear after an

upgrade.
Application Options
Select an application to edit or delete, or click the plus sign to add an application.
The Applications data grid displays an overview of the state of each application.
VMware, Inc. 483

Table 4-145. Application Data Grid Options

Option Description
Name Select the application name to display a summary of the application. Select to the right of the
name to edit or delete the application.
Summary Criticality of the health, risk, and efficiency of any application. Click an application with a red,
orange, or yellow criticality to see more details about potential problems with objects in the
application.
User Scenario: Adding an Application

As the system administrator of an online training system, you must monitor components in the
Web, application, and database tiers of your environment that can affect the performance of the
system. You build an application that groups related objects together in each tier. If a problem
occurs with one of the objects, it is reflected in the application display and you can open a
summary to investigate the source of the problem further.
In your application, you add the DB-related objects that store data for the training system in a
tier, Web-related objects that run the user interface in a tier, and application-related objects that
process the data for the training system in a tier. The network tier might not be needed. Use this
model to develop your application.
Procedure
1 In the menu, click Environment, then click Groups and Applications in the left pane.
2 Click the Applications tab and click the plus sign.
3 Click Basic n-tier Web App and click OK.
The Application Management page that appears has two rows. Select objects from the
bottom row to populate the tiers in the top row.
4 Type a meaningful name such as Online Training Application in the Application text box.
5 For each of the Web, application and database tiers listed, add the objects to the Tier
Objects section.
a Select a tier name. This is the tier that you populate.
b To the left of the object row, select object tags to filter for objects that have that tag
value. Click the tag name once to select the tag from the list and click the tag name again
to deselect the tag from the list. If you select multiple tags, objects displayed depend on
the values that you select.
You can also search for the object by name.
c To the right of the object row, select the objects to add to the tier.
d Drag the objects to the Tier Objects section.
6 Click Save to save the application.
VMware, Inc. 484

Results
The new application appears in the list of applications on the Environment Overview Applications
page. If any of the components in any of the tiers develops a problem, the application displays a
yellow or red status.
What to do next
To investigate the source of the problem, click the application name and see Evaluating Object
Information Using Badge Alerts and the Summary Tab.
Add Application
When you add an application to an environment, you select from a list of predefined templates
or create your own custom template, to group the objects to monitor in your application.
Where You Find Add Application
In the menu, click Environment, then Groups and Applications > Applications in the left pane. On
the Applications tab, click the plus sign.
Add Applications Options
Each predefined template provides you with a list of suggested tiers designed to help you group
related objects that perform a specific task in your application. After you select an option, you
can alter the selection and number of tiers on the Application Management page.
Option Description
Basic n-tier Web App Use this template for any basic application.
Advanced n-tier Web App Use this template for an application that monitors more physical devices, such as the devices
that vRealize Operations Manager discovers when you add a network-related Management
Pack or Management Packs.
Legacy non-Web App Use this template for an application that has no Web-related objects.
Network Use this template for an application that has only network-related objects.
Custom Select this option to build your own application topology.
Application Management Dialog Box

You use Application Management to select the objects for your application. The objects you
select are grouped in tiers and help you to track the health of your application.
Where You Find Application Management
In the menu, click Environment, then click the Groups and Applications menu and select
Applications. On the Applications tab, click the plus sign. After you select an application
template, click OK.
Application Management Options
At the top of the screen, enter a new application name or use the default name from the Add
Application page. The application name must be unique.
VMware, Inc. 485

Below the name, the page is divided into the tier row and the objects row. On each row,
selections in the pane on the left filter the selections in the pane on the right.
The tier row is where you select the tiers to populate with objects to monitor for the application.
Table 4-146. Tier Row

Option Description
Tiers pane Select the tier where you want to place your objects. You can add or delete tiers to fit your
application.
Tier Objects pane Add or remove objects that serve a common function and to monitor. For example, to monitor
all the virtual machines that are database servers for the application, put them in the database
tier.
The object row is where you select objects to add to the tiers.
Table 4-147. Object Row

Option Description
Object Tags pane Expand a tag to see a group of objects with that tag value. For example, if Adapter Types is an
object tag, the tag values include vCenter Adapter, and an object is an adapter instance.
Objects are not displayed. The tag filters the object pane. To select a tag value, click once. To
deselect a tag value, click twice. Tag values remain selected until they are deselected.
Objects pane Drag an object with the object tag value to add to the Tier Objects pane. To find an object,
search by name. Each object listed includes identifier information to help distinguish between
objects of similar names. Add All Objects To Parent adds all the objects to a tier.
Configuring Data Display

You configure the content in vRealize Operations Manager to suit your information needs, using
views, reports, dashboards, and widgets.
Views display data, based on an object type. You can select from various view types to see your
data from a different perspective. Views are reusable components that you can include in reports
and dashboards. Reports can contain predefined or custom views and dashboards in a specified
order. You build the reports to represent objects and metrics in your environment. You can
customize the report layout by adding a cover page, a table of contents, and a footer. You can
export the report in a PDF or CSV file format for further reference.
You use dashboards to monitor the performance and state of objects in your virtual
infrastructure. Widgets are the building blocks of dashboards and display data about configured
attributes, resources, аpplications, or the overall processes in your environment. You can also
incorporate views in dashboards using the vRealize Operations Manager View Widget.
Widgets
Widgets are the panes on your dashboards. You add widgets to a dashboard to create a
dashboard. Widgets show information about attributes, resources, applications, or the overall
processes in your environment.
VMware, Inc. 486

You can configure widgets to reflect your specific needs. The available configuration options
vary depending on the widget type. You must configure some of the widgets before they display
any data. Many widgets can provide or accept data from one or more widgets. You can use this
feature to set the data from one widget as filter and display related information on a single
dashboard.
Widget Interactions
Widget interactions are the configured relationships between widgets in a dashboard where one
widget provides information to a receiving widget. When you are using a widget in the
dashboard, you select data on one widget to limit the data that appears in another widget,
allowing you to focus on a smaller subset data.
How Interactions Work

If you configured interactions between widget at the dashboard level, you can then select one or
more objects in the providing widget to filter the data that appears in the receiving widget,
allowing you to focus on data related to an object.
To use the interaction option between the widgets in a dashboard, you configure interactions at
the dashboard level. If you do not configure any interactions, the data that appears in the
widgets is based on how the widget is configured.
When you configure widget interaction, you specify the providing widget for the receiving
widget. For some widgets, you can define two providing widgets, each of which can be used to
filter data in the receiving widget.
For example, if you configured the Object List widget to be a provider widget for the Top-N
widget, you can select one or more objects in the Object List widget and the Top-N displays data
only for the selected objects.
For some widgets, you can define more than one providing widget. For example, you can
configure the Metric Chart widget to receive data from a metrics provider widget and an objects
providing widget. In such case, the Metric Chart widget shows data for any object that you select
in the two provider widgets.
Manage Metric Configuration

You can create a custom set of metrics to display the widgets. You can configure one or more
files that define different sets of metrics for a particular adapter and object types so that the
supported widgets are populated based on the configured metrics and selected object type.
How the Metric Configuration Works

From the Metric Configuration page, you create an XML file that displays a set of metrics at a
supported widget. The widgets are Metric Chart, Property List, Rolling View Chart, Scoreboard,
Sparkline Chart, and Topology Graph. To use the metric configuration, you must set the widget
Self Provider to Off and create a widget interaction with a provider widget.
VMware, Inc. 487

Where You Find the Metric Configuration

To manage metric configurations, in the menu, click Administration, and then in the left pane
click Configuration > Metric Configurations.
Table 4-148. Manage Metric Config Toolbar Options

Option Description
Create Configuration Creates an empty XML file in a selected folder.
Edit Configuration Activates a selected XML file for edit in the text box on the
right.
Delete Configuration Deletes a selected XML file.
Text box Displays a selected XML file. You must select an XML file
and click Edit to edit it.
Add a Resource Interaction XML File

A resource interaction file is a custom set of metrics that you want to display in widgets that
support the option. You can configure one or more files that define different sets of metrics for
particular object types so that the supported widgets are populated based the configured
metrics and selected object type.
The following widgets support the resource interaction mode:
n Metric Chart
n Property List
n Rolling View Chart
n Scoreboard
n Sparkline Chart
n Topology Graph
To use the metric configuration, which displays a set of metrics that you defined in an XML file,
the dashboard and widget configuration must meet the following criteria:
n The dashboard Widget Interaction options are configured so that another widget provides
objects to the target widget. For example, an Object List widget provides the object
interaction to a chart widget.
n The widget Self Provider option is set to Off.
n The custom XML file in the Metric Configuration drop-down menu is in the/usr/lib/vmware-
vcops/tools/opscli directory and has been imported into the global storage using the
import command.
If you add an XML file and later modify it, the changes might not take effect.
VMware, Inc. 488

Prerequisites
n Verify that you have the necessary permissions to access the installed files for vRealize
Operations Manager and add files.
n Create a new files based on the existing examples. Examples are available in the following
location:
n vApp. The XML file is in /usr/lib/vmware-vcops/tomcat-web-app/webapps/vcops-web-

ent/WEB-INF/classes/resources/reskndmetrics.
Procedure
1 Create an XML file that defines the set of metrics.
For example:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

<AdapterKinds>
<AdapterKind adapterKindKey="VMWARE">
<ResourceKind resourceKindKey="HostSystem">
<Metric attrkey="sys:host/vim/vmvisor/slp|resourceMemOverhead_latest" />
<Metric attrkey="cpu|capacity_provisioned" />
<Metric attrkey="mem|host_contention" />
</ResourceKind>
</AdapterKind>
</AdapterKinds>
In this example, the displayed data for the host system based on the specified metrics.
2 Save the XML file in one of the following directories base on the operating system of your
vRealize Operations Manager instance.
Operating System File Location
vApp /usr/lib/vmware-vcops/tools/opscli
3 Run the import command.
Operating System File Location
vApp ./ops-cli.sh file import reskndmetric YourCustomFilename.xml
The file is imported into global storage and is accessible from the supported widgets.
4 If you update an exisiting file and must re-import the file, append --force to the above
import command and run it.
For example, ./vcops-cli.sh file import reskndmetric YourCustomFilename.xml --

force.
What to do next
To verify that the XML file is imported, configure one of the supported widgets and ensure that
the new file appears in the drop-down menu.
VMware, Inc. 489

You can also create a custom set of metrics to display the widgets, from the Manage Metric
Configuration.
Widget Definitions List

A widget is a pane on a dashboard that contains information about configured attributes,
resources, applications, or the overall processes in your environment. Widgets can provide a
holistic, end-to-end view of the health of all of the objects and applications in your enterprise. If
your user account has the necessary access rights, you can add and remove widgets from your
dashboards.
Table 4-149. Summary of Widgets

Widget Name Description
Alert List Shows a list of alerts for the objects that the widget is configured to monitor. If no objects
are configure, the list displays all alerts in your environment.
Alert Volume Shows a trend report for the last seven days of alerts generated for the objects it is
configured to monitor.
Anomalies Shows a chart of the anomalies count for the past 6 hours.
Anomaly Breakdown Shows the likely root causes for symptoms for a selected resource.
Capacity Remaining Shows a percentage indicating the remaining computing resources as a percent of the
total consumer capacity. It also displays the most constrained resource.
Container Details Shows the health and alert counts for each tier in a single selected container.
Container Overview Shows the overall health and the health of each tier for one or more containers.
Current Policy Shows the highest priority policy applied to a custom group.
Data Collection Results Shows a list of all supported actions specific for a selected object.
DRS Cluster Settings Shows the workload of the available clusters and the associated hosts.
Efficiency Shows the status of the efficiency-related alerts for the objects that it is configured to
monitor. Efficiency is based on generated efficiency alerts in your environment.
Environment Lists the number of resources by object or groups them by object type.
Environment Overview Shows the performance status of objects in your virtual environment and their
relationships. You can click an object to highlight its related objects and double-click an
object to view its Resource Detail page.
Environment Status Shows statistics for the overall monitored environment.
Faults Shows a list of availability and configuration issues for a selected resource.
Forensics Shows how often a metric had a particular value, as a percentage of all values, within a
given time period. It can also compare percentages for two time periods.
Geo Shows where your objects are located on a world map, if your configuration assigns
values to the Geo Location object tag.
Health Shows the status of the health-related alerts for the objects that it is configured to
monitor. Health is based on generated health alerts in your environment.
Health Chart Shows health information for selected resources, or all resources that have a selected tag.
Heat Map Shows a heat map with the performance information for a selected resource.
VMware, Inc. 490

Table 4-149. Summary of Widgets (continued)

Mashup Chart Brings together disparate pieces of information for a resource. It shows a health chart and
metric graphs for key performance indicators (KPIs). This widget is typically used for a
container.
Metric Chart Shows a chart with the workload of the object over time based on the selected metrics.
Metric Picker Shows a list of available metrics for a selected resource. It works with any widget that can
provide resource ID.
Object List Shows a list of all defined resources.
Object Relationship Shows the hierarchy tree for the selected object.
Object Relationship Shows the hierarchy tree for the selected objects. It provides advanced configuration
(Advanced) options.
Property List Shows the properties and their values of an object that you select.
Recommended Actions Displays recommendations to solve problems in your vCenter Server instances. With
recommendations, you can run actions on your data centers, clusters, hosts, and virtual
machines.
Risk Shows the status of the risk-related alerts for the objects that it is configured to monitor.
Risk is based on generated risk alerts in your environment.
Rolling View Chart Cycles through selected metrics at an interval that you define and shows one metric graph
at a time. Miniature graphs, which you can expand, appear for all selected metrics at the
bottom of the widget.
Scoreboard Shows values for selected metrics, which are typically KPIs, with color coding for defined
value ranges.
Scoreboard Health Shows color-coded health, risk, and efficiency scores for selected resources.
Sparkline Chart Shows graphs that contain metrics for an object . If all of the metrics in the Sparkline Chart
widget are for an object that another widget provides, the object name appears at the top
right of the widget.
Tag Picker Lists all defined resource tags.
Text Display Reads text from a Web page or text file and shows the text in the user interface.
Time Remaining Shows a chart of the Time Remaining values for a specific resources over the past 7 days.
Top Alerts Lists the alerts most likely to negatively affect your environment based on the configured
alert type and objects.
Top-N Shows the top or bottom N number metrics or resources in various categories, such as the
five applications that have the best or worst health.
Topology Graph Shows multiple levels of resources between nodes.
View Shows a defined view depending on the configured resource.
Weather Map Uses changing colors to show the behavior of a selected metric over time for multiple
resources.
Workload Shows workload information for a selected resource.
VMware, Inc. 491

Table 4-149. Summary of Widgets (continued)

Workload Pattern Shows a historical view of the hourly workload pattern of an object.
Workload Utilization Shows the workload utilization for objects so that you can identify problems with
workload.
Alert List Widget

The Alert List widget is a list of alerts for the objects it is configured to monitor. You can create
one or more alert lists in vRealize Operations Manager for objects that you add to your custom
dashboards. The widget provides you with a customized list of alerts on objects in your
environment.
How the Alert List Widget and Configuration Options Work
You can add the Alert List widget to one or more custom dashboards and configure it to display
data that is important to different dashboard users. The data that appears in the widget is based
on the configured options for each widget instance. You edit an Alert List widget after you add it
to a dashboard. The changes you make to the options create a custom alert list to meet the
needs of the dashboard users.
Where You Find the Alert List Widget

The widget might be included on any of your custom dashboards. In the menu, click Dashboards
to see your configured dashboards.
To customize the data that appears in the dashboard widget, in the menu, click Dashboards.
Click Actions > Create Dashboard/Edit Dashboard to add or edit a dashboard. Toggle between
the Views and Widgets option to view and add a widget to the dashboard. The widgets list panel
displays a list of all the predefined widgets. Drag a widget to the dashboard workspace in the
upper panel.
VMware, Inc. 492

Alert List Widget Toolbar Options

On the title bar of the widget, click the Show Toolbar icon to access the toolbar options.
Option Description
Dashboard Navigation Actions you can run on the selected alert.

For example, you use the option to open a vCenter Server,
data center, virtual machine, or in the vSphere Web Client,
allowing you to directly modify an object for which an alert
was generated and fix any problems.
Reset Interaction Returns the widget to its initial configured state and undoes
any interactions selected in a providing widget.
Interactions are usually between widgets in the same
dashboard, or you can configure interactions between
widgets on different dashboards.
Perform Multi-Select Interaction If the widget is a provider for another widget on the
dashboard, you can select multiple rows and click this
button. The receiving widget then displays only the data
related to the selected interaction items.
Use Ctrl+click for Windows, or Cmd+click for Mac OS X, to
select multiple individual objects or Shift+click to select a
range of objects, and click the icon to enable the interaction.
Display Filtering Criteria Displays the object information on which this widget is
based.
Select Date Range Limits the alerts that appear in the list to the selected date
range.
from the list.
Canceling the alert does not cancel the underlying condition
that generated the alert. Canceling alerts is effective if the
alert is generated by triggered fault and event symptoms
because these symptoms are triggered again only when
subsequent faults or events occur on the monitored objects.
If the alert is generated based on metric or property
symptoms, the alert is canceled only until the next collection
and analysis cycle. If the violating values are still present, the
alert is generated again.

owner.
VMware, Inc. 493

Option Description
alert.
ownership.
Group By Group alerts by the options in the drop-down menu.
Filter Locate data in the widget.

Option Description
Time Group alerts by time triggered. The default.
Alert List Widget Data Grid table.

together.
Alert List Widget Data Grid Options

The data grid provides information on which you can sort and search.
Expand the grouped alerts to view the data grid.
Option Description

Alert Description of the alert.
Triggered On Name of the object for which the alert was generated.
VMware, Inc. 494

Option Description
Alert Type Alert type is assigned when you create the alert definition.
It helps you categorize and route the alert to the
appropriate domain administrator for resolution.
n Application
n Virtualization/Hypervisor
n Hardware (OSI)
n Storage
n Network
Alert Sub-Type Alert subtype is assigned when you create the alert
definition. It helps you categorize and route the alert to the
appropriate domain administrator for resolution.
n Availability
n Performance
n Capacity
n Compliance
n Configuration
Alert List Widget Configuration Options

On the title bar of the widget, click the Edit Widget icon to configure the widget.
The configuration options are grouped into one or more sections. You can select the objects on
which you want to base the widget data and refine the objects in the following sections. Each
section filters the objects further and pushes the filtered objects to the next section. The widget
data is based on the objects that are the output of the last section.
The Configuration section provides general configuration options for the widget.
The Input Data section provides options to specify input for the widget. This section appears
when the widget is in self provider mode.
The Input Transformation section provides options to transform the input for the widget.
The Output Filter section provides options to restrict the widget data based on the selected filter
criteria.
Option Description
Title Enter a custom title that identifies this widget from other
instances that are based on the same widget template.
Configuration
Refresh Content Enable or disable the automatic refreshing of the data in this
widget.
If not enabled, the widget is updated only when the
dashboard is opened or when you click the Refresh button
on the widget in the dashboard.
VMware, Inc. 495

Option Description
Refresh Interval If you enable the Refresh Content option, specify how often
to refresh the data in this widget.
Self Provider Indicates whether the objects for which data appears in the
widget are defined in the widget or provided by another
widget.
n On. You define the objects for which data appears in the
widget.
n Off. You configure other widgets to provide the objects
to the widget using the dashboard widget interactions
options.
Input Data
Objects Select objects on which you want to base the widget data.
1 Click the Add New Objects icon and select objects in the
pop-up window. The selected objects appear in a list in
this section.
While selecting objects, you can use the Filter text box
to search for objects. You can also expand the Tag Filter
pane on the left hand side to select one or more object
tag values. A list of objects with the selected tag values
appears.. If you select more than one value for the same
tag, you can choose objects that have any of the tags
applied. If you select more than one value for different
tags, you can choose only the objects that have all the
tags applied.
2 Optionally, select objects from the list and click the
Remove Selected Objects icon to remove the selected
objects.
Click the Select All icon to select all the objects in the
list.
Click the Clear Selection icon to clear your selection of

objects in the list.
All If you select this option, the widget data is based on all the
objects in your environment. The following sections provide
options to refine the objects for the widget data.
Input Transformation
Relationship Transform the input for the widget based on the relationship
of the objects. For example, if you select the Children check
box and a Depth of 1, the child objects are the transformed
inputs for the widget.
Output Filter
VMware, Inc. 496

Option Description
Basic Pick tags to refine the widget data. The widget data is based
on the objects that have the picked tags applied. If you pick
more than one value for the same tag, the widget includes
objects that have any of the tags applied. If you pick more
than one value for different tags, the widget includes only
the objects that have all the tags applied.
If the objects have an input transformation applied, you
select tag values for the transformed objects.
Advanced Refine the widget data further based on the filter criteria for
object types. The widget data is based on the objects for
the filtered object types.
If the objects have a tag filter applied in the Basic
subsection, you define filter criteria for the object types of
the objects with tag filter applied. If the objects with tag filter
applied do not belong to any of the object types in this filter
criteria, the widget skips this filter and includes all the
objects with tag filter applied.
define filter criteria for the object types of the transformed
objects.
1 In the first drop-down menu, select an object type.
2 In the second drop-down menu, select the option based
on which you want to define the filter criteria. For
example, if you select Metrics for the Datacenter object
type, you can define a filter criteria based on the value
of a specific metric for data centers.
3 In the drop-down menus and text boxes that appear,
select or enter values to filter the objects.
4 To add more filter criteria, click Add.
5 To add another filter criteria set, click Add another
criteria set.
Alert Related A group of filters limits the alerts that appear in this alert list
to those that meet the selected criteria.
If the objects on which the alerts are based have an input
transformation applied, you define filters for the alerts based
on the transformed objects.
You can configure the following filters:
n Alert Type. Select the subtype in the type list. This value
was assigned when you configured the alert definition.
n Status. Select one or more alert states to include in the
list.
n Control State. Select one or more control states to
include in the list.
n Criticality. Select one or more levels of criticality.
n Impact. Select one or more alert badges to include in the
list.
VMware, Inc. 497

Alert Volume Widget

The Alert Volume widget is a trend report for the last seven days of alerts generated for the
objects it is configured to monitor in vRealize Operations Manager. You can create one or more
alert volume widgets for objects that you add to your dashboards. The alert volume provides
you with a customized trend report on objects that helps you identify changes in alert volume,
indicating a problem in your environment.
How the Alert Volume Widget and Configuration Options Work
You can add the Alert Volume widget to one or more custom dashboards and configure it to
display data that is important to different dashboard users. The data that appears in the widget is
based on the configured options for each widget instance. The changes you make to the options
create a custom widget to meet the needs of the dashboard users.
Where You Find the Alert Volume Widget

upper panel.
Alert Volume Widget Display Options
The Alert Volume widget displays a trend chart, symptoms by criticality, and active alerts.
Option Description
Trend chart Volume of critical, immediate, and warning symptoms for

the configured objects.
Symptoms by criticality Number of symptoms for each criticality level.
Active Alerts Number of active alerts. Alerts can have more than one
triggering symptom.
VMware, Inc. 498

Alert Volume Widget Configuration Options

Option Description
Configuration
Refresh Content Enable or disable the automatic refreshing of the data in

this widget.
Refresh Interval If you enable the Refresh Content option, specify how
often to refresh the data in this widget.
widget.
n On. You define the objects for which data appears in
the widget.
options.
Input Data
Object Search for objects in your environment and select the

object on which you are basing the widget data. You can
also click the Add Object icon and select an object from
the object list. You can use the Filter text box to refine the
object list and the Tag Filter pane to select an object
based on tag values.
Anomalies Widget
The Anomalies widget displays the anomalies for a resource for the past 6 hours at time intervals
you set.
The Anomalies widget shows or hides time periods when the metric violates a threshold that
configured. The widget color indicates the criticality of the violation.
VMware, Inc. 499

Where You Find the Anomalies Widget

upper panel.
Anomalies Widget Configuration Options
Option Description
Configuration

this widget.
VMware, Inc. 500

Option Description
Self Provider n On. You define the objects for which data appears in
the widget.
options.
Input Data

Anomaly Breakdown Widget

The Anomaly Breakdown widget shows the likely root causes for symptoms for a selected
resource.
How the Anomaly Breakdown Widget and Configuration Options Work
You can add the Anomaly Breakdown widget to one or more custom dashboards and configure
it to display data that is important to the dashboard users.
Where You Find the Anomaly Breakdown Widget
upper panel.
VMware, Inc. 501

Anomaly Breakdown Widget Display Options

The Anomaly Breakdown widget displays scores, volume, and a list of anomaly metrics.
Option Description
Score Anomaly value.
Volume vRealize Operations Manager full set metric count for the
selected object in the specified time range.
Anomaly Metrics List List of alarms for the selected object in the specified time range.
Anomaly Breakdown Widget Toolbar Options

Option Description
Show Bar Details If the widget is displaying data for multiple objects, you can
select a row and click this button to view the list of alarms for the
selected object.
Perform Multiple Interaction If the widget is a provider for another widget on the dashboard,
you can select multiple rows and click this button. The receiving
widget then displays only the data related to the selected
interaction items.
Use Ctrl+click for Windows, or Cmd+click for Mac OS X, to select
multiple individual objects or Shift+click to select a range of
objects, and click the icon to enable the interaction.
Anomaly Breakdown Widget Configuration Options

criteria.
Option Description
Configuration
VMware, Inc. 502

Option Description

this widget.
widget.
the widget.
options.
Mode Display a single object or multiple objects.
Show Select the number of objects to display in multiple objects

mode.
Input Data

Output Filter
Basic Pick tags to refine the widget data. The widget data is
based on the objects that have the picked tags applied. If
you pick more than one value for the same tag, the widget
includes objects that have any of the tags applied. If you
pick more than one value for different tags, the widget
includes only the objects that have all the tags applied.
Container Details Widget

The Container Details widget displays graphs that show a summary of child objects, metrics, and
alerts of an object in the inventory.
VMware, Inc. 503

How the Container Details Widget and Configuration Options Work

The Container Details widget treats objects from the inventory as containers and objects.
Containers are objects that contain other objects. The widget lists the containers and shows the
number of containers, objects, metrics, and alerts of the observed object. The widget also
displays the alerts of each container and an icon links to its child objects. For example, if you
select from the inventory a host that contains three objects such as, two virtual machines and
one datastore, the Container Details widget displays summary information with three containers,
two objects that are the child objects of the two virtual machines, and the number of alerts for
the host and the number of metrics for the child objects of the host. The widget also lists each of
the three containers, with the number of alerts for each object. Clicking an object in the graph
takes you to the object details page. When you point to the icon next to the object, a tool tip
shows the name of the related resource and its health. For example, when you point to the icon
next to a virtual machine, the tool tip shows a related datastore and its health. Clicking the icon
takes you to the object detail page of the related object, which is the datastore following the
example.
You edit a container details widget after you add it to a dashboard. You can configure the widget
to take information from another widget in the dashboard and to analyze it. When you select Off
from the Self Provider option and set source and receiver widgets in the Widget Interactions
menu during editing of the dashboard, the receiver widget shows information about an object
that you select from the source widget. For example, you can configure the Container Details
widget to display information about an object that you select from the Object Relationship
widget in the same dashboard.
Where You Find the Container Details Widget
upper panel.
VMware, Inc. 504

Container Details Widget Configuration Options

Option Description
Configuration

this widget.
widget.
the widget.
options.
Mode You can change the size of the graph using the Compact or
Large buttons.
Input Data

Capacity Remaining Widget

The Capacity Remaining widget displays a percentage indicating the remaining computing
resources as a percent of the total consumer capacity. It also displays the most constrained
resource.
VMware, Inc. 505

Where You Find the Capacity Remaining Widget

upper panel.
Capacity Remaining Widget Configuration Options
Option Description
Title Enter a custom title that identifies this widget from other instances that are based on the same widget
template.
Configuration
Refresh Content Enable or disable the automatic refreshing of the data in this widget.
If not enabled, the widget is updated only when the dashboard is opened or when you click the
Refresh button on the widget in the dashboard.
Refresh Interval If you enable the Refresh Content option, specify how often to refresh the data in this widget.
Self Provider Indicates whether the objects for which data appears in the widget are defined in the widget or
provided by another widget.
n On. You define the objects for which data appears in the widget.
n Off. You configure other widgets to provide the objects to the widget using the dashboard widget
interactions options.
Input Data
Object Search for objects in your environment and select the object on which you are basing the widget
data. You can also click the Add Object icon and select an object from the object list. You can use the
Filter text box to refine the object list and the Tag Filter pane to select an object based on tag values.
Container Overview Widget

The Container Overview widget gives a graphical presentation of the health, risk, and efficiency
of an object or list of objects in the environment.
VMware, Inc. 506

How the Container Overview Widget and Configuration Options Work

The Container Overview widget displays the current status, the status for a previous time period
of the health, risk, and the efficiency of an object or list of objects. You can configure the widget
to display information for one or more objects that you are interested in when you select the
Object mode during configuration of the widget. The widget displays information for all objects
from an object type or types when you select the Object Type mode during configuration of the
widget. You can open the object detailed page of each object in the data grid when you click the
object.
You edit a container overview widget after you add it to a dashboard. You can configure the
widget to display information about an object or to display information about all objects from an
object type by using the Object or Object Type mode. The configuration options change
depending on your selection of mode.
Where You Find the Container Overview Widget
upper panel.
Container Overview Widget Toolbar Options
The toolbar contains icons that you can use to get more information about other widgets or
dashboards.
VMware, Inc. 507

Option Description
Filter You can filter the objects in the data grid.
Dashboard Navigation You can explore information from another dashboard.
Note This toolbar icon exists when you configure the

widget to interact with a widget from another dashboard.
Use Dashboard Navigation menu during dashboard
configuration to configure the widgets to interact.
When you select an object from an object data grid and

click the toolbar icon, it takes you to a related dashboard.
For example, you can configure the widget to send
information to a Topology Graph widget that is on another
dashboard, for example dashboard 1. When you select a VM
from the data grid, click Perform Multi-Select Interaction ,
click Dashboard Navigation and select Navigate >
dashboard 1. It takes you to dashboard 1, where you can
observe selected VM and objects related to it.
Container Overview Widget Data Grid Options

Option Description
Name Name of the object
Health Shows information about the health parameter.

Status displays the badge of the current health status of an
object. You can check the status in a tool tip when you
point to the badge.
Last 24 Hours displays the statistic of health parameter for
last 24 hours.
Risk Shows information about the risk parameter.

Status displays the badge of the current risk status of an
object. You can check the status in a tool tip when you
point to the badge.
Last Week displays the statistics of the health parameter
for the last week.
Efficiency Shows information about the efficiency parameter.

Status displays the badge of the current efficiency status
of an object. You can check the status in a tool tip when
you point to the badge.
Last Week displays statistic of the efficiency parameter for
the last week.
VMware, Inc. 508

Container Overview Widget Configuration Options

Option Description
Configuration
Mode Use Object to select an object from the environment to

observe.
Use Object Type to select the type of the objects to
observe.

this widget.
widget.
the widget.
options.
Input Data
VMware, Inc. 509

Option Description
Object Select objects on which you want to base the widget data.
1 Click the Add New Objects icon and select objects in
the pop-up window. The selected objects appear in a
list in this section.
to search for objects. You can also expand the Tag
Filter pane on the left hand side to select one or more
object tag values. A list of objects with the selected tag
values appears.. If you select more than one value for
the same tag, you can choose objects that have any of
the tags applied. If you select more than one value for
different tags, you can choose only the objects that
have all the tags applied.
objects.
list.

Object Type Select an object type in your environment on which you

want to base the widget data.
1 Click the Add Object Type icon to search for and add
an object type.
When you search for object types, you can filter the
types in the list by selecting a type from the Adapter
Type drop-down menu or by using the Filter text box.
2 Optionally, select the object type from the list and click
the Delete Object Type icon to remove the selected
object type.
Current Policy Widget

The Current Policy widget displays the active operational policy that is assigned to your object or
object group. vRealize Operations Manager uses the assigned policy to analyze your objects,
control the data that is collected from those objects, generate alerts when problems occur, and
display the results in the dashboards.
How the Current Policy Widget and Configuration Options Work
You add the Current Policy widget to a dashboard so that you can quickly see which operational
policy is applied to an object or object group. To add the widget to a dashboard, you must have
access permissions associated with the roles assigned to your user account.
VMware, Inc. 510

The configuration changes that you make to the widget creates a custom instance of the widget
that you use in your dashboard to identify the current policy assigned to an object or object
group. When you select an object on the dashboard, the policy applied to the object appears in
the Current Policy widget, with an embedded link to the policy details. To display the inherited
and local settings for the applied policy, click the link.
Where You Find the Current Policy Widget
upper panel.
Current Policy Widget Configuration Options
Option Description
Title Enter a custom title that identifies this widget from other instances that are based on
the same widget template.
Configuration
If not enabled, the widget is updated only when the dashboard is opened or when you
click the Refresh button on the widget in the dashboard.
Refresh Interval If you enable the Refresh Content option, specify how often to refresh the data in this
widget.
Self Provider Indicates whether the objects for which data appears in the widget are defined in the
widget or provided by another widget.
n Off. You configure other widgets to provide the objects to the widget using the
dashboard widget interactions options.
For example, to view the policy applied to each object that you select in the Object
List widget, select Off for Self Provider.
VMware, Inc. 511

Option Description
Input Data
Object Search for objects in your environment and select the object on which you are basing
the widget data. You can also click the Add Object icon and select an object from the
object list. You can use the Filter text box to refine the object list and the Tag Filter
pane to select an object based on tag values.
Data Collection Results Widget

The Data Collection Result widget shows a list of all supported actions specific for a selected
object. The widget retrieves data specific to a selected object actions and uses the action
framework to run data collection actions.
How the Data Collection Results Widget and Configuration Options Work
You can add the Data Collection Results widget to one or more custom dashboards and
configure it to display data that is important to different dashboard users. The data that appears
in the widget is based on the configured options for each widget instance.
The Data Collection Results widget is a receiver of a resource or metric ID. It can interact with any
resource or metric ID that provides widgets such as Object List and Metric Picker. To use the
widget, you must have an environment that contains the following items.
n A vCenter Adapter instance
n A vRealize Operations Manager for Horizon View Adapter
n A vRealize Operations Manager for Horizon View Connection Server
You edit a Data Collection Result widget after you add it to a dashboard. The changes you make
to the options create a custom widget to meet the needs of the dashboard users.
Where You Find the Data Collection Results Widget
upper panel.
Data Collection Results Widget Toolbar Options
VMware, Inc. 512

Option Description
Results Shows all finished and currently running actions for the
selected object.
Choose Action Shows a list with all supported actions specific for the
selected object. The selected object is a result of widget
interactions.
Data Collection Results Widget Configuration Options

The Input Data section provides options to specify input for the widget.
Option Description
Configuration

this widget.
If not enabled, the widget updates only when you open the
dashboard.
widget.
the widget.
options.
Input Data
Config Specifies self provider choice and selection of a resource

instance.
Selected Object When you select an object, this text box is populated by
the object.
Start new data collection on interaction change Indicates whether to start a new data collection action
when the object selection changes in the source widget.
Objects List of objects in your environment that you can search or

sort by column so that you can locate the object on which
you are basing the data that appears in the widget.
VMware, Inc. 513

Option Description
Defaults Specifies the default data collection action selected for

each object type.
Object Types List of object types in your environment that you can
search or sort by column so that you can locate the object
type on which you are basing the data that appears in the
widget. You can filter the types in the list by selecting a
type from the Adapter Type drop-down menu or by using
the Filter text box.
Default Data Collection Action This panel is populated by the object type that you select
in the object types list.
You can select only one default data collection action for
an object type.
DRS Cluster Settings Widget

The DRS Cluster Settings widget displays the workload of the available clusters and the
associated hosts. You can change the Distributed Resource Scheduler (DRS) automation rules for
each cluster.
How the DRS Cluster Settings Widget and Configuration Options Work
You can view CPU workload and memory workload percentages for each of the clusters. You can
view CPU workload and memory workload percentages for each host in the cluster by selecting a
cluster in the data grid. The details are displayed in the data grid below. You can set the level of
DRS automation and the migration threshold by selecting a cluster and clicking Cluster Actions >
Set DRS Automation.
You edit a DRS Cluster Settings widget after you add it to a dashboard. To configure the widget,
click the edit icon at the upper-right corner of the widget window. You can add the DRS Cluster
Settings widget to one or more custom dashboards and configure it to display data that is
important to different dashboard users. The data that appears in the widget is based on the
configured options for each widget instance.
The DRS Cluster Settings widget appears on the dashboard named vSphere DRS Cluster
Settings, which is provided with vRealize Operations Manager.
Where You Find the DRS Cluster Settings Widget
VMware, Inc. 514

upper panel.
DRS Cluster Settings Widget Toolbar Options
Option Description
Cluster Actions Limits the list to actions that match the cluster you select.
Show The drop-down menu displays the parent vCenter Server

instances where the clusters reside. You can also view the
data centers under each parent vCenter Server instance.
Select a parent vCenter Server to view the workload of the
available clusters in the data grid.
The default setting displays the clusters across all vCenters.
Filter Filters the data grid by name, data center, vCenter, DRS
settings, and migration threshold.
DRS Cluster Settings Widget Data Grid Options

Option Description
Name Displays the names of the clusters in the selected parent

vCenter Server instance.
Datacenter Displays the data centers that belong to each cluster.
vCenter Displays the parent vCenter Server instance where the

cluster resides.
DRS Settings Displays the level of DRS automation for the cluster.
To change the level of DRS automation for the cluster,
select Cluster Actions > Set DRS Automation from the
toolbar. You can change the automation level by selecting
an option from the drop-down menu in the Automation
Level column.
Migration Threshold Recommendations for the migration level of virtual

machines. Migration thresholds are based on DRS priority
levels, and are computed based on the workload imbalance
metric for the cluster.
CPU Workload % Displays the percentage of CPU in GHz available on the

cluster.
Memory Workload % Displays the percentage of memory in GB available on the

cluster.
DRS Cluster Settings Configuration Options

VMware, Inc. 515

Option Description
Configuration

this widget.
Efficiency Widget
The efficiency widget is the status of the efficiency-related alerts for the objects it is configured
to monitor. Efficiency alerts in vRealize Operations Manager usually indicate that you can reclaim
resources. You can create one or more efficiency widgets for objects that you add to your
custom dashboards.
How the Efficiency Widget and Configuration Options Work
You can add the efficiency widget to one or more custom dashboards and configure it to display
data that is important to the dashboard users.
The state of the badge is based on your alert definitions. Click the badge to see the Summary
tab for objects or groups configured in the widget. From the Summary tab, you can begin
determining what caused the current state. If the widget is configured for an object that has
descendants, you should also check the state of descendants. Child objects might have alerts
that do not impact the parent.
If the Badge Mode configuration option is set to Off, the badge and a chart appears. The type of
chart depends on the object that the widget is configured to monitor.
n A population criticality chart displays the percentage of group members with critical,
immediate, and warning efficiency alerts generated over time, if the monitored object is a
group.
n A trend line displays the efficiency status of the monitored object over time if the object does
not provide its resources to any other object, or where no other object depends on the
monitored object's resources. For example, if the monitored object is a virtual machine or a
distributed switch.
VMware, Inc. 516

n A pie chart displays the reclaimable, stress, and optimal percentages for the virtual machines
that are descendants of the monitored object for all other object types. You use the chart to
identify objects in your environment from which you can reclaim resources. For example, if
the object is a host or datastore.
If the Badge Mode is set to On, only the badge appears.
Edit an efficiency widget after you add it to a dashboard. The changes you make to the options
create a custom widget that provides information about an individual object, a custom group of
objects, or all the objects in your environment.
Where You Find the Efficiency Widget
upper panel.
Efficiency Widget Display Options
The Efficiency widget displays an efficiency badge. The widget also displays an efficiency trend
when not in badge mode.
Option Description
Efficiency Badge Status of the objects configured for this instance of the widget.
Click the badge to open the Alerts tab for the object that
provides data to the widget.
Efficiency Trend Displays a chart, depending on the selected or configured

object. The charts vary, depending on whether the monitored
object is a group, a descendent object, or an object that
provides resources to other objects. The chart appears only if
the Badge Mode configuration option is off. If the Badge Mode is
on, only the badge appears.
Efficiency Widget Configuration Options

VMware, Inc. 517

Option Description
Configuration

this widget.
widget.
the widget.
options.
Badge Mode Determines whether the widget displays only the badge, or
the badge and a weather map or trend chart.
Select one of the following options:
n On. Only the badge appears in the widget.
n Off. The badge and a chart appear in the widget. The
chart provides additional information about the state of
the object.
Input Data

Environment Widget
The Environment widget displays the resources for which vRealize Operations Manager collects
data. You can create one or more lists in vRealize Operations Manager for the resources that you
add to your custom dashboards.
How the Environment Widget and Configuration Options Work
The Environment widget lists the number of resources by object or groups them by object type.
You can add the Environment widget to one or more custom dashboards and configure it to
based on the configured options for each widget instance.
You edit an Environment widget after you add it to a dashboard. The changes you make to the
options help create a custom widget to meet the needs of the dashboard users.
VMware, Inc. 518

Where You Find the Environment Widget

upper panel.
Environment Widget Configuration Options
Option Description
Configuration

this widget.
VMware, Inc. 519

Option Description
widget.
the widget.
options.
Input Data

Environment Overview Widget

The Environment Overview widget displays the health, risk, and efficiency of resources for a
given object from the managed inventory.
How the Environment Overview Widget and Configuration Options Work

You can add the Environment Overview widget to one or more custom dashboards.
The widget displays data for objects from one or several types. The data that the widget displays
depends on the object type and category that you selected when you configured the widget.
The objects in the widget are ordered by object type.
The parameters for the health, risk, and efficiency of an object appear in a tool tip when you
point to the object.
VMware, Inc. 520

When you double-click an object on the Environment Overview widget, you can view detailed
information for the object.
To use the Environment Overview widget, you must add it to the dashboard and configure the
data that appears in the widget. You must select at least one badge and an object. Additionally,
you can select an object type.
The Environment Overview widget has basic and advanced configuration options. The basic
configuration options are enabled by default.
To use all features of the Environment Overview widget, you must change the default
configuration of the widget. Log in to the vRealize Operations Manager machine and set
skittlesCustomMetricAllowed to true in the web.properties file. The web.properties file is
located in the /usr/lib/vmware-vcops/user/conf/web folder. The change is propagated after
you use the service vmware-vcops-web restart command to restart the UI.
You must use the Badge tab to select the badge parameters that the widget shows for each
object. You must use the Config tab to select an object or object type. To observe a concrete
object from the inventory, you can use the Basic option. To observe a group of objects or
objects from different types, you must use the Advanced option.
Where You Find the Environment Overview Widget
upper panel.
Environment Overview Widget Toolbar Options
The toolbar contains icons that you can use to get more information about badges.
Option Description
Badge You can select a Health, Risk, or Efficiency badge for objects
that appear in the widget. The tool tip of a badge shows the
standard name of the badge.
Status You can filter objects based on their badge status and their
state.
Sort You can sort objects by letter or by number.
Environment Overview Widget Configuration Options

VMware, Inc. 521

Option Description
Selected Object Object that is the basis for the widget data.
To populate the text box, select Config > Basic and select
an object from the list.

this widget.
widget.
the widget.
options.
Badge Defines a parameter to observe. You can select or deselect

Health, Risk, and Efficiency parameters using check boxes.
Default configuration of the widget selects all badges.
Select at least one badge parameter.
VMware, Inc. 522

Option Description
Config Basic
List of objects in your environment that you can search or
sort by column so that you can locate the object on which
you are basing the data that appears in the widget.
Advanced
You can use Object Types to select a type of the objects to
observe information about health, risk, and efficiency.
Double-click the object type to select it.
Use the Adapter Type drop-down menu to filter the
objects types based on an adapter.
You can use the Use vSphere Default button to observe
the main vSphere object types.
To remove an object type from the list, click Remove
Selected next to Use vSphere Default.
You can use the Object Type Categories menu to select a
group or groups of object types to observe.
You can use the Object tree to select an object to filter the
displayed objects. For example, to observe a datastore of a
VM, double-click Datastore from the Object Types menu to
select it. Click the datastore when it is in the list of object
types, and find the VM in the object tree and select it. To
return to your previous configuration of the widget, click
Datastore from the list of object types and click Deselect
All in the object tree window.
The metrics tree and badge data grids are available
configuration options only if the default configuration of
the widget is changed. To use these configuration options,
log in to the vRealize Operations Manager machine and set
skittlesCustomMetricAllowed to true in the
web.properties file. The web.properties file is located in
the /usr/lib/vmware-vcops/user/conf/web folder.
Environment Status Widget

The Environment Status widget displays the statistics for the overall monitored environment.
VMware, Inc. 523

How the Environment Status Widget and Configuration Options Work

You customize the output of the widget by choosing a category such as Objects, Metrics,
Applications, Alerts, Analytics, and Users. You can filter the data by using the tags tree from
Select which tags to filter in the configuration window.
You edit an environment status widget after you add it to a dashboard. To configure the widget,
click the pencil at the right corner of the widget window. You must select at least one type of
information from OBJECTS, METRICS, APPLICATIONS, ALERTS, ANALYTICS, USERS categories
for the widget to display. By default, the widget displays statistics information about all objects in
the inventory. You can use the Select which tags to filter option to filter the information. The
widget can interact with other widgets in the dashboard, taking data from them and displaying
statistics . For example, you can have a Object List widget , which is the source of the data and
an Environment Status widget, which is the destination. If you select objects and perform a
multiselection interaction from the Object List widget, the Environment Status widget results are
updated based on the selections you made in the Object List.
Where You Find the Environment Status Widget
upper panel.
Environment Status Widget Configuration Options
The Output Data section provides options to select object types on which you are basing the
widget data.
criteria.
VMware, Inc. 524

Option Description
Configuration

this widget.
The widget is also updated when it is in interaction mode.
For example, when an item is selected in the provider
widget, the content of the Environment Status widgets is
refreshed.
widget.
the widget.
options.
Input Data
objects.
list.

objects in your environment. The following sections
provide options to refine the objects for the widget data.
VMware, Inc. 525

Option Description
Relationship Transform the input for the widget based on the

relationship of the objects. For example, if you select the
Children check box and a Depth of 1, the child objects are
the transformed inputs for the widget.
Output Data
Objects The widget shows summarized information about the

objects in your environment. You can filter the information
that appears in self provider mode when you select an
object from Select which tag to filter. You can select what
type of information to include in the summary of resources.
For example, if you select Adapter Types > Container from
Select which tag to filter and click Objects and Objects
Collecting , the widget displays the number of containers
and collecting containers.
Metrics The widget shows summarized information about available

metrics. You can filter the information that appears in self
provider mode when you select an object from Select
which tag to filter. You can select what type of information
to include in the summary of metrics.
Applications The widget shows summarized information about available

applications. You can filter the information that appears in
self provider mode when you select an object from Select
which tag to filter. You can select what type of information
to include in the summary of applications.
Alerts The widget shows summarized information about alerts in

your environment. You can filter the information that
appears in self provider mode when you select an object
from Select which tag to filter. You can select what type of
information to include in the summary of alerts.
Analytics The widget shows summarized information about the

analytics plug-ins. You can filter the information that
appears in self provider mode when you select an object
from Select which tag to filter. You can select what type of
information to include in the summary of analytics.
Users The widget shows the number of users defined in vRealize

Operations Manager. Select Administration > Access
Control > User Accounts.
Output Filter
VMware, Inc. 526

Option Description
Advanced Refine the widget data further based on the filter criteria
for object types. The widget data is based on the objects
for the filtered object types.
the objects with tag filter applied. If the objects with tag
filter applied do not belong to any of the object types in
this filter criteria, the widget skips this filter and includes all
the objects with tag filter applied.
objects.
2 In the second drop-down menu, select the option
based on which you want to define the filter criteria.
For example, if you select Metrics for the Datacenter
object type, you can define a filter criteria based on the
value of a specific metric for data centers.
criteria set.
Faults Widget
The Faults widget displays detailed information about faults experienced by an object
The Faults widget configuration options are used to customize each instance of the widget that
you add to your dashboards.
Where You Find the Faults Widget
upper panel.
VMware, Inc. 527

Faults Widget Configuration Options

Option Description
Configuration

this widget.
widget.
the widget.
options.
Input Data

Forensics Widget
The Forensics widget shows how often a metric has a particular value as a percentage of all
values, within a given time period. It can also compare percentages for two time periods.
How the Forensics Widget and Configuration Options Work
You can add the Forensics widget to one or more custom dashboards and configure it to display
on the configured options for each widget instance.
You edit the Forensics widget after you add it to a dashboard. The changes you make to the
options create a custom widget to meet the needs of the dashboard users.
VMware, Inc. 528

Where you Find the Forensics Widget

upper panel.
Forensics Widget Configuration Options
Option Description
Configuration

this widget.
widget.
the widget.
options.
Percentile Indicates how much data is above or below the specific

value. For example, it indicates that 90% of the data is
more than 4 when a vertical line occurs on the value 4.
VMware, Inc. 529

Option Description
Input Data
Select metrics on which you want to base the widget data.

You can select an object and pick its metrics.
1 Click the Add New Metrics icon to add metrics for the
widget data. Select an object to view its metric tree and
pick metrics for the object. The picked metrics appear
in a list in this section.
The metric tree shows common metrics for several

objects when you click the Show common metrics icon.
While selecting objects for which you want to pick

metrics, you can use the Filter text box to search for
objects. You can also expand the Tag Filter pane on
the left hand side to select one or more object tag
values. A list of objects with the selected tag values
appears. If you select more than one value for the same
tags applied.
2 Optionally, select metrics from the list and click the
Remove Selected Metrics icon to remove the selected
metrics.
Click the Select All icon to select all the metrics in the
list.

metrics in the list.
Geo Widget
If your configuration assigns values to the Geo Location object tag, the geo widget shows where
your objects are located on a world map. The geo widget is similar to the Geographical tab on
the Inventory page.
How the Geo Widget and Configuration Options Work
You can move the map and zoom in or out by using the controls on the map. The icons at each
location show the health of each object that has the Geo Location tag value. You can add the
geo widget to one or more custom dashboards and configure it to display data that is important
to different dashboard users. The data that appears in the widget is based on the configured
options for each widget instance.
You edit a Geo widget after you add it to a dashboard. The changes you make to the options
help create a custom widget to meet the needs of the dashboard users.
Where You Find the Geo Widget
VMware, Inc. 530

upper panel.
Geo Widget Toolbar Options
Option Description
Zoom in Zooms in on the map.
Zoom out Zooms out on the map.
Geo Widget Configuration Options

criteria.
Option Description
Configuration

this widget.
widget.
the widget.
options.
Output Filter
VMware, Inc. 531

Option Description
criteria set.
Heatmap Widget
The Heatmap widget contains graphical indicators that display the current value of two selected
attributes of objects of tag values that you select. In most cases, you can select only from
internally generated attributes that describe the general operation of the objects, such as health
or the active anomaly count. When you select a single object, you can select any metric for that
object.
How the Heatmap Widget and Configuration Options Work
You can add the Heatmap widget to one or more custom dashboards and configure it to display
data that is important to the dashboard users.
The Heatmap widget has a General mode and an Instance mode. The General mode shows a
colored rectangle for each selected resource. In the Instance mode, each rectangle represents a
single instance of the selected metric for an object.
You can click a color or the size metric box in the bottom of the Heatmap widget to filter the
display of cells in the widget. You can click and drag the color filter to select a range of colors.
The Heatmap widget displays cells that match the range of colors.
When you point to a rectangle for an object, the widget shows the resource name, group-by
values, and the current values of the two tracked attributes.
VMware, Inc. 532

You edit a Heatmap widget after you add it to a dashboard. The changes you make to the
options create a custom widget that provides information about an individual object, a custom
group of objects, or all the objects in your environment.
Where You Find the Heatmap Widget

upper panel.
Heatmap Widget Toolbar Options
Option Description
Dashboard Navigation Actions you can run on the selected alert.

For example, you use the option to open a vCenter Server,
data center, virtual machine, or in the vSphere Web Client,
allowing you to directly modify an object for which an alert
was generated and fix any problems.
Group Zoom You can roll-up non-significant resources with similar

characteristics into groups to obtain only the relevant data
among the thousands of resources in the system. The roll-
up method improves performance and decreases the
memory usage. The roll-up box encompasses the average
color and the sum of the sizes of all the resources. You can
view all the resources by zooming in the roll-up box.
Show/Hide Text Show or hide the cell name on the heatmap rectangle.
VMware, Inc. 533

Option Description
Show Details If you configure the Heatmap widget as a provider to

another widget, such as the Metric Chart widget , you can
double-click a rectangle to select that object for the widget.
If the widget is in Metric mode, double-clicking a rectangle
selects the resource associated with the metric and
provides that resource to the receiving widget. Optionally,
you can select a cell from the heatmap and click the Show
Details icon to see details about the cell.
Reset Zoom Resets the heatmap display to fit in the available space.
Heatmap Configuration Drop-down Select from a list of predefined heatmaps.
Heatmap Widget Configuration Options

widget data.
criteria.
Option Description
Configuration

this widget.
VMware, Inc. 534

Option Description
widget.
the widget.
options.
Input Data
objects.
list.


Output Data
Configurations List of saved heatmap configuration options. You can

create new configuration and save it in the list. From the
options on the right, you can also delete, clone, and
reorder the configurations.
Name Name of the widget.
Group by First-level grouping of the objects in the heatmap.
Then by Second-level grouping of the objects in the heatmap.
VMware, Inc. 535

Option Description
Relational Grouping After you select the Group by and Then by objects, select
the Relational Grouping check box to reorganize the
grouping of the objects, and to relate the objects selected
in the Group by text box with the objects selected in the
Then by text box.
Mode
General mode
The widget shows a colored rectangle for each selected

resource. The size of the rectangle indicates the value
of one selected attribute. The color of the rectangle
indicates the value of another selected attribute.
Instance mode
Each rectangle represents a single instance of the

selected metric for a resource. A resource can have
multiple instances of the same metric. The rectangles
are all the same size. The color of the rectangles varies
based on the instance value. You can use instance
mode only if you select a single resource kind.
Object Type Object that is the basis for the widget data.
Size by An attribute to set the size of the rectangle for each

resource.
Resources that have higher values for the Size By attribute
have larger areas of the widget display. You can also select
fixed-size rectangles. In most cases, the attribute lists
include only metrics that vRealize Operations Manager
generates. If you select a resource kind, the list shows all of
the attributes that are defined for the resource kind.
Color by An attribute to set the color of the rectangle for each

resource.
Solid Coloring Select this option to use solid colors instead of a color
gradient. By default, the widget assigns red color for high
value, brown color for intermediate value and green color
for low value. Click the color box to set a different color for
the values. You can add up to seven color thresholds by
clicking on color range
VMware, Inc. 536

Option Description
Color Shows the color range for high, intermediate and low
values. You can set each color and type minimum and
maximum color values in the Min Value and Max Value text
boxes. By default, green indicates a low value and red
indicates the high end of the value range. You can change
the high and low values to any color and set the color to
use for the midpoint of the range. You can also set the
values to use for either end of the color range, or let
vRealize Operations Manager define the colors based on
the range of values for the attribute.
If you leave the text boxes blank, vRealize Operations
Manager maps the highest and lowest values for the Color
By metric to the end colors. If you set a minimum or
maximum value, any metric at or beyond that value
appears in the end color.
Output Filter
objects.
criteria set.
VMware, Inc. 537

Health Widget
The Health widget is the status of the health-related alerts for the objects it is configured to
monitor in vRealize Operations Manager. Health alerts usually require immediate attention. You
can create one or more health widgets for different objects that you add to your custom
dashboards.
How the Health Widget and Configuration Options Work
You can add the Health widget to one or more custom dashboards and configure it to display
data that is important to the dashboard users. The information that it displays depends on how
the widget is configured.
If the Badge Mode configuration option is set to Off, the badge and a chart appears. The type of
chart depends on the object that the widget is configured to monitor.
n A trend line displays the health status of the monitored object if the object does not provide
its resources to any other object. For example, if the monitored object is a virtual machine or
a distributed switch.
n A weather map displays the health of the ancestor and descendant objects of the monitored
object for all other object types. For example, if the monitored object is a host that provides
CPU and memory to a virtual machine.
You edit a Health widget after you add it to a dashboard. The changes you make to the options
Where You Find the Health Widget
VMware, Inc. 538

upper panel.
Heath Widget Display Options
The Health widget displays a health badge. The widget also displays a health trend when not in
badge mode.
Option Description
Health Badge Status of the objects configured for this instance of the widget.
If the Badge Mode option is off, a health weather map or trend
chart appears for the object. Whether the map or chart appears
depends on the object type. The health weather map displays
tool tips for up to1000 objects.
Health Trend Displays a chart, depending on the selected or configured

object. The charts vary, depending on whether the monitored
object is a group, a descendent object, or an object that
provides resources to other objects. The chart appears only if
the Badge Mode configuration option is off. If the Badge Mode is
on, only the badge appears.
Heath Widget Configuration Options

Option Description
Configuration

this widget.
VMware, Inc. 539

Option Description
widget.
the widget.
options.
the object.
Input Data

Health Chart Widget

The Health Chart widget displays Health, Risk, Efficiency, or custom metric charts for selected
objects. You use the widget to compare the status of similar objects based on the same value.
How the Health Chart Widget and Configuration Options Work
You can add the Health Chart widget to one or more custom dashboards and configure it to
display data that is important to the dashboard users. The information that it displays depends
on how the widget is configured.
If the widget is configured to display Health, Risk, or Efficiency, the chart values are based on the
generated alerts for the selected alert type for the selected objects.
VMware, Inc. 540

If the widget is configured to display custom metrics, chart values are based on the metric value
for the configured time period.
You edit the Health Chart widget after you add it to the dashboard. The changes you make to
the options create a custom widget with the selected charts.
The charts are based either on Health, Risk, or Efficiency alert status, or you can base them on a
selected metric. You can include a single object, multiple objects, or all objects of a selected type.
To view the value of the object at a particular time, hover your mouse over the chart. A date
range and metric value tool tip appear.
Where You Find the Health Chart Widget
upper panel.
Health Chart Widget Toolbar Options
Option Description
Date Controls Use the date selector to limit the data that appears in each
chart to the time period you are examining.
Select Dashboard Time to enable the dashboard time panel.
The option chosen in the dashboard time panel is effective.
The default time is 6 hours.
Dashboard Time is the default option.
Health Chart Widget Graph Selector Options

The graph selector options determine how individual data appears in the graph.
Option Description
Close Deletes the chart.
Save a snapshot Creates a PNG file of the current chart. The image is the size that appears on you
screen.
You can retrieve the file in your browser's download folder.
Save a full screen snapshot Downloads the current graph image as a full-page PNG file, which you can display
or save.
VMware, Inc. 541

Option Description
Download comma-separated data Creates a CSV file that includes the data in the current chart.
Units Select the units in which the widget displays data. This option is visible when you
select a custom source of data in the widget configuration.
Health Chart Configuration Options

criteria.
Option Description
Configuration

this widget.
widget.
the widget.
options.
Order By Determines how the object charts appear in the widget.

You can order them based on value or name, and in
ascending or descending order.
Chart Height Controls the height of all charts. Choose from three
possible choices - Small, Medium, Large. Default is Medium.
Pagination number Number of charts that appears on a page.

If you prefer scrolling through the charts, select a higher
number. If you prefer to page through the results, select a
lower number.
VMware, Inc. 542

Option Description
Auto Select First Row Determines whether to start with the first row of data.
Metric Determines the source of the data.

n Health, Risk, or Efficiency. The displayed charts are
based on one of these alert badges.
n Custom. The displayed charts are based on the
selected metric and use either alert symptom state
colors or the selected custom color. You can select a
unit for the custom metric from the drop-down menu or
choose to allow the widget to automatically pic a unit.
If you apply custom colors, type the value in each box

that is the highest or lowest value that should be that
color. You can select a unit for the metric.
Metric Unit Select a unit for the custom metric.
Show Select one or more of the following items to display in the

widget:
n Select Object Name to display the name of the object
in the widget.
n Select Metric Name to display the name of the metric in
the widget.
Input Data
objects.
list.

VMware, Inc. 543

Option Description

Output Filter
objects.
criteria set.
Mashup Chart Widget

The Mashup Chart widget shows disparate pieces of information for a resource. It shows a health
chart and metric graphs for key performance indicators (KPIs).
How the Mashup Chart Widget and Configuration Options Work
The Mashup Chart widget contains charts that show different aspects of the behavior of a
selected resource. By default, the charts show data for the past six hours.
VMware, Inc. 544

The Mashup Chart widget contains the following charts.
n A Health chart for the object, which can include each alert for the specified time period. Click
an alert to see more information, or double-click an alert to open the Alert Summary page.
n Metric graphs for any or all of the KPIs for any objects listed as a root cause object. For an
application, this chart shows the application and any tiers that contain root causes. You can
select the KPI to include by selecting Chart Controls > KPIs on the widget toolbar. Any
shared area on a graph indicates that the KPI violated its threshold during that time period.
The metric graphs reflect up to five levels of resources, including the selected object and four
child levels.
You edit a Mashup Chart widget after you add it to a dashboard. The changes you make to the
options create a custom widget to meet the needs of the dashboard users.
Where You Find the Mashup Chart Widget
upper panel.
Mashup Chart Widget Toolbar Options
The toolbar contains icons that you can use to change the view.
VMware, Inc. 545

Option Description
Filters Filter data based on criticality, status, and alert type.
Event Filters Filter based on the type of event such as, change,
notification, and fault.
Date Controls Use the date selector to limit the data that appears in each
chart to the time period you are examining.
Select Dashboard Time to enable the dashboard time
panel. The option chosen in the dashboard time panel is
effective. The default time is 6 hours.
Dashboard Navigation You can navigate to another dashboard when the object
under consideration is also available in the dashboard to
which you navigate.
Mashup Chart Widget Configuration Options

Option Description
Configuration

this widget.
widget.
the widget.
options.
VMware, Inc. 546

Option Description
Input Data

Metric Chart Widget

You can use the Metric Chart widget to monitor the workload of your objects over time. The
widget displays data based on the metrics that you select.
How the Metric Chart Widget and Configuration Options Work

You can add the Metric Chart widget to one or more custom dashboards and configure it to
display the workload for your objects. The data that appears in the widget is based on the
configured menu items for each widget instance.
You edit the Metric Chart widget after you add it to a dashboard. The changes you make to the
menu items create a custom widget with the selected metrics that display the workload on your
objects.
To select metrics, you can select an object from the object list, then select the metrics. Or, you
can select a tag from the object tag list to limit the object list, then select an object. You can
configure multiple charts for the same object or multiple charts for different objects.
To use the metric configuration, which displays a set of metrics that you defined in an XML file,
the dashboard and widget configuration must meet the following criteria:
n The dashboard Widget Interaction menu items are configured so that another widget
provides objects to the target widget. For example, an Object List widget provides the object
interaction to a chart widget.
n The widget Self Provider options are set to Off.
VMware, Inc. 547

n The custom XML file in the Metric Configuration drop-down menu is in the /usr/lib/vmware-
vcops/tools/opscli directory and has been imported into the global storage using the
import command.
Where You Find the Metric Chart Widget
The Metric Chart widget is also displayed on the Workload Utilization dashboard with the name
Workload Trend.
upper panel.
Metric Chart Widget Toolbar Options
The toolbar contains icons that you can use to change the view of the graphs.
Option Description
Split Charts Displays each metric in a separate chart.
Stacked Chart Consolidates all charts into one chart. This chart is useful for seeing how the total or
sum of the metric values vary over time. To view the stacked chart, ensure that the
split chart option is turned off.
Dynamic Thresholds Shows or hides the calculated dynamic threshold values for a 24-hour period.
Show Entire Period Dynamic Shows or hides dynamic thresholds for the entire time period of the graph.
Thresholds
Static Thresholds Shows or hides the threshold values that have been set for a single metric.
Anomalies Shows or hides anomalies. Time periods when the metric violates a threshold are
shaded. Anomalies are generated when a metric crosses a dynamic or static
threshold, either above or below.
Trend Line Shows or hides the line and data points that represents the metric trend. The trend
line filters out metric noise along the timeline by plotting each data point relative to
the average of its adjoining data points.
Show Data Values Enables the data point tooltips if you switched to a zoom or pan option. Show Data
Point Tips must be enabled.
Zoom All Charts Resizes all the charts that are open in the chart pane based on the area captured
when you use the range selector.
You can switch between this option and Zoom the View.
Zoom the View Resizes the current chart when you use the range selector.
Pan When you are in zoom mode, allows you to drag the enlarged section of the chart
so that you can view higher or lower, earlier or later values for the metric.
Zoom to Fit Resets the chart to fit in the available space.
VMware, Inc. 548

Option Description
Remove All Removes all the charts from the chart pane, allowing to you begin constructing a
new set of charts.
Refresh Charts Reloads the charts with current data.
Date Controls Opens the date selector.

Use the date selector to limit the data that appears in each chart to the time period
you are examining.
Select Dashboard Time to enable the dashboard time panel. The option chosen in
the dashboard time panel is effective. The default time is 6 hours.
Generate Dashboard Saves the current charts as a dashboard.
Metric Chart Widget Graph Selector Options

The graph selector options determine how individual data appears in the graph.
Option Description
Save a snapshot Creates a PNG file of the current chart. The image is the size that appears on you
screen.
Download comma-separated data Creates a CSV file that includes the data in the current chart.
Save a full screen snapshot Downloads the current graph image as a full-page PNG file, which you can display
or save.
Units You can display the data with dots or as a percentage.
Thresholds You can choose to show/hide Critical, Immediate, and Warning thresholds in the
current chart.
Scales You can choose a scale for a stacked chart.

n Select Linear to view a chart in which the Y axis scale increases in a linear
manner. For example, the Y axis can have ranges from 0 to 100, 100 to 200,
200 to 300, and so on.
n Select Logarithmic to view a chart in which the Y axis scale increases in a
logarithmic manner. For example, the Y axis can have ranges from 10 to 20, 20
to 300, 300 to 4000, and so on. This scale gives a better visibility of minimum
and maximum values in the chart when you have a large range of metric values.
Note If you select a logarithmic scale, the chart does not display data points
for metric values less than or equal to 0, which leads to gaps in the graph.
n Select Combined to view overlapping graphs for the metrics. The chart uses
individual scales for each graph instead of using a relative scale, and displays a
combined view of the graphs.
n Select Combined by Unit to view a chart that groups the graphs for similar
metric units together. The chart uses a common scale for the combined graphs.
VMware, Inc. 549

Option Description
Move Down Moves the chart down one position.
Move Up Moves the chart up one position.
You can take the following actions on the Metric Chart graph.
Option Description
Y Axis Shows or hides the Y-axis scale.
Chart Shows or hides the line that connects the data points on the chart.
Data Point Tips Shows or hides the data point tooltips when you hover the mouse over a data point
in the chart.
Zoom by X Enlarges the selected area on the X axis when you use the range selector in the
chart to select a subset of the chart. You can use Zoom by X and Zoom by Y
simultaneously.
Zoom by Y Enlarges the selected area on the Y axis when you use the range selector in the
chart to select a subset of the chart. You can use Zoom by X and Zoom by Y
simultaneously.
Zoom by Dynamic Thresholds Resizes the Y axis of the chart so that the highest and the lowest values on the axis
are the highest and the lowest values of the dynamic threshold calculated for this
metric.
Vertical resize Resizes the height of a graph in the chart.
Remove icon next to each metric Removes the graph for the metric from the chart.
name in a stacked chart
Metric Chart Configuration Options

widget data.
criteria.
VMware, Inc. 550

Option Description
Title Enter a custom title that identifies this widget from other instances that are based on the same widget
template.
Configuration
n Off. You configure other widgets to provide the objects to the widget using the dashboard widget
Input Data
Metrics Select metrics on which you want to base the widget data. You can select an object and pick its
metrics.
1 Click the Add New Metrics icon to add metrics for the widget data. Select an object to view its
metric tree and pick metrics for the object. The picked metrics appear in a list in this section.
The metric tree shows common metrics for several objects when you click the Show common
metrics icon.
While selecting objects for which you want to pick metrics, you can use the Filter text box to
search for objects. You can also expand the Tag Filter pane on the left hand side to select one or
more object tag values. A list of objects with the selected tag values appears. If you select more
than one value for the same tag, you can choose objects that have any of the tags applied. If you
select more than one value for different tags, you can choose only the objects that have all the
tags applied.
2 Optionally, select metrics from the list and click the Remove Selected Metrics icon to remove the
selected metrics.
Click the Select All icon to select all the metrics in the list.
Click the Clear Selection icon to clear your selection of metrics in the list.
Optionally, you can customize a metric and apply the customization to other metrics in the list.
1 Double-click a metric box in the list to customize the metric and click Update.
You can use the Box Label text box to customize the label of a metric box.
You can use the Unit text box to define a measurement unit of each metric.
You can use the Color Method option to define a coloring criteria for each metric. If this option is
set to Custom, you can enter color values in the Yellow, Orange, and Red text boxes. You can
also set coloring by symptom definition. If you do not want to use color, select None.
For example, to view the remaining memory capacity of a VM, select Virtual Machine as an object
type, expand the Memory from the metric tree and double-click Capacity Remaining(%). Define a
meaningful label name and measurement unit to help you when you observe the metrics. You can
select Custom from the Color Method drop-down menu and specify different values for each
color, for example 50 for Yellow, 20 for Orange, and 10 for Red.
2 Select a metric and click the Apply to All icon to apply the customization for the selected metric to
all the metrics in the list.
VMware, Inc. 551

Option Description
1 Click the Add New Objects icon and select objects in the pop-up window. The selected objects
appear in a list in this section.
While selecting objects, you can use the Filter text box to search for objects. You can also expand
the Tag Filter pane on the left hand side to select one or more object tag values. A list of objects
with the selected tag values appears.. If you select more than one value for the same tag, you can
choose objects that have any of the tags applied. If you select more than one value for different
tags, you can choose only the objects that have all the tags applied.
2 Optionally, select objects from the list and click the Remove Selected Objects icon to remove the
selected objects.
Click the Select All icon to select all the objects in the list.
Click the Clear Selection icon to clear your selection of objects in the list.
All If you select this option, the widget data is based on all the objects in your environment. The following
sections provide options to refine the objects for the widget data.
Relationship Transform the input for the widget based on the relationship of the objects. For example, if you select
the Children check box and a Depth of 1, the child objects are the transformed inputs for the widget.
Output Data
Empty drop- Specifies a list with attributes to display.

down menu To add a resource interaction XML file through the CLI directory, see Add a Resource Interaction XML
File. To add a resource interaction XML file through the UI, see Manage Metric Configuration.
The newly created XML file appears in this drop-down menu.
VMware, Inc. 552

Option Description
Select metrics on which you want to base the widget data. You can select an object and pick its
metrics.
1 Click the Add New Metrics icon to add metrics for the widget data. Select an object to view its
metric tree and pick metrics for the object. The picked metrics appear in a list in this section.
The metric tree shows common metrics for several objects when you click the Show common
metrics icon.
While selecting objects for which you want to pick metrics, you can use the Filter text box to
search for objects. You can also expand the Tag Filter pane on the left hand side to select one or
more object tag values. A list of objects with the selected tag values appears. If you select more
than one value for the same tag, you can choose objects that have any of the tags applied. If you
select more than one value for different tags, you can choose only the objects that have all the
tags applied.
2 Optionally, select metrics from the list and click the Remove Selected Metrics icon to remove the
selected metrics.
Click the Clear Selection icon to clear your selection of metrics in the list.
Optionally, you can customize a metric and apply the customization to other metrics in the list.
1 Double-click a metric box in the list to customize the metric and click Update.
You can use the Box Label text box to customize the label of a metric box.
You can use the Unit text box to define a measurement unit of each metric.
You can use the Color Method option to define a coloring criteria for each metric. If this option is
set to Custom, you can enter color values in the Yellow, Orange, and Red text boxes. You can
also set coloring by symptom definition. If you do not want to use color, select None.
For example, to view the remaining memory capacity of a VM, select Virtual Machine as an object
type, expand the Memory from the metric tree and double-click Capacity Remaining(%). Define a
meaningful label name and measurement unit to help you when you observe the metrics. You can
select Custom from the Color Method drop-down menu and specify different values for each
color, for example 50 for Yellow, 20 for Orange, and 10 for Red.
2 Select a metric and click the Apply to All icon to apply the customization for the selected metric to
all the metrics in the list.
Output Filter
Refine the widget data further based on the filter criteria for object types. The widget data is based on
the objects for the filtered object types.
If the objects have an input transformation applied, you define filter criteria for the object types of the
transformed objects.
2 In the second drop-down menu, select the option based on which you want to define the filter
criteria. For example, if you select Metrics for the Datacenter object type, you can define a filter
criteria based on the value of a specific metric for data centers.
3 In the drop-down menus and text boxes that appear, select or enter values to filter the objects.
5 To add another filter criteria set, click Add another criteria set.
Metric Picker Widget

The Metric Picker widget displays a list of available metrics for a selected object.
VMware, Inc. 553

How the Metric Picker Widget and Configuration Options Work

With the Metric Picker widget, you can check the list of the object's metrics. To select an object
to pick its metrics, you use another widget as a source of data, for example, Topology Graph
widget. To set a source widget that is on the same dashboard, you use the Widget Interactions
menu when you edit a dashboard. To set a source widget that is on another dashboard, use the
Dashboard Navigation menu when you edit a dashboard that contains the source widget.
You edit a Metric Picker widget after you add it to a dashboard. The changes you make to the
options create a custom chart to meet the needs of the dashboard users.
Where You Find the Metric Picker Widget
upper panel.
Metric Picker Widget Toolbar Options
VMware, Inc. 554

Option Description
Show common metrics Filter based on common metrics.
Show collecting metrics Filter based on collecting metrics.
Metrics or Properties Filter based on metrics or property metrics.
Time Range Filter based on selected time range.
Metric Picker Widget Configuration Options

Option Action
Configuration

this widget.
Object List Widget

The Object List widget displays a list of the objects available in the environment.
VMware, Inc. 555

How the Object List Widget and Configuration Options Work

The Object List widget displays a data grid with objects in the inventory. The default
configuration of the data grid appears in Object List Widget Options section. You can customize
it by adding or removing default columns. You can use the Additional Column option to add
metrics when you configure the widget.
You edit an Object List widget after you add it to a dashboard. Configuration of the widget
enables you to observe parent and child objects. You can configure the widget to display the
child objects of an object selected from another widget, for example, another Object List or
Object Relationship widget, in the same dashboard.
Where You Find the Object List Widget
upper panel.
Object List Widget Toolbar Options
Option Description
Action Selects from a set of actions specific for each object type.
To see available actions, select an object from the list of
objects and click the toolbar icon to select an action. For
example, when you select a datastore object in the graph,
you can select Delete Unused Snapshots for Datastore.
Dashboard Navigation Navigates you to the object. For example, when you select
a datastore from the list of objects and click Dashboard
Navigation, you can open the datastore in vSphere Web
Client.
Reset Grid Sort Returns the list of resources to its original order.
Interactions are usually between widgets in the same
dashboard, or you can configure interactions between
widgets on different dashboards.
Object Detail Select an object and click this icon to show the Object Detail
page for the object.
VMware, Inc. 556

Option Description
Display Filtering Criteria Displays the object information on which this widget is
based.
Filter Locate data in the widget.
Object List Widget Data Grid Options

The data grid provides a list of inventory objects on which you can sort and search.
Option Description
ID Unique ID for each object in the inventory, randomly

generated and produced by vRealize Operations Manager.
Name Name of the object in the inventory.
Description Displays the short description of the object given during

creation of the object
Adapter Type Shows the adapter type for each object .
Object Type Displays the type of the object in the inventory.
Policy Displays policies that are applied to the object. To see

policy details and create policy configurations, in the menu
click Administration, and then in the left pane click Policies.
Creation Time Displays the date, time, and time zone of the creation of an
object that was created in the inventory.
Identifier 1 Can contain the custom name of the object in the inventory
or default unique identifier, depending on the type of
inventory object. For example, My_VM_1 for a VM in the
inventory, or 64-bit hexadecimal value for vRealize
Operations Manager Node.
Identifier 2 Can contain the abbreviation of an object type and the

unique decimal number or parent instance, depending on
the type of the object. For example, vm-457 for a VM and
an IP address for vRealize Operations Manager Node .
Identifier 3 Can contain a unique number identifying an adapter type.

For example, 64-bit hexadecimal value for vCenter Adapter
Identifier 4 Additional unique identifiers for the object. This option

varies and depends on the adapter type that the object
uses.
Identifier 5 Additional unique identifiers for the object. This option

varies and depends on the adapter type that the object
uses.
VMware, Inc. 557

Option Description
Object Flag Displays a badge icon for each object. You can see the
status when you point to the badge.
Collection State Displays the collection state of an adapter instance of each

object. You can see the name of the adapter instance and
its state in a tool tip when you point to the state icon. To
manage an adapter instance to start and stop collection of
data, in the menu, click Administration, and then in the left
pane click Inventory.
Collection Status Displays the collection status of the adapter instance of

each object. You can see the name of the adapter instance
and its status in a tool tip when you point to the status icon.
To manage an adapter instance to start and stop collection
of data, in the menu, click Administration, and then in the
left pane click Inventory.
Internal ID Unique number that vRealize Operations Manager uses to

identify the object internally. For example, the internal ID
appears in log files used for troubleshooting.
Object List Widget Configuration Options

criteria.
The Additional Columns section provides options to select metrics that are displayed as
additional columns in the widget.
Option Description
Configuration

this widget.
VMware, Inc. 558

Option Description
widget.
the widget.
options.
Auto Select First Row Determines whether to start with the first row of data.
Input Data
objects.
list.


Output Filter
VMware, Inc. 559

Option Description
objects.
criteria set.
Additional Columns
VMware, Inc. 560

Option Description
Empty drop-down menu Specifies a list with attributes to display.

To add a resource interaction XML file through the CLI
directory, see Add a Resource Interaction XML File. To add
a resource interaction XML file through the UI, see Manage
Metric Configuration.
The newly created XML file appears in this drop-down
menu.
Add metrics based on object types. The selected metrics

are displayed as additional columns in the widget.
1 Click the Add New Metrics icon to add metrics based
on object types. The metrics that you add appear in a
While selecting object types for which you want to pick

metrics, you can filter the object types by adapter type
to pick an object type. On the metrics pane, click the
Select Object icon to select an object for the object
type. Pick metrics of the selected object from the
metric tree.
For example, you can select the Datacenter object

type, click the Select Object icon to display the list of
data centers in your environment, and pick metrics of
the selected data center.
2 Optionally, you can double-click a metric box in the list
to customize the label of the metric and click Update.
Object Relationship Widget

The Object Relationship widget displays the hierarchy tree for the selected object. You can
create one or more hierarchy trees in vRealize Operations Manager for the selected objects that
you add to your custom dashboards.
How the Object Relationship Widget and Configuration Options Work
You can add the Object Relationship widget to one or more custom dashboards and configure it
to display data that is important to different dashboard users. The data that appears in the
widget is based on the configured options for each widget instance.
You edit an Object Relationship widget after you add it to a dashboard. The changes you make
to the options help create a custom widget to meet the needs of the dashboard users.
VMware, Inc. 561

Where You Find the Object Relationship Widget

upper panel.
Object Relationship Widget Toolbar Options
Option Description
Dashboard Navigation You can navigate to another dashboard when the object
under consideration is also available in the dashboard to
which you navigate. To be able to navigate to another
dashboard, configure the relevant option when you create
or edit the dashboard.
Badge Displays the Health, Risk, or Efficiency alerts on the objects

in the relationship map. You can select a badge for objects
that appear in the widget. The tool tip of a badge shows
the object name, object type, and the name of the selected
badge with the value of the badge. You can only select one
badge at a time.
Zoom to fit Resets the chart to fit in the available space.
Pan Click this icon and click and drag the hierarchy to show
different parts of the hierarchy.
Show values on point Shows or hides the data point tooltips when you hover the
mouse over a data point in the chart.
Zoom the view Click this icon and drag to outline a part of the hierarchy.
The display zooms to show only the outlined section.
Display Filtering Criteria Shows the filtering settings for the widget in a pop-up
window.
Zoom in Zooms in on the hierarchy.
Zoom out Zooms out on the hierarchy.
Reset to Initial Object If you change the hierarchy of the initial configuration or
the widget interactions, click this icon to return to the initial
resource. Clicking this icon also resets the initial display
size.
Object Detail Select an object and click this icon to show the Object
Detail page for the object.
Show Alerts Select the resource in the hierarchy and click this icon to
show alerts for the resource. Alerts appear in a pop-up
window. You can double-click an alert to view its Alert
Summary page.
VMware, Inc. 562

Object Relationship Widget Configuration Options

criteria.
Option Description
Configuration

this widget.
widget.
the widget.
options.
Auto Zoom to Fixed Node Size You can configure a fixed zoom level for object icons in the
widget display.
If your widget display contains many objects and you
always need to use manual zooming, this feature is useful
because you can use it to set the zoom level only once.
Node Size You can set the fixed zoom level at which the object icons
display. Enter the size of the icon in pixels.
The widget shows object icons at the pixel size that you
configure.
Input Data
VMware, Inc. 563

Option Description

Output Filter
criteria set.
Object Relationship (Advanced) Widget

The Object Relationship (Advanced) widget displays a graph or tree view that depicts the parent-
child relationship of the selected object. It provides advanced configuration options. You can
create a graph or tree view in vRealize Operations Manager for the selected objects that you add
to your custom dashboards.
How the Object Relationship (Advanced) Widget and Configuration Options Work
You can add the Object Relationship (Advanced) widget to one or more custom dashboards
and configure it to display data that is important to different dashboard users. The data that
appears in the widget is based on the configured options for each widget instance.
VMware, Inc. 564

You edit an Object Relationship (Advanced) widget after you add it to a dashboard. The
changes you make to the options help create a custom widget to meet the needs of the
dashboard users.
You can double-click any object in the graph or tree view and see the specific parent-child
objects for the focus object. When you double-click the object again, you see the original graph
or tree view. If you point your cursor over an object icon, you see the health, risk, and efficiency
details. You can also click the Alerts link for the number of generated alerts. Click the purple icon
to view the child relationships of the object.
Where You Find the Object Relationship (Advanced) Widget
upper panel.
Object Relationship (Advanced) Widget Toolbar Options
Options Description
Dashboard Navigation You can navigate to another dashboard when the object under consideration is also
available in the dashboard to which you navigate. To navigate to another
dashboard, configure the relevant option when you create or edit the dashboard.
Reset to Initial Object If you change the hierarchy of the initial configuration or the widget interactions,
click this icon to return to the initial resource. Clicking this icon also resets the initial
display size.
Display Filtering Criteria Shows the filtering settings for the widget in a pop-up window.
View Tree/View graph Displays a tree or graph view of the relationships.
Vertical/Horizontal Displays a vertical or horizontal view of the graph or tree view.
Hide Text/Show Text Hides or displays the object names.
Standard View/Fit View The Standard View option fixes the view to a specific zoom level
The Fit View option adjusts the graph or tree view to fit the screen.
Group Items/Ungroup Items Groups by objects types. You can view further details by double-clicking on the
object. You can also choose to display the graph or tree view without grouping the
object types.
Path Exploration Displays the relative relationship path between two selected objects on the graph
or tree view. To highlight the path, click the Path Exploration icon and then select
the two objects from the graph or tree view.
VMware, Inc. 565

Options Description
Layers n Parent/Child: Displays a graph or tree view of the parent and child relationship
for the specific object selected.
n Custom: Indicates the relationship between the objects that are part of the
custom relationship. These objects have a connection via the selected custom
relationship.
Quick Filter Enter the name of an object that you want to see in the graph or tree view.
Object Relationship (Advanced) Widget Configuration Options

criteria.
Option Description
Name Enter a custom title that identifies this widget from other
Configuration

this widget.
widget.
the widget.
options.
Parents Depth Select the depth of parent objects to be displayed.
Children Depth Select the depth of child objects to be displayed.
Inventory trees Select an existing predefined traversal spec for the initial
object relationship graph or tree view.
VMware, Inc. 566

Option Description
Input Data

Output Filter
criteria set.
Property List Widget

You can use the Property List widget to view the properties of objects and their values.
How the Property List Widget and Configuration Options Work
To observe the properties of objects in the Property List widget, you can select object property
metrics when you configure the widget itself (Self Provider mode enabled). Alternatively, you can
select objects or object property metrics from another widget (Self Provider mode disabled). You
can also view a default or custom set of properties by selecting a preconfigured XML file in the
Metric Configuration drop-down menu of the widget configuration window.
VMware, Inc. 567

You edit a Property List widget after you add it to a dashboard. You can configure a widget to
receive data from another widget by selecting Off for Self Provider mode. When the widget is
not in Self Provider mode, it displays a set of predefined properties and their values of an object
that you select on the source widget. For example, you can select a host on a Topology widget
and observe its properties in the Property List widget. To configure the Property List as a
receiver widget that is on the same dashboard, use the Widget Interactions menu when you edit
a dashboard. To configure a receiver widget that is on another dashboard, use the Dashboard
Navigation menu when you edit a source dashboard.
Where You Find the Property List Widget
upper panel.
Property List Widget Data Grid Options
Option Description
Object Name Name of the object, whose properties you observe. You can
sort the properties by object name. To open the Object
Details page, click an object name.
Property Name Name of the property. You can sort the properties by
property name.
Value Value of the property. You can sort the properties by value.
Property List Widget Configuration Options

VMware, Inc. 568

widget data.
criteria.
Option Description
Title Enter a custom title that identifies this widget from other instances
that are based on the same widget template.
Configuration
Refresh Content Enable or disable the automatic refreshing of the data in this
widget.
If not enabled, the widget is updated only when the dashboard is
opened or when you click the Refresh button on the widget in the
dashboard.
Refresh Interval If you enable the Refresh Content option, specify how often to
refresh the data in this widget.
Self Provider Indicates whether the objects for which data appears in the widget
are defined in the widget or provided by another widget.
n On. You define the objects for which data appears in the
widget.
n Off. You configure other widgets to provide the objects to the
widget using the dashboard widget interactions options.
Visual Theme Select a predefined visual style for each instance of the widget. The
options are: Original and Compact.
Input Data
VMware, Inc. 569

Option Description
Metrics Select metrics on which you want to base the widget data. You can
select an object and pick its metrics.
1 Click the Add New Metrics icon to add metrics for the widget
data. Select an object to view its metric tree and pick metrics
for the object. The picked metrics appear in a list in this section.
The metric tree shows common metrics for several objects

when you click the Show common metrics icon.
While selecting objects for which you want to pick metrics, you
can use the Filter text box to search for objects. You can also
expand the Tag Filter pane on the left hand side to select one
or more object tag values. A list of objects with the selected tag
values appears. If you select more than one value for the same
tag, you can choose objects that have any of the tags applied. If
you select more than one value for different tags, you can
choose only the objects that have all the tags applied.
2 Optionally, select metrics from the list and click the Remove
Selected Metrics icon to remove the selected metrics.
Click the Clear Selection icon to clear your selection of metrics

in the list.
You can define measurement units for the metrics in the list.
Double-click a metric box in the list, select a measurement unit in
the Unit drop-down menu, and click Update.
1 Click the Add New Objects icon and select objects in the pop-
up window. The selected objects appear in a list in this section.
While selecting objects, you can use the Filter text box to
search for objects. You can also expand the Tag Filter pane on
the left hand side to select one or more object tag values. A list
of objects with the selected tag values appears.. If you select
more than one value for the same tag, you can choose objects
that have any of the tags applied. If you select more than one
value for different tags, you can choose only the objects that
2 Optionally, select objects from the list and click the Remove
Selected Objects icon to remove the selected objects.
Click the Select All icon to select all the objects in the list.
Click the Clear Selection icon to clear your selection of objects

in the list.
All If you select this option, the widget data is based on all the objects
in your environment. The following sections provide options to
refine the objects for the widget data.
Relationship Transform the input for the widget based on the relationship of the
objects. For example, if you select the Children check box and a
Depth of 1, the child objects are the transformed inputs for the
widget.
VMware, Inc. 570

Option Description
Output Data

To add a resource interaction XML file through the CLI directory,
see Add a Resource Interaction XML File. To add a resource
interaction XML file through the UI, see Manage Metric
Configuration.
The newly created XML file appears in this drop-down menu.
1 Click the Add New Metrics icon to add metrics based on object
types. The metrics that you add appear in a list in this section.
While selecting object types for which you want to pick metrics,
you can filter the object types by adapter type to pick an object
type. On the metrics pane, click the Select Object icon to select
an object for the object type. Pick metrics of the selected object
from the metric tree.
For example, you can select the Datacenter object type, click
the Select Object icon to display the list of data centers in your
environment, and pick metrics of the selected data center.
2 Optionally, you can define measurement units for the metrics in
the list. Double-click a metric box in the list, select a
measurement unit in the Unit drop-down menu, and click
Update.
Output Filter
Refine the widget data further based on the filter criteria for object
types. The widget data is based on the objects for the filtered
object types.
If the objects have a tag filter applied in the Basic subsection, you
define filter criteria for the object types of the objects with tag filter
applied. If the objects with tag filter applied do not belong to any of
the object types in this filter criteria, the widget skips this filter and
includes all the objects with tag filter applied.
If the objects have an input transformation applied, you define filter
criteria for the object types of the transformed objects.
2 In the second drop-down menu, select the option based on
which you want to define the filter criteria. For example, if you
select Metrics for the Datacenter object type, you can define a
filter criteria based on the value of a specific metric for data
centers.
3 In the drop-down menus and text boxes that appear, select or
enter values to filter the objects.
5 To add another filter criteria set, click Add another criteria set.
VMware, Inc. 571

Recommended Actions Widget

The Recommended Actions widget displays recommendations to solve problems in your vCenter
Server instances. With recommendations, you can run actions on your data centers, clusters,
hosts, and virtual machines.
How the Recommended Actions Widget and Configuration Options Work
The Recommended Actions widget appears on the Home dashboard, and displays the health
status for the objects in your vCenter Server instance. At a glance, you can see how many
objects are in a critical state, and how many objects need immediate attention.
From the Recommended Actions widget, you can focus in on problems further by, for example,
clicking an object where the alerts triggered, and by clicking an individual alert.
You can edit the Recommended Actions widget on the Home dashboard, or on another
dashboard where you add the widget. With the widget configuration options, you can assign a
new name to the widget, set the refresh content, and set the refresh interval.
The Recommended Actions widget includes a selection bar, a summary pane, a toolbar for the
data grid, and alert information for your objects in a data grid.
Where You Find the Recommended Actions Widget
upper panel.
Recommended Actions Widget Selection Bar and Summary Pane
Option Description
Scope Allows you to select an instance of vCenter Server, and a data center in that instance.
Object tabs Displays the object types with the number of objects affected in parentheses. You can display the
actions for virtual machines, host systems, clusters, vCenter Server instances, and datastores.
VMware, Inc. 572

Option Description
Badge Select the Health, Risk, or Efficiency badge to display alerts on your objects. Health alerts require
immediate attention. Risk alerts require attention in the immediate future. Efficiency alerts require
your input to reclaim wasted space or to improve the performance of your objects. For each badge,
you can view critical, immediate, and warning alerts.
n Health Status. With the Health badge selected, displays the number of affected objects and a
summary of their health based on the alerts that triggered on the object. Lists the objects that
have the worst health, and the number of alerts that triggered on each object.
n Risk Status. With the Risk badge selected, displays the number of affected objects and a
summary of their risk based on the alerts that triggered on the object. Lists the objects that have
the highest, and the number of alerts that triggered on each object.
n Efficiency Status. With the Efficiency badge selected, displays the number of affected objects.
Lists the objects that have the lowest efficiency based on the alerts that triggered on the object,
and the number of alerts that triggered on each object.
Search filter Narrows the scope of the objects that appear. Enter a character or a number to search and display
an object. When a filter is active, the name of the filter appears below the Search filter text box.
Recommended Actions Widget Toolbar Options

The toolbar allows you to address an alert, and to filter the alert list.
Option Description
Cancel Alert Cancels the selected alert.

You cancel alerts when you do not need to address them. Canceling the alert does not cancel the
underlying condition that generated the alert. Canceling alerts is effective if the alert is generated by
triggered fault and event symptoms because these symptoms are triggered again only when
subsequent faults or events occur on the monitored objects. If the alert is generated based on metric
or property symptoms, the alert is canceled only until the next collection and analysis cycle. If the
violating values are still present, the alert is generated again.
Suspend Suspends an alert for a specified number of minutes.

You suspend alerts when you are investigating an alert and do not want the alert to affect the health,
risk, or efficiency of the object while you are working. If the problem persists after the elapsed time,
the alert is reactivated and it will again affect the health, risk, or efficiency of the object.
The user who suspends the alert becomes the assigned owner.
All Filters Narrows the search to one of the available filter types. For example, you can display all alerts that
are related to the Compliance Alert Subtype.
Recommended Actions Widget Data Grid Options

The data grid displays the alerts that triggered on your objects. To resolve the problems
indicated by the alerts, you can link to the alerts and the objects on which the alerts triggered.
For more information, see All Alerts.
Option Description
Criticality Criticality is the level of importance of the alert in your environment. The alert criticality appears in a
tooltip when you hover the mouse over the criticality icon.
The level is based on the level assigned when the alert definition was created, or on the highest
symptom criticality, if the assigned level was Symptom Based.
Actionable When an alert has an associated action, you can run the action on the object to resolve the alert.
VMware, Inc. 573

Option Description
Suggested Fix Describes the recommendation to resolve the problem. For example, for Compliance alerts, the
recommendation instructs you to use the vSphere Hardening Guide to resolve the problem.
guides.html.
You can view other available recommendations and their associated actions, if any, to resolve the
problem when you click the drop-down menu.
Name Name of the object for which the alert was generated, and the object type, which appears in a tooltip
when you hover the mouse over the object name.
Click the object name to view the object details tabs where you can begin to investigate any
additional problems with the object.

Click the alert name to view the alert details tabs where you can begin troubleshooting the alert.
Alert Type Describes the type of alert that triggered on the selected object, and helps you categorize the alerts
so that you can assign certain types of alerts to specific system administrators. For example,
Application, Virtualization/Hypervisor, Hardware, Storage, and Network.
Alert Subtype Describes additional information about the type of alert that triggered on the selected object, and
helps you categorize the alerts to a more detailed level than Alert Type, so that you can assign
certain types of alerts to specific system administrators. For example, Availability, Performance,
Capacity, Compliance, and Configuration.
Time Date and time that the alert triggered.
Alert ID Unique identification for the alert. This column is hidden by default.
Recommended Actions Widget Configuration Options

Option Description
Title Enter a custom title that identifies this widget from other instances that are based on the same
widget template.
Configuration
n Off. You configure other widgets to provide the objects to the widget using the dashboard
widget interactions options.
VMware, Inc. 574

Risk Widget
The risk widget is the status of the risk-related alerts for the objects it is configured to monitor.
Risk alerts in vRealize Operations Manager usually indicate that you should investigate problems
in the near future. You can create one or more risk widgets for objects that you add to your
custom dashboards.
How the Risk Widget and Configuration Options Work
You can add the risk widget to one or more custom dashboard and configure it to display data
that is important to the dashboard users.
If the Badge Mode configuration option is set to Off, the badge and a chart appear. The type of
chart depends on the object type that the widget is configured to monitor.
n A population criticality chart displays the percentage of group members with critical,
immediate, and warning risk alerts generated over time, if the monitored object is a group.
n A trend line displays the risk status of the monitored object for all other object types.
You edit a risk widget after you add it to a dashboard. The changes you make to the options
Where You Find the Risk Widget

upper panel.
Risk Widget Display Options
The Risk Widget displays a risk badge. The widget also displays a risk trend chart when not in
badge mode.
VMware, Inc. 575

Option Description
Risk Badge Status of the objects configured for this instance of the
widget.
Risk Trend Displays a chart, depending on the selected or configured

object. The charts vary, depending on whether the
monitored object is a group, a descendent object, or an
object that provides resources to other objects. The chart
appears only if the Badge Mode configuration option is off.
If the Badge Mode is on, only the badge appears.
Risk Widget Configuration Options

Option Description
Configuration

this widget.
widget.
the widget.
options.
VMware, Inc. 576

Option Description
the object.
Input Data

Rolling View Chart Widget

The Rolling View Chart widget cycles through selected metrics at an interval that you define and
shows one metric graph at a time. Miniature graphs, which you can expand, appear for all
selected metrics at the bottom of the widget.
How the Rolling View Chart Widget and Configuration Options Work
The Rolling View Chart widget shows a full chart for one selected metric at a time. Miniature
graphs for the other selected metrics appear at the bottom of the widget. You can click a
miniature graph to see the full graph for that metric, or set the widget to rotate through all
selected metrics at an interval that you define. The key in the graph indicates the maximum and
minimum points on the line chart.
You edit a Rolling View Chart widget after you add it to a dashboard. The changes you make to
the options create a custom chart to meet the needs of the dashboard users.
Where You Find the Rolling View Chart Widget
VMware, Inc. 577

upper panel.
Rolling View Chart Widget Toolbar Options
Option Description
Trend Line Shows or hides the line and data points that represents the metric trend. The trend
line filters out metric noise along the timeline by plotting each data point relative to
the average of its adjoining data points.
Dynamic Thresholds Shows or hides the calculated dynamic threshold values for a 24-hour period.
Show Entire Period Dynamic Shows or hides dynamic thresholds for the entire time period of the graph.
Thresholds
Anomalies Shows or hides anomalies. Time periods when the metric violates a threshold are
shaded. Anomalies are generated when a metric crosses a dynamic or static
threshold, either above or below.
Zoom to Fit Changes all graphs to show the entire time period and value range.
Zoom the view Click this icon and drag to outline a part of the hierarchy. The display zooms to
show only the outlined section.
Pan Click this icon and click and drag the hierarchy to show different parts of the
hierarchy.
Show Data Values After you click the Show data point tips icon to retrieve the data, click this icon and
point to a graphed data point to show its time and exact value. In non-split mode,
you can hover over a metric in the legend to show the full metric name, the names
of the adapter instances (if any) that provide data for the resource to which the
metric belongs, the current value, and the normal range. If the metric is currently
alarming, the text color in the legend changes to yellow or red, depending on your
color scheme. Click a metric in the legend to highlight the metric in the display.
Clicking the metric again toggles its highlighted state.
Date Controls Use the date selector to limit the data that appears in each chart to the time period
you are examining.
Select Dashboard Time to enable the dashboard time panel. The option chosen in
the dashboard time panel is effective. The default time is 6 hours.
Rolling View Chart Widget Configuration Options

VMware, Inc. 578

widget data.
criteria.
Option Description
Configuration

this widget.
widget.
the widget.
options.
Auto Transition Interval Time interval for a switch between charts in the widget.
Input Data
VMware, Inc. 579

Option Description
Metrics Select metrics on which you want to base the widget data.


tags applied.
metrics.
list.

You can define measurement units for the metrics in the
list. Double-click a metric box in the list, select a
measurement unit in the Unit drop-down menu, and click
Update.
VMware, Inc. 580

Option Description
objects.
list.


Output Data

menu.
VMware, Inc. 581

Option Description
Add metrics based on object types. The objects

corresponding to the selected metrics are the basis for the
widget data.

metric tree.

2 Optionally, you can define measurement units for the
metrics in the list. Double-click a metric box in the list,
select a measurement unit in the Unit drop-down menu,
and click Update.
Output Filter
Refine the widget data further based on the filter criteria

objects.
criteria set.
Scoreboard Widget
The Scoreboard widget shows the current value for each metric of objects that you select.
VMware, Inc. 582

How the Scoreboard Widget and Configuration Options Work

Each metric appears in a separate box. The value of the metric determines the color of the box.
You define the ranges for each color when you edit the widget. You can customize the widget to
use a sparkline chart to show the trend of changes of each metric. If you point to a box, the
widget shows the source object and metric data.
You edit a Scoreboard widget after you add it to a dashboard. The widget can display metrics of
the objects selected during editing of the widget or selected on another widget. When the
Scoreboard widget is not in Self Provider mode, it shows metrics defined in a configuration XML
file that you select in the Metric Configuration. It shows 10 predefined metrics if you do not select
an XML file or if the type of the selected object is not defined in the XML file.
For example, you can configure the Scoreboard widget to use the sample Scoreboard metric
configuration and to receive objects from the Topology Graph widget. When you select a host
on a Topology Graph widget, the Scoreboard widget shows the workload, memory, and CPU
usage of the host.
To set a source widget that is on the same dashboard, you must use the Widget Interactions
menu when you edit a dashboard. To set a source widget that is on another dashboard, you
must use the Dashboard Navigation menu when you edit the source dashboard.
Where You Find the Scoreboard Widget
VMware, Inc. 583

upper panel.
Scoreboard Widget Configuration Options
widget data.
criteria.
Option Description
Configuration

this widget.
widget.
the widget.
options.
When the Scoreboard widget is not in self provider mode,
it shows metrics defined in a configuration XML file that
you select in the Metric Configuration.
VMware, Inc. 584

Option Description
Round Decimals Select the number of decimal places to round the scores
that the widget displays.
Box Columns Select the number of columns that appear in the widget.
Layout Mode Select a Fixed Size or Fixed View layout.
Fixed Size Use these options to customize the size of the box for each
Fixed View object.
Old metric values Select whether you want to show or hide old metric values.
Visual Theme Select a predefined visual style for each instance of the
widget.
Max Scores Count Use these menus to customize the format of the scores
that the widget displays.

widget:
n Select Object Name to display the name of the object
in the widget.
n Select Metric Name to display the name of the metric in
the widget.
n Select Metric Unit to display the metric unit in the
widget.
Select Sparkline to display the Sparkline chart for each
metric. Select a length of time for the statistic information
that the sparkline chart shows from the Period Length
option. Select an option for Show DT to show or hide the
dynamic threshold for the sparkline chart.
Input Data
VMware, Inc. 585

Option Description


tags applied.
metrics.
list.

Optionally, you can customize a metric and apply the
customization to other metrics in the list.
1 Double-click a metric box in the list to customize the
metric and click Update.
You can use the Box Label text box to customize the
label of a metric box.
You can use the Unit text box to define a measurement

unit of each metric.
You can use the Color Method option to define a

coloring criteria for each metric. If this option is set to
Custom, you can enter color values in the Yellow,
Orange, and Red text boxes. You can also set coloring
by symptom definition. If you do not want to use color,
select None.
For example, to view the remaining memory capacity of

a VM, select Virtual Machine as an object type, expand
the Memory from the metric tree and double-click
Capacity Remaining(%). Define a meaningful label
name and measurement unit to help you when you
observe the metrics. You can select Custom from the
Color Method drop-down menu and specify different
values for each color, for example 50 for Yellow, 20 for
Orange, and 10 for Red.
VMware, Inc. 586

Option Description
You can use the Link to option to add links to external

and internal pages. Internal links will open in the same
tab. External links will open in a new tab. Example of
external links are URLs whose hostname does not
match with the current vRealize Operations Manager
instance hostname. Internal links are URLs whose
hostname matches the current vRealize Operations
Manager instance hostname or starts with index.action.
2 Select a metric and click the Apply to All icon to apply
the customization for the selected metric to all the
objects.
list.


Output Data

menu.
VMware, Inc. 587

Option Description

widget data.

metric tree.

metrics.
list.



select None.

VMware, Inc. 588

Option Description
You can use the Link to option to add links to external

and internal pages. Internal links will open in the same
tab. External links will open in a new tab. Example of
external links are URLs whose hostname does not
match with the current vRealize Operations Manager
instance hostname. Internal links are URLs whose
hostname matches the current vRealize Operations
Manager instance hostname or starts with index.action.
Output Filter
Refine the widget data further based on the filter criteria

objects.
criteria set.
Scoreboard Health Widget

The Scoreboard Health widget displays color-coded health, risk, efficiency, and custom metrics
scores for objects that you select.
How the Scoreboard Health Widget and Configuration Options Work
The icons for each object are color coded to give a quick indication of the state of the object.
You can configure the widget to display the scores of common or specific metrics of the object.
You can use the symptom state color code or you can define your criteria to color the images. If
you configure the widget to show the metric for objects that do not have this metric, those
objects have blue icons.
VMware, Inc. 589

You can double-click an object icon to show the Object Detail page for the object. When you
point to the icon, a tool tip shows the name of the object and the name of the metric.
You edit a Scoreboard Health widget after you add it to a dashboard. To configure the widget,
click the pencil at the upper-right corner of the widget window. The widget can display metrics of
the objects that you select when you edit the widget, or that you select on another widget. For
example, you can configure the widget to show the CPU workload of an object that you select on
the Topology Graph widget. To set a source widget that is on the same dashboard, you must use
the Widget Interactions menu when you edit a dashboard. To set a source widget that is on
another dashboard, you must use the Dashboard Navigation menu when you edit the source
dashboard.
Where You Find the Scoreboard Health Widget
upper panel.
Scoreboard Health Widget Configuration Options
Option Description
Configuration

this widget.
VMware, Inc. 590

Option Description
widget.
the widget.
options.
Image Type Select an image type for the metrics.
Metric Select the default or custom metric.
Pick Metric Active only when you select Custom from the Metric menu.
Use to select a custom metric for the objects that the
widget displays. Click Pick Metric and select an object type
from the Object Type pane.
Use the Metric Picker pane to select a metric from the
metric tree and click Select Object to check the objects
from the type that you select on the Object Types pane.
Use Symptom state to color chart Select to use the default criteria to color the image.
Custom ranges Use to define custom criteria to color the image. You can
define a range for each color.
Input Data
Select objects on which you want to base the widget data.

objects.
list.

VMware, Inc. 591

Sparkline Chart Widget

The Sparkline Chart widget displays graphs that contain metrics for an object in vRealize
Operations Manager. You can use vRealize Operations Manager to create one or more graphs
that contain metrics for objects that you add to your custom dashboards.
How the Sparkline Chart Widget and Configurations Options Work

If the metrics in the Sparkline Chart are for an object that another widget provides, the object
name appears at the top right of the widget. If you select a metric when you edit the widget
configuration, the widget uses the metric and its corresponding object as the source for
dashboard interactions. The line in the graphs represents the average value of the selected
metric for the specified time period. The boxed area in the graph represents the dynamic
threshold of the metric.
Point to a graph in the Sparkline Chart widget to view the value of a metric in the form of a tool
tip. You can also view the maximum and minimum values on a graph. The values are displayed as
orange dots.
You can add the Sparkline Chart widget to one or more custom dashboards and configure it to
Where You Find the Sparkline Chart Widget
The widget might be included on any of your custom dashboards. On the menu, click
Dashboards to display a list of dashboards in the left pane.
Sparkline Chart Widget Toolbar Options
VMware, Inc. 592

Option Description
Dashboard Navigation You can navigate to another dashboard when the object you select is also available in
the dashboard to which you want to navigate.
Refresh Refreshes the widget data.
Time Range Select the range for the time period to show on the graphs. You can select a period
from the default time range list or select start and end dates and times.
Select Dashboard Time to enable the dashboard time panel. The option chosen in the
dashboard time panel is effective. The default time is 6 hours.
Remove All Removes all graphs.
Sparkline Chart Widget Configuration Options

widget data.
criteria.
Option Description
Configuration

this widget.
VMware, Inc. 593

Option Description
widget.
the widget.
options.
Show Object Name You can view the name of the object before the metric
name in the Sparkline Chart widget.
n On. Displays the name of the object before the metric
name in the widget.
n Off. Does not display the name of the object in the
widget.
Column Sequence Select the order in which to display the information.

n Graph First. The metric graph appears in the first
column in the widget display.
n Label First. The metric label appears in the first column
in the widget display.
Show DT Select an option to show or hide the dynamic threshold for

the sparkline chart.
Input Data
VMware, Inc. 594

Option Description


objects. You can also expand the Tag Filter pane on the
left hand side to select one or more object tag values. A
list of objects with the selected tag values appears. If
you select more than one value for the same tag, you
can choose objects that have any of the tags applied. If
you select more than one value for different tags, you
can choose only the objects that have all the tags
applied.
metrics.
list.



select None.

VMware, Inc. 595

Option Description

objects.
list.

objects in your environment. The following sections provide
options to refine the objects for the widget data.

Output Data

menu.
VMware, Inc. 596

Option Description

widget data.
Click the Add New Metrics icon to add metrics for the
pick metrics for the object. The picked metrics appear in a
The metric tree shows common metrics for several objects
when you click the Show common metrics icon.
While selecting objects for which you want to pick metrics,
you can use the Filter text box to search for objects. You
can also expand the Tag Filter pane on the left hand side to
select one or more object tag values. A list of objects with
the selected tag values appears. If you select more than
one value for the same tag, you can choose objects that
have any of the tags applied. If you select more than one
value for different tags, you can choose only the objects
that have all the tags applied.


select None.

VMware, Inc. 597

Option Description
Output Filter
Refine the widget data further based on the filter criteria for
object types. The widget data is based on the objects for
the filtered object types.
objects.
2 In the second drop-down menu, select the option based
on which you want to define the filter criteria. For
example, if you select Metrics for the Datacenter object
type, you can define a filter criteria based on the value
of a specific metric for data centers.
criteria set.
Tag Picker Widget

The Tag Picker widget lists all available object tags.
How the Tag Picker Widget and Configuration Options Work
With the Tag Picker widget you can check the list of the object tags. You can use the widget to
filter the information that another widget shows. You can select one or more tags from the object
tree and the destination widget displays information about the objects with this tag. For example,
you can select Object Types > Virtual Machine on the Tag Picker widget to observe statistic
information about the VMs on the Environment Status widget.
VMware, Inc. 598

You edit a Tag Picker widget after you add it to a dashboard. To configure the widget, click the
pencil in the upper-right of the widget window. You can configure the Tag Picker widget to send
information to another widget on the same dashboard or on another dashboard. To set a
receiver widget that is on the same dashboard, use the Widget Interactions menu when you edit
a dashboard. To set a receiver widget that is on another dashboard, use the Dashboard
Navigation menu when you edit a source dashboard. You can configure two Tag Picker widgets
to interact when they are on different dashboards.
Where You Find the Tag Picker Widget
upper panel.
Tag Picker Widget Toolbar Options
Option Description
Collapse All Close all expanded tags and tag values.
Deselect All Remove all filtering and view all objects in the widget.
Tag Picker Select an object from your environment.
Dashboard Navigation Note Appears on the source widget and when the
destination widget is on another dashboard.
Use to explore the information on another dashboard.
Tag Picker Widget Configuration Options

Option Description
Configuration
VMware, Inc. 599

Option Description

this widget.
widget.
the widget.
options.
Text Display Widget

You can use the Text Display widget to show text in the user interface. The text appears in the
Text Display widget on the dashboard.
The Text Display widget can read text from a Web page or text file. You specify the URL of the
Web page or the name of the text file when you configure the Text widget. To use the Text
Display widget to read text files you must set a property in the web.properties file to specify the
root folder that contains the file.
You can enter content in the Text Display widget in plain text or rich text format based on the
view mode that you configure. Configure the Text Display widget in HTML view mode to display
content in rich text format. Configure the Text Display widget in Text mode to display content in
plain text format.
The Text Display widget can display web sites that use the HTTPS protocol. The behavior of the
Text Display widget with web sites that use HTTP, depends on the individual settings of the web
sites.
Note If the webpage that you are linking to has X-Frame-Options set to sameorigin, which
denies rendering a page in an iframe, the Text Display widget cannot display the contents of the
webpage.
How the Text Display Widget Configuration Options Work

You can configure the widget in the Text view mode or HTML view mode. In the HTML view
mode, you can click Edit in the widget and use the rich text editor to add content.
If you configure the widget to use Text view mode, you can specify the path to the directory that
contains the files to read or you can provide a URL. The content in the URL will be shown as text.
If you do not specify the a URL or text file, you can add content in the widget. Double click the
widget and enter content in plain text.
VMware, Inc. 600

You can also use command line interface (CLI) commands to add file content to the Text Display
widget.
n To view a list of parameters, run the file -h|import|export|delete|list txtwidget

command.
n To import text or HTML content, run the import txtwidget input-file [--title title]
[--force] command.
n To export the content to the file, run the export txtwidget all|title[{,title}] [output-
dir] command.
n To delete imported content, run the delete txtwidget all|title[{,title}] command.
n To view the titles of the content, run the list txtwidget command.
Where You Find the Text Display Widget
upper panel.
Text Display Widget Configuration Options
Option Description
Configuration

this widget.
VMware, Inc. 601

Option Description
widget.
the widget.
options.
View mode Display text in text or rich text format. You can configure
the widget in HTML view mode only when the URL and File
fields are blank.
URL Enter the URL.
File Navigate to the file that contains the source text file by
clicking the Browse button.
To add, edit, and remove source text files, go to the
TxtWidgetContent node in the Metric Configurations page.
In the menu, click Administration, and then in the left pane
click Configuration > Metric Configurations from the
vRealize Operations Manager user interface.
Test Validates the correctness of the text file or URL that you
enter.
Time Remaining Widget

The Time Remaining widget displays how much time remains before the resources of the object
are exhausted.
vRealize Operations Manager calculates the percentage by object type based on historical data
for the pattern of use for the object type. You can use the time remaining percentage to plan
provisioning of physical or virtual resources for the object or rebalance the workload in your
virtual infrastructure.
VMware, Inc. 602

Where You Find the Time Remaining Widget

upper panel.
Time Remaining Widget Configuration Options
Option Description
Configuration

this widget.
widget.
the widget.
options.
VMware, Inc. 603

Option Description
Input Data

Top Alerts Widget

Top alerts are the alerts with the greatest significance on the objects it is configured to monitor in
vRealize Operations Manager. These are the alerts most likely to negatively affect your
environment and you should evaluate and address them.
How the Top Alerts Widget and Configuration Options Work
You can add the top alerts widget to one or more custom dashboards and configure it to display
on the configured options for each widget instance.
You edit a top alerts widget after you add it to a dashboard. The changes you make to the
options help create a custom widget to meet the needs of the dashboard users.
Where You Find the Top Alerts Widget

upper panel.
VMware, Inc. 604

Top Alerts Widget Display Options

The Top Alerts widget includes the short description of alerts configured for the widget. The alert
name opens a secondary window from which you can link to the alert details. In the alert details,
you can begin resolving the alerts.
Option Description
Alert name Name of the generated alert. Click the name to open the
alert details.
Alert description Number of affected objects, and the number of

recommendations and the best recommendation to resolve
the alert.
Top Alerts Configuration Options

Option Description

this widget.
widget.
the widget.
options.
Impact Badge Select the badge for which you want alerts to appear.
The affected badge is configured when you configure the
alert definition.
VMware, Inc. 605

Option Description
Number of Alerts Select the maximum number of alerts to display in the

widget.
Input Data


Top-N Widget
The Top-N widget displays the top n results from analysis of an object or objects that you select.
How the Top-N Widget and Configuration Options Work

You can select an object when you configure the Top-N widget or you can select an object on
another widget. The widget shows an analysis of the applications, alerts, and metrics of an object
and its child objects depending on how you configure the widget. The widget can show an
analysis of the current values or values over a period of time. You can receive detailed
information about each object on the widget. When you double-click an object, the Object Detail
page appears.
VMware, Inc. 606

You can configure a widget to receive data from another widget by selecting Off for Self
Provider. You can configure a widget to display results from analysis of an object that you select
on the source widget.
For example, you can select a host on a Topology widget and observe the metric analysis of the
virtual machines on the host. To set a receiver widget that is on the same dashboard, use the
Widget Interactions menu when you edit a dashboard. To set a receiver widget that is on
another dashboard, use the Dashboard Navigation menu when you edit a source dashboard.
Where You Find the Top-N Widget
upper panel.
Top-N Widget Toolbar Options
Icon Description
Dashboard Navigation Takes you to a predefined object. For example, when you select a datastore from the
data grid and click Dashboard Navigation, you can open the datastore in the vSphere
Web Client.
Select Date Range Limits the alerts that appear in the list to the selected date range.
Select Dashboard Time to enable the dashboard time panel. The option chosen in the
dashboard time panel is effective. The default time is 6 hours.
Object details Select an object and click this icon to show the Object Detail page for the object.
Display Filtering Criteria Shows the filtering settings for the widget in a pop-up window.
Top-N Widget Configuration Options

VMware, Inc. 607

widget data.
criteria.
The Additional Columns section provides options to select metrics that are displayed as
additional columns in the widget.
Option Description
Configuration

this widget.
Self Provider Indicates whether the objects for which data appears in
the widget are defined in the widget or provided by
another widget.
the widget.
n Off. You configure other widgets to provide the
objects to the widget using the dashboard widget
Redraw Rate Set the redraw rate.
Bars Count Select the number of top results.
Round Decimals Select the number of decimals to round the scores

displayed in the widget.
Filter old metrics Select or deselect whether the analysis includes old metric
values.
Application Health and Performance n Top Least Healthy. The top n results from an analysis
of the object or objects that are the least healthy.
n Top Most Healthy. The top n results from an analysis of
the object or objects that are the most healthy.
n Top Most Volatile. The sorted list of values based on
the standard deviation of values for several alerts over
time.
Select the criteria for analysis of the objects.
Alert Analysis Select the criteria for analysis of the alerts.
VMware, Inc. 608

Option Description
Metric Analysis If you select this option, you must select a metric in the
Output Data section.
n Top Highest Utilization. A list of objects with similar
object types that have the highest utilization on
configuring usage metrics like CPU usage and memory
usage.
n Top Lowest Utilization. A list of objects with similar
object types that have the lowest utilization on
configuring usage metrics like CPU usage and memory
usage.
n Top Abnormal States. The objects are ordered by the
duration of all alarms that are triggered on the
selected metric for a selected interval.
n Top Highest Volatility. The sorted list of values based
on the standard deviation of values for several alerts
over time.
Select the criteria for analysis of the metric that you select
from the metric tree.
Input Data
object tag values. A list of objects with the selected
tag values appears.. If you select more than one value
for the same tag, you can choose objects that have
any of the tags applied. If you select more than one
value for different tags, you can choose only the
objects that have all the tags applied.
objects.
list.


VMware, Inc. 609

Option Description
Output Data
Select an object type in your environment on which you

an object type.
object type.
If the objects have an input transformation applied, the
transformed objects are the basis for the widget data.
Metric Select a common metric or a metric for the selected object

type in the list. The metric will be the basis for the widget
data.
Output Filter
objects.
object type, you can define a filter criteria based on
the value of a specific metric for data centers.
criteria set.
VMware, Inc. 610

Option Description
Additional Columns
Add metrics based on object types. The selected metrics

are displayed as additional columns in the widget.
While selecting object types for which you want to

pick metrics, you can filter the object types by adapter
type to pick an object type. On the metrics pane, click
the Select Object icon to select an object for the
object type. Pick metrics of the selected object from
the metric tree.

2 Optionally, you can double-click a metric box in the list
to customize the label of the metric and click Update.
Topology Graph Widget

The Topology Graph widget gives a graphical presentation of objects and their relationships in
the inventory. You can customize each instance of the widget in your dashboard.
How the Topology Graph Widget and Configuration Options Work

The Topology Graph widget enables you to explore all nodes and paths connected to an object
from your inventory. Connection between the objects might be a logical, physical, or network
connection. The widget can display a graph that shows all of the nodes in the path between two
objects, or that shows the objects related to a node in your inventory. You select the type of
graph in the Exploration Mode when you configure the widget. You can select the levels of
VMware, Inc. 611

exploration between nodes in the displayed graph by using Relationship check boxes when you
edit the widget. The widget displays all object types in the inventory by default, but you can
select object types to view by using the Object View list during the configuration process.
Double-clicking an object on the graph takes you to a detailed page about the object.
Where You Find the Topology Graph Widget
upper panel.
Topology Graph Widget Toolbar Options
Option Description
Action Use to select from predefined actions for each object type.
To see available predefined actions, select an object in the
graph and click the toolbar to select an action. For example,
when you select a datastore object in the graph, you can
click Delete Unused Snapshots for Datastore to apply this
action to the object.
Dashboard Navigation Takes you to a predefined object . For example, when you
select a datastore from the graph and click Dashboard
Navigation, you can open the datastore in the vSphere
Web Client .
Pan Use to move the entire graph.
Show values on point Provides a tool tip with parameters when you point to an
object in the graph.
Zoom in Zooms in the graph.
Zoom out Zooms out the graph.
Hierarchical View Use to switch to hierarchical view. Hierarchical view is

enabled only for Node Exploration mode and with selected
inventory tree.
Graph View Use to switch to graph view.
Object Detail Select an object and click this icon to show the Object Detail
page for the object.
Expand Node Selects which object types related to your object to show
on the graph. For example, if you select a virtual machine
from the graph and click Expand Node toolbar icon and
select Host System, the host on which the virtual machine is
located is added to the graph.
Hide Node(s) Use to remove a given object from the graph
VMware, Inc. 612

Option Description
Reset To Initial Object Use to return to the initially displayed graph and configured
object types.
Explore Node Use to explore a node from a selected object in the graph.
For example, if the graph displays a connection between a
VM, a host, and a datastore, and you want to check the
connection of the host with the other objects in the
inventory, you can select the host and click Explore Node.
Status Use to select objects based on their status or their state.
Topology Graph Widget Configuration Options

Option Description
Configuration

this widget.
widget.
the widget.
options.
VMware, Inc. 613

Option Description
Exploration Mode Use Node Exploration mode to observe a selected object

from an object list and the objects related to it. For
example, if you select a virtual machine and select node
exploration mode, the widget shows the host where the
VM is placed and the datastore storing the files of the VM.
Use Path Exploration mode to observe the relation
between two objects. You must select them from the
Select First Object list and the Select Second Object list.
For example, if you select to explore the path between a
VM and a vCenter Server, the graph shows you both
objects and all nodes in the path between the VM and
server as datastore, datastore cluster, and datacenter .
Important To select object view is mandatory for the

widget to start working in path exploration mode.
Show Paths Use All to observe connections between a node and nodes
related to it as well as connections between the nodes. For
example, if you are using node exploration mode and you
select to observe a VM and all objects types, the graph
shows a VM connected to its datastore and host and the
connection between the host and datastore.
Use Discovered Only to observe directly related nodes.

For example, if you are using node exploration mode and
you select to observe a VM and all objects types, the graph
will shows the VM connected to its datastore and to its
host, but without the connection between the host and
datastore .
Configuration File The default configuration includes parent and child

relationship. Drop-down options depend on the installed
Solutions. You can add a new type of relationship to the
Relationship pane.
Metric Configuration Specifies a list with attributes to display.

The newly created XML file appears in the Metric
Configuration drop-down menu of the widget.
Layout Select whether you want a graph view or hierarchical view

for the topology graph.
Tree type For a hierarchical layout, select whether you want a tree
type view.
Input Data
Selected object From the object list, select an object on which you want to
base the widget data.
VMware, Inc. 614

Option Description
Degree of separation Available only when node exploration mode is selected.

Use to define the levels of exploration in node exploration
mode. The lowest degree configuration shows only directly
related nodes rather than higher degrees that show the
inventory in details.
Select First Object Available only in path exploration mode. Select the first
object from the object list.
Select Second Object Available only in path exploration mode. Select the second
object from the object list.
Object view Use to select which types of objects to observe in the

graph.
Relationship Select the type of relationship between objects to observe

in the graph, respectively the details about your inventory .
The common relationships for all objects are parent and
child, but the list of relationships can vary depending on
added solutions to vRealize Operations Manager.
View Widget
The View widget provides the vRealize Operations Manager view functionality into your
dashboard.
How the View Widget and Configuration Options Work
A view presents collected information for an object in a certain way depending on the view type.
Each type of view helps you to interpret metrics, supermetrics, properties, alerts, policies, and
data from a different perspective.
You can add the View widget to one or more custom dashboards and configure it to display data
that is important to the dashboard users. List views can send interactions to other widgets.
Where You Find the View Widget
upper panel.
You can export the view as a CSV file for any view type.
View Widget Toolbar Options
The View widget toolbar depends on the displayed view type.
VMware, Inc. 615

Option Description
Export as CSV You can export the view as a CSV file for any view type.
Open in External Application Ability to link to another application for information about
the object. For example, you have a List view with VMs.
You can select any VM and select Open in External
Application to open the VM in vSphere Web Client.
Time Settings Use the time settings to select the time interval of data
transformation. These options are available for all view
types, except Image.
n Relative Date Range. Select a relative date range of
data transformation.
n Specific Date Range. Select a specific date range of
data transformation.
n Absolute Date Range. Select a date or time range to
view data for a time unit such as a complete month or a
week. For example, you can run a report on the third of
every month for the previous month. Data from the first
to the end of the previous month is displayed as
against data from the third of the previous month to
the third of the current month.
The units of time available are: Hours, Days, Weeks,

Months, and Years.
The locale settings of the system determine the start

and end of the unit. For example, weeks in most of the
European countries begin on Monday while in the
United States they begin on Sunday.
Roll up interval The time interval at which the data is rolled up.
Actions An action on the selected object. Depends on the object

type.
Filter Limits the list to objects for a specific host, datacenter, and
so on. You can drill-down in the hierarchical level. Available
for List, Trend, and Distribution types of Views.
View Widget Configuration Options

The Input Data section provides options to specify input for the widget.
widget data.
VMware, Inc. 616

Option Description
Configuration

this widget.
widget.
the widget.
options.
Input Data
Inventory trees Select an existing predefined traversal spec to pick an

object for the widget data.
Object In self provider mode, click the Add Object icon to select
an object from the object list. The object list is displayed
based on the inventory tree selection. You can also search
for the object in this text box.
Output Data
A list of defined views available for the selected object is

displayed.
You can create, edit, delete, clone, export, and import
views directly from the View widget configuration options.
For more information, see Views.
Auto Select First Row Determines whether to start with the first row of data for
list type views.

widget:
n To display the list of legends in the widget, select
Legend.
n To display the name of the labels in the widget, select
Labels.
Weather Map Widget

The Weather Map widget provides a graphical display of the changing values of a single metric
for multiple resources over time. The widget uses colored icons to represent each value of the
VMware, Inc. 617

metric. Each icon location represents the metric value for particular resources. The color of an
icon changes to show changes in the value of the metric.
How the Weather Map Widget and Configuration Options Work
You can add the Weather Map widget to one or more custom dashboards and configure it to
Watching how the map changes can help you understand how the performance of the metric
varies over time for different resources. You can start or stop the display using the Pause and
Play options at the bottom of the map. You can move the slider forwards or backwards to a
specific frame in the map. If you leave the widget display and return, the slider remains in the
same state.
The map does not show the real-time performance of the metrics. You select the time period,
how fast the map refreshes, and the interval between readings. For example, you might have the
widget play the metric values for the previous day, refreshing every half second, and have each
change represent five minute's worth of metric values.
To view the object that an icon represents, click the object.

Where You Find the Weather Map Widget
upper panel.
Weather Map Widget Toolbar Options
The toolbar contains the icons that you can use to view the graph.
VMware, Inc. 618

Icon Description
Pause and Play Start or stop the display. The icon remains in the same state if you leave the widget
display and return.
Display Filtering Criteria View the current settings for the widget, including the current metric.
Weather Map Widget Configuration Options

widget data.
criteria.
Option Description
Configuration

this widget.
Redraw Rate An interval at which cashed data is refreshed based on

newly collected data.
For example, if you set metric history to Last 6 hours and
image redraw rate to 15 minutes, and data is collected
every 5 minutes, the data collected during 10 minutes will
not be calculated at the 15 minutes.
For example, if you set metric history to Last 6 hours and
image redraw rate to 15 minutes, and data is collected
every 5 minutes, the data collected during 10 minutes will
not be calculated at the 15 minutes.
Metric History Select the time period for the weather map, from the
previous hour to the last 30 days.
Metric Sample Increment Select the interval between metric readings. For example, if
you set this option to one minute and set the Metric History
to one hour, the widget has a total of 60 readings for each
metric.
VMware, Inc. 619

Option Description
Group by Select a tag value by which to group the objects.
Sort by Select Object name or Metric value to set the way to sort
the objects.
Frame Transition Interval Select how fast the icons change to show each new value.
You can select the interval between frames and the
number of frames per second (fps).
Start Over Delay The number of seconds for the display to remain static
when it reaches the end of the Metric History period, the
most current readings, before it starts over again from the
beginning.
Color Shows the color range for high, intermediate and low
values. You can set each color and type minimum and
maximum color values in the Min Value and Max Value text
boxes.
If you leave the text boxes blank, vRealize Operations
Manager maps the highest and lowest values for the Color
By metric to the end colors.
If you set a minimum or maximum value, any metric at or
beyond that value appears in the end color.
If you set a minimum or maximum value, any metric at or
beyond that value appears in the end color.
Output Data
Select an object type in your environment on which you

an object type.
object type.
Metric Select a common metric or a metric for the selected object

type in the list. The metric will be the basis for the widget
data. The object corresponding to the metric will be the
selected object for the widget.
Output Filter
VMware, Inc. 620

Option Description
criteria set.
Workload Widget
The Workload widget displays data a indicating how hard a selected resource is working.
The Workload widget displays a graph depicting how hard the object that you selected is
working. The Workload widget reports data on CPU usage, Memory usage, Disk I/O, and
Network I/O.
Where You Find the Workload Widget
upper panel.
VMware, Inc. 621

About Datastore Metrics for Virtual SAN

The metric named datastore|oio|workload is not supported on Virtual SAN datastores. This
metric depends on datastore|demand_oio, which is supported for Virtual SAN datastores.
The metric named datastore|demand_oio also depends on several other metrics for Virtual SAN
datastores, one of which is not supported.
n The metrics named devices|numberReadAveraged_average and devices|

numberWriteAveraged_average are supported.
n The metric named devices|totalLatency_average is not supported.
As a result, vRealize Operations Manager does not collect the metric named datastore|oio|
workload for Virtual SAN datastores.
Workload Widget Configuration Options
Option Description
Configuration

this widget.
VMware, Inc. 622

Option Description
widget.
the widget.
options.
Input Data

Workload Pattern Widget

The Workload Pattern widget displays a historical view of the hourly workload of an object.
Where You Find the Workload Pattern Widget
upper panel.
Workload Pattern Widget Configuration Options

VMware, Inc. 623

Option Description
Configuration

this widget.
widget.
the widget.
options.
Input Data

Workload Utilization Widget

The Workload Utilization widget displays a visual summary of the workload resources used by
the objects in your environment.
How the Workload Utilization Widget and Configuration Options Work
Use the Workload Utilization widget to identify which workload objects are underutilized and
overutilized.
You can add the Workload Utilization widget to one or more custom dashboards and configure it
to display data that is important to the dashboard users.
VMware, Inc. 624

Where You Find the Workload Utilization Widget

upper panel.
Workload Utilization Widget Toolbar Options
Option Description
Action Displays the available actions for a specific object. For

example, if you select the host object icon, the Action icon
is enabled and displays all the available actions you can
carry out. Some of the options are: Power Off VM, Power
On VM, and so on . The actions displayed change based on
the type of object you select.
The button is dimmed when actions are not available for an
object you select.
Constrained by Sorts the objects in the chart based on a metric you select.
For example, if you select CPU Demand, all the objects
constrained by CPU demand are displayed in the chart.
You can sort the chart based on options like: CPU, CPU
Demand, Memory, Memory Consumed, and vSphere
Configuration Limit.
Reset to initial object Displays the original view of the chart.
Workload Utilization Widget Configuration Options

Option Description
Title Enter a custom title that identifies this widget from other instances that are based on the same
widget template.
Configuration
VMware, Inc. 625

Option Description
n Off. You configure other widgets to provide the objects to the widget using the dashboard
widget interactions options.
Input Data
Select Object Your inventory where you can locate the object on which you are basing the data that appears in
the widget.
Object Type Select specific object types to see in the charts. Press Ctrl+click to select multiple object types. If
you leave the object type deselected, you see all base object children in the charts.
Dashboards
Dashboards present a visual overview of the performance and state of objects in your virtual
infrastructure. You use dashboards to determine the nature and timeframe of existing and
potential issues with your environment. You create dashboards by adding widgets to a
dashboard and configuring them.
vRealize Operations Manager collects performance data from monitored software and hardware
resources in your enterprise and provides predictive analysis and real-time information about
problems. The data and analysis are presented through alerts, in configurable dashboards, on
predefined pages, and in several predefined dashboards.
n You can start with several predefined dashboards in vRealize Operations Manager.
n You can create extra ones that meet your specific needs using widgets, views, badges, and
filters to change the focus of the information.
n You can clone and edit the predefined dashboards or start from scratch.
n To display data that shows dependencies, you can add widget interactions in dashboards.
n You can provide role-based access to various dashboards for better collaboration in teams.
VMware, Inc. 626

Table 4-151. Menu Options

Menu Description
All Dashboards Lists the dashboards that are enabled. You can use this
menu for a quick navigation through your dashboards.
When you navigate to a dashboard using the All
Dashboards option, the dashboard is listed in the left pane
of the Dashboards page.
Actions Available dashboard actions, such as create, edit, delete,

and set as default. These actions are applied directly to the
dashboard that you are on.
Dashboard Time The dashboard time panel is enabled by default on all

predefined and user-created dashboards. Using this option,
you can select a time for the widgets in the dashboard. The
default time is 6 hours. The pre-defined time/day options in
the panel are 10 months, 1 hour, 6 hours, or 1 day. You can
also set a customized time option.
To enable widgets to use the dashboard time, select Date
Controls/Time Range > Dashboard Time from the widget
toolbar. Some widgets have Dashboard Time as the
default option. For example, Metric Chart, Rolling View,
Sparkline, Health Chart, and Mashup Chart widgets.
Dashboard Time as an option persists for all widgets
except the View widget. For example, the dashboard time
persists if:
n You enable a widget in a dashboard to use the
dashboard time and then log out and log back in, or
n You enable a widget in a dashboard to use the
dashboard time, and you export and then import the
dashboard into another instance of vRealize Operations
Manager.
Types Of Dashboards
You can use the predefined dashboards or create your own custom dashboard in vRealize
Operations Manager.
Custom Dashboards
vRealize Operations Manager has predefined dashboards. You can also create dashboards that
meet your environment needs.
To manage your dashboards, in the menu, click Dashboards. Click Actions > Manage
Dashboards and then click the gear icon.
Depending on your access rights, you can add, delete, and arrange widgets on your dashboards.
You can also clone and create dashboards, import or export dashboards from other instances,
edit widget configuration options, configure widget interactions, and transfer ownership of
dashboards.
VMware, Inc. 627

Table 4-152. Dashboards Options

Option Description Usage
Save as Template Contains all the information in a You can use any dashboard to create a template.
dashboard definition.
Export Dashboards When you export a dashboard, You can export a dashboard from one vRealize
vRealize Operations Manager Operations Manager instance and import it to
creates a dashboard file in another.
JSON format.
Import Dashboards A PAK or JSON file that You can import a dashboard that was exported
contains dashboard information from another vRealize Operations Manager
from vRealize Operations instance.
Manager.
Enable Dashboards(s) Enables a dashboard that was

previously disabled.
Disable Dashboard(s) Disables a dashboard.
Transfer Dashboard(s) Assigns a new owner to the After you assign a dashboard to a new owner, the
dashboard. dashboard is no longer displayed as one of your
dashboards.
When you transfer a dashboard that was
previously shared with user groups, information
about the shared user groups and group hierarchy
is retained.
Remove Dashboard(s) from Removes a dashboard from the You can add any dashboard to the vRealize
Home vRealize Operations Manager Operations Manager home page.
home page.
Reorder/Autoswitch Dashboards Changes the order of the You can configure vRealize Operations Manager to
dashboard tabs on vRealize switch from one dashboard to another.
Operations Manager home
page.
Manage Summary Dashboards Provides you with an overview You can change the Summary tab with a
of the state of the selected dashboard to get information specific to your
object, group, or application. needs.
Manage Dashboard Groups Groups dashboards in folders. You can create dashboard folders to group the
dashboards in a way that is meaningful to you.
Share Dashboards Makes a dashboard available to You can share a dashboard or dashboard
other users or user groups. template with one or more user groups.
Copy Dashboards Copies a dashboard to other You can copy a dashboard to another user or user
another user or user group. group. Specify the dashboards to be shared and
select a target user and specify the target folder.
The dashboard list depends on your access rights.
Predefined Dashboards
vRealize Operations Manager has predefined dashboards that address several key questions
including how you can troubleshoot your VMs, the workload distribution of your hosts, clusters,
VMware, Inc. 628

and datastores, the capacity of your data center, and information about the VMs. You can also
view log details.
The default dashboard that appears when you click Dashboards in the menu is the Getting
Started dashboard. You can close a dashboard from the left pane by selecting the dashboard
and clicking the X icon. The dashboard you last opened is displayed the next time you navigate
to Dashboards in the menu. If there is only one dashboard left in the left pane, you cannot close
it.
The following predefined dashboards can be accessed by clicking Dashboards in the menu, and
then clicking All Dashboards:
n Capacity and Utilization
n Capacity Allocation Overview
n Cluster Utilization
n Datastore Utilization
n Heavy Hitter VMs
n Host Utilization
n Utilization Overview
n VM Utilization
n vSAN Capacity Overview
n Configuration and Compliance
n Cluster Configuration
n Distributed Switch Configuration
n Host Configuration
n VM Configuration
n vSphere Hardening Compliance
n Operations
n Datastore Usage Overview
n Host Usage Overview
n Migrate to vSAN
n Operations Overview
n vSAN Operations Overview
n Optimize
n Assess Cost
n Optimization History
VMware, Inc. 629

n Optimize Performance
n Performance Troubleshooting
n Troubleshoot a Cluster
n Troubleshoot a Datastore
n Troubleshoot a Host
n Troubleshoot a VM
n Troubleshoot vSAN
n Troubleshoot with Logs
n vRealize Assessments
n Hybrid Cloud Assessment
n vSphere Optimization Assessment
n vRealize Automation
n Application Overview
n Environment Overview
n Resource Consumption Overview
n Top-N
n vRealize Operations
n MP Statistics
n Self Cluster Statistics
n Self Health
n Self Performance Details
n Self Services Communications
n Self Services Summary
n Self Troubleshooting
n vCenter Adapter Details
n Inventory
n vSphere Compute Inventory
n vSphere Network Inventory
n vSphere Storage Inventory
n Getting Started
VMware, Inc. 630

Getting Started Dashboard

The Getting Started dashboard is a guide to answering the most frequent questions of your IT
staff. The dashboard breaks tasks into broad categories including Capacity and Utilization,
Configuration and Compliance, Operations, Performance Troubleshooting, and Optimize.
Using each of these categories you can drill down to the specific use cases and problems you are
trying to solve. Each problem statement is associated with a predefined dashboard that you can
access through this page. To view a dashboard, click the dashboard name listed on the right side
of the Getting Started dashboard.
Capacity and Utilization Dashboards
The dashboards in the Capacity and Utilization category cater to the teams responsible for
tracking the utilization of the provisioned capacity in their virtual infrastructure. The dashboards
within this category allow you to take capacity procurement decisions, reduce wastage through
reclamation, and track usage trends to avoid performance problems due to capacity shortfalls.
Key questions these dashboards help you answer are as follows:
n How much capacity exists, how much is used, and the usage trends for a specific vCenter,
data center, or cluster?
n How much disk, vCPU, or memory you can reclaim from large VMs in your environment to
reduce wastage and improve performance?
n Which clusters have the highest resource demands?
n Which hosts are being heavily utilized and why?
n Which datastores are running out of disk space and who are the top consumers?
n The storage capacity and utilization of your vSAN environment with the savings achieved by
enabling deduplication and compression.
Capacity Allocation Overview Dashboard

This dashboard provides an overview of allocation ratios for virtual machines, vCPUs, and
memory for a specific data center or cluster.
Cluster Utilization Dashboard
The Cluster Utilization dashboard helps you identify vSphere clusters that are extensively
consumed from a CPU, memory, disk, and network perspective.
You can use this dashboard to identify the clusters that cannot serve the virtual machine
demand.
You can select a cluster with high CPU, memory, disk, or network demand. The dashboard lists
the ESXi hosts that are a part of the given cluster. If there is an imbalance in the use of hosts
within the selected clusters, you can balance the hosts by moving the VMs within the cluster.
You can use this dashboard to view the historical cluster demand. If the situation is critical, use
Workload Balance and move the VMs out of the clusters to avoid potential performance issues.
For more information, see Configuring and Using Workload Optimization. If all the clusters in a
given environment display the same pattern, you might have to add new capacity to cater to the
increase in demand.
Datastore Utilization Dashboard
VMware, Inc. 631

The Datastore Utilization dashboard helps you identify storage provisioning and utilization
patterns in a virtual infrastructure.
As a best practice, ensure that the datastores are of standard size, to manage storage in your
virtual environments. The heat map on this dashboard displays all the datastores monitored by
vRealize Operations Manager and groups them by clusters.
The dashboard uses colors to depict the utilization pattern of the datastores. Grey represents an
underutilized datastore, red represents a datastore that has run out of disk space, and green
represents an optimally used datastore. You can select a datastore from the dashboard to see
the past utilization trends and forecasted usage. The dashboard lists all the VMs that run on the
selected datastore. You can reclaim storage used by large VM snapshots or powered off VMs.
You can use the vRealize Operations Manager action framework to reclaim resources by deleting
the snapshots or unwanted powered off VMs.
n Datastore Capacity and Utilization: Use this widget to find out which datastores are
overused and which ones are underused. You can also find out whether the datastores are of
equal size. When you select a datastore from this widget, the dashboard is automatically
populated with the relevant data.
n VMs in the Selected Datastore: Use this widget to view a list of VMs based on the datastore
you select. You can also view relevant details such as whether the VMs are powered on and
the size of the snapshot if any.
n Usage Trend of Selected Datastore: Use this widget to find out the trends in capacity used
by a selected datastore as against the total capacity available.
n All Shared Datastores in the Environment: Use this widget to view a list of datastores that
are shared in your environment. The information displayed in this widget helps you make an
informed decision about whether you have to rebalance the capacity of the datastores based
on usage.
Heavy Hitter VMs

The Heavy Hitter VMs dashboard helps you identify virtual machines which are consistently
consuming a large amount of resources from your virtual infrastructure. In heavily over-
provisioned environments, this might create resource bottlenecks resulting in potential
performance issues.
You can use this dashboard to identify the resource utilization trends of each of your vSphere
clusters. With the utilization trends, you can also view a list of VMs within those clusters based on
their resource demands from the CPU, memory, disk, and network within your environment. You
can also analyze the workload pattern of these VMs over the past week to identify heavy hitter
VMs which might be running a sustained, heavy workload that is measured over a day, or bursty
workloads that is measured using peak demand.
You can export a list of offenders and take appropriate action to distribute this demand and
reduce potential bottlenecks.
VMware, Inc. 632

You can use the dashboard widgets in several ways.
n Select a Cluster: Use this widget to select a cluster. You can use the filter to narrow your list
based on several parameters. After you identify the cluster you want to view, select it. The
dashboard is automatically populated with the relevant data.
n Cluster CPU and Cluster Memory: Use these widgets to view the CPU and memory for the
cluster.
n Cluster IOPS and Cluster Network Throughput: Use these widgets to view the IOPS and
network throughput for the cluster.
n Use the other widgets in the dashboard to view which VMs in the cluster generated the
highest network throughput and IOPS. You can also view which VMs in the cluster generated
the highest CPU demand and the highest memory demand. You can compare the information
for the VM with the results for the cluster and correlate the trends. You can manually set the
time to the time period for which you want to view data.
Host Utilization Dashboard

The Host Utilization dashboard helps you identify hosts that are extensively consumed from a
CPU, memory, disk, and network perspective.
You can use this dashboard to identify hosts that cannot serve the virtual machine demand. The
dashboard provides a list of the top 10 virtual machines. You can identify the source of this
unexpected demand and take appropriate actions.
You can use the dashboard to view demand patterns over the last 24 hours and identify hosts
that have a history of high demand. You must move the virtual machines out of these hosts to
avoid potential performance issues. If all the hosts of a given cluster display the same pattern,
you might have to add new capacity to cater to the increase in demand.
Utilization Overview Dashboard
The Utilization Overview dashboard helps you view the available capacity in the virtual
infrastructure.
The Utilization Overview dashboard allows you to assess the utilization at each resource group
level such as vCenter, data center, custom data center, or vSphere cluster. You can quickly select
an object and view the total capacity, used capacity, and usable capacity of the object to
understand the current capacity situation.
n Total Environment Summary: Use this widget to view the total available capacity in the
environment including information about the number of hosts and datastores. You can also
view storage, memory, and CPU capacity, and the number of physical CPUs.
n Select an Environment: Use this widget to select a data center, a cluster compute resource,
or a vCenter Server. You can use the filter to narrow your list based on several parameters.
After you identify the data center you want to view, select it. The dashboard is populated
with the relevant data.
VMware, Inc. 633

n Inventory: Use this widget to view the number of running VMs and hosts. You can also view
the number of datastores and the consolidation ratio in the environment.
n Usable Capacity (Exclude HA Buffers): Use this widget to view the capacity that is available
in the virtual infrastructure.
n Used Capacity: Used this widget to view how the capacity is used in various data centers and
clusters.
n Capacity Remaining: Use this widget to view the capacity remaining in terms of memory,
storage, and CPU capacity remaining.
n Predicted Time Remaining: Use this widget to view the predicted time remaining based on
the use patterns in the environment.
n Cluster Capacity Details: Use this widget to view detailed capacity information for each
cluster.
VM Utilization Dashboard
The VM Utilization dashboard helps you as an administrator to capture the utilization trends of
any VM in your environment. You can list the key properties of a VM and the resource utilization
trends for a specific time period. You can share the details with the VM or application owners.
The dashboard displays resource utilization trends so that the VM or application owners can view
these trends when they expect a high load on applications. For example, activities like batch jobs,
backup schedules, and load testing. Application owners must ensure that the VMs do not
consume 100% of the provisioned resources during these periods. Excessive consumption of the
provisioned resources can lead to resource contention within the applications and can cause
performance issues.
n Search for a VM to Report its Usage: Use this widget to select the VM you want to
troubleshoot. You can use the filter to narrow your list based on several parameters. After
you identify the VM that you want to view, select it. The dashboard is automatically
n About the VM: Use this widget to view the VM you selected and its details. You select the VM
in the Search for a VM to Report its Usage widget.
n VM Utilization Trend: CPU, Memory, IOPS, Network: Use this widget to view information
about the utilization and allocation trends for CPU demand, memory workload, disk
commands per second, and the network usage rate.
vSAN Capacity Overview

The vSAN Capacity Overview dashboard provides an overview of vSAN storage capacity and
savings achieved by enabling deduplication and compression across all vSAN clusters.
You can view current and historical use trends, and future procurement requirements from the
dashboard. You can view details such as capacity remaining, time remaining, and storage
reclamation opportunities to make effective capacity management decisions.
You can view the distribution of use among vSAN disks from the dashboard. You can view these
details either as an aggregate or at an individual cluster level.
VMware, Inc. 634

vSAN Stretched Clusters

The vSAN Stretched Clusters dashboard provides an overview of the cluster resources used
across vSAN fault domains. Using the stretched clusters dashboard you can monitor the resource
consumption at the site level for Preferred Sites and Secondary Sites. You can create custom
dashboards for specific vSAN stretched cluster metrics.
Where to View vSAN Stretched Cluster Objects
On the menu, click Dashboard > Capacity and Utilization > vSAN Stretched Clusters.
You can also view the vSAN stretched cluster objects from Environment > VMware vSAN >
vSAN and Storage Devices > vSAN Clusters, if the vSAN cluster is a stretched cluster.
The vSAN Stretched Clusters dashboard provides information about CPU Capacity, Cores,
Memory Capacity, and Disk Capacity for the Preferred Site and the Secondary Site. You can
identify the vSAN stretched clusters running out of capacity looking at the utilization metrics.
Configuration and Compliance Dashboards
The dashboards in the Configuration and Compliance category cater to administrators who are
responsible for managing configuration drifts within a virtual infrastructure. Since most of the
issues in a virtual infrastructure are a result of inconsistent configurations, dashboards in this
category highlight the inconsistencies at various levels such as VMs, hosts, clusters, and virtual
networks. You can view a list of configuration improvements that helps you avoid problems that
are caused because of misconfigurations.
Your IT security teams can also measure your environment against the vSphere hardening best
practices to ensure that your environment is fully secured and meets all the compliance
standards.
n Are the vSphere clusters consistently configured for high availability (HA) and optimal
performance?
n Are the ESXi hosts consistently configured and available to use?
n Are the VMs sized and configured as per the recommended best practices?
n Are virtual switches configured optimally?
n Is the environment configured in accordance with the vSphere Hardening Guide?
Cluster Configuration Dashboard

The Cluster Configuration dashboard provides a quick overview of your vSphere cluster
configurations. The dashboard highlights the areas that are important in delivering performance
and availability to your virtual machines. The dashboard also highlights if there are clusters which
are not configured for DRS, High Availability (HA), or admission control to avoid any resource
bottlenecks or availability issues when a host fails.
VMware, Inc. 635

The heat map in this dashboard helps you to identify if you have hosts where vMotion was not
enabled as this may not allow the VMs to move from or to that host. This may cause potential
performance issues for the VMs on that host if the host gets too busy. You can also view how
consistently your clusters are sized and whether the hosts on each of those clusters are
consistently configured.
The Cluster Properties widget in this dashboard allows you to report on all these parameters by
exporting the data. You can share the data with the relevant stakeholders within your
organization.
n vSphere DRS Status, vSphere HA Status, and HA Admission Control Status: Use these
widgets to view if there are clusters that are not configured for DRS, HA, or admission
control. With the information, you can avoid resource bottlenecks or availability issues when
a host fails.
n Is vMotion enabled on hosts in a cluster: Use this widget to identify if you have hosts where
vMotion was not enabled. If vMotion is not enabled, the VMs do not move from or to the host
and causes potential performance issues in the VMs on that host if the host gets too busy.
n Host Count across Clusters: Use this widget to view all the clusters in your environment. If
the clusters have a consistent number of hosts, the boxes displayed are of equal size. This
representation helps you determine whether there is a large deviation among cluster sizes,
whether there is a small cluster with fewer than four hosts, or whether there is a large cluster.
Operationally, keep your clusters consistent and of moderate size.
n Attributes of ESXi Hosts in the Selected Cluster: Use this widget to view the configuration
details for the hosts within a cluster.
n All Clusters Properties: Use this widget to view the properties for all the clusters in the
widget.
Distributed Switch Configuration Dashboard

The Distributed Switch Configuration dashboard allows you to view details of virtual switch
configuration and utilization. When you select a virtual switch, you can see the list of ESXi hosts,
distributed port groups, and virtual machines that use or are on the selected switch. You can also
find out which ESXi hosts and VMs use a specific switch.
You can identify misconfigurations within various network components by reviewing the
properties listed in the views within the dashboard. You can track important information such as
the IP address and the MAC address assigned to the virtual machines.
As a network administrator, you can use this dashboard to get visibility into the virtual
infrastructure network configuration.
VMware, Inc. 636

n Select a Distributed Switch: Use this widget to select the switch for which you want to view
details. You can use the filter to narrow your list based on several parameters. After you
identify the switch that you want to view, select it. The dashboard is automatically populated
n Distributed Port Groups on the Switch: Use this widget to view the port groups on the
switch, how many ports each switch has, and the usage details.
n ESXi Hosts/VMs Using the Selected Switch: Use these widgets to find out which ESXi hosts
and VMs use the selected switch. You can also view configuration details about the ESXi
hosts and VMs that use the selected switch.
Host Configuration Dashboard

The Host Configuration dashboard provides an overview of your ESXi host configurations, and
displays inconsistencies so that you can take corrective action.
The dashboard also measures the ESXi hosts against the vSphere best practices and indicates
deviations that can impact the performance or availability of your virtual infrastructure. Although
you can view this type of data in other dashboards, in this dashboard you can export the ESXi
configuration view and share it with other administrators.
VM Configuration Dashboard
The VM dashboard focuses on highlighting the key configurations of the virtual machines in your
environment. You can use this dashboard to find inconsistencies in configuration within your
virtual machines and take quick remedial measures. You can safeguard the applications which are
hosted on these virtual machines by avoiding potential issues due to misconfigurations.
Some of the basic problems the dashboard focuses on includes identifying VMs running on older
VMware tools versions, VMware tools not running, or virtual machines running on large disk
snapshots. VMs with such symptoms can lead to potential performance issues and hence it is
important that you ensure that they do not deviate from the defined standards. This dashboard
includes a predefined Virtual Machine Inventory Summary report which you can use to report the
configurations highlighted in this dashboard for quick remediation.
n Use the Large VMs widgets to view graphical representations of VMs that have a large CPU,
RAM, and disk space.
n Guest OS Distribution: Use this widget to view a break up of the different flavors of
operating systems you are running.
n Guest Tools Version and Guest Tools Status: Use these widgets to identify if you have
inconsistent or older version of VMware tools which might lead to performance issues.
n View the VMs with limits, large snapshots, orphaned VMs, VMs with more than one NIC, and
VMs with a nonstandard operating system. These VMs have a performance impact on the
rest of the VMs in your environment even though they do not fully use their allocated
resources.
VMware, Inc. 637

You can customize the views in the widgets.
1 Click the Edit Widget icon from title bar of the widget. The Edit widget dialog box is
displayed.
2 From the Views section, click the Edit View icon. The Edit View dialog box is displayed.
3 Click the Presentation option in the left pane and make the required modifications.
vSphere Security Compliance Dashboard

The vSphere Security Compliance dashboard measures your environment against the vSphere
Hardening Guide and lists any objects which are non-compliant.
This dashboard displays the trend of high risk, medium risk, and low risk violations and shows the
overall compliance score of your virtual infrastructure. Using heat maps, you can investigate
various components to check the compliance for your ESXi hosts, clusters, port groups, and
virtual machines. Each non-compliant object is listed in the dashboard with recommendations on
the remediation required to secure your environment.
Operations Dashboards
The dashboards in the Operations category are most helpful to personnel within an organization
that require a summary of important data to take quick decisions. As a member of the network
operations center (NOC) team, you may want to identify problems and take action or as an
executive, you may want a quick overview of your environments to keep track of important KPIs.
n What does the infrastructure inventory look like?
n What is the alert volume trend in the environment?
n Are virtual machines being served well?
n Are there areas in the data center you have to worry about?
n What does the vSAN environment look like and are there optimization opportunities by
migrating VMs to vSAN?
Datastore Usage Overview Dashboard

The Datastore Usage Overview dashboard provides a view of all the virtual machines in your
environment in a heat map. The dashboard is suitable for an NOC environment.
The heat map contains a box for each virtual machine in your environment. You can identify the
virtual machines that are generating excessive IOPS because the boxes are sized by the number
of IOPS they generate.
The colors of the boxes represent the latency experienced by the virtual machines from the
underlying storage. An NOC administrator can investigate the cause of this latency and resolve it
to avoid potential performance problems.
Host Usage Overview Dashboard
The Host Usage Overview dashboard provides a view of all the ESXi hosts in your environment in
a heat map. The dashboard is suitable for an NOC environment.
VMware, Inc. 638

Using this dashboard an NOC administrator can easily find resource bottlenecks created due to
excessive Memory Demand, Memory Consumption or CPU Demand.
The heat map displays hosts grouped by clusters to help you locate clusters that are using
excessive CPU or memory. You can also identify if you have ESXi hosts within the clusters that
are not evenly utilized. An administrator can then trigger activities such as workload balance or
set DRS to ensure that hot spots are eliminated.
Migrate to vSAN
The Migrate to vSAN dashboard provides you with an easy way to move virtual machines from
existing storage to newly deployed vSAN storage.
You can use this dashboard to select non-vSAN datastores that might not serve the virtual
machine IO demand. By selecting the virtual machines on a given datastore, you can identify the
historical IO demand and the latency trends of a given virtual machine. You can then find a
suitable vSAN datastore which has the space and the performance characteristics to serve the
demand of this VM. You can move the virtual machine from the existing non-vSAN datastore to
the vSAN datastore. You can continue to watch the use patterns to see how the VM is served by
vSAN after you move the VM.
Operations Overview Dashboard
The Operations Overview dashboard provides you with a high-level view of objects which make
up your virtual environment. You can view an aggregate of the virtual machine growth trends
across the different data centers that vRealize Operations Manager monitors.
You can also view a list of all your data centers with inventory information about how many
clusters, hosts, and virtual machines you are running in each of your data centers. By selecting a
particular data center, you can narrow down on the areas of availability and performance. The
dashboard provides a trend of known issues in each of your data centers based on the alerts
which have triggered in the past.
You can also view a list of the top 15 virtual machines in the selected data center which might be
contending for resources.
n Environment Summary: Use this widget to view a summary of the overall inventory of your
environment.
n Select a Datacenter: Use this widget to select the data center for which you want to view
operational information. You can use the filter to narrow your list based on several
parameters. After you identify the data center you want to view, select it. The dashboard is
automatically populated with the relevant data.
n Cumulative Up-time of all Clusters: Use this widget to view the overall health of the clusters
in the data center you selected. The metric value is calculated based on the uptime of each
ESXi host, when you take into account one host as the HA host. If the number displayed is
less than 100%, it means that at least two hosts within the cluster were not operational for
that period.
VMware, Inc. 639

n Alert Volume (in selected DC): Use this widget to view the breakdown of alert trends based
on their criticality.
n Top-N: You can also view a list of 15 VMs that had the highest average CPU contention, the
highest use of memory, and the highest disk latency for the last 24 hours. To obtain specific
data, you can manually set the time to the time of the problem. To set the time, click the Edit
Widget icon from the title bar of the widget and edit the Period Length drop-down menu.
vSAN Operations Overview

The vSAN Operations Overview dashboard provides an aggregated view of the health and
performance of your vSAN clusters.
You can use this dashboard to get a complete view of your vSAN environment and what
components make up the environment. You can also view the growth trend of virtual machines
served by vSAN.
You can use the dashboard to understand the utilization and performance patterns for each of
your vSAN clusters by selecting one from the list that is provided. You can use this dashboard to
track vSAN properties such as hybrid or all flash, deduplication and compression, or a stretched
vSAN cluster.
You can view the historic performance, utilization, growth trends, and events related to vSAN,
with the current state.
You can identify the vSAN encryption status at cluster levels.

Optimize Dashboards
The Optimize group of dashboards include the Optimize Performance, Access Cost, and
Optimization History dashboards.
Assess Cost Dashboard
The Assess Cost dashboard gives you cost and reclaimable resources for your data centers and
clusters.
The Assess Cost dashboard belongs to the Optimize group of dashboards. This dashboard is
ideal for executives, finance, or others who are accountable for overall IT spend. It is also helpful
for identifying and planning cost optimization initiatives.
Any cost information shown in this dashboard is using the currency settings you select during
vRealize Operations Manager configuration.
The dashboard provides an overview of the cost and inventory for your environment, including
total cost of ownership and a total of the potential cost savings based on vRealize Operations
capacity engine recommendations.
Individual data centers are listed showing population details, cost information, and reclaimable
resources.
At the bottom of the dashboard, you can find the top 10 lists for the most expensive and least
expensive clusters in your environment. These lists include the total monthly cost and count of
hosts, datastores, and virtual machines. These lists can be helpful in identification of under-
utilized clusters by noting the number of virtual machines hosted relative to the monthly cluster
cost.
VMware, Inc. 640

Optimization History Dashboard

The Optimization History dashboard displays the results of optimization activity.
The Optimization History dashboard belongs to the Optimize group of dashboards. The
dashboard covers three optimization benefits; optimize performance, optimize capacity, and
optimize virtual machine placement.
Optimizing performance can be performed in vRealize Operations Manager using Workload

Optimization, or started on demand. The charts on this row show a box for each data center or
custom data center and the optimization recommendation. Green indicates an optimized data
center or custom data center. A red box means that optimization might be required, and a white
box means that optimization is not configured for that object.
For capacity optimization, this row provides a summary of the average VM cost per month, the
savings that can be achieved through reclaiming idle or powered off virtual machines, or deleting
old snapshots.
Virtual Machine Happiness is a term used to describe VMs that are getting the resources they
need, when they need them. You can also see recent vMotion activity related to vSphere's
Distributed Resource Scheduler, which together with vRealize Operations predictive DRS feature
makes sure your VMs are getting the resources they need. Workload placement vMotions are
also shown as Non-DRS Moves in the graph.
Optimize Performance Dashboard
The Optimize Performance dashboard helps you identify virtual machines that can be configured
to improve overall performance.
The capacity analytics engine intelligently calculates the settings for CPU and memory for virtual
machines to give you the best performance and accurate resource allocation for all workloads.
The dashboard organizes virtual machines by undersized - or virtual machines that are not being
served well - and oversized - which are virtual machines that are not using all allocated resources.
Both categories consider CPU and memory usage and provide recommendations for optimal
sizing.
Performance Troubleshooting Dashboards
The dashboards in the Performance Troubleshooting category cater to the administrators
responsible for managing the performance and availability of the virtual machines running in the
virtual infrastructure. This category runs you through a guided workflow to answer questions that
help you with the troubleshooting process. The dashboards in this category identify and isolate
problems that may impact your applications. They provide insight into the full stack to isolate and
identify the root cause quickly.
n Is the application performance impacted due to virtual infrastructure?
n Are noisy neighbors impacting multiple virtual machines and corresponding applications?
n Are there active alerts which require action?
n Are there any known issues impacting the performance and availability of a vSAN cluster?
VMware, Inc. 641

Troubleshoot a Cluster
The Troubleshoot a Cluster dashboard allows you to identify clusters that have issues and isolate
them easily.
You can use the search option to identify a cluster that has an issue. You can also sort the
clusters based on the number of active alerts.
After you select the cluster you want to work with, you can view a quick summary of the number
of hosts in that cluster and the VMs served by the cluster. The dashboard provides you with
current and past utilization trends and also known issues in the cluster in the form of alerts.
You can view the hierarchy of objects related to the cluster and review the status to identify if
the objects are impacted because of the current health of the cluster. You can quickly identify
any contention issues by looking at the maximum and average contention faced by the VMs on
the selected cluster. You can narrow down and view those VMs that have resource contention
and take specific steps to troubleshoot and resolve issues.
n Search for a cluster: Use this widget to select the cluster for which you want to view
performance details. You can use the filter to narrow your list based on several parameters.
After you identify the cluster you want to view, select it. The dashboard is automatically
n Is your cluster busy?: Use this widget to view the CPU and memory demand.
n Are there active alerts on your cluster: Use this widget to view only the critical alerts.
n Are the relatives healthy?: Use this widget to view the hierarchy of the objects related to the
cluster and if any of the objects are impacted.
n View the maximum and average CPU, memory, and disk latency for the VMs. If the VM faces
contention, it might mean that the underlying infrastructure does not have enough resources
to meet the needs of the VMs.
n View a list of VMs that face CPU, memory, and disk latency contention. You can then
troubleshoot and take steps to resolve the problem.
Troubleshoot a Datastore
The Troubleshoot a Datastore dashboard allows you to identify storage issues and act on them.
You can use the search option to identify a datastore that has an issue or you can identify a
datastore that has high latency as seen in red on the heat map. You can also sort all the
datastores with active alerts and troubleshoot the datastore with known issues.
You can select a datastore to see its current capacity and utilization with the number of VMs
served by that datastore. The metric charts help you view historical trends of key storage metrics
such as latency, outstanding IOs, and throughput.
The dashboard also lists the VMs served by the selected datastore and helps you analyze the
utilization and performance trends of those VMs. You can migrate the VMs to other datastores to
even out the IO load.
VMware, Inc. 642

n Search for a datastore: Use this widget to select the datastore for which you want to view
performance details. You can use the filter to narrow your list based on several parameters.
After you identify the datastore you want to view, select it. The dashboard is automatically
n Are there active alerts on your datastore: Use this widget to view only the critical alerts.
n Are the relatives healthy?: Use this widget to view the hierarchy of the objects related to the
datastore and if any of the objects are impacted.
n Is your datastore experiencing high latency? and Any outstanding disk I/Os?: Use these
widgets to view those datastores with high latency and outstanding disk I/O trends. Ideally,
your datastores must not have outstanding disk I/O.
n How many IOPS is your datastore serving and Latency trend for the I/Os done by the VM:
Use these widgets to view the current IOPS and latency of the VMs in the selected datastore.
n Use the other widgets in the dashboard to view trends for the selected datastore regarding
disk latency, IOPS, and throughput, VMs served by the datastore and I/O pattern of the
selected VM.
Troubleshoot a Host
The Troubleshoot a Host dashboard allows you to search for specific hosts or sort hosts with
active alerts. ESXi hosts are the main source of providing resources to a VM and are critical for
performance and availability.
To view the key properties of each host, select a host from the dashboard. You can ensure that
the host is configured according to the virtual infrastructure design. Any deviation from
standards might cause potential issues. You can use the dashboard to answer key questions
about current and past utilization and workload trends over the last week. You can also view if
the VMs served by the host are healthy.
Since the dashboard lists all the critical events that might affect the availability of the hosts, you
can view hardware faults associated with the host. You can view a list of the top 10 VMs that
demand CPU and memory resources from the identified host.
Troubleshoot a VM Dashboard
The Troubleshoot a VM dashboard helps an administrator to troubleshoot everyday issues in a
virtual infrastructure. While most of the IT issues in an organization are reported at the
application layer, you can use the guided workflow in this dashboard to help investigate an
ongoing or a suspected issue with the VMs supporting the impacted applications.
You can search for a VM by its name or you can sort the list of VMs with active alerts on them to
start your troubleshooting process. When you select a VM, you can view its key properties to
ensure that the VM is configured as per your virtual infrastructure design. Any deviation from
standards may cause potential issues. You can view known alerts and the workload trend of the
VM over the past week. You can also view if any of the resources serving the virtual machine
have an ongoing issue.
VMware, Inc. 643

The next step in the troubleshooting process allows you to eliminate the major symptoms which
might impact the performance or availability of a VM. You can use key metrics to find out if the
utilization patterns of the VMs are abnormal or if the VM is contending for basic resources such
as CPU, memory, or disk.
n Search for a VM: Use this widget to view all the VMs in the environment. You can select the
VM you want to troubleshoot. You can use the filter to narrow your list based on several
parameters, such as name, folder name, associated tag, host, or vCenter Server. After you
identify the VM you want to troubleshoot, select it. The dashboard is automatically populated
n About the VM: Use this widget to understand the context of the VM. This widget also lends
insights to analyze the root cause of the problem or potential mitigations.
n Are there active alerts on the VM?: Use this widget to view active alerts. To see noncritical
alerts, click the VM object.
n Is the VM working hard over the last week?: Use this widget to view the workload trend of
the VM for the last week.
n Are the relatives healthy?: Use this widget to view the ESXi host where the VM is now
running. This host might not be the ESXi host where the VM was running in the past. You can
view the remaining related objects and see whether they might contribute to the problem.
n Is the VMs demand spiking or abnormal?: Use this widget to identify spikes in the VM
demand for any of the resources such as CPU, memory, and network. Spikes in the demand
might indicate an abnormal behavior of the VM or that the VM is undersized. The memory
utilization is based on the Guest OS metric. It requires VMware Tools 10.0.0 or later and
vSphere 6 Update 1 or later. If you do not have these products, the metric remains blank.
n Is the VM facing contention?: Use this widget to identify whether the VM is facing
contention. If the VM is facing contention, the underlying infrastructure might not have
enough resources to meet the needs of the VM.
n Does the cluster serving the VM have contention?: Use this widget to view the trend for the
maximum CPU contention for a VM within the cluster. The trend might indicate a constant
contention within the cluster. If there is contention, you must troubleshoot the cluster as the
problem is no longer with the VM.
n Does the datastore serving the VM have latency?: Use this widget to help you correlate the
latency at the datastore level with the total latency of the VM. If the VM has latency spikes,
but the datastore does not have such spikes, it might indicate a problem with the VM. If the
datastore faces latency as well, you can troubleshoot to find out why the datastore has these
spikes.
n Parent Host and Parent Cluster: Use these widgets to view the host and the cluster on which
the VM resides.
Troubleshoot vSAN Dashboard
VMware, Inc. 644

The Troubleshoot vSAN dashboard helps you view the properties of your vSAN cluster and the
active alerts on the cluster components. The cluster components include hosts, disk groups, or
the vSAN datastores.
You can select a cluster from the dashboard and then list all the known problems with the objects
associated with the cluster. The objects include clusters, datastores, disk groups, physical disks,
and VMs served by the selected vSAN cluster.
You can view the key use and performance metrics from the dashboard. You can also view the
usage and performance trend of the cluster for the last 24 hours. You can also view historical
issues and analyze the host, disk group, or physical disk.
You can use the heat maps within the dashboard to answer questions about write buffer usage,
cache hit ratio, and host configurations. You can also use the heat maps to answer questions
about physical issues with capacity and cache disks, such as drive wear out, drive temperature,
and read-write errors.
n Search for a vSAN cluster: Use this widget to search vSAN clusters. You can view the details
of each vSAN cluster including the number of hosts, VMs, cache disks, capacity disks, and
cluster type are provided. You can also view if the vSAN cluster is dedupe and compression
enabled, and stretched.
n Any alerts on the cluster, hosts, VMs or disks?: Use this widget to view alerts on the cluster,
VMs, or disks in your environment.
n Are the relatives healthy?: Use this widget to view the health, risk, and efficiency of the
relatives. This widget also allows you to view the health of the datastore in a host and disks in
each disk group.
n Are outstanding I/Os high?: Use this widget to view the key performance metrics. The
widget indicates outstanding I/Os within 24 hours time period.
n Are VMs facing read latency?: Use this widget to view the read latency of VMs.
n Are VMs facing write latency?: Use this widget to view the write latency of VMs.
n Is the write buffer low?: Use this widget to view the usage of the write buffer on diskgroups
in a cluster.
n Are the hosts consistently configured?: Use this widget to view the participating hosts in the
selected cluster and to determine if the hosts are consistently configured.
n Cache Disks: Any hardware issues?: Use this widget to view the individual cache disks
measured against various metrics.
n Capacity Disks: Any hardware issues?: Use this widget to view the individual capacity disks
measured against various metrics.
Troubleshoot with Logs Dashboard

When vRealize Operations Manager is integrated with vRealize Log Insight, you can access the
custom dashboards and content pack dashboards from the Troubleshoot with Logs dashboard.
VMware, Inc. 645

You can view graphs of log events in your environment, or create custom sets of widgets to
access the information that matters most to you.
You can investigate an ongoing issue within your virtual infrastructure using the logs. You can
view predefined views created within vRealize Log Insight to answer questions from predefined
queries within vRealize Log Insight.
You can correlate metrics and queries within vRealize Operations Manager to troubleshoot issues
across applications and infrastructure.
For more information about the Troubleshoot with Logs dashboard, see the vRealize Log Insight
documentation.
To access the Troubleshoot with Logs dashboard from vRealize Operations Manager, you must
either:
n Configure the vRealize Log Insight adapter from the vRealize Operations Manager interface,
or
n Configure vRealize Operations Manager in vRealize Log Insight.
For more information on configuring, see Configuring vRealize Log Insight with vRealize
Operations Manager.
vRealize Automation Dashboards
With the vRealize Automation dashboards, you can monitor and troubleshoot objects in your
cloud infrastructure.
The following vRealize Automation solution dashboards are added to the predefined vRealize
Operations Manager dashboards:
n Application Overview
n Environment Overview
n Resource Consumption Overview
n Top-N
Application Overview Dashboard

You can use the widgets in the Application Overview dashboard to view the blueprint objects
and the blueprint deployment details.
You can use the Application Overview dashboard to view the hierarchy, the properties of the
blueprint and deployments, and the metric information.
n Blueprint List: Use this widget to view the blueprint objects in the environment.
n Blueprint Overview: Use this widget to view the relationship between the blueprint objects
and the deployment, virtual machines, cluster compute resources, and the datastore objects.
To find the deployment, virtual machine, and other related details, click the blueprint object.
n Blueprint Property List: Use this widget to view the properties of the blueprint object such as
the total cost, average deployment time, and the average cost of the blueprint object .
VMware, Inc. 646

n Deployment List: Use this widget to view the blueprint objects deployed in the environment.
n Deployment Property List: Use this widget to view the properties for the deployment object
such as the cost until date and the approval time for each deployment.
n Blueprint Deployment Info: Use this widget to select a metric. You can view the details in the
Metric Chart widget.
n Metric Chart: Use this widget to view the relevant data based on the metric you select in the
Blueprint Deployment Info widget.
n Virtual Machine: Use this widget to view VMs that belong to the deployment.
n Configured Users: Use this widget to view information about the user that the virtual machine
belongs to.
Environment Overview Dashboard

You can use the Environment Overview dashboard to view information about the tenants and the
related alerts.
You can use the Environment Overview dashboard to perform some of the following tasks:
n To view the active alerts on vCenter resources that are managed by vRealize Automation.
n Environment Summary. Use this widget to view the health of tenants, business groups,
virtual machines, blueprints, reservations, deployments, cluster compute resources and the
relationships between these objects. If you double-click an object in the Environment
Overview widget, you can view detailed information for the object.
n Tenant List. Use this widget to view the tenant objects available in the environment. You can
see a data grid with a list of objects in the inventory on which you can sort and search.
n Business Group List. Use this widget to view the business group objects available in the
environment. You can see a data grid with a list of objects in the inventory on which you can
sort and search. You can see a data grid with a list of objects in the inventory on which you
can sort and search.
n Configured Users. Use this widget to view the business group name and the user configured
for the business group.
n vRealize Automation Inventory. Use this widget to view the objects available for each
vRealize Automation solution that is deployed in the environment.
n vRealize Automation Managed Clusters. Use this widget to view the vCenter clusters which
are managed by vRealize Automation. You can see a data grid with a list of objects in the
inventory on which you can sort and search.
n Top Alerts. Alerts with the greatest significance on the selected objects it is configured to
monitor. The top alerts include a short description of alerts configured for the widget. The
alert name opens a secondary window from which you can link to the alert details. In the alert
details, you can begin resolving the alerts.
VMware, Inc. 647

Resource Consumption Overview Dashboard

You can use the widgets in the Resource Consumption Overview dashboard to view the
resources consumed by vRealize Automation on a vCenter Server.
You can use the Resource Consumption Overview dashboard widgets in several ways.
n Tenant List: Use this widget to view the tenant objects available in the environment. You can
see a data grid with a list of tenants objects in the inventory on which you can sort and
search.
n Business Group List: Use this widget to view the business group objects available in the
environment. You can see a data grid with a list of objects in the inventory on which you can
sort and search.
n Reservation List: Use this widget to view the reservation objects available in the environment.
You can see a data grid with a list of objects in the inventory on which you can sort and
search.
n Tenant Capacity: Use this widget to analyze the capacity of the tenant object.
n Business Group Capacity: Use this widget to view the memory, storage, and quota capacity
that is allocated, reserved, and free for each business group object.
n Reservation Capacity: Use this widget to view the memory, storage, and quota capacity that
is allocated, reserved, and free for each reservation object.
n Tenant Capacity Remaining: Use this widget to view the capacity constrained for a tenant
object.
n Business Group Capacity Remaining: Use this widget to view the capacity constrained for a
business group object.
n Reservation Capacity Remaining: Use this widget to view the capacity constrained for a
reservation object.
n Tenant Memory Trend: Use this widget to view and analyze a seven-day trend for the
memory allocated, reserved, and free for a tenant object.
n Tenant Storage Trend: Use this widget to view and analyze a seven-day trend for the
storage allocated, reserved, and free for a tenant object.
Top-N Dashboard
You can use the widgets in the Top-N dashboard to view the top results from analysis of
blueprints, business groups, and tenants that you select.
You can use the Top-N dashboard to perform some of the following tasks:
n To view the most popular blueprints, business groups, and tenants.
n To view the business groups that have the most critical alerts.
n Tenant with most critical alerts. Use this widget to view the top- five tenant objects that
have the most critical alerts.
VMware, Inc. 648

n Business Groups with most Critical Alerts. Use this widget to view the top-five business
group objects that have the most critical alerts.
n Tenant with most failed requests. Use this widget to view the top-five tenant objects that
have the most failed requests.
n Most popular deployed Tenant. Use this widget to view the top-five most popular deployed
tenant objects in the environment.
n Most popular deployed Business Group. Use this widget to view the top-five most popular
deployed business group objects in the environment.
n Most Popular Deployed Blueprints. Use this widget to view the top-five most popular
deployed blueprint objects in the environment.
n Most Popular Deployed Business Group (7 day trend). Use this widget to view graphical
trends that contain metrics for the virtual machine count that has been deployed the most for
the business group object over a seven-day period.
n Most Popular Deployed Blueprints (7 day trend). Use this widget to view graphical trends
that contain metrics for the virtual machine count that has been deployed the most for the
blueprint object over a seven-day period.
Inventory Dashboards
The three vSphere Inventory dashboards cater to the compute, network, and storage teams.
Using these dashboards, you can navigate through the environment and view your inventory and
their key metrics at a glance. The Network and Storage dashboards can be shared with the
network and storage teams respectively, giving them the necessary visibility, and increasing the
collaboration between teams.
While each dashboard is built specifically for each role, they share a common design. They have
a similar layout and are used in the same manner. This makes learning easier, especially in smaller
environments where the same team manages the full environment.
These dashboards help you answer several key questions:
n What is the topology of your vSphere compute inventory?
n What is the topology of your vSphere storage inventory?
n What is the topology of your vSphere network inventory?
vSphere Compute Inventory Dashboard

You can use the vSphere Compute Inventory Dashboard to browse through the topology of your
vSphere compute inventory which includes information related to vSphere world, vCenter Server,
data center, clusters, hosts, virtual machines, properties, and metrics.
You can select an object type to view the properties and metrics related to it. You can also view
the clusters, ESXi hosts, and virtual machines associated with the object.
n Properties: View the properties related to an object in the environment.
VMware, Inc. 649

n Metrics: View the metrics related to the object.
n Clusters: View the cluster functionality.
n ESXi Hosts: View the data related to the hosts.
n Virtual Machines: View VMs that belong to the object.
vSphere Network Inventory Dashboard

The vSphere Network Inventory Dashboard allows you to browse through the topology of your
vSphere network inventory which includes information related to vSphere world, vCenter Server,
data center, distributed vSwitches, distributed port groups, virtual machines, properties, and
metrics.
the distributed vSwitches, distributed port groups, virtual machines associated with it.
n Properties: View the properties related to the object in the environment.
n Metrics: View the metrics of the object.
n Distributed vSwitches: View details related to the distributed vSwitches.
n Distributed Port Groups: View data relevant to distributed port groups.
vSphere Storage Inventory Dashboard

The vSphere Storage Inventory dashboard allows you to browse through the topology of your
vSphere storage inventory which includes information related to vSphere world, vCenter Server,
data center, datastore clusters, datastores, virtual machines, properties, and metrics.
the datastore clusters, datastores, and virtual machines associated with it.
n Properties: View the properties related to the object in the environment.
n Metrics: View the metrics of the object.
n Datastore Clusters: View the datastore cluster functionality.
n Datastores: View the datastore functionality.
Create and Configure Dashboards

To view the status of all objects in vRealize Operations Manager, create a dashboard by adding
widgets or views. You can create and modify dashboards and configure them to meet your
environment needs.
VMware, Inc. 650

Procedure
1 In the menu, click Dashboards.
2 Click Actions > Create Dashboard to create and configure a dashboard.
3 Complete the following steps to:
a Enter a name for the dashboard.
Dashboard Name
b Add widgets or views to the dashboard.
Widget or View List Details
c Configure widget interactions.
Widget and View Interactions Details
d Create dashboard navigation.
Dashboard Navigation Details
4 Click Save.
5 Click Actions > Edit Dashboard to modify the dashboard.
Dashboard Name
The name and visualization of the dashboard as it appears on the vRealize Operations Manager
Home page.
Where You Add a Name in a Dashboard
To create or edit your dashboard, in the menu, click Dashboards. Click Actions > Create
Dashboard to add a dashboard or Actions > Edit Dashboard to edit the selected dashboard.
Enter a name in the New Dashboard field.
If you use a forward slash while entering a name, the forward slash acts as a group divider and
creates a folder with the specified name in the dashboards list if the name does not exist. For
example, if you name a dashboard clusters/hosts, the dashboard is named hosts under the
group clusters.
Widget or View List Details

vRealize Operations Manager provides a list of widgets or views that you can add to your
dashboard to monitor specific metrics and properties of objects in your environment.
Where You Add Widgets or Views to a Dashboard
To create or edit your dashboard, in the menu, click Dashboards. Click Actions > Create
Dashboard to add a dashboard or Actions > Edit Dashboard to edit the selected dashboard.
Toggle between the Views and Widgets option to view and add a widget or view to the
dashboard.
VMware, Inc. 651

How to Add Widgets or Views to a Dashboard

In the widgets list panel, you see a list of all the predefined vRealize Operations Manager widgets
or views. Drag the widget or view to the dashboard workspace in the upper panel.
To locate a widget or view, you can type the name or part of the name of a widget or view in the
Filter option. For example, when you enter top, the list is filtered to display the Top Alerts, Top-
N, and Topology Graph widgets. You can then select the widget you require.
Note The Topology Widget becomes unresponsive if the number of objects is more. You can
use Advanced Relationship Widget in such cases.
Most widgets or views must be configured individually to display information. For more
information about how to configure each widget, see Widgets.
How to Arrange Widgets or Views in a Dashboard
You can modify your dashboard layout to suit your needs. By default, the first widgets or views
that you add are automatically arranged horizontally wherever you place them.
n To position a widget or a view, drag the widget or view to the desired location in the layout.
Other widgets and views automatically rearrange to make room.
n To resize a widget or a view, drag the bottom right corner of the widget or the view.
Widget and View Interactions Details

You can connect widgets and views so that the information they show depends on each other.
Where You Create Widget and View Interactions
To create interactions for widgets or views in a dashboard, in the menu, click Dashboards. Click
Actions > Create Dashboard to add a dashboard or Actions > Edit Dashboard to edit the
selected dashboard. From the toolbar, click Show Interactions.
How to Create and Remove Widget Interactions
The list of available interactions depends on the widgets or views in the dashboard. Widgets and
views can provide, receive, and can both provide and receive interactions at the same time.
To create interactions, click Show Interactions. Click a provider plug and drag to the receiver.
You can also apply interactions from receiver to provider plugs. For more information about how
interactions work, see Widget Interactions.
To remove interactions, click on the interaction line and select Remove Interaction. You can also
click the provider plug and select Remove Interaction > <widget name>.
Dashboard Navigation Details

You can apply sections or context from one dashboard to another. You can connect widgets and
views to widgets and views on other dashboards to investigate problems or better analyze the
provided information.
VMware, Inc. 652

Where You Add Another Dashboard

To create dashboard navigation to a dashboard, in the menu, click Dashboards. Click Actions >
Create Dashboard to add a dashboard or Actions > Edit Dashboard to edit the selected
dashboard. In the dashboard workspace, click Show Interactions. From the Select Another
Dashboard drop-down menu, select the dashboard to which you want to navigate.
How Dashboard Navigation Works
You can create dashboard navigation only for provider widgets and views. The provider widget
or view sends information to the destination widget or view. When you create dashboard
navigation, the destination widgets or views are filtered based on the information type they can
receive.
How to Add a Dashboard Navigation to a Dashboard
The list of available dashboards for navigation depends on the available dashboards and the
widgets and views in the current dashboard. To add navigation, you can drag and drop from a
sender widget interaction plug to a receiver widget interaction plug. You can select more than
one applicable widget or view.
Note If a dashboard is unavailable for selection, it is unavailable for dashboard navigation.
The Dashboard Navigation icon ( ) appears in the top menu of each widget or view when a
dashboard navigation is available.
Managing Dashboards
You can change the order of the dashboard tabs, configure vRealize Operations Manager to
switch from one dashboard to another, create dashboard folders to group the dashboards in a
way that is meaningful to you, share a dashboard or dashboard template with one or more user
groups, and transfer selected dashboards to a new owner.
Reorder and Switch Dashboards

You can change the order of the dashboard tabs on your home page. You can configure vRealize
Operations Manager to switch from one dashboard to another. This feature is useful if you have
several dashboards that show different aspects of your enterprise's performance and you want
to look at each dashboard in turn.
Where You Configure a Dashboard Order and Automatic Switch
To reorder and configure a dashboard switch, in the menu, click Dashboards. Select Actions >
Manage Dashboards. Click the gear icon and select Reorder/Autoswitch Dashboards.
How You Reorder the Dashboards
The list shows the dashboards as they are ordered. Drag the dashboards up and down to change
their order on the home page.
How You Configure an Automatic Dashboard Switch

1 Double-click a dashboard from the list to configure.
VMware, Inc. 653

2 From the Auto Transition drop-down menus, select On.
3 Select the switch time interval in seconds.
4 Select the dashboard to switch to and click Update.
5 Click Save to save your changes.
On the home page, the current dashboard will switch to the dashboard that is defined after the
specified time interval.
Manage Summary Dashboards

The Summary tab provides you with an overview of the state of the selected object, group, or
application. You can change the Summary tab with a dashboard to get information specific to
your needs.
Where You Configure a Summary Tab Dashboard
To manage the summary dashboards, in the menu, click Dashboards. Select Actions > Manage
Dashboards. Click the gear icon and select Manage Summary Dashboards.
How You Manage the Summary Tab Dashboard
Table 4-153. Manage Summary Dashboards Options
Option Description
Adapter Type Adapter type for which you configure a summary

dashboard.
Filter Use a word search to limit the number of adapter types

that appear in the list.
Name List with all available objects.
Use Default icon Click to use vRealize Operations Manager default Summary
tab.
Detail Page Shows what kind of Summary tab you use for the selected
object.
Assign a Dashboard icon Click to view the Dashboard List dialog box that lists all the
available dashboards.
To change the Summary tab for an object, select the object in the left panel, click the Assign a
Dashboard icon. Select a dashboard for it from the Dashboard List dialog box and click OK. From
the Manage Summary Dashboards dialog box click Save. You see the dashboard you have
associated to the object type when you navigate to the Summary tab of the object details page.
Manage Dashboard Groups

You can create dashboard folders to group the dashboards in a way that is meaningful to you.
Where You Configure a Dashboard Group
To manage the dashboard groups, in the menu, click Dashboards. Select Actions > Manage
Dashboards. Click the gear icon and select Manage Dashboard Groups.
VMware, Inc. 654

How You Manage the Dashboard Groups

Table 4-154. Manage Dashboard Groups Options
Option Description
Dashboard Groups A hierarchy tree with all available group folders.
Dashboards List A list with all available dashboards.
To create a dashboard group folder, right-click the Dashboard Groups folder or another folder
and click Add. To add a dashboard, drag one from the Dashboards list to the folder.
Share Dashboards with Users

You can share a dashboard or dashboard template with one or more user groups. When you
share a dashboard, it becomes available to all the users in the user group that you select. The
dashboard appears the same to all the users who share it. If you edit a shared dashboard, the
dashboard changes for all users. Other users can only view a shared dashboard. They cannot
change it.
Where You Share a Dashboard From
To share a dashboard, in the menu, click Dashboards. Select Actions > Manage Dashboards.
Click the gear icon and select Share Dashboards.
Table 4-155. Share Dashboards Options

Option Description
Accounts Group All available groups with which you can share a dashboard.
Shared Dashboards All available dashboards and templates that you can share.
You can switch between dashboard tabs and dashboard
templates by clicking the Share Dashboard Tabs/
Templates icon.
How You Manage a Shared Dashboard Tab

To share a dashboard tab, navigate to the dashboard in the list of Shared Dashboards and drag it
to the group to share it with on the left.
To stop sharing a dashboard with a group, click that group on the left panel, navigate to the
dashboard in the right panel, and click the Stop Sharing icon above the list.
To stop sharing a dashboard with more than one group, click the Not Grouped name on the left
panel, navigate to the dashboard in the right panel, and click the Stop Sharing icon above the list.
Options for Sharing Dashboards

You can share predefined or custom dashboards using URLs, emails, and by copying the code to
embed the dashboard into confluence or other internal official web pages. You can also assign
and unassign a dashboard to specific user groups and export the dashboard configuration
details.
VMware, Inc. 655

When you use a non-authenticated shared URL, as a user you can open the dashboard in a new
browser session. If you have already logged into vRealize Operations Manager in another
session, you are redirected to this dashboard and the user authentication permissions apply. To
ensure that the non-authenticated URL opens the intended dashboard, as a user you must log
out from all existing user sessions.
The dashboard shared with the URL opens in a page where you can access all the widgets within
the dashboard and you can interact with the given widgets at the same time. A non-
authenticated dashboard however, does not allow you to browse to other areas of vRealize
Operations Manager.
Where You Can Access the Options to Share Dashboards
From the menu, select Dashboards. Click on an existing dashboard and then click the Share
Dashboard icon in the top right corner.
VMware, Inc. 656

Table 4-156. Options in the Share Dashboard Dialog Box

Option Description
URL Allows you to copy the tiny URL for the selected
dashboard.
n Set the expiry period for the link to 1 day, 1 week, 1
month, 3 Months, or Never Expire.
n Click Copy Link to copy the link to a new window from
where you can view the dashboard.
Note
n As a user, if you open a shared link and you are logged
into vRealize Operations Manager, you are navigated to
your default dashboard, instead of viewing the shared
one.
n As a user, if you log in to the same IP that was shared
with you previously, you cannot access the page with
the same browser.
n As a user, ensure that you have the following
permission: Dashboards > Dashboard Management >
Share (Public).
You can stop sharing a dashboard you had previously

shared. To stop sharing a dashboard, click the Unshare
Link option and enter the URL of the dashboard that you
want to stop sharing and click Unshare.
Authentication is not required to view the shared
dashboard.
Email Allows you to send an email with the URL details of the
dashboard, to a specific person.
month, 3 months, or Never Expire.
n Configure an SMTP instance. See Add a Standard Email
Plug-In for vRealize Operations Manager Outbound
Alerts.
n Enter an email address and click the Send Email button
to send an email with the URL details of the dashboard.
dashboard.
VMware, Inc. 657

Table 4-156. Options in the Share Dashboard Dialog Box (continued)

Option Description
Embed Provides an embedded code for the dashboard. You can

use this code to embed the dashboard in relevant
confluence pages that your company executives routinely
use and analyze.
month, 3 Months, or Never Expire.
Note
n If you embed a dashboard in the Text widget, the
widget does not display any data.
n When you open an HTML/confluence page with an
embedded dashboard from the same browser that you
have logged into vRealize Operations Manager, the
dashboard does not load.

dashboard.
Groups Allows you to assign and unassign a dashboard to specific

user groups.
n Select the group to which you want to grant dashboard
access from the drop-down menu and click Include.
You can include more than one dashboard.
n From the label, select the cross mark to unassign the
dashboard.
Log in to vRealize Operations Manager to view the shared
dashboard.
Export Allows you to export the dashboard configuration details.

Log in to vRealize Operations Manager to export/import a
dashboard.
Manage Widgets in Dashboards

You can replicate widgets multiple times in a dashboard by using the copy and paste
functionality.
Navigate to the dashboard from which you want to copy widgets. Select Actions > Edit
Dashboards. Select one or more widgets that you want to copy by clicking the title of the widget
and then select Actions > Copy Widget(s). Click Actions > Paste Widget(s) to paste one or more
widgets in the same dashboard.
To paste one or more widgets into another dashboard, exit the edit screen of the dashboard by
selecting Cancel. Navigate to the dashboard to which you want to paste one or more widgets
and select Actions > Edit Dashboards and then Actions > Paste Widget(s).
Views
vRealize Operations Manager provides several types of views. Each type of view helps you to
interpret metrics, properties, policies of various monitored objects including alerts, symptoms,
VMware, Inc. 658

and so on, from a different perspective. vRealize Operations Manager Views also show
information that the adapters in your environment provide.
You can configure vRealize Operations Manager views to show transformation, forecast, and
trend calculations.
n The transformation type determines how the values are aggregated.
n The trend option shows how the values tend to change, based on the historical, raw data.
The trend calculations depend on the transformation type and roll up interval.
n The forecast option shows what the future values can be, based on the trend calculations of
the historical data.
Create Views
(http://link.brightcove.com/services/player/bcpid2296383276001?
bctid=ref:video_create_view_vrop)
You can use vRealize Operations Manager views in different areas of vRealize Operations
Manager.
n To manage all views, in the menu, click Dashboards, and then in the left pane click Views.
n To see the data that a view provides for a specific object, navigate to that object, click the
Details tab, and click Views.
n To see the data that a view provides in your dashboard, add the View widget to the
dashboard. For more information, see View Widget.
n To have a link to a view in the Further Analysis section, select the Further Analysis option on
the view workspace visibility step.
Views and Reports Ownership

The default owner of all predefined views and templates is System. If you edit them, you become
the owner. If you want to keep the original predefined view or template, you have to clone it.
After you clone it, you become the owner of the clone.
The last user who edited a view, template, or schedule is the owner. For example, if you create a
view you are listed as its owner. If another user edits your view, that user becomes the owner
listed in the Owner column.
The user who imports the view or template is its owner, even if the view is initially created by
someone else. For example, User 1 creates a template and exports it. User 2 imports it in back,
the owner of the template becomes User 2.
The user who generated the report is its owner, regardless of who owns the template. If a report
is generated from a schedule, the user who created the schedule is the owner of the generated
report. For example, if User 1 creates a template and User 2 creates a schedule for this template,
the generated report owner is User 2.
VMware, Inc. 659

Views Overview
A view presents collected information for an object in a certain way depending on the view type.
Each type of view helps you to interpret metrics, properties, policies of various monitored objects
including alerts, symptoms, and so on, from a different perspective.
How Do You Access the View Page
In the menu, click Dashboards, and then in the left pane click Views to access the Views page.
On the Views page you can create, edit, delete, clone, export, and import views from the toolbar.
You can order the listed views by name, type, description, subject, or owner. You can limit the
views list by adding a filter from the upper-right corner of the panel.
Table 4-157. Filter Groups

Filter Group Description
Name Filter by the view name. For example, type my view to list
all views that contain the my view phrase in their name.
Type Filter by the view type.
Description Filter by the view description. For example, type my view

to list all views that contain the my view phrase in their
description.
Subject Filter by the subject.
Owner Filter by the owner.
Manage and Preview Views

You can preview a view by clicking a view from the Views page. Add an object if necessary, by
clicking Select preview source from the upper-right corner of the Views page. The preview of
the view appears just below the Views option in the right pane.
To edit, delete, create, and manage a view, from the specific view preview page, select Actions
and then the relevant option from the drop-down menu.
Views are also categorized and listed in the All Views menu based on the type of view and
subject. You can access the All Views menu from a specific view preview page.
Views and Reports Ownership

The owner of views, reports, or templates might change over time.
The default owner of all predefined views and templates is System. If you edit them, you become
the owner. If you want to keep the original predefined view or template, you have to clone it.
After you clone it, you become the owner of the clone.
The last user who edited a view, template, or schedule is the owner. For example, if you create a
view you are listed as its owner. If another user edits your view, that user becomes the owner
listed in the Owner column.
VMware, Inc. 660

The user who imports the view or template is its owner, even if the view is initially created by
someone else. For example, User 1 creates a template and exports it. User 2 imports it in back,
the owner of the template becomes User 2.
The user who generated the report is its owner, regardless of who owns the template. If a report
is generated from a schedule, the user who created the schedule is the owner of the generated
report. For example, if User 1 creates a template and User 2 creates a schedule for this template,
the generated report owner is User 2.
Create and Configure a View

To collect and display information for a specific object, you can create a custom view.
Procedure
1 In the menu, click Dashboards, and then in the left pane click Views.
2 Click the Create View icon to create a view.
3 Complete the steps in the left pane to:
a Enter a name and description for the view.
Name and Description Details
b Change the presentation of a view.
Presentation Details
c Select the base object type for a view.
Subjects Details
d Add data to a view.
Data Details
e Change the visibility of a view.
Visibility Details
4 Click Save.
5 From the Views page, click the Edit View icon to modify the view.

The name and description of the view as they appear in the list of views on the Views page.
To add a name and description to a view, in the menu, click Dashboards, and then in the left
pane click Views. On the Views toolbar, click the plus sign to add a view or the pencil to edit the
selected view. In the workspace, on the left, click Name and Description.
VMware, Inc. 661

Table 4-158. Name and Description Options in the View Workspace

Option Description
Name Name of the view as it appears on the Views page.
Description Description of the view.
Presentation Details
A presentation is a way the collected information for the object is presented. Each type of view
helps you to interpret metrics and properties from a different perspective.
To change the presentation of a view, in the menu, click Dashboards, and then in the left pane
click Views. On the Views toolbar, click the plus sign to add a view or the pencil to edit the
selected view. In the workspace, on the left, click Presentation. If you create a view, complete
the required previous steps.
Table 4-159. Presentation Options in the View Workspace

View Type Description
List Provides tabular data about specific objects in the

monitored environment.
Column count is limited to 25 in a PDF report and 50 in a
CSV report. Page count is unlimited.
Summary Provides tabular data about the use of resources in the

monitored environment.
Trend Uses historic data to generate trends and forecasts for

resource use and availability in the monitored
environment.
Distribution Provides aggregated data about resource distribution in

the monitored environment.
When you add a distribution type of View to a
dashboard, you can click a section of the pie chart or on
one of the bars in the bar chart to view the list of objects
filtered by the selected segment.
Text Inserts the provided text. The text can be dynamic and
contain metrics and properties.
You can format text to increase or decrease the font size,
change the font color, highlight text, and align text to the
left, right, or center. You can also make the selected text
appear bold, in italics, or underlined.
By default the text view is available only for report
template creation and modification. You can change this
on the Visibility step of the view workspace.
Image Inserts a static image.

By default the image view is available only for report
template creation and modification. You can change this
on the Visibility step of the view workspace.
VMware, Inc. 662

You can see a live preview of the view type when you select a subject and data, and Select
preview source.
How to Configure the Presentation of a View
Some of the view presentations have specific configuration settings.
Table 4-160. Presentation Configuration Options in the View Workspace

View Type Configuration Description
List n Select the number of items per page. Each item is one
row and its metrics and properties are the columns.
n Select the top results. Restricts the number of results.
For example, if you list all the clusters in a View,
selecting 10 in this option displays the top 10 clusters
with the relevant information. You can reduce the
number of rows for the purposes of reporting.
Summary Select the number of items per page. Each row is an

aggregated metric or property.
Trend Enter the maximum number of plot lines. Limits the output
in terms of the objects displayed in the live preview of the
view type on the left upper pane. The number you set as
the maximum number of plot lines determines the plot
lines.
For example, if you plot historical data and set the
maximum at 30 plot lines, then 30 objects are displayed. If
you plot historical, trend, and forecast lines, and set the
maximum to 30 plot lines, then only 10 objects are
displayed as each object has three plot lines.
Distribution Select the visualization of the distribution information in a

pie chart or a bar chart.
Select the distribution type, and configure the buckets
count and size.
To understand vRealize Operations Manager distribution
type, see View Distribution Type.
Coloring
Configuration Option Description
Colorize The colors of the slices in the pie chart are displayed in the
order of the colors in the color palette.
Select Color Select the color that you want the chart to appear in. If
there is more than one slice in a pie chart, the colors are
chosen sequentially from the color palette. In a bar chart,
the bars are all the same color.
Distribution Type
vRealize Operations Manager view distribution type provides aggregated data about resource
distribution in the monitored environment.
Dynamic distribution
VMware, Inc. 663

You specify in details how vRealize Operations Manager distributes the data in the buckets.
Table 4-161. Dynamic Distribution Configuration Options

Buckets Count The number of buckets to use in the data distribution.
Buckets Size Interval The bucket size is determined by the defined interval
divided by the specified number of buckets.
Buckets Size Logarithmic bucketing The bucket size is calculated to logarithmically increasing
sizes. This provides a continuous coverage of the whole
range with the specified number of buckets. The base of
the logarithmic sizing is determined by the given data.
Buckets Size Simple Max/Min bucketing The bucket size is divided equally between the measured
min and max values. This provides a continuous
coverage of the whole range with the specified number
of buckets.
Manual distribution
You specify the number of buckets and the minimum and maximum values of each bucket.
Discrete distribution
You specify the number of buckets in which vRealize Operations Manager distribute the data.
View Distribution Type
vRealize Operations Manager view distribution type provides aggregated data about resource
distribution in the monitored environment.
Visualization
You can choose to view the data as a pie chart or a bar chart. When you add a distribution
type of View to a dashboard, you can click on a section of the pie chart or on one of the bars
in the bar chart to view the list of objects filtered by the selected segment. You can select the
display colors for single or multi-colored charts.
Dynamic distribution
You specify in details how vRealize Operations Manager distributes the data in the buckets.
Table 4-162. Dynamic Distribution Configuration Options

Buckets Count The number of buckets to use in the data distribution.
Buckets Size Interval The bucket size is determined by the defined interval
divided by the specified number of buckets.
VMware, Inc. 664

Table 4-162. Dynamic Distribution Configuration Options (continued)

Buckets Size Logarithmic bucketing The bucket size is calculated to logarithmically increasing
sizes. This provides a continuous coverage of the whole
range with the specified number of buckets. The base of
the logarithmic sizing is determined by the given data.
Buckets Size Simple Max/Min bucketing The bucket size is divided equally between the measured
min and max values. This provides a continuous
coverage of the whole range with the specified number
of buckets.
Manual distribution
You specify the number of buckets and the minimum and maximum values of each bucket.
Discrete distribution
You specify the number of buckets in which vRealize Operations Manager distribute the data.
If you increase the number of buckets, you can see more detailed data.
Subjects Details
The subject is the base object type for which the view shows information.
To specify a subject for a view, in the menu, click Dashboards, and then in the left pane click
Views. On the Views toolbar, click the plus sign to add a view or the pencil to edit the selected
view. In the workspace, on the left, click Subjects. If you create a view, complete the required
previous steps.
The subject you specify determines where the view is applicable. If you select more than one
subject, the view is applicable for each of them. You can limit the level where the view appears
with the Blacklist option in the Visibility step.
View availability depends on the view configuration subject, inventory view, user permissions,
and view Visibility settings.
For list views with Symptom as a subject, the following columns can be sorted: Criticality Level,
Status, Object Type, Object Name, Created on, and Canceled on. You cannot sort the Triggered
On and Violation Info columns. If other symptom metrics exist, you cannot sort any of the
columns.
In a List view, you can group the results based on a parent object, by making a selection in the
Group By drop-down option. If you generate a report based on the list view for which a group
has been specified, the report displays group-based information for the selected object. You can
also view summary calculations for the group of objects in the report, along with the total
summary results for all the objects.
VMware, Inc. 665

Views Applicability
Views might not always appear where you expect them to. The main applicability of views
depends on the view subject and the inventory view.
List View
When you navigate through the environment tree, you can see the List view at the subjects
that you specify during the view configuration and at their object containers. Depending on
the inventory view, the List view might be missing at the object containers. For example, you
create a List view with subject Host System. When you go to Environment > vSphere Hosts
and Clusters > vSphere World, select a vCenter Server, and click the Details tab, you can see
your List view. If you go to Environment > vSphere Storage > vSphere World, select the
same vCenter Server, and click the Details tab, your List view is missing. Your List view with
subject Host System is missing because the object Host System is not included in the vSphere
Storage inventory view.
Summary View
When you navigate through the environment tree, you can see the Summary view at the
subjects that you specify during the view configuration and at their object containers.
Depending on the inventory view, the Summary view might be missing at the object
containers. For example, you create a Summary view with subject Datastore. When you go to
Environment > vSphere Storage > vSphere World, select a vCenter Server, and click the
Details tab, you can see your List view. If you go to Environment > vSphere Networking >
vSphere World, select the same vCenter Server, and click the Details tab, your Summary
view is missing. Your Summary view with subject datastore is missing because the object
Datastore is not included in the vSphere Networking inventory view.
Trend View
When you navigate through the environment tree, you can see the Trend view only at the
subjects that you specify during the view configuration. For example, you create a Trend
view with subject Virtual Machine. When you navigate to a virtual machine in the navigation
tree, you see your view.
Distribution View
When you navigate through the environment tree, you can see the Distribution view only at
the object containers of the subjects that you specify during the view configuration.
Depending on the inventory view, the Distribution view might be missing at the object
containers. For example, you create a Distribution view with subject Host System. When you
go to Environment > vSphere Hosts and Clusters > vSphere World, select a vCenter Server,
and click the Details tab, you can see your Distribution view. If you go to Environment >
vSphere Networking > vSphere World, select the same vCenter Server, and click the Details
tab, your Distribution view is missing. Your Distribution view with subject Host System is
missing because the object Host System is not included in the vSphere Networking inventory
view.
VMware, Inc. 666

Text View
When you navigate through the environment tree, you can see the Text view only at the
subjects that you specify during the view configuration. For example, you create a Text view
with subject vCenter Server. When you navigate to a vCenter Server in the navigation tree,
you see your view. If you did not specify a subject, you see your view for every subject in the
environment.
Image View
The Image view is applicable for every object in the environment.
Note Views applicability depends also on your user permissions and the view Visibility
configuration.
Data Details
The data definition process includes adding properties, metrics, policies, or data that adapters
provide to a view. These are the items by which vRealize Operations Manager collects, calculates,
and presents the information for the view.
To add data to a view, in the menu, click Dashboards, and then in the left pane click Views. On
the Views toolbar, click the plus sign to add a view or the pencil to edit the selected view. In the
workspace, on the left, click Data. If you create a view, complete the required previous steps.
How to Add Data to a View
If you selected more than one subject, specify the subject for which you add data. Double-click
the data from the tree in the left panel to add it to the view. For each subject the data available
to add might be different.
How to Configure the Data Transformation
The data configuration options depend on the view and data type that you select. Most of the
options are available for all views.
Table 4-163. Data Configuration Options

Metric name Default metric name.

Available for all views.
Metric label Customizable label as it appears in the view or report.

Units Depends on the added metric or property. You can select

in what unit to display the values. For example, for CPU|
Demand(MHz) from the Units drop-down menu, you can
change the value to Hz, KHz, or GHz. If you select Auto, the
scaling is set to a meaningful unit.
Sort order Orders the values in ascending or descending order.

Available for List view and Summary view.
VMware, Inc. 667

Table 4-163. Data Configuration Options (continued)

Transformation Determines what calculation method is applied on the raw

data. You can select the type of transformation:
n Minimum. The minimum value of the metric over the
selected time range.
n Maximum. The maximum value of the metric over the
n Average. The mean of all the metric values over the
n Sum. The sum of the metric values over the selected
time range.
n First. The first metric value for the selected time range.
n Last. The last value of a metric within the selected time
range. If you have selected Last as the transformation
in versions before vRealize Operations Manager 6.7,
and the end of specified time range is not before the
last five minutes, use the Current transformation.
n Current. The last available value of a metric if it was last
updated not before five collection cycles were
complete, otherwise it is null.
n Standard Deviation. The standard deviation of the
metric values.
n Metric Correlation. Displays the value when another
metric is at the minimum or maximum. For example,
displays the value for memory.usage when cpu.usage is
at a maximum.
n Forecast. Performs a regressive analysis and predicts
future values. Displays the last metric value of the
selected range.
n Percentile. Calculates the specified percentile for the
data range. For example, you can view the 95th
percentile, 99th percentile, and so on.
n Expression. Allows you to construct a mathematical
expression over already existing transformations using
minus, plus, multiplication, division, unary minus, unary
plus, and round brackets. For example,
sum/((max + min)/2). You can use the operands of
some of the existing transformations such as,
max, min, avg, sum, first, last, current. You cannot
use
standard deviation, forecast, metric correlation, and percentile
.
Available for all views, except Trend.
Timestamp Adds a timestamp when metrics and properties are added

or modified.
Available for List view and Minimum, Maximum, Current,
First, and Last transformations.
VMware, Inc. 668

Table 4-163. Data Configuration Options (continued)

Ranges for metric coloring You can associate colors to metrics by entering a
percentage, range, or specific state. For example, you can
enter Powered Off in the Red Bound field when you select
virtual machine as an object. You can set the colors only for
views and not for csv or pdf formats.
Data Series You can select whether to include historical data, trend of
historical data, and forecast for future time in the trend
view calculations.
Available for Trend view.
Series Roll up The time interval at which the data is rolled up. You can
select one of the available options. For example, if you
select Sum as a Transformation and 5 minutes as the roll-up
interval, then the system selects 5-minute interval values
and adds them.
This option is applicable to the Transformation
configuration option.
Threshold Lines You can set a threshold for a single metric:

n None. You have not set a threshold.
n By Symptom Definition. You can set a threshold value
based on a symptom definition.
n Custom. You can set the threshold value as Warning,
Critical, or Immediate. These options are available only
for the Custom option.
Available for Trend view.
How to Configure Time Settings

Use the time settings to select the time interval of data transformation. These options are
available for all view types, except Image.
You can set a time range for a past period or set a future date for the end of the time period.
When you select a future end date and no data is available, the view is populated by forecast
data.
Table 4-164. Time Settings Options

Time Range Mode In Basic mode, you can select date ranges.
In Advanced mode, you can select any combination of
relative or specific start and end dates.
Relative Date Range Select a relative date range of data transformation.

Available in Basic mode.
Specific Date Range Select a specific date range of data transformation.

VMware, Inc. 669

Table 4-164. Time Settings Options (continued)

Absolute Date Range Select a date or time range to view data for a time unit
such as a complete month or a week. For example, you can
run a report on the third of every month for the previous
month. Data from the first to the end of the previous month
is displayed as against data from the third of the previous
month to the third of the current month.
The units of time available are: Hours, Days, Weeks,
Months, and Years.
The locale settings of the system determine the start and
end of the unit. For example, weeks in most of the
European countries begin on Monday while in the United
States they begin on Sunday.
Relative Start Date Select a relative start date of data transformation.

Available in Advanced mode.
Relative End Date Select a relative end date of data transformation.

Specific Start Date Select a specific start date of data transformation.

Specific End Date Select a specific end date of data transformation.

Currently selected date range Displays the date or time range you selected. For example,
if you select a specific date range from 5/01/2016 to
5/18/2016, the following information is displayed: May 1,
2016 12:00:00 AM to May 18, 2016 11:55:00 PM.
How to Break Down Data

You can break down data in List views by adding interval or instance breakdown columns from
the Group By tab.
VMware, Inc. 670


Option Description
Add interval breakdown column (see data for column Select this option to see the data for the selected
settings) resources broken down in time intervals.
In the Data tab, select Interval Breakdown to configure the
column. You can enter a label and select a breakdown
interval for the time range.
Add instance breakdown column (see data for column Select this option to see the data for all instances of the
settings) selected resources.
In the Data tab, select Instance Name to configure the
column. You can enter a label and select a metric group to
break down all the instances in that group. Deselect Show
non-instance aggregate metric to display only the
separate instances. Deselect Show only instance name to
display the metric group name and instance name in the
instance breakdown column.
For example, you can create a view to display CPU usage
by selecting the metric CPU:0|Usage. If you add an
instance breakdown column, the column CPU:0|Usage
displays the usage of all CPU instances on separate rows
(0, 1, and so on). To avoid ambiguity, you can change the
metric label of CPU:0|Usage to Usage.
How to Add a Filter

The filter option allows you to add additional criteria when the view displays too much
information. For example, a list view shows information about the health of virtual machines.
From the Filter tab you add a risk metric less than 50%. Then the view shows the health of all
virtual machines with risk less than 50%.
To add filter to a view, select Content > Views in the left pane. On the Views toolbar, click the
plus sign to add a view or the pencil to edit the selected view. In the workspace, on the left, click
Data and click the Filter tab in the main panel. If you create a view, complete the required
previous steps.
Each subject has a separate filter box. For Alerts Rollup, Alert, and Symptom subjects not all
applicable metrics are supported for filtering.
Table 4-166. Filter Add Options

Option Description
Add Adds another criteria to the criteria set. The filter returns
results that match all the specified criteria.
Add another criteria Adds another criteria set. The filter returns results that
match one criteria set or another.
VMware, Inc. 671

How to Add a Summary Row or Column to a View

The summary option is available only for List and Summary views. It is mandatory for the
Summary views. You can add more than one summary row or column and configure each to
show different aggregations. In the summary configuration panel, you select the aggregation
method and what data to include or exclude from the calculations.
To add a summary row or column to a view, select Content > Views in the left pane. On the
Views toolbar, click the plus sign to add a view or the pencil to edit the selected view. In the
workspace, on the left, click Data and click the Summary tab in the main panel. If you create a
view, complete the required previous steps.
For the List view, the summary row shows aggregated information by the specified subjects.
For the Summary view, the summary column shows aggregated information by the items
provided on the Data tab.
Visibility Details
The view visibility defines where you can see a view in vRealize Operations Manager.
To change the visibility of a view, in the menu, click Dashboards, and then in the left pane click
Views. On the Views toolbar, click the plus sign to add a view or the pencil to edit the selected
view. In the workspace, on the left, click Visibility. If you create a new view, complete the
required previous steps.
Table 4-167. View Workspace Visibility Options

Option Description
Availability Select where in vRealize Operations Manager you want to

see this view. If you want to have the view available in a
dashboard, select the check box, add the View widget, and
configure it. You can also make the view available in report
templates and in the Detail tab of a specific object when
you select the specific check box.
Further Analysis Select the Compliance check box to make the view
available in the Compliance tab for a specific object.
Blacklist Select a subject level where you do not want to see this
view.
For example, you have a list view with subject virtual
machines. It is visible when you select any of its parent
objects. You add datacenter in the banned list. The view is
not visible anymore on datacenter level.
Editing, Cloning, and Deleting a View

You can edit, clone, and delete a view. Before you do, familiarize yourself with the consequences
of these actions.
When you edit a view, all changes are applied to the report templates that contain it.
When you clone a view, the changes that you make to the clone do not affect the source view.
VMware, Inc. 672

When you delete a view, it is removed from all the report templates that contain it.
User Scenario: Create, Run, Export, and Import a vRealize Operations Manager
View for Tracking Virtual Machines
As a virtual infrastructure administrator, you use vRealize Operations Manager to monitor several
environments. You must know the number of virtual machines on each vCenter Server instance.
You define a view to gather the information in a specific order and use it on all vRealize
Operations Manager environments.
Prerequisites
Verify that you have the necessary access rights to perform this task. Your vRealize Operations
Manager administrator can tell you which actions you can perform.
You will create a distribution view and run it on the main vRealize Operations Manager
environment. You will export the view and import it in another vRealize Operations Manager
instance.
Procedure
1 Create a vRealize Operations Manager View for Supervising Virtual Machines

To collect and display data about the number of virtual machines on a vCenter Server, you
create a custom view.
2 Run a vRealize Operations Manager View

To verify the view and capture a snapshot of information at any point, you run the view for a
specific object.
3 Export a vRealize Operations Manager View

To use a view in another vRealize Operations Manager, you export a content definition XML
file.
4 Import a vRealize Operations Manager View

To use views from other vRealize Operations Manager environments, you import a content
definition XML file.
Create a vRealize Operations Manager View for Supervising Virtual Machines

To collect and display data about the number of virtual machines on a vCenter Server, you create
a custom view.
Procedure
2 Click the plus sign to create a new view.
3 Enter Virtual Machines Distribution, the name for the view.
VMware, Inc. 673

4 Enter a meaningful description for the view.
For example, A view showing the distribution of virtual machines per hosts.
5 Click Presentation and select the Distribution view type.
The view type is the way the information is displayed.

a From the Visualization drop-down menu, select Pie Chart.
b From the Distribution Type configurations, select Discrete distribution.
Leave Max number of buckets deselected because you do not know the number of hosts
on each vCenter Server instance. If you specify a number of buckets and the hosts are
more than that number, one of the slices shows unspecified information labeled Others.
6 Click Subjects to select the object type that applies to the view.
a From the drop-down menu, select Host System.
The Distribution view is visible at the object containers of the subjects that you specify
during the view configuration.
7 Click Data and in the filter text box enter Total Number of VMs.
8 Select Summary > Total Number of VMs and double-click to add the metric.
9 Retain the default metric configurations and click Save.
Run a vRealize Operations Manager View

To verify the view and capture a snapshot of information at any point, you run the view for a
specific object.
Prerequisites
Procedure
2 In the left pane, navigate to a vCenter Server instance and click the Details tab.
All listed views are applicable for the vCenter Server instance.
3 From the All Filters drop-down menu on the left, select Type > Distribution.
You filter the views list to show only distribution type views.
4 Navigate to and click the Virtual Machines Distribution view.
The bottom pane shows the distribution view with information about this vCenter Server.
Each slice represents a host and the numbers on the far left show the number of virtual
machines.
VMware, Inc. 674

Export a vRealize Operations Manager View

To use a view in another vRealize Operations Manager, you export a content definition XML file.
If the exported view contains custom created metrics, such as what-if, supermetrics, or custom
adapter metrics, you must recreate them in the new environment.
Prerequisites
Procedure
2 Click the gear icon and select Export View.
3 In the list of views, navigate to and click the Virtual Machines Distribution view .
4 Select a location on your local system to save the XML file and click Save.
Import a vRealize Operations Manager View

To use views from other vRealize Operations Manager environments, you import a content
definition XML file.
Prerequisites
Procedure
2 Click the gear icon and select Import View.
3 Browse to select the Virtual Machines Distribution content definition XML file and click Import.
If the imported view contains custom created metrics, such as what-if, supermetrics, or
custom adapter metrics, you must recreate them in the new environment.
Note The imported view overwrites if a view with the same name exists. All report templates
that use the existing view are updated with the imported view.
Reports
A report is a scheduled snapshot of views and dashboards. You can create it to represent
objects and metrics. It can contain table of contents, cover page, and footer.
With the vRealize Operations Manager reporting functions, you can generate a report to capture
details related to current or predicted resource needs. You can download the report in a PDF or
CSV file format for future and offline needs.
VMware, Inc. 675

Create Reports
bctid=ref:video_reports_vrops)
Report Templates Tab

On the Report Templates tab you can create, edit, delete, clone, run, schedule, export, and
import templates.
In the menu, click Environment, and then in the left pane select an object and click Reports >
Report Templates to access the Reports Templates tab.
All templates that are applicable for the selected object are listed on the Report Templates tab.
You can order them by report name, subject, date they were modified, last run, or owner.
You can filter the templates list by adding a filter from the right side of the panel.
Table 4-168. Predefined Filter Groups

Name Filter by the template name. For example, you can list all
reports that contain my template in their name by typing
my template.
Subject Filter by another object. If the report contains more than

one view applicable for another type of object, you can
filter by those objects.
vSphere users must be logged in until the report generation is complete. If you log out or your
session expires, the report generation fails.
Note The maximum number of reports per template is 10. With every new generated report,
vRealize Operations Manager deletes the oldest report.
Generated Reports Tab

All reports that are generated for a selected object are listed on the Generated Reports tab.
In the menu, click Environment, and then in the left pane select an object and click Reports >
Generated Reports to access the Generated Reports tab.
You can order the reports by the date and time that they were created, the report name, the
owner, or their status. If the report is generated through a schedule, the owner is the user who
created the schedule.
Note The maximum number of reports per template is 10. With every new generated report,
You can filter the reports list by adding a filter from the right side of the panel.
VMware, Inc. 676


Report Name Filter by the report template name. For example, you can
list all reports that contain my template in their name by
typing my template.
Template Filter by the report template. You can select a template

from a list of templates applicable for this object.
Completion Date/Time Filter by the date, time, or time range.
Status Filter by the status of the report.

On each data node, only one report can be processed.
Therefore, reports that are queued can be moved to the
processed state only after the previous report on the
specific node has failed or completed. The maximum queue
time is restricted to 4 hours. After 4 hours, if processing of
the report has not started, the report is marked as failed.

filter by those objects.
You can download a report in a PDF or CSV format. You define the format that a report is
generated in the report template.
Create and Modify a Report Template

You create a report to generate a scheduled snapshot of views and dashboards. You can track
current resources and predict potential risks to the environment. You can schedule automated
reports at regular intervals.
Procedure
1 In the menu, click Dashboards, and then in the left pane click Reports.
2 On the Report Templates tab, click the New Template icon to create a template.
3 Complete the steps in the left pane to:
a Enter a name and description for the report template.
b Add a view or a dashboard.
Views and Dashboards Details
c Select an output for the report.
Formats Details
d Select the layout options.
Layout Options Details
4 Click Save.
VMware, Inc. 677

5 From the Report Templates tab, click Edit Template to modify the report template.

The name and description of the report template as they appear in the list of templates on the
Report Templates tab.
Where You Add Name and Description
To create or edit report templates, in the menu, click Dashboards, and then in the left pane click
Reports. On the Report Templates toolbar, click the New Template icon to add a template or the
Edit Template icon to edit the selected template. From the New Template or Edit Report
Template dialog box, in the workspace, on the left, click Name and Description.
Table 4-170. Name and Description Options in the Report Template Workspace
Option Description
Name Name of the template as it appears on the Report

Templates tab.
Description Description of the template.
Views and Dashboards Details

The report template contains views and dashboards. Views present collected information for an
object. Dashboards give a visual overview of the performance and state of objects in your virtual
infrastructure. You can combine different views and dashboards and order them to suit your
needs.
Where You Add Views and Dashboards
Template dialog box, in the workspace, on the left, click Views and Dashboards. If you create a
template, complete the required previous steps of the workspace.
How You Add Views and Dashboards

To add a view or a dashboard to your report template, select it from the list on the left pane and
drag it to the main panel. You can drag the views and dashboards in the main panel to reorder
them. You can select a portrait or landscape orientation for each view or dashboard from the
drop-down menu next to its title.
Table 4-171. Views and Dashboards Options in the Report Template Workspace
Option Description
Data type Select Views or Dashboards to display a list of available

views or dashboards that you can add to the template.
Create View Create a view directly from the template workspace. This
option is available when you select Views from the Data
type drop-down menu.
VMware, Inc. 678

Table 4-171. Views and Dashboards Options in the Report Template Workspace (continued)
Option Description
Edit View Edit a view directly from the template workspace. This
option is available when you select Views from the Data
type drop-down menu.
Create Dashboard Create a dashboard directly from the template workspace.

This option is available when you select Dashboards from
the Data type drop-down menu.
Edit Dashboard Edit a dashboard directly from the template workspace.

This option is available when you select Dashboards from
the Data type drop-down menu.
Search Search for views or dashboards by name. To see the

complete list of views or dashboards, delete the search
box contents and press Enter.
List of views List of the views that you can add to the template. This list
is available when you select Views from the Data type
drop-down menu.
List of dashboards List of the dashboards that you can add to the template.
This list is available when you select Dashboards from the
Data type drop-down menu.
Preview of views and dashboards In the main panel, you see a preview of the views and
dashboards that you add.
When you create a template in the context of an object
from the environment, you see a live preview of the views
and dashboards.
Colorization You can enable or disable a colorized PDF output for each
list view. This option is available from the right panel when
you select Views from the Data type drop-down menu.
Formats Details
The formats are the outputs in which you can generate the report.
Where You Add Formats
Template dialog box, in the workspace, on the left, click Formats to select a format for the report
template. If you create a template, complete the required previous steps of the workspace.
Table 4-172. Formats Options in the Report Template Workspace

Option Description
PDF With the PDF format, you can read the reports, either on or
off line. This format provides a page-by-page view of the
reports, as they appear in printed form.
CSV In the CSV format, the data is in a structured table of lists.
VMware, Inc. 679

Layout Options Details

The report template can contain layout options such as a cover page, table of contents, and
footer.
Where You Add Layout Options
Template dialog box, in the workspace, on the left, click Layout Options. If you create a
template, complete the required previous steps of the template.
Table 4-173. Layout Options in the Report Template Workspace

Option Description
Cover Page Can contain an image up to 5 MB.

The default report size is 8.5 inches by 11 inches. The image
is resized to fit the report front page.
Table of contents Provides a list of the template parts, organized in the order
of their appearance in the report.
Footer Includes the date when the report is created, a note that
the report is created by VMware vRealize Operations
Manager, and page number.
Add a Network Share Plug-In for vRealize Operations Manager Reports

You add a Network Share plug-in when you want to configure vRealize Operations Manager to
send reports to a shared location. The Network Share plug-in supports only SMB version 2.1. Note
that SMB version 1.0 is not supported.
Prerequisites
Verify that you have read, write, and delete permissions to the network share location.
Procedure
Settings.
3 From the Plug-In Type drop-down menu, select Network Share Plug-in.
notification rules.
VMware, Inc. 680

5 Configure the Network Share options appropriate for your environment.
Option Description
Domain Your shared network domain address.
User Name The domain user account that is used to connect to the network.
Password The password for the domain user account.
Network share root The path to the root folder where you want to save the reports. You can
specify subfolders for each report when you configure the schedule
publication.
You must enter an IP address. For example, \\IP_address\ShareRoot. You
can use the host name instead of the IP address if the host name is resolved
to an IPv4 when accessed from the vRealize Operations Manager host.
Note Verify that the root destination folder exists. If the folder is missing,
the Network Share plug-in logs an error after 5 unsuccessful attempts.
6 Click Test to verify the specified paths, credentials, and permissions.
The test might take up to a minute.
7 Click Save.
The outbound service for this plug-in starts automatically.
8 (Optional) To stop an outbound service, select an instance and click Disable on the toolbar.
Results
This instance of the Network Share plug-in is configured and running.
What to do next
Create a report schedule and configure it to send reports to your shared folder. See Schedule
Reports Overview.
Report Templates Overview

The report template contains views and dashboards. Views present collected information for an
object. Dashboards give a visual overview of the performance and state of objects in your virtual
infrastructure. You can combine different views and dashboards and order them to suit your
needs.
In the menu, click Dashboards, and then in the left pane select Reports > Report Templates to
access the Report Templates tab.
On the Report Templates tab, you can create, edit, delete, clone, run, schedule, export, and
import templates.
The listed templates are user-defined and predefined by vRealize Operations Manager. You can
order them by template name, subject, date they were modified, last run, or owner. For each
template, you can see the number of generated reports and schedules.
VMware, Inc. 681

You can filter the templates list by adding a filter from the right side of the panel.

Name Filter by the template name. For example, type

my template to list all reports that contain the my template
phrase in their name.

filter by the other objects.
The maximum number of reports per template is 10. After the tenth report is generated, vRealize
Operations Manager deletes the oldest report.
Generated Reports Overview

A report is a scheduled snapshot of views and dashboards. It presents data in downloadable
formats.
In the menu, click Dashboards, and then in the left pane select Reports > Generated Reports to
access the Generated Reports tab.
The list contains all generated reports. You can order them by the date and time they were
created, report name, owner, or status. If the report is generated through a schedule, the owner
is the user who created the schedule.
Note The maximum number of reports per template is 10. After the tenth report is generated,
You can filter the reports list by adding a filter from the upper-right corner of the panel.

Report Name Filter by the report template name. For example, type
my template to list all reports that contain the my template
phrase in their name.
Template Filter by the report template. You can select a template

from a list of templates applicable for this object.
Completion Date/Time Filter by the date, time, or time range.

filter by that second object.
Status Filter by the status of the report.
You can download a report in a PDF or CSV format. You define the format that a report is
generated in the report template.
VMware, Inc. 682

If you log in to vRealize Operations Manager with vCenter Server credentials and generate a
report, the generated report is always blank.
Generate a Report
To generate a report, use a report template.
Prerequisites
Create a report template.
Procedure
2 In the left pane, navigate to the relevant object.
3 Click the Reports tab and click Report Templates.
The listed report templates are associated with the current object.
4 Navigate to the relevant report template and click the Run Template icon.
Results
The report is generated and listed on the Generated Reports tab.
What to do next
Download the generated report and verify the output.
Download a Report
To verify that the information appears as expected, you download the generated report.
Prerequisites
Generate a report.
Procedure
2 In the left pane, navigate to the object for which you want to download a report.
3 Click the Reports tab and click Generated Reports.
The listed reports are generated for the current object.
4 Click the PDF ( ) icon to save the report.
Results
vRealize Operations Manager saves the report file to the location you selected.
VMware, Inc. 683

What to do next
Schedule a report generation and set the email options, so your team receives the report.
Schedule Reports Overview

The schedule of a report is the time and recurrence of a report generation.
Where Do You Schedule a Report

To schedule a report generation, in the menu, click Environment, and then in the left pane
navigate to an object and click the Reports tab. Select a template to schedule, and click the gear
icon > Schedule report. To edit the schedule of a report, click the Schedules link of a report
from the Report Templates tab, and then from the Scheduled Reports dialog box, click Edit
Schedule.
How Do You Schedule a Report

Table 4-176. Schedule Report Options
Option Description
Recurrence Schedule a report to run automatically at regular intervals.
Publishing Email a generated report to a predefined email group or to

a network shared location. For more information about
how to set up and configure the email options, see Add a
Standard Email Plug-In for vRealize Operations Manager
Outbound Alerts.
Save a generated report to an external location. For more
information about how to configure an external location,
see Add a Network Share Plug-In for vRealize Operations
Manager Reports
You can add a relative path to upload the report to a
predefined subfolder of the Network Share Root folder. For
example, to upload the report to the share host C:/
documents/uploadedReports/SubFolder1, in the Relative
Path text box, enter SubFolder1. To upload the report to
the Network Share Root folder, leave the Relative Path
text box empty.
Note Only users created in vRealize Operations Manager can add and edit report schedules.
Table 4-177. Scheduled Reports Toolbar Options

Options Description
New Schedule You can create a schedule for the report.
Edit Schedule You can edit an existing report schedule.
Delete Schedule You can delete an existing report schedule.
Transport Report Schedule You can assign a new owner for the selected report
schedule. You can select a target user from the Transfer
Report Schedules dialog box.
VMware, Inc. 684

Schedule a Report
To generate a report on a selected date, time, and recurrence, you create a schedule for the
report template. You set the email options to send the generated report to your team.
The date range for the generated report is based on the time when vRealize Operations Manager
generates the report and not on the time when you schedule the report or when vRealize
Operations Manager places the report in the queue.
Prerequisites
n Download the generated report to verify the output.
n To enable sending email reports, you must have configured Outbound Alert Settings. See
Notifications .
Procedure
2 In the left pane, navigate to the object.
3 Click the Reports tab and click Report Templates.
4 Select the relevant report template from the list.
5 Click the gear icon ( ) and select Schedule report.
6 Select an object and click Next.
7 Select the time zone, date, hour, and minutes (in the range of 0, 15, 30, and 45 minutes) to
start the report generation.
vRealize Operations Manager generates the scheduled reports in sequential order.

Generating a report can take several hours. This process might delay the start time of a
report when the previous report takes an extended period of time.
8 From the Recurrence drop-down menu, select one of the following options for report
generation:
Option Description
Daily You can set the periodicity in days. For example, you can set report
generation to every two days.
Weekly You can set the periodicity in weeks. For example, you can set report
generation to every two weeks on Monday.
Monthly You can set the periodicity in months.
VMware, Inc. 685

9 Select the Email report check box to send an email with the generated report.
a In the Email addresses text box, enter the email addresses that must receive the report.
You can also add email addresses in the CC list and BCC list.
b Select an outbound rule.
An email is sent according to this schedule every time a report is generated.
10 Save a generated report to an external location.
11 You can add a relative path to upload the report to a predefined subfolder of the Network
Share Root folder.
To upload the report to the Network Share Root folder, leave the Relative Path text box
empty.
12 Click Finish.
What to do next
You can edit, clone, and delete report templates. Before you do, familiarize yourself with the
consequences of these actions.
When you edit a report template and delete it, all reports generated from the original and the
edited templates are deleted. When you clone a report template, the changes that you make to
the clone do not affect the source template. When you delete a report template, all generated
reports are also deleted.
Upload a Default Cover Page Image for Reports

You can upload a common default image for the cover page of reports. You do not have to
upload a cover page for each report. The cover pages of predefined reports are modified when
you use this option. The cover pages of user-defined reports do not change.
Where Do You Upload a Default Cover Page Image for Reports

To upload a default cover page for reports, in the menu, click Environment, and then in the left
pane navigate to an object and click the Reports tab. Click the gear icon and select Change
default cover image.
How Do You Upload a Default Cover Page Image for Reports

Browse for the image that you want to add to the cover page and click Save. You can also use
the default product image that is available.
Configuring Administration Settings

After vRealize Operations Manager is installed and configured, you can use administration
settings to manage your environment. You find most administration settings under the
Administration selection of the vRealize Operations Manager interface.
VMware, Inc. 686

vRealize Operations Manager License Keys

To activate vRealize Operations Manager monitoring , you add licenses at installation or later.
You track licenses so that you know what vRealize Operations Manager may monitor and when
your licenses expire. A new license key is required for vRealize Operations Manager 7.0 and later
versions. All license keys except vSOM Enterprise Plus and its add-ons are invalidated. The
product will work in evaluation mode until a new valid license key is installed. After you log in to
the user interface of vRealize Operations Manager, if you see that you are using an evaluation
license, consider applying for a new license before the end of the 60-day evaluation period.
You can obtain the new license keys from the MyVMware portal.
Note If you added new licenses when you upgraded to vRealize Operations Manager 7.0, you
may skip this step.
How License Keys Work

License keys activate the solution or product and are available in varying levels. Higher levels
typically allow vRealize Operations Manager to monitor more objects.
Where You Find the License Keys

1 In the menu, click Administration, and in the left pane click Management > Licensing.
2 Click the License Keys tab.
License Key Options

The options include toolbar and data grid options.
Use the toolbar options to add, edit, or remove items.
Table 4-178. License Key Toolbar Options

Option Description
Add Select a solution or product, and enter and validate a

license key for it.
Delete Remove a license key.
Refresh Update the list of keys.
Use the data grid options to view item details.
Table 4-179. License Key Data Grid Options

Option Description
Product or Solution Name of the product or solution associated with the key
License Type Level of the license
License Capacity Number of objects that the license allows the product to
monitor
VMware, Inc. 687

Table 4-179. License Key Data Grid Options (continued)

Option Description
License Usage Number of monitored objects that count against the

capacity. If you have an unlimited capacity, this number is
zero (0).
Status Indicates whether the license is currently valid
Expiry Date and time when the license expires
License Information (below) Details for the selected license key
Overview Solution or product, expiration, capacity, type, and use of

the selected license key
Associated License Groups License groups that this key is a member of, and the
number of objects in the groups
vRealize Operations Manager License Groups

Like other vRealize Operations Manager groups, you create a license group of objects as a way
of gathering those objects for data collection. In this case, you are associating the objects with a
product license.
How License Groups Work

License groups require that you select one or more keys that you already added for solution or
product activation, and add objects as members to a custom group for those licenses. You might,
for example, want to add objects into groups that are associated with a particular level of license
key, and monitor or manage by level of key in order to control licensing costs.
Where You Find the License Groups

1 In the menu, click Administration, and then in the left pane click Management > Licensing.
2 Click the License Groups tab.
License Groups
vCloud Suite
Host CPU-based licenses applied to an object type "Host system" for a given set of clusters.
When you apply a CPU license to a group containing Hosts, the VMs on the Hosts will still
show "License is invalid" watermark.
VM Licenses
VMware, Inc. 688

VM based licenses applied to an object type "Virtual Machine" for all other VMs except those
on hosts licensed with vCloud Suite. When you apply a VM license key to Virtual Machines,
the Hosts on which those VMs run will still show the "License is invalid" watermark.
Note In vRealize Operations Manager, it is possible to mix Operating System Instance (OSI) and
CPU based licenses. By mixing difference kind of licenses, you will need to perform extra
configurations, like creating separate license groups for each type of license keys (one for CPU
and one for OSI (VM)). It is recommended that you use non overlapping exclusive Licensing
Groups to have the best advantage when you mix OSI (VM) and CPU licensing. However, in
vRealize Operations Manager you cannot mix core and standard license with any other advanced
and enterprise licenses.
Dynamic
Use dynamic membership criteria, not static "Always include/exclude" lists to avoid manual
maintenance of license groups.
Note When the license is applied to the respective Object type of each License key, the related
objects (parent or children) are also going to have to be included in membership for the License
Group. License in invalid" watermark appears in vRealize Operations Manager 6.6 and later. For
more information, see the following KB article 51556.
License Group Options

The license group options include toolbar and data grid options.
Table 4-180. License Group Toolbar Options

Option Description
Add Launch a wizard to select licenses and objects, to create a

new license group.
You can also associate the license group with a monitoring
policy.
Edit Launch a wizard to select licenses and objects, to change a

license group.
You can also associate the license group with a monitoring
policy.
Delete Remove a license group.
Table 4-181. License Group Data Grid Options

Option Description
License Group Name of the license group
Total Members Number of objects in the license group
VMware, Inc. 689

Table 4-181. License Group Data Grid Options (continued)

Option Description
Licensable Usage Number of objects in the group that count against the
license in order to monitor them. If you have a license for
unlimited object monitoring, this number is zero (0).
License Group Information (below) Details for the selected license group
Overview Name, license serial number, and number of keys

associated with the selected license group
Members List of objects associated with the selected license group
vRealize Operations Manager Maintenance Schedules

Maintenance schedules identify objects that are in maintenance mode at specific times, which
prevents vRealize Operations Manager from showing misleading data based on those objects
being offline or in other unusual states because of maintenance.
Many objects in the enterprise might be intentionally taken offline. For example, a server might
be deactivated to update software. If vRealize Operations Manager collects metrics when an
object is offline, it might generate incorrect anomalies and alerts that affect the data for setting
dynamic thresholds for the object attributes. When an object is identified as being in
maintenance mode, vRealize Operations Manager does not collect metrics from the object or
generate anomalies or alerts for it. In addition, vRealize Operations Manager cancels any active
symptoms and alerts for the object.
If an object undergoes maintenance at fixed intervals, you can create a maintenance schedule
and assign it to the object. For example, you can put an object in maintenance mode from
midnight until 3 a.m. each Tuesday night. You can also manually put an object in maintenance
mode, either indefinitely or for a specified period of time. These methods are not mutually
exclusive. You can manually put an object in maintenance mode, or take it out of maintenance
mode, even it if has an assigned maintenance schedule
Note When you perform maintenance operations, it is good practice to stop the End Point
Operations Management agent and to restart it after the maintenance is complete to avoid
unnecessary system overhead.
How Maintenance Schedules Work

Maintenance schedules require that you select the days and time-of-day when updates or other
object maintenance occurs. Note that creating a maintenance schedule does not activate the
schedule. A maintenance schedule must be part of a policy before the schedule can take effect.
Where You Find the Maintenance Schedules

In the menu, click Administration, and then in the left pane click Configuration > Maintenance
Schedules .
VMware, Inc. 690

Table 4-182. Maintenance Schedule Toolbar Options

Option Description
Add Open a window in which you can select the maintenance

schedule settings for a new schedule.
Edit Open a window in which you can change the maintenance

schedule settings for an existing schedule.
Delete Remove the selected maintenance schedule.
Manage Maintenance Schedules

Add or edit a maintenance schedule to take an object offline. vRealize Operations Manager does
not collect data from an object that is offline.
Where You Find Manage Maintenance Schedules

1 In the menu, click Administration, and then in the left pane click Configuration > Maintenance
Schedules.
2 Click the plus sign to add a maintenance schedule or the pencil to edit the selected object.
Table 4-183. Manage Maintenance Schedule Add or Edit Options

Option Description
Schedule Name Name that describes the maintenance schedule
Time Zone Time zone in which you are currently located
Days Number of days the maintenance period covers
Recurrence Specify a maintenance schedule to run over a selected

period
n Once
n Daily
n Weekly
n Monthly
Expire after The number of times the schedule is run
Expire on The date upon which the schedule stops running
Managing Users and Access Control in vRealize Operations Manager

To ensure security of the objects in your vRealize Operations Manager instance, as a system
administrator you can manage all aspects of user access control. You create user accounts,
assign each user to be a member of one or more user groups, and assign roles to each user or
user group to set their privileges.
VMware, Inc. 691

Users must have privileges to access specific features in the vRealize Operations Manager user
interface. Access control is defined by assigning privileges to both users and objects. You can
assign one or more roles to users, and enable them to perform a range of different actions on the
same types of objects. For example, you can assign a user with the privileges to delete a virtual
machine, and assign the same user with read-only privileges for another virtual machine.
User Access Control

You can authenticate users in vRealize Operations Manager in several ways.
n Create local user accounts in vRealize Operations Manager.
n Use VMware vCenter Server users. After the vCenter Server is registered with vRealize
Operations Manager, configure the vCenter Server user options in the vRealize Operations
Manager global settings to enable a vCenter Server user to log in to vRealize Operations
Manager. When logged into vRealize Operations Manager, vCenter Server users access
objects according to their vCenter Server-assigned permissions.
n Add an authentication source to authenticate imported users and user group information that
resides on another machine.
n Use LDAP to import users or user groups from an LDAP server. LDAP users can use their
LDAP credentials to log in to vRealize Operations Manager.
n Create a single sign-on source and import users and user groups from a single sign-on
server. Single sign-on users can use their single sign-on credentials to log in to vRealize
Operations Manager and vCenter Server. You can also use Active Directory through
single sign-on by configuring the Active Directory through single sign-on and adding the
single sign-on source to vRealize Operations Manager.
User Preferences
To determine the display options for vRealize Operations Manager, such as colors for the display
and health chart, the number of metrics and groups to display, and whether to synchronize
system time with the host machine, you configure the user preferences on the top toolbar.
Users of vRealize Operations Manager

Each user has an account to authenticate them when they log in to vRealize Operations Manager.
The accounts of local users and LDAP users are visible in the vRealize Operations Manager user
interface when they are set up. The accounts of vCenter Server and single sign-on users only
appear in the user interface after a user logs in for the first time. Each user can be assigned one
or more roles, and can be an authenticated member of one or more user groups.
Local Users in vRealize Operations Manager

When you create user accounts in a local vRealize Operations Manager instance, vRealize
Operations Manager stores the credentials for those accounts in its global database, and
authenticates the account user locally.
VMware, Inc. 692

Each user account must have a unique identity, and can include any associated user preferences.
If you are logging in to vRealize Operations Manager as a local user, and on occasion receive an
invalid password message, try the following workaround. In the Login page, change the
Authentication Source to All vCenter Servers, change it back to Local Users, and log in again.
vCenter Server Users in vRealize Operations Manager

vRealize Operations Manager supports vCenter Server users. To log in to vRealize Operations
Manager, vCenter Server users must be valid users in vCenter Server.
Roles and Associations
A vCenter Server user must have either the vCenter Server Admin role or one of the vRealize
Operations Manager privileges, such as PowerUser which assigned at the root level in vCenter
Server, to log in to vRealize Operations Manager. vRealize Operations Manager uses only the
vCenter privileges, meaning the vRealize Operations Manager roles, at the root level, and applies
them to all the objects to which the user has access. After logging in, vCenter Server users can
view all the objects in vRealize Operations Manager that they can already view in vCenter Server.
Logging in to vCenter Server Instances and Accessing Objects
vCenter Server users can access either a single vCenter Server instance or multiple vCenter
Server instances, depending on the authentication source they select when they log in to
n If users select a single vCenter Server instance as the authentication source, they have
permission to access the objects in that vCenter Server instance. After the user has logged in,
an account is created in vRealize Operations Manager with the specific vCenter Server
instance serving as the authentication source.
n If users select All vCenter Servers as the authentication source, and they have identical
credentials for each vCenter Server in the environment, they see all the objects in all the
vCenter Server instances. Only users that have been authenticated by all the vCenter Servers
in the environment can log in. After a user has logged in, an account is created in vRealize
Operations Manager with all vCenter Server instances serving as the authentication source.
vRealize Operations Manager does not support linked vCenter Server instances. Instead, you
must configure the vCenter Server adapter for each vCenter Server instance, and register each
vCenter Server instance to vRealize Operations Manager.
Only objects from a specific vCenter Server instance appear in vRealize Operations Manager. If a
vCenter Server instance has other linked vCenter Server instances, the data does not appear.
vCenter Server Roles and Privileges
You cannot view or edit vCenter Server roles or privileges in vRealize Operations Manager.
vRealize Operations Manager sends roles as privileges to vCenter Server as part of the vCenter
Server Global privilege group. A vCenter Server administrator must assign vRealize Operations
Manager roles to users in vCenter Server.
VMware, Inc. 693

vRealize Operations Manager privileges in vCenter Server have the role appended to the name.
For example, vRealize Operations Manager ContentAdmin Role, or vRealize Operations Manager
PowerUser Role.
Read-Only Principal
A vCenter Server user is a read-only principal in vRealize Operations Manager, which means that
you cannot change the role, group, or objects associated with the role in vRealize Operations
Manager. Instead, you must change them in the vCenter Server instance. The role applied to the
root folder applies to all the objects in vCenter Server to which a user has privileges. vRealize
Operations Manager does not apply individual roles on objects. For example, if a user has the
PowerUser role to access the vCenter Server root folder, but has read-only access to a virtual
machine, vRealize Operations Manager applies the PowerUser role to the user to access the
virtual machine.
Refreshing Permissions
When you change permissions for a vCenter Server user in vCenter Server, the user must log out
and log back in to vRealize Operations Manager to refresh the permissions and view the updated
results in vRealize Operations Manager. Alternatively, the user can wait for vRealize Operations
Manager to refresh. The permissions refresh at fixed intervals, as defined in the $ALIVE_BASE/
user/conf/auth.properties file. The default refreshing interval is half an hour. If necessary, you
can change this interval for all nodes in the cluster.
Single Sign-On and vCenter Users
When vCenter Server users log into vRealize Operations Manager by way of single sign-on, they
are registered on the vRealize Operations Manager User Accounts page. If you delete the
account of a vCenter Server user that has logged into vRealize Operations Manager by way of
single sign-on, or remove the user from a single sign-on group, the user account entry still
appears on the User Account page and you must delete it manually.
Generating Reports
vCenter Server users cannot create or schedule reports in vRealize Operations Manager.
Backward Compatibility for vCenter Server Users in vRealize Operations Manager

vRealize Operations Manager provides backward compatibility for users of the earlier version of
vRealize Operations Manager, so that users of vCenter Server who have privileges in the earlier
version in vCenter Server can log in to vRealize Operations Manager.
When you register vRealize Operations Manager in vCenter Server, certain roles become
available in vCenter Server.
n The Administrator account in the previous version of vRealize Operations Manager maps to
the PowerUser role.
n The Operator account in the previous version of vRealize Operations Manager maps to the
ReadOnly role.
VMware, Inc. 694

During registration, all roles in vRealize Operations Manager, except for vRealize Operations
Manager Administrator, Maintenance, and Migration, become available dynamically in vCenter
Server. Administrators in vCenter Server have all of the roles in vRealize Operations Manager that
map during registration, but these administrator accounts only receive a specific role on the root
folder in vCenter Server if it is specially assigned.
Registration of vRealize Operations Manager with vCenter Server is optional. If users choose not
to register vRealize Operations Manager with vCenter Server, a vCenter Server administrator can
still use their user name and password to log in to vRealize Operations Manager, but these users
cannot use the vCenter Server session ID to log in. In this case, typical vCenter Server users must
have one or more vRealize Operations Manager roles to log in to vRealize Operations Manager.
When multiple instances of vCenter Server are added to vRealize Operations Manager, user
credentials become valid for all of the vCenter Server instances. When a user logs in to vRealize
Operations Manager, if the user selects all vCenter Server options during login, vRealize
Operations Manager requires that the user's credentials are valid for all of the vCenter Server
instances. If a user account is only valid for a single vCenter Server instance, that user can select
the vCenter Server instance from the login drop-down menu to log in to vRealize Operations
Manager.
vCenter Server users who log in to vRealize Operations Manager must have one or more of the
following roles in vCenter Server:
n vRealize Operations Content Admin Role
n vRealize Operations General User Role 1
n vRealize Operations Power User Role
n vRealize Operations Power User without Remediation Actions Role
n vRealize Operations Read Only Role
For more information about vCenter Server users, groups, and roles, see the vCenter Server
documentation.
External User Sources in vRealize Operations Manager

You can obtain user accounts from external sources so that you can use them in your vRealize
Operations Manager instance.
There are two types of external user identity sources:
n Lightweight Directory Access Protocol (LDAP): Use the LDAP source if you want to use the
Active Directory or LDAP servers as authentication sources. The LDAP source does not
support multi-domains even when there is a two-way trust between Domain A and Domain B.
VMware, Inc. 695

n Single Sign-On (SSO): Use a single sign-on source to perform single sign-on with any
application that supports vCenter single sign-on, including vRealize Operations Manager. For
example, you can install a standalone vCenter Platform Services Controller (PSC) and use it to
communicate with an Active Directory server. Use a PSC if the Active Directory has a setup
that is too complex for the simple LDAP source in vRealize Operations Manager, or if the
LDAP source is experiencing slow performance.
Roles and Privileges in vRealize Operations Manager

vRealize Operations Manager provides several predefined roles to assign privileges to users. You
can also create your own roles.
Each predefined role includes a set of privileges for users to perform, create, read, update, or
delete actions on components such as dashboards, reports, administration, capacity, policies,
problems, symptoms, alerts, user account management, and adapters. For information about
roles and associated permissions, see KB 59484.
Administrator
Includes privileges to all features, objects, and actions in vRealize Operations Manager.
PowerUser
user management and cluster management. vRealize Operations Manager maps vCenter
Server users to this role.
PowerUserMinusRemediation
user management, cluster management, and remediation actions.
ContentAdmin
Users can manage all content, including views, reports, dashboards, and custom groups in
AgentManager
Users can deploy and configure End Point Operations Management agents.
GeneralUser-1 through GeneralUser-4
These predefined template roles are initially defined as ReadOnly roles. vCenter Server
administrators can configure these roles to create combinations of roles to give users
VMware, Inc. 696

multiple types of privileges. Roles are synchronized to vCenter Server once during
registration.
ReadOnly
Users have read-only access and can perform read operations, but cannot perform write
actions such as create, update, or delete.
User Scenario: Manage User Access Control

As a system administrator or virtual infrastructure administrator, you manage user access control
in vRealize Operations Manager so that you can ensure the security of your objects. Your
company just hired a new person, and you must create a user account and assign a role to the
account so that the new user has permission to access specific content and objects in vRealize
Operations Manager.
In this scenario you will learn how to create user accounts and roles, and assign roles to the user
accounts to specify access privileges to views and objects. You will then demonstrate the
intended behavior of the permissions on these accounts.
You will create a new user account, named Tom User, and a new role that grants administrative
access to objects in the vRealize Operations Clusters. You will apply the new role to the user
account.
Finally, you will import a user account from an external LDAP user database that resides on
another machine to vRealize Operations Manager, and assign a role to the imported user account
to configure the user's privileges.
Prerequisites
Verify that the following conditions are met:
n vRealize Operations Manager is installed and operating properly, and contains objects such
as clusters, hosts, and virtual machines.
n One or more user groups are defined.
What to do next
Create a new role.
Create a New Role

You use roles to manage access control for user accounts in vRealize Operations Manager.
In this procedure, you will add a new role and assign administrative permissions to the role.
Prerequisites
Verify that you understand the context of this scenario. See User Scenario: Manage User Access
Control. For information about roles and associated permissions, see KB 59484.
VMware, Inc. 697

Procedure
1 In the menu, click Administration, and then in the left pane click Access > Access Control.
2 Click the Roles tab.
3 Click the Add icon on the toolbar to create a role.
The Create Role dialog box appears.
4 For the role name, type admin_cluster, then type a description and click OK.
The admin_cluster role appears in the list of roles.
5 Click the admin_cluster role.
6 In the Details grid below, on the Permissions pane, click the Edit icon.
The Assign Permissions to Role dialog box appears.
7 Select the Administrative Access - all permissions check box.
8 Click Update.
This action gives this role administrative access to all the features in the environment.
What to do next
Create a user account, and assign this role to the account.
Create a User Account

As an administrator you assign a unique user account to each user so that they can use vRealize
Operations Manager. While you set up the user account, you assign the privileges that determine
what activities the user can perform in the environment, and upon what objects.
In this procedure, you will create a user account, assign the admin_cluster role to the account,
and associate the objects that the user can access while assigned this role. You will assign access
to objects in the vRealize Operations Cluster. Then, you will test the user account to confirm that
the user can access only the specified objects.
Prerequisites
Create a new role. See Create a New Role.
Procedure
2 Click the User Accounts tab.
3 Click the Add icon to create a new user account, and provide the information for this account.
Option Description
User Name Type the user name to use to log in to vRealize Operations Manager.
Password Type a password for the user.
VMware, Inc. 698

Option Description
Confirm Password Type the password again to confirm it.
First Name Type the user's first name. For this scenario, type Tom.
Last Name Type the user's last name. For this scenario, type User.
Email Address (Optional). Type the user's email address.
Description (Optional). Type a description for this user.
Disable this user Do not select this check box, because you want the user to be active for this
scenario.
Require password change at next Do not select this check box, because you do not need to change the user's
login password for this scenario.
4 Click Next.
The list of user groups appears.
5 Select a user group to add the user account as a member of the group.
6 Click the Objects tab.
7 Select the admin_cluster role from the drop-down menu.
8 Select the Assign this role to the user check box.
9 In the Object Hierarchies list, select the vRealize Operations Cluster check box.
10 Click Finish.
You created a new user account for a user who can access all the vRealize Operations Cluster
objects. The new user now appears in the list of user accounts.
11 Log out of vRealize Operations Manager.
12 Log in to vRealize Operations Manager as Tom User, and verify that this user account can
access all the objects in the vRealize Operations Cluster hierarchy, but not other objects in
the environment.
Results
You used a specific role to assign permission to access all objects in the vRealize Operations
Cluster to a user account named Tom User.
What to do next
Import a user account from an external LDAP user database that resides on another machine,
and assign permissions to the user account.
VMware, Inc. 699

Import a User Account and Assign Permissions

You can import user accounts from external sources, such as an LDAP database on another
machine, or a single sign-on server, so that you can give permission to those users to access
certain features and objects in vRealize Operations Manager.
Prerequisites
n Configure an authorization source. See Authentication Sources .
Procedure
1 Log out of vRealize Operations Manager, then log in as a system administrator.
3 On the toolbar, click the Import Users icon.
4 Specify the options to import user accounts from an authorization source.
a On the Import Users page, from the Import From drop-down menu, select an
authentication source.
b In the Domain Name drop-down menu, type the domain name from which you want to
import users, and click Search.
c Select the users you want to import, and click Next.
d On the Groups tab, select the user group to which you want to add this user account.
e Click the Objects tab, select the admin_cluster role, and select the Assign this role to the
user check box.
f In the Object Hierarchies list, select the vRealize Operations Cluster check box, and click
Finish.
6 Log in to vRealize Operations Manager as the imported user.
7 Verify that the imported user can access only the objects in the vRealize Operations Cluster.
Results
You imported a user account from an external user database or server to vRealize Operations
Manager, and assigned a role and the objects the user can access while holding this role to the
user.
You have finished this scenario.
Configure a Single Sign-On Source in vRealize Operations Manager

As a system administrator or virtual infrastructure administrator, you use single sign-on to enable
SSO users to log in securely to your vRealize Operations Manager environment.
VMware, Inc. 700

After the single sign-on source is configured, users are redirected to an SSO identity source for
authentication. When logged in, users can access other vSphere components such as the
vCenter Server without having to log in again.
Prerequisites
n Verify that the server system time of the single sign-on source and vRealize Operations
Manager are synchronized. If you need to configure the Network Time Protocol (NTP), see
vRealize Operations Manager Cluster and Node Maintenance.
n Verify that you have access to a Platform Services Controller through the vCenter Server. See
the VMware vSphere Information Center for more details.
Procedure
1 Log in to vRealize Operations Manager as an administrator.
2 In the menu, click Administration, then in the left pane click Access > Authentication
Sources.
3 Click Add.
4 In the Add Source for User and Group Import dialog box, provide information for the single
sign-on source.
Option Action
Source Display Name Type a name for the import source.
Source Type Verify that SSO SAML is displayed.
Host Enter the IP address or FQDN of the host machine where the single sign-on
server resides. If you enter the FQDN of the host machine, verify that every
non-remote collector node in the vRealize Operations Manager cluster can
resolve the single sign-on host FQDN.
Port Set the port to the single sign-on server listening port. By default, the port is
set to 443.
User Name Enter the user name that can log into the SSO server.
Password Enter the password.
Grant administrator role to vRealize Select Yes so that the SSO source is reregistered automatically if you make
Operations Manager for future changes to the vRealize Operations Manager setup. If you select No, and the
configuration? vRealize Operations Manager setup is changed, single sign-on users will not
be able to log in until you manually reregister the single sign-on source.
Automatically redirect to vRealize Select Yes to direct users to the vCenter single-sign on log in page. If you
Operations single sign-on URL? select No, users are not redirected to SSO for authentication.
Import single sign-on user groups Select Yes so that the wizard directs you to the Import User Groups page
after adding the current source? when you have completed the SSO source setup. If you want to import user
accounts, or user groups at a later stage, select No.
Advanced options If your environment uses a load balancer, enter the IP address of the load
balancer.
VMware, Inc. 701

5 Click Test to test the source connection, and then click OK.
The certificate details are displayed.
6 Select the Accept this Certificate check box, and click OK.
7 In the Import User Groups dialog box, import user accounts from an SSO server on another
machine.
Option Action
Import From Select the single sign-on server you specified when you configured the
single sign-on source.
Domain Name Select the domain name from which you want to import user groups. If
Active Directory is configured as the LDAP source in the PSC, you can only
import universal groups and domain local groups if the vCenter Server
resides in the same domain.
Result Limit Enter the number of results that are displayed when the search is
conducted.
Search Prefix Enter a prefix to use when searching for user groups.
8 In the list of user groups displayed, select at least one user group, and click Next.
9 In the Roles and Objects pane, select a role from the Select Role drop-down menu, and select
the Assign this role to the group check box.
10 Select the objects users of the group can access when holding this role.
To assign permissions so that users can access all the objects in vRealize Operations
Manager, select the Allow access to all objects in the system check box.
11 Click OK.
12 Familiarize yourself with single-sign on and confirm that you have configured the single sign-
on source correctly.
a Log out of vRealize Operations Manager.
b Log in to the vSphere Web Client as one of the users in the user group you imported from
the single sign-on server.
c In a new browser tab, enter the IP address of your vRealize Operations Manager
environment.
d If the single sign-on server is configured correctly, you are logged in to vRealize
Operations Manager without having to enter your user credentials.
Edit a Single Sign-On Source

Edit a single sign-on source if you need to change the administrator credentials used to manage
the single sign-on source, or if you have changed the host of the source.
VMware, Inc. 702

When you configure an SSO source, you specify either the IP address or the FQDN of the host
machine where the single sign-on server resides. If you want to configure a new host, that is, if
the single sign-on server resides on a different host machine than the one configured when the
source was set up, vRealize Operations Manager removes the current SSO source, and creates a
new source. In this case, you must reimport the users you want to associate with the new SSO
source.
If you want to change the way the current host is identified in vRealize Operations Manager, for
example, change the IP address to the FQDN and the reverse, or update the IP address of the
PSC if the IP address of the configured PSC has changed, vRealize Operations Manager updates
the current SSO source, and you are not required to reimport users.
Procedure
1 Log in to vRealize Operations Manager as an administrator.
2 In the menu, click Administration, and then in the left pane click Access > Authentication
Sources.
3 Select the single sign-on source and click the Edit icon.
4 Make changes to the single sign-on source, and click OK.
If you are configuring a new host, the New Single Sign-On Source Detected dialog box
appears.
5 Enter the administrator credentials that were used to set up the single sign-on source, and
click OK.
The current SSO source is removed, and a new one created.
6 Click OK to accept the certificate.
7 Import the users you want to associate with the SSO source.
Access Control in vRealize Operations Manager

Each user must have a unique account with one or more roles assigned to enforce role-based
security when they use vRealize Operations Manager. You create a user account, and assign the
account to be a member of one or more user groups to allow the user to inherit the roles and
objects associated with the user group.
Where You Find the Access Control Options

You can manage user accounts and their associated user groups, roles, and passwords.
In the menu, click Administration, and then click Access > Access Control .
VMware, Inc. 703

Table 4-184. Access Control Tabs

Option Description
User Accounts Add, edit, remove, or import vRealize Operations Manager user accounts from an
LDAP database, and manage user roles, their membership in groups, and the objects
assigned for association with the user. Import user accounts from an LDAP database
that resides on another machine.
vCenter Server users who are logged in to vRealize Operations Manager, either logged
in directly or through the vSphere Client, appear in the list of user accounts.
User Groups Add, edit, or remove, or import user groups, update the members in a group and the
associated objects that they can access. Import user groups from an LDAP database
or a single sign-on database that resides on another machine.
vRealize Operations Manager continuously synchronizes the user membership of
imported LDAP user groups when the autosync option is enabled in the LDAP
configuration.
Roles For users to perform actions in vRealize Operations Manager, they must be assigned
specific roles. With role-based access, when you assign a role to a user, you are
determining not only what actions the user can perform in the system, but also the
objects upon which he can perform those actions while holding the role. For example,
to import or export a policy, the role assigned to your user account must have the
Import or Export permissions enabled for policy management.
Password Policy Manage local user passwords, set the criteria for account lockout, password strength,
and the password change policy settings.
Access Control: User Accounts Tab

You can add, edit, or remove vRealize Operations Manager user accounts, and import user
accounts from an external LDAP database. With access control, you manage roles, the objects a
user can access while assigned a specific role, and the membership in user groups.
Where You Manage User Accounts
In the menu, click Administration, and then click Access > Access Control.
Table 4-185. Access Control User Accounts Summary Grid

Summary Grid Options Description
User Accounts toolbar To manage user accounts, use the toolbar icons.
n Add icon. Add a user account, and provide the details for the user account in the
Add User Account dialog box.
n Edit icon. Edit the selected user account, and modify the details for the user group
in the Edit User Account dialog box.
n Delete icon. Delete a user account.
n Import Users icon. Import a user account from an authentication source.
First Name User's first name, created when you create the user account.
Last Name User's last name, created when you create the user account.
User Name User name, without spaces, that will log in to vRealize Operations Manager.
Email User's email address, created when you create the user account.
Description Description of the user account, defined when you create the user account. This
information can identify the type of user and a summary of their access privileges.
VMware, Inc. 704

Table 4-185. Access Control User Accounts Summary Grid (continued)

Summary Grid Options Description
Source Type Indicates whether the user account is a local user, or an external user who is integrated
through an external authentication source, such as from LDAP, SSO, AD, OpenLDAP,
vCenter Server.
Enabled Indicates whether the user account is enabled to use vRealize Operations Manager
features. An administrator can edit a user account to manually enable it, or disable it to
prevent user access to vRealize Operations Manager.
Locked Indicates whether vRealize Operations Manager has locked the user account. For
example, a user account could become locked based on the password lockout policy,
or if the user enters an incorrect password three times in the span of five minutes.
Access All Objects Indicates whether the user account is allowed to access all of the objects that are
imported into the vRealize Operations Manager instance.
After you add a user account, use the Details grid to view and edit which user accounts are
assigned to user groups, and view the permissions assigned to the user account.
Table 4-186. Access Control User Accounts Details Grid

Details Grid Options Description
User Groups Assigned user groups appear when you click a user in the summary grid. You can then
view and modify which user groups the user is associated with.
n Group Name: Identifies the user group. To change the user groups associated with
the user account, click the Edit icon.
n Members: Displays the number of users that are assigned to the user group.
Permissions Permissions appear when you click a user in the summary grid, and click the
Permissions tab in the Details grid. You can then view the roles assigned to the user,
and object hierarchy details.
n Role: Indicates the name of the role or roles assigned to the user.
n Role Description: Displays the description entered for the role.
n Object Hierarchy: Displays the name of the object hierarchy assigned to the user
while holding this role.
n Objects: Displays the number of objects included in the hierarchy that the user can
access.
n Association: Indicates if the role and objects are assigned to the selected user, or
assigned to a user group to which the user belongs.
Add or Edit User Accounts and Assign Groups and Permissions

You can add user accounts so that users can access the features of vRealize Operations Manager
and certain objects in the environment. Or, modify user accounts to change their attributes,
disable or lock the accounts, or require them to change their password. After you add user
accounts, you can assign them to one or more user groups, and assign roles and objects to the
account to specify the actions the user can perform and upon what objects. Assign the
Administrators role only to specific users who must access objects and perform actions in the
entire environment.
VMware, Inc. 705

Where You Add or Edit User Accounts
1 To add a user account, in the menu, click Administration, and then in the left pane click
Access > Access Control
2 In the User Accounts tab, click the Add icon.
3 Optionally, to edit a user account, select a user account and click the Edit icon.
Table 4-187. Add or Edit Users Accounts- User Details Page

User Details Options Description
User Name User name, without spaces, that will log in to vRealize Operations Manager.
Password User's password to access the vRealize Operations Manager instance.
Confirm Password Confirmation of the user's password.
First Name User's first name, created when you create the user account.
Last Name User's last name, created when you create the user account.
Email Address User's email address, created when you create the user account.
Description Description of the user account, defined when you create the user account. This
information can identify the type of user and a summary of their access rights.
Disable this user Disable the user account so that a user cannot access the vRealize Operations
Manager instance.
Account is locked out Indicates that vRealize Operations Manager has locked the user account.
Require password change at Enable users to change their password the next time they log in to the vRealize
next login Operations Manager instance.
4 After you enter the user details, click Next.
VMware, Inc. 706

Table 4-188. Add or Edit User Accounts - Assign Groups and Permissions page
Assign Groups Roles, and
Objects Options Description
Groups Select or deselect the groups associated with the user account. To select or
deselect all accounts, click the Group Name check box. You cannot add user
accounts to groups that you imported from an LDAP database.
Objects Roles determine which actions a user can perform in the system. Select a role from
the Select Role drop-down menu, and then select the Assign this role to the user
check box. You can associate more than one role with the user account.
Select which objects the user can access when assigned this role.
n Select Object Hierarchies: Displays groups of objects. Select an object in this list
to select all the objects in the hierarchy.
n Select Object: To select specific objects within the object hierarchy, click the
down arrow to expand the list of objects. For example, expand the Adapter
Instance hierarchy, and select one or more adapters.
n Allow access to all objects in the system: Select this check box to permit the
user account access to all objects in the system.
Note The roles and object permissions are interlinked when you assign more than
one role to a user. For example, if the user has both, ReadOnly and PowerUser
roles, the permissions associated with the PowerUser role will apply, because the
PowerUser role includes the permissions associated with the ReadOnly role along
with other permissions.
If the user has a custom role and the PowerUser role and the permissions of the
custom role are not included in the permissions of the PowerUser role, the
permissions of both the roles are merged and applied to the user.
The same rule (object permissions from different roles are merged) applies to the
object hierarchies as well.
Import User Accounts

You can import user accounts so that users can access the features of vRealize Operations
Manager and the objects in the environment. After you import user accounts, you can assign
them to user groups and roles. You can also specify the objects users can access while using the
assigned roles.
Where You Import User Accounts
1 To import user accounts, click Administration, and then in the left pane click Access > Access
Control.
2 Click the Import Users icon on the User Accounts toolbar.
VMware, Inc. 707

Table 4-189. Import Users from a LDAP Source

Import From LDAP host machine, Active Directory or Other sources configured to import user
accounts.
n Add icon. Add an LDAP import source, and provide the information for the
LDAP import source in the Add Source for User and Group Import dialog box.
n Edit icon. Edit the selected LDAP import source, and modify the details in the
Edit Source for User and Group Import dialog box.
User Name Click Change Credentials to display the user name of the LDAP source credential
used to import user accounts to the vRealize Operations Manager instance.
Password Password for the LDAP source credential to import user accounts to the vRealize
Search String Enter a search string, and click Search to start the search for user accounts.
User Name Summary grid Lists the users available for import. Select the check box for each user to import, or
select the User Name check box to import all users. User accounts that are already
imported to vRealize Operations Manager do not appear in the list.
Table 4-190. Import Users from a VMware Identity Manager Source

Import From VMware Identity Manager configured as the source to import user accounts.
n Add icon. Add a VMware Identity Manager import source, and provide the
information for the VMware Identity Manager import source in the Add Source
for User and Group Import dialog box.
n Edit icon. Edit the selected VMware Identity Manager import source, and
modify the details in the Edit Source for User and Group Import dialog box.
Domain Name Enter the domain name for import.
Search Prefix Enter a search string, and click Search to start the search for user accounts.
select the User Name check box to import all users. To appear in the list, the user
configuration must be set to primary group in the default domain user group. User
accounts that are already imported to vRealize Operations Manager do not appear
in the list.
Table 4-191. Import Users from a Single Sign On Source

Import From SSO source configured as the source to import user accounts.
n Add icon. Add an SSO import source, and provide the information for the SSO
import source in the Add Source for User and Group Import dialog box.
n Edit icon. Edit the selected SSO import source, and modify the details in the
Edit Source for User and Group Import dialog box.
Result Limit Determines the number of users displayed.
VMware, Inc. 708

Table 4-191. Import Users from a Single Sign On Source (continued)

Search Prefix Enter a search prefix, and click Search to start the search for user accounts.
select the User Name check box to import all users. To appear in the list, the user
configuration must be set to primary group in the default domain user group. User
accounts that are already imported to vRealize Operations Manager do not appear
in the list.
3 After you enter the import users details, click Next.
Table 4-192. Import Users Accounts- Assign Groups and Permissions Page
Assign Groups Roles, and
Objects Options Description
Groups Select or deselect the groups associated with the user account. To select or
deselect all accounts, click the Group Name check box. You cannot add user
accounts to groups imported from LDAP.
Objects Select or deselect roles in the Select Role drop down menu. When you have
selected a role, click the Assign this role to the user check box. You can assign
more than one role to a user account.
Select which objects the user can access when assigned this role.
to select all the objects in the hierarchy,
n Allow access to all objects in the system: Select this check box to permit the
user account access to all objects in the system.
Access Control: User Groups Tab

You can manage the user groups associated with the users and objects in your environment. You
can import user groups from an LDAP database that resides on another machine, or from a single
sign-on server.
Where You Manage User Groups
1 To manage user groups, in the menu, click Administration, and then in the left pane click
Access > Access Control.
2 Click the User Groups tab.
VMware, Inc. 709

Table 4-193. Access Control User Groups Summary Grid

Option Description
User Groups toolbar To manage user groups, use the toolbar icons.
n Add icon. Add a user group, and provide the details for the user group in the Add
User Group dialog box.
n Edit icon. Edit the selected user group, and modify the details for the user group in
the Edit User Group dialog box.
n Clone Group icon. Clone a user group, and type a name and description for the
cloned user group.
n Delete icon. Delete a user group.
n Import Group icon. Import a user group, and provide the details to import the user
group in the Import User Groups dialog box.
Group Name Name of the user group.
Description Description of the group, indicating its purpose.
Members Number of members in the group.
Group Type Type of group, either a local user group or a group imported from LDAP.
Distinguished Name Names for LDAP objects, such as domains and users.
Access All Objects Indicates if the user group account is allowed to access all of the objects that are
imported into the vRealize Operations Manager instance.
After you select a user group in the summary grid, view details about associated users in the
Details pane.
Table 4-194. Access Control User Groups Details Grid

Option Description
User Accounts You can add members to the selected group, view only the selected or deselected
members in the group, or search for a member. You can remove a user from the group
by selecting the user in the Details pane and clicking Delete.
n User Name: Name of each user who is a member of the selected group.
n First Name: First name of each user in the group.
n Last Name: Last name of each user in the group.
Permissions View the permissions of the role associated with the user group. To add or remove
roles, view only the selected or deselected roles, or search for a specific role, click the
Edit icon.
n Role Name: Indicates the roles assigned to the selected user group.
n Role Description: Description for the selected user group, defined when you
created the group.
n Object Hierarchy: The names of the object hierarchies assigned to the group while
holding a specific role.
n Objects: The number of objects the user group can access within the selected
hierarchy.
Add or Edit User Groups and Assign Members and Permissions

You can view and modify the details for user groups, including users, roles, and objects.
VMware, Inc. 710

Where You Add or Edit User Groups
1 To add a user group, in the menu, click Administration and then click Access > Access
Control.
2 Select the User Groups tab and then click the Add icon.
3 Optionally, to edit a user group, select a user group and click the Edit icon.
Table 4-195. Add or Edit User Group - Name and Description Page
Option Description
Group Name Name of the user group, either created manually, imported from a single sign-on
server, or imported from an LDAP database that resides on another machine.
Description Description of the user group, indicating its purpose.
4 After you enter the name and description, click Next
Table 4-196. Add or Edit User Group - Assign Members and Permissions Page
Option Description
Members Select the members associated with the user group.
Objects Roles determine which actions users of the group can perform in the system. Select
a role from the Select Role drop-down menu, and then select the Assign this role
to the user check box. You can associate more than one role with the user group.
Select which objects the users of the group can access when assigned this role.
to select all the objects in the hierarchy.
n Allow access to all objects in the system: Select this check box to permit users
of the group access to all objects in the system.
Note The roles and object permissions are interlinked when you assign more than
one role to a user. For example, if the user has both, ReadOnly and PowerUser
roles, the permissions associated with the PowerUser role will apply, because the
PowerUser role includes the permissions associated with the ReadOnly role along
with other permissions.
If the user has a custom role and the PowerUser role and the permissions of the
custom role are not included in the permissions of the PowerUser role, the
permissions of both the roles are merged and applied to the user.
The same rule (object permissions from different roles are merged) applies to the
object hierarchies as well.
Import User Groups

You import user groups from a single sign-on server, VMware Identity Manager, Active Directory,
or an LDAP database on another machine so that you can use those groups in vRealize
Operations Manager.
VMware, Inc. 711

Where You Import User Groups
1 To import a user group, in the menu, click Administration, and then in the left pane click
2 Select the User Groups tab and click the Import Group icon.
The options displayed in the Import User Groups page depend upon the authentication
source you select.
Table 4-197. Import User Groups Page - LDAP, Active Directory, and Others Sources
Option Description
Import From Host machine configured as the source to import the user groups. These options
are displayed when the host machine of an LDAP, Active Directory, or Other source
is selected.
User Name User name of the source credential to import user groups to the vRealize
Password Password for the source credential to import user groups to the vRealize
Search String Invoke the search for user groups.
Advanced Displays the advanced import settings.

n Group Search Criteria. Search criteria to find LDAP groups. If not included,
vRealize Operations Manager uses the default search parameters: (|
(objectClass=group)(objectClass=groupOfNames))
n Member Attribute. Name of the attribute for a group object that contains the
list of members. If not included, vRealize Operations Manager uses member by
default.
n User Search Criteria. Search criteria to use the member field to find and cache
LDAP users. You type sets of key=value pairs in the form (|(key1=value1)
(key2=value2)). If not included, vRealize Operations Manager searches for each
user separately. This operation might take extra time.
n Member Match Field. Name of the attribute for a user object to match with the
member entry from a group object. If not included, vRealize Operations
Manager treats the member entry as a distinguished name.
n LDAP Context Attributes. Attributes that vRealize Operations Manager applies
to the LDAP context environment. You type sets of key=value pairs separated
by commas, such as
java.naming.referral=ignore,java.naming.ldap.deleteRDNfalse.
Group Name Displays the user groups found. Click the check box for each user group to import.
Table 4-198. Import User Groups Page - Single Sign On Source

Option Description
Import From Host machine configured as the source to import the user groups.
Domain Name User name of the source credential to import user groups to the vRealize
Result Limit Determines the number of groups displayed.
VMware, Inc. 712

Table 4-198. Import User Groups Page - Single Sign On Source (continued)
Option Description
Search Prefix Enter a search prefix to narrow your search.
Group Name Displays a list of user groups. Select the Group Name check box to import all the
displayed user groups, or select the check box next to each user group that you
want to import.
Table 4-199. Import User Groups from a VMware Identity Manager Source
Import From VMware Identity Manager configured as the source to import user groups.
n Add icon. Add an VMware Identity Manager import source, and provide the
information for the VMware Identity Manager import source in the Add Source
for User and Group Import dialog box.
n Edit icon. Edit the selected VMware Identity Manager import source, and
modify the details in the Edit Source for User and Group Import dialog box.
Search Prefix Enter a search string, and click Search to start the search for user groups.
User Name Summary grid Lists the users available for import. Select the check box for each user group to
import, or select the Group Name check box to import all groups. User groups that
are already imported to vRealize Operations Manager do not appear in the list.
3 After you enter the import user group details, click Next.
Table 4-200. Import User Groups - Roles and Objects Page

Option Description
Select Role Displays available roles in a drop-down menu.
Assign this role to the group Roles determine which actions users of the group can perform in the system. Select
a role from the Select Role drop-down menu, and then select the Assign this role
to the user check box. You can associate more than one role with the user group.
Select Object Hierarchies Select which objects the users of the group can access when assigned this role.
to select all the objects in the hierarchy,
n Allow access to all objects in the system: Select this check box to permit users
of the group access to all objects in the system.
Access Control: Roles Tab

You can assign users specific roles to perform actions and view features and objects in vRealize
Operations Manager. With role-based access, users can only perform the actions that their
permissions allow.
VMware, Inc. 713

Where You Manage User Roles

1 To manage user roles, in the menu, click Administration, and then in the left pane click
2 Click Roles tab.
You can view and edit details about a role, by selecting a role in the summary grid, and clicking
the Edit icon in the Roles toolbar.
Table 4-201. Access Control Roles Summary Grid

Option Description
Roles toolbar To manage roles, use the toolbar icons.

n Add icon. Add a user role, and provide the name and description for the role in the
Create Role dialog box.
n Edit icon. Edit the selected user role, and modify the details for the role in the Edit
Role dialog box.
n Clone icon. Clone the selected user role.
n Delete icon. Delete a user role.
Role Name Name of the role to apply to a specific level of users, such as user for base users or
Administrator for users with administrative permissions.
Role Description Description of the role, indicating its purpose.
You can view details for the user accounts and user groups associated with a selected role in the
Details panes
Table 4-202. Access Control Roles Details Panes

Option Description
User Accounts The users assigned to the selected role. The information in this pane is based on the
data entered when you created the user, or imported with the user.
n First Name. Indicates the first name of each user who is assigned this role.
n Last Name. Indicates the last name of each users who is assigned this role.
n User name, without spaces, that will log in to vRealize Operations Manager.
n Email. Indicates the email address for each user who is assigned this role.
User Groups The user groups assigned the selected role.

n Group Name: Name of each group that is associated with the selected role.
n Members: Number of members in each group.
Permissions Displays the permissions assigned to the role according to five categories:
Administration, Alerts, Dashboards, Environment and Home. Expand the tree of each
category to view all the assigned permissions.
You can edit the permissions assigned to the role by clicking the Edit icon.
n Click the Expand All button to expand the trees of all three categories, and select
the check boxes to apply permissions for the selected role.
n To assign all the available permissions to the selected role, select the
Administrative Access - all permissions check box.
VMware, Inc. 714

these actions.
set to true.
Access Control: Password Policy Tab

To ensure security in vRealize Operations Manager, you must manage user passwords.
Determine the criteria used for account lockout, password strength, and the password change
policy. When a user session becomes inactive for 30 minutes, the session times out, and the user
must log in to vRealize Operations Manager again.
Where You Manage the Password Policy
1 To manage user roles, in the menu, click Administration, and then click Access > Access
Control.
2 Click Password Policy tab.
Account Lockout
Indicates whether the account lockout is in effect, and indicates the number of login attempts
allowed before the account is locked. The account lockout policy is enabled by default.
Password Strength
Indicates whether the policy that requires users to strengthen their password is in effect, and
the minimum number of characters required to make a strong password. The password
strength policy is enabled by default.
Password Change
Indicates whether the policy that requires users to change their password is in effect, how
often the password expires, and whether users will receive a warning. The account password
change policy is enabled by default.
Modify the Password Policy
You can modify the password policy by clicking Edit.
VMware, Inc. 715

Table 4-203. Access Control Edit Password Policy Settings

Option Description
Account Lockout Modify the settings to lock user accounts.

n Activate Account Lockout Policy. Enable the policy to lock user accounts. For a
super administrator user, the account lockout policy is enabled by default and
cannot be disabled. The super administrator user account is locked for
approximately one hour, and then unlocked.
n Number of failed login attempts before lockout. Indicates the number of tries that a
user can attempt to log in to vRealize Operations Manager before their account is
locked. The default number of tries is seven, and the time frame allowed for login is
45 seconds.
Password Strength Modify the settings required for users to create strong passwords.
n Activate Password Strength Policy. When checked, enables the policy to require
users to strengthen their password.
n Minimum password length. Indicates the number of characters required for user
passwords. The default length is eight characters.
n Passwords must contain numbers. Users must include a combination of letters and
numbers.
n Passwords must not match user names. To ensure security, users are not allowed
to use their user name as their password.
n Passwords must contain at least one uppercase and one lowercase letter. When
checked, users must include one or more uppercase characters.
n Passwords must contain special characters. When checked, users must include one
or more special characters. Special characters include: !@#$%^&*+=
Password Change Modify the settings required for users to change their password.
n Activate Password Change Policy. Enable the policy to require users to change
their password at specific intervals.
n Passwords expire every 90 days. Users receive notification five days before the
password expires.
n Warn users 5 days prior to expiration. Indicate when to have vRealize Operations
Manager notify users that their password will expire. The default is five days before
their password expires.
Authentication Sources
vRealize Operations Manager uses authentication sources that enable you to import and
authenticate users and user group information that reside on another machine: the Lightweight
Directory Access Protocol (LDAP) platform-independent protocol, Active Directory, VMware
Identity Manager, Single Sign-On, and Others.
Where You Manage Authentication Sources

To manage authentication sources, in the menu, click Administration, and then in the left pane
click Access > Authentication Sources.
VMware, Inc. 716

Table 4-204. Authentication Sources Toolbar and Data Grid

Option Description
Authentication Sources toolbar To manage authentication sources, use the toolbar icons.
n Add icon: Add an authentication source, and provide the information for the
source in the Add Source for User and Group Import dialog box.
n Edit icon: Edit the selected authentication source, and modify the details in the
Edit Source dialog box.
n Delete icon. Delete an authentication source.
n Synchronize User Groups icon. Synchronize users within the groups imported
through the selected Active Directory or LDAP authentication source
Source Display Name Name that you assign to the authentication source.
Source Type Indicates the type of directory services access technology to access the source
machine where the authentication database of user accounts resides. Options include:
n Open LDAP: A platform-independent protocol that provides access to an LDAP
database on another machine to import user accounts.
n Active Directory or Other: Specifies any other LDAP based directory services, such
as Novel or Open DJ, used to import user accounts from an LDAP database on a
Linux Mac machine.
n SSO SAML: An open-standard data format that enables Web browser single sign-
on.
n VMware Identity Manager: A platform where you can manage users and groups,
manage resources and user authentication, and access policies and entitle users to
resources.
Host Name or IP address of the host machine where the user database resides.
Port Port used for the import.
Base DN Base distinguished name for the user search. vRealize Operations Manager will locate
only the users under the Base DN. The Base DN is an elementary entry for an
imported user's distinguished name (DN), which is the base entry for the user name
without the need for other related information such as the full path to the user
account, or the inclusion of related domain components. Although vRealize Operations
Manager populates the Base DN, an Administrator must verify the Base DN before
saving the LDAP configuration.
Auto Synchronization When selected, enables vRealize Operations Manager to map imported LDAP users to
user groups.
Last Synchronized Date and time that the synchronization last occurred.
Authentication Sources: Add Authentication Source for User and Group Import
When you import user account information that resides on another machine, you must define the
criteria used to import the user accounts from the source machine.
Where You Add or Edit Authentication Sources
1 To add authentication sources, in the menu, click Administration, and then in the left pane
click Access > Authentication Sources.
2 Click Add.
3 To edit authentication sources, click Edit.
VMware, Inc. 717

Table 4-205. Authentication Sources Add Source for User and Group Import
Option Description
Source Display Name Name that you assign to the authentication source.
Source Type Indicates the type of directory services access technology

to access the source machine where the database of user
Note The option you select in the Source Type drop-
accounts resides. There are two types of databases: LDAP
down box, determines the options available in this dialog
and single sign-on. Options include:
box.
n SSO SAML: An XML-based standard for web browser
single sign-on that enables users to perform single sign-
on to multiple applications.
n Open LDAP: A platform-independent protocol that
provides access to an LDAP database on another
machine to import user accounts.
n Other: Specifies any other LDAP based directory
services, such as Novel or OpenDJ, used to import user
accounts from an LDAP database on a Linux Mac
machine.
n VMware Identity Manager: A platform where you can
manage users and groups, manage resources and user
authentication, and access policies and entitle users to
resources.
Table 4-206. Authentication Sources Add Source for User and Group Import - options available
when SSO SAML is selected.
Name Description
Host Name or IP address of the host machine where the single

sign-on user server resides.
Port The single sign-on listening port. By default this is set to

443.
User Name Name of the user account that can log in to the single sign-
on host machine.
Password Password of the user account that can log in to the single
sign-on host machine.
Grant administrator role to vRealize Operations Manager When you create a single sign-on source, a new vRealize
for future configuration? Operations Manager user account is created on the single
sign-on server.
n Select Yes, to grant vRealize Operations Manager an
administrative role so that it can be used to configure
the SSO source if changes are made to the vRealize
Operations Manager setup.
n If you select No and the vRealize Operations Manager
setup is changed, SSO users will not be able to log in
until you re-register the SSO source.
VMware, Inc. 718

when SSO SAML is selected. (continued)
Name Description
Automatically redirect to vRealize Operations single sign-on After you have configured a single sign-on source, users
URL? are redirected to the vCenter SSO server.
n Select Yes, to redirect users to the single sign-on server
for authentication.
n If you select No users must sign in through the vRealize
Operations Manager login page.
Import single sign-on user groups after adding the current When you have set up a single sign-on source, you import
source? users and user groups into vRealize Operations Manager so
that single sign-on users can access the system with their
single sign-on permissions.
n If you select Yes, the wizard directs you to the Import
User Groups page so that you can import user groups
as soon as you have finished setting up the SSO
source.
n If you want to import user accounts, or user groups at a
later stage, select No.
Advanced If your system uses a load balancer, enter the IP address of

the load balancer.
Test Tests whether the host machine can be reached with the
credentials provided.
VMware, Inc. 719

when Open LDAP, Active Directory, and Other are selected.
Option Description
Integration Mode Basic settings Applies basic settings to integrate the LDAP import source with the instance of
Use Basic integration mode to have vRealize Operations Manager discover the host
machine where the LDAP database resides, and set the base distinguished name (Base
DN) used to search for users. You provide the name of the domain and the subdomain,
which vRealize Operations Manager uses to populate the Host and Base DN details,
and the name and password of the user who can log in to the LDAP host machine.
In Basic mode, vRealize Operations Manager attempts to fetch the host and port from
the DNS server, and obtain the Global Catalog and domain controllers for the domain,
with preference given to SSL/TLS-enabled servers.
n Domain/Subdomain. Domain information for the LDAP user account.
n Use SSL/TLS. When selected, vRealize Operations Manager uses the Secure
Sockets Layer/Transport Layer Security (SSL/TLS) protocol to provide secure
communication when you import users from an LDAP database. You do not need
to install the SSL/TLS certificate. Instead, vRealize Operations Manager prompts
you to view and verify the thumbprint, and accept the LDAP server certificate.
After you accept the certificate, the LDAP communication proceeds.
n User Name. Name of the user account that can log in to the LDAP host machine.
n Reset Password. Reset the password of the user account that can log in to the
LDAP host machine.
n Automatically synchronize user membership for configured groups. When
selected, enables vRealize Operations Manager to map imported LDAP users to
user groups.
n Host. Name or IP address of the host machine where the LDAP user database
resides.
n Port. Port used for the import. Use port 389 if you are not using SSL/TLS, or port
636 if you are using SSL/TLS, or another port number of your choice. Global
Catalog ports are 3268 for non-SSL/TLS, and 3269 for SSL/TLS.
n Base DN. Base distinguished name for the user search. vRealize Operations
Manager will locate only the users under the Base DN. The Base DN is an
elementary entry for an imported user's distinguished name (DN), which is the base
entry for the user name without the need for other related information such as the
full path to the user account, or the inclusion of related domain components.
Although vRealize Operations Manager populates the Base DN, an Administrator
must verify the Base DN before saving the LDAP configuration.
n Common Name. LDAP attribute used to identify the user name. The default
attribute for Active Directory is userPrincipalName.
Integration Mode Advanced Applies advanced settings to integrate the LDAP import source with the instance of
settings vRealize Operations Manager.
Use Advanced integration mode to manually provide the host name and base
distinguished name (Base DN) to have vRealize Operations Manager import users. You
provide the name and password of the user who can log in to the LDAP host machine.
n Host. Name or IP address of the host machine where the LDAP user database
resides.
n Use SSL/TLS. When selected, vRealize Operations Manager uses the Secure
Sockets Layer/Transport Layer Security (SSL/TLS) protocol to provide secure
VMware, Inc. 720

when Open LDAP, Active Directory, and Other are selected. (continued)
Option Description
communication when you import users from an LDAP database. You do not need
to install the SSL/TLS certificate. Instead, vRealize Operations Manager prompts
you to view and verify the thumbprint, and accept the LDAP server certificate.
After you accept the certificate, the LDAP communication proceeds.
n Base DN. Base distinguished name for the user search. vRealize Operations
Manager will locate only the users under the Base DN. The Base DN is an
elementary entry for an imported user's distinguished name (DN), which is the base
entry for the user name without the need for other related information such as the
full path to the user account, or the inclusion of related domain components.
Although vRealize Operations Manager populates the Base DN, an Administrator
must verify the Base DN before saving the LDAP configuration.
n User Name. Name of the user account that can log in to the LDAP host machine.
n Reset Password. Reset the password of the user account that can log in to the
LDAP host machine.
n Automatically synchronize user membership for configured groups. When
selected, enables vRealize Operations Manager to map imported LDAP users to
user groups.
n Common Name. LDAP attribute used to identify the user name. The default
attribute for Active Directory is userPrincipalName.
n Port. Port used for the import. Use port 389 if you are not using SSL/TLS, or port
636 if you are using SSL/TLS, or another port number of your choice. Global
Catalog ports are 3268 for non-SSL/TLS, and 3269 for SSL/TLS.
Search Criteria Displays the search criteria settings.

Although vRealize Operations Manager populates part of the search criteria, an
Administrator must verify the settings to ensure that the settings are correct according
to the properties of the LDAP type.
n Group Search Criteria. Search criteria to find LDAP groups. If not included, vRealize
Operations Manager uses the default search parameters: (|(objectClass=group)
(objectClass=groupOfNames))
n Member Attribute. Name of the attribute for a group object that contains the list of
members. If not included, vRealize Operations Manager uses member by default.
n User Search Criteria. Search criteria to use the member field to find and cache
LDAP users. You type sets of key=value pairs in the form (|(key1=value1)
(key2=value2)). If not included, vRealize Operations Manager searches for each
user separately. This operation might take extra time.
n Member Match Field. Name of the attribute for a user object to match with the
member entry from a group object. If not included, vRealize Operations Manager
treats the member entry as a distinguished name.
n LDAP Context Attributes. Attributes that vRealize Operations Manager applies to
the LDAP context environment. You type sets of key=value pairs separated by
commas, such as java.naming.referral=ignore,java.naming.ldap.deleteRDNfalse.
Test Tests whether the host machine can be reached, with the credentials provided.
Although a test of the connection is successful, users who use the search feature must
have read permissions in the LDAP source.
This test does not verify the accuracy of the Base DN or Common Name entries.
VMware, Inc. 721

Table 4-208. Authentication Sources Add Source for User and Group Import - Options available
when VMware Identity Manager is selected.
Option Description
Host Name or IP address of the VMware Identity Manager

machine where the single sign-on user server resides.
Port The single sign-on listening port. By default this is set to

443.
Tenant This is an optional field.
Username VMware Identity Manager system-domain tenant

administrator username.
Password Password of the VMware Identity Manager system-domain

tenant administrator.
Redirect IP/ FQDN This is the IP address of vRealize Operations Manager node
where a user is redirected after a successful authentication
from VMware Identity Manager. By default, this is the IP
address of the vRealize Operations Manager primary node.
Note When the primary replica becomes the primary node

on vRealize Operations Manager, then vRealize Operations
Manager administrator has to manually edit the IP address
and set it to the IP address of the current primary node.
Test Tests whether the VMware Identity Manager machine can

be reached, with the credentials provided.
Audit Users and the Environment in vRealize Operations Manager

At times you might need to provide documentation as evidence of the sequence of activities that
took place in your vRealize Operations Manager environment. Auditing allows you to view the
users, objects, and information that is collected. To meet audit requirements, such as for business
critical applications that contain sensitive data that must be protected, you can generate reports
on the activities of your users, the privileges assigned to users to access objects, and the counts
of objects and applications in your environment.
Auditing reports provide traceability of the objects and users in your environment.
User Activity Audit
Run this report to understand the scope of user activities, such as logging in, actions on
clusters and nodes, changes to system passwords, activating certificates, and logging out.
User Permissions Audit
Generate this report to understand the scope of user accounts and their roles, access groups,
and access privileges.
System Audit
Run this report to understand the scale of your environment. This report displays the counts
of configured and collecting objects, the types and counts of adapters, configured and
VMware, Inc. 722

collecting metrics, super metrics, applications, and existing virtual environment objects. This
report can help you determine whether the number of objects in your environment exceeds a
supported limit.
System Component Audit
Run this report to display a version list of all the components in your environment.
Reasons for Auditing Your Environment

Auditing in vRealize Operations Manager helps data center administrators in the following types
of situations.
n You must track each configuration change to an authenticated user who initiated the change
or scheduled the job that performed the change. For example, after an adapter changes an
object, which is associated with a specific object identifier at a specific time, the data center
administrator can determine the principal identifier of the authenticated user who initiated the
change.
n You must track who made changes to your data center during a specific range of time, to
determine who changed what on a particular day. You can identify the principal identifiers of
authenticated users who were logged in to vRealize Operations Manager and running jobs,
and determine who initiated the change.
n You must determine which objects were affected by a particular user during a time specific
range of time.
n You must correlate events that occurred in your data center, and view these events
overlayed so that you can visualize relationships and the cause of the events. Events can
include login attempts, system startup and shutdown, application failures, watchdog restarts,
configuration changes of applications, changes to security policy, requests, responses, and
status of success.
n You must validate that the components installed in your environment are running the latest
version.
User Activity Audit

The user activity report helps you understand the scope of user activities in your vRealize
Operations Manager instance, such as when users logged in, actions they took on clusters and
nodes, changes they made to system passwords, when they activated certificates, and when
they logged out.
Where You Audit User Activity
To audit user activity, in the menu, click Administration, and then in the left pane click History >
Audit. The activities that users performed in the environment appear on the page.
VMware, Inc. 723

Table 4-209. User Activity Audit Actions

Option Description
Download Download the user activity audit information to a report in PDF or XLS format.
Configure Configure the settings to send the user activity log to an external syslog server to
meet security auditing requirements.
n Output log to external syslog server. When checked, vRealize Operations Manager
sends the log to a separate server machine.
n IP Address or Host Name. Identification for the syslog server.
n Port. vRealize Operations Manager port used to send the audit information to the
external server.
Date Range Display the list of user activities performed in the past based on a selected number of
hours, days, weeks, months, or years, or between two specific dates and times.
Starting Line Indicates the starting line of the file . 0 is for the first line. -1 or no value indicates that
the file has to be displayed from the end.
Number of Lines Specifies the number of lines to be displayed in the search result. For example: If you
want to see the first 10 occurrences of a particular chunk of text, enter the number of
lines as 10 and the starting line as 0.
Filter Filters the data according to User ID, User Name, Auth Source, Session, Message, and
Category.
User Permissions Audit

A user permissions audit report provides an overview of the local users and LDAP imported users
in your vRealize Operations Manager instance, and a list of groups to which each user belongs.
This report helps you understand the scope of the user accounts and their roles, access groups,
and access privileges in your environment.
The report displays the access group associated with each local user and LDAP imported user
and the access privileges granted to the user in each access group. This report does not include
vCenter Server users, roles, or privileges.
When a user is a member of a specific user group, the associated access group could provide
the user with access to configuration, dashboards, and templates, or to specific navigation areas
in the user interface such as Administration. The access rights associated with the access group
include actions for each access group, such as the ability to add, edit, or delete dashboards, or to
view, configure, or manage objects.
Where You Audit User Permissions
1 To audit user permissions, in the menu, click Administration, and then in the left pane click
History > Audit.
2 Click the User Permissions Audit tab.
The permissions assigned to users, and their associated access groups and access privileges,
appear on the page.
VMware, Inc. 724

Table 4-210. User Permissions Audit Actions

Option Description
Download Download the user permissions audit information to a report in PDF or XLS format.
System Audit for vRealize Operations Manager

A system audit report provides an overview of the counts of objects, metrics, super metrics,
applications, and custom groups in your vRealize Operations Manager instance. This report can
help you understand the scale of your environment.
The system audit report displays the types and number of objects that vRealize Operations
Manager manages. Reported objects include those that are configured and collecting data, the
types of objects, object counts for adapters, the metrics that are configured and being collected,
super metrics, vRealize Operations Manager generated metrics, the number of applications used,
and the number of custom groups.
You can use this report to help determine whether the number of objects in your environment
exceeds a supported limit.
Where You Audit the System
1 To audit the objects, metrics, applications, and custom groups in your environment, click
Administration, and then in the left pane click History > Audit.
2 Click the System Audit tab.
The objects and their associated counts appear in the report.
Table 4-211. System Audit Actions

Option Description
Download Download the system information to a report in PDF or XLS format.
System Component Audit

A system component audit report provides a version list of every component installed in the
system.
Where You Audit System Components
1 To audit system components, in the menu, click Administration, and then in the left pane
click History > Audit.
2 Click the System Component Audit tab.
A list of components installed in the environment appears on the page.
Table 4-212. System Component Audit Actions

Option Description
Download Display the version information in a new browser window.
VMware, Inc. 725

User Preferences in vRealize Operations Manager

You can configure the user preferences to determine the vRealize Operations Manager display
options, such as the number of metrics and groups to display and whether to synchronize system
time with the host machine.
To configure the user preferences, in the menu, click the icon, and then click Preferences.
The user preference settings appear in the dialog box.
Table 4-213. User Preference Settings

Option Description
Display Configure how many metrics and root cause groups to display.
n Color scheme: Set the user interface to display in light or dark colors.
n Important metrics count to show. Set the number of metrics to display.
n Root cause groups count to show. Set the number of root cause groups to display.
n Font. Select the font for reports.
Time Synchronize the time used for the vRealize Operations Manager instance, and display
the updated time when vRealize Operations Manager communicates with the host
machine.
n Browser time. All dates and times displayed in the user interface use the time zone
settings of the local browser.
n Host time. All dates and times displayed in the user interface use the time zone of
the host machine.
n Show update time in the application header. Displays the updated time in the top
level header of the vRealize Operations Manager user interface. The updated
timestamp appears to the left of the refresh button. Other features, such as
dashboards, use the updated time to display data at specific intervals.
Account Change the password for the user account.
vRealize Operations Manager Passwords and Certificates

For secure vRealize Operations Manager operation, you might need to perform maintenance on
passwords or authentication certificates.
n Passwords are for user access to the product interfaces or to console sessions on cluster
nodes.
n Authentication certificates are for secure machine-to-machine communication within vRealize

Operations Manager itself or between vRealize Operations Manager and other systems.
Reset the vRealize Operations Manager Administrator Password

You might need to reset the vRealize Operations Manager administrator password as part of
securing or maintaining your deployment and if you forget the admin account password.
Procedure

https://<master-node-name> or <master-node-ip-address>/admin.
VMware, Inc. 726

3 In the left pane, click Administrator Settings.
4 In the Change Administrator Password section, enter the current password, and enter the
new password twice to ensure its accuracy.
Note You cannot change the administrator user name.
5 Click Save.
6 Optionally, to recover a forgotten password, configure the Password Recovery Settings.
Table 4-214. Password Recovery Settings

Password Recovery Settings Options Description
Your E-mail Email id to which you want to receive the recovery email.
SMTP Server smtp.vmware.com
Port Port used for the communication. By default, 25 is used

for a non secure port and 465 for a secure port.
SSL (SMTPS) Enable or disable to protect the communication using the

secure socket layer.
STARTTLS Encryption Enable or disable to switch the insecure communication

starting with the TLS handshake.
Sender E-mail The email from which the password recovery email is
sent.
User name Username for the STMP server account, as some servers
require authentication.
Password Password for the SMTP server account.
Test To verify the mandatory fields and make an attempt to

communicate with the given SMTP server.
7 Click Save. Optionally, click Reset to enter the details again.
Reset the vRealize Operations Manager Administrator Password on vApp

Clusters
You need to reset the password if the admin account password is lost.
When the vRealize Operations Manager password for the built-in admin account is lost, follow
these steps to reset it on vApp clusters.
Prerequisites
This procedure requires root account credentials.
n In vRealize Operations Manager vApp deployments, when you log in to the console of the
virtual application for the first time, you are forced to set a root password.
VMware, Inc. 727

n The vRealize Operations Manager console root password can be different than the admin
account password that you set when configuring the vRealize Operations Manager primary
node.
Procedure
1 Log in to the master node command line console as root.
2 Enter the following command, and follow the prompts.
$VMWARE_PYTHON_BIN $VCOPS_BASE/../vmware-vcopssuite/utilities/sliceConfiguration/bin/
vcopsSetAdminPassword.py --reset
Generate a vRealize Operations Manager Passphrase

When users need to add a node to the vRealize Operations Manager cluster, you can generate a
temporary passphrase instead of giving them the primary administrator login credentials, which
might be a security issue.
A temporary passphrase is good for one use only.
Prerequisites
Create and configure the primary node.
Procedure

https://master-node-name-or-ip-address/admin.
3 In the list of cluster nodes, select the master node.
4 From the toolbar above the list, click the option to generate a passphrase.
5 Enter a number of hours before the passphrase expires.
6 Click Generate.
A random alphanumeric string appears, which you can send to a user who needs to add a
node.
What to do next
Have the user supply the passphrase when adding a node.
Custom vRealize Operations Manager Certificates

By default, vRealize Operations Manager includes its own authentication certificates. The default
certificates cause the browser to display a warning when you connect to the vRealize Operations
Manager user interface.
VMware, Inc. 728

Your site security policies might require that you use another certificate, or you might want to
avoid the warnings caused by the default certificates. In either case, vRealize Operations
Manager supports the use of your own custom certificate. You can upload your custom
certificate during initial primary node configuration or later.
Custom vRealize Operations Manager Certificate Requirements

A certificate used with vRealize Operations Manager must conform to certain requirements. Using
a custom certificate is optional and does not affect vRealize Operations Manager features. You
can also use wildcard certificates in vRealize Operations Manager.
Requirements for Custom Certificates

Custom vRealize Operations Manager certificates must meet the following requirements.
n The certificate file must include the terminal (leaf) server certificate, a private key, and all
issuing certificates if the certificate is signed by a chain of other certificates.
n In the file, the leaf certificate must be first in the order of certificates. After the leaf certificate,
the order does not matter.
n In the file, all certificates and the private key must be in PEM format. vRealize Operations
Manager does not support certificates in PFX, PKCS12, PKCS7, or other formats.
n In the file, all certificates and the private key must be PEM-encoded. vRealize Operations
Manager does not support DER-encoded certificates or private keys.
PEM-encoding is base-64 ASCII and contains legible BEGIN and END markers, while DER is a
binary format. Also, file extension might not match encoding. For example, a generic .cer
extension might be used with PEM or DER. To verify encoding format, examine a certificate
file using a text editor.
n The file extension must be .pem.
n The private key must be generated by the RSA or DSA algorithm.
n The private key may be encrypted by a pass phrase. The generated certificate can be
uploaded using the primary node configuration wizard or the administration interface.
n The REST API in this vRealize Operations Manager release supports private keys that are
encrypted by a pass phrase. Contact VMware Technical Support for details.
n The vRealize Operations Manager Web server on all nodes will have the same certificate file,
so it must be valid for all nodes. One way to make the certificate valid for multiple addresses
is with multiple Subject Alternative Name (SAN) entries.
n SHA1 certificates creates browser compatibility issues. Therefore, ensure that all certificates
that are created and being uploaded to vRealize Operations Manager are signed using SHA2
or newer.
n The vRealize Operations Manager supports custom security certificates with key length up to
8192 bits. An error is displayed when you try to upload a security certificate generated with a
stronger key length beyond 8192 bits.
VMware, Inc. 729

For more information, see the following KB articles:
n vRealize Operations Manager 6.x fails to accept and apply Custom CA Certificate (2144949)
Configure a Custom Certificate

You can use OpenSSL to configure an authentication certificate for use with vRealize Operations
Manager. You must first generate a Certificate PEM for vRealize Operations Manager, then install
the Certificate PEM in vRealize Operations Manager. The certificates applied through the vRealize
Operations Manager Admin UI will be used only for securely connecting and serving the user
interfaces to (external) clients. We do not update the certificates for specific components of
Procedure
1 Generate a Certificate PEM file for use with vRealize Operations Manager
a Generate a key pair by running this command:
openssl genrsa -out key_filename.key 2048
b Use the key to generate a certificate signing request by running this command:
openssl req -new -key key_filename.key -out certificate_request.csr
c Submit the CSR file to your Certificate Authority (CA) to obtain a signed certificate.
d From your Certificate Authority, download the certificate and the complete issuing chain
(one or more certificates). Download them in Base64 format.
e Enter the command to create a single PEM file containing all certificates and the private
key. In this step, the example certificate is server_cert.cer and the issuing chain is
cacerts.cer.
Note The order of CA's certs in the .PEM file: Cert, Private Key, Intermediate Cert and then
Root Cert.
cat server_cert.cer key_filename.key cacerts.cer > multi_part.pem
In Windows replace cat with type.
The finished PEM file should look similar to the following example, where the number of
CERTIFICATE sections depends on the length of the issuing chain:
-----BEGIN CERTIFICATE-----
(Your Primary SSL certificate: your_domain_name.crt)
-----END CERTIFICATE-----
-----BEGIN RSA PRIVATE KEY-----
(Your Private Key: your_domain_name.key)
-----END RSA PRIVATE KEY-----
(Your Intermediate certificate: DigiCertCA.crt)
VMware, Inc. 730

(Your Root certificate: TrustedRoot.crt)
2 Install a PEM in vRealize Operations Manager
a In a Web browser, navigate to the vRealize Operations Manager administration interface.
https://vrops-node-FQDN-or-ip-address/admin
b Log in with the admin username and password.
c At the upper right, click the yellow SSL Certificate icon.
d In the SSL Certificate window, click Install New Certificate.
e Click Browse for certificate.
f Locate the certificate .pem file, and click Open to load the file in the Certificate
Information text box. The certificate file must contain a valid private key and a valid
certificate chain.
g Click Install.
Verifying a Custom vRealize Operations Manager Certificate

When you upload a custom certificate file, the vRealize Operations Manager interface displays
summary information for all certificates in the file.
For a valid custom certificate file, you should be able to match issuer to subject, issuer to subject,
back to a self-signed certificate where the issuer and subject are the same.
In the following example, OU=MBU,O=VMware\, Inc.,CN=vc-ops-slice-32 is issued by OU=MBU,O=VMware

\, Inc.,CN=vc-ops-intermediate-32, which is issued by OU=MBU,O=VMware\, Inc.,CN=vc-ops-cluster-
ca_33717ac0-ad81-4a15-ac4e-e1806f0d3f84, which is issued by itself.
Thumbprint: 80:C4:84:B9:11:5B:9F:70:9F:54:99:9E:71:46:69:D3:67:31:2B:9C
Issuer Distinguished Name: OU=MBU,O=VMware\, Inc.,CN=vc-ops-intermediate-32
Subject Distinguished Name: OU=MBU,O=VMware\, Inc.,CN=vc-ops-slice-32
Subject Alternate Name:
PublicKey Algorithm: RSA
Valid From: 2015-05-07T16:25:24.000Z
Valid To: 2020-05-06T16:25:24.000Z
Thumbprint: 72:FE:95:F2:90:7C:86:24:D9:4E:12:EC:FB:10:38:7A:DA:EC:00:3A
Issuer Distinguished Name: OU=MBU,O=VMware\, Inc.,CN=vc-ops-cluster-ca_33717ac0-ad81-4a15-ac4e-
e1806f0d3f84
Subject Distinguished Name: OU=MBU,O=VMware\, Inc.,CN=vc-ops-intermediate-32
Subject Alternate Name: localhost,127.0.0.1
Valid From: 2015-05-07T16:25:19.000Z
Valid To: 2020-05-06T16:25:19.000Z
Thumbprint: FA:AD:FD:91:AD:E4:F1:00:EC:4A:D4:73:81:DB:B2:D1:20:35:DB:F2
VMware, Inc. 731

Issuer Distinguished Name: OU=MBU,O=VMware\, Inc.,CN=vc-ops-cluster-ca_33717ac0-ad81-4a15-ac4e-

e1806f0d3f84
Subject Distinguished Name: OU=MBU,O=VMware\, Inc.,CN=vc-ops-cluster-ca_33717ac0-ad81-4a15-ac4e-
e1806f0d3f84
Subject Alternate Name: localhost,127.0.0.1
Valid From: 2015-05-07T16:24:45.000Z
Valid To: 2020-05-06T16:24:45.000Z
Sample Contents of Custom vRealize Operations Manager Certificates

For troubleshooting purposes, you can open a custom certificate file in a text editor and inspect
its contents.
PEM Format Certificate Files
A typical PEM format certificate file resembles the following sample.
MIIF1DCCBLygAwIBAgIKFYXYUwAAAAAAGTANBgkqhkiG9w0BAQ0FADBhMRMwEQYK
CZImiZPyLGQBGRYDY29tMRUwEwYKCZImiZPyLGQBGRYFdm13Y3MxGDAWBgoJkiaJ
<snip>
vKStQJNr7z2+pTy92M6FgJz3y+daL+9ddbaMNp9fVXjHBoDLGGaLOvyD+KJ8+xba
aGJfGf9ELXM=
MIIEowIBAAKCAQEA4l5ffX694riI1RmdRLJwL6sOWa+Wf70HRoLtx21kZzbXbUQN
mQhTRiidJ3Ro2gRbj/btSsI+OMUzotz5VRT/yeyoTC5l2uJEapld45RroUDHQwWJ
<snip>
DAN9hQus3832xMkAuVP/jt76dHDYyviyIYbmxzMalX7LZy1MCQVg4hCH0vLsHtLh
M1rOAsz62Eht/iB61AsVCCiN3gLrX7MKsYdxZcRVruGXSIh33ynA
-----END RSA PRIVATE KEY-----
MIIDnTCCAoWgAwIBAgIQY+j29InmdYNCs2cK1H4kPzANBgkqhkiG9w0BAQ0FADBh
MRMwEQYKCZImiZPyLGQBGRYDY29tMRUwEwYKCZImiZPyLGQBGRYFdm13Y3MxGDAW
<snip>
ukzUuqX7wEhc+QgJWgl41mWZBZ09gfsA9XuXBL0k17IpVHpEgwwrjQz8X68m4I99
dD5Pflf/nLRJvR9jwXl62yk=
Private Keys
Private keys can appear in different formats but are enclosed with clear BEGIN and END markers.
Valid PEM sections begin with one of the following markers.

-----BEGIN PRIVATE KEY-----
Encrypted private keys begin with the following marker.
-----BEGIN ENCRYPTED PRIVATE KEY-----
VMware, Inc. 732

Bag Attributes
Microsoft certificate tools sometimes add Bag Attributes sections to certificate files. vRealize
Operations Manager safely ignores content outside of BEGIN and END markers, including Bag
Attributes sections.
Bag Attributes
Microsoft Local Key set: <No Values>
localKeyID: 01 00 00 00
Microsoft CSP Name: Microsoft RSA SChannel Cryptographic Provider
friendlyName: le-WebServer-8dea65d4-c331-40f4-aa0b-205c3c323f62
Key Attributes
X509v3 Key Usage: 10
-----BEGIN PRIVATE KEY-----
MIICdwIBADANBgkqhkiG9w0BAQEFAASCAmEwggJdAgEAAoGBAKHqyfc+qcQK4yxJ
om3PuB8dYZm34Qlt81GAAnBPYe3B4Q/0ba6PV8GtWG2svIpcl/eflwGHgTU3zJxR
gkKh7I3K5tGESn81ipyKTkPbYebh+aBMqPKrNNUEKlr0M9sa3WSc0o3350tCc1ew
5ZkNYZ4BRUVYWm0HogeGhOthRn2fAgMBAAECgYABhPmGN3FSZKPDG6HJlARvTlBH
KAGVnBGHd0MOmMAbghFBnBKXa8LwD1dgGBng1oOakEXTftkIjdB+uwkU5P4aRrO7
vGujUtRyRCU/4fjLBDuxQL/KpQfruAQaof9uWUwh5W9fEeW3g26fzVL8AFZnbXS0
7Z0AL1H3LNcLd5rpOQJBANnI7vFu06bFxVF+kq6ZOJFMx7x3K4VGxgg+PfFEBEPS
UJ2LuDH5/Rc63BaxFzM/q3B3Jhehvgw61mMyxU7QSSUCQQC+VDuW3XEWJjSiU6KD
gEGpCyJ5SBePbLSukljpGidKkDNlkLgbWVytCVkTAmuoAz33kMWfqIiNcqQbUgVV
UnpzAkB7d0CPO0deSsy8kMdTmKXLKf4qSF0x55epYK/5MZhBYuA1ENrR6mmjW8ke
TDNc6IGm9sVvrFBz2n9kKYpWThrJAkEAk5R69DtW0cbkLy5MqEzOHQauP36gDi1L
WMXPvUfzSYTQ5aM2rrY2/1FtSSkqUwfYh9sw8eDbqVpIV4rc6dDfcwJBALiiDPT0
tz86wySJNeOiUkQm36iXVF8AckPKT9TrbC3Ho7nC8OzL7gEllETa4Zc86Z3wpcGF
BHhEDMHaihyuVgI=
-----END PRIVATE KEY-----
Bag Attributes
localKeyID: 01 00 00 00
1.3.6.1.4.1.311.17.3.92: 00 04 00 00
1.3.6.1.4.1.311.17.3.20: 7F 95 38 07 CB 0C 99 DD 41 23 26 15 8B E8
D8 4B 0A C8 7D 93
friendlyName: cos-oc-vcops
1.3.6.1.4.1.311.17.3.71: 43 00 4F 00 53 00 2D 00 4F 00 43 00 2D 00
56 00 43 00 4D 00 35 00 37 00 31 00 2E 00 76 00 6D 00 77 00 61 00
72 00 65 00 2E 00 63 00 6F 00 6D 00 00 00
1.3.6.1.4.1.311.17.3.87: 00 00 00 00 00 00 00 00 02 00 00 00 20 00
00 00 02 00 00 00 6C 00 64 00 61 00 70 00 3A 00 00 00 7B 00 41 00
45 00 35 00 44 00 44 00 33 00 44 00 30 00 2D 00 36 00 45 00 37 00
30 00 2D 00 34 00 42 00 44 00 42 00 2D 00 39 00 43 00 34 00 31 00
2D 00 31 00 43 00 34 00 41 00 38 00 44 00 43 00 42 00 30 00 38 00
42 00 46 00 7D 00 00 00 70 00 61 00 2D 00 61 00 64 00 63 00 33 00
2E 00 76 00 6D 00 77 00 61 00 72 00 65 00 2E 00 63 00 6F 00 6D 00
5C 00 56 00 4D 00 77 00 61 00 72 00 65 00 20 00 43 00 41 00 00 00
31 00 32 00 33 00 33 00 30 00 00 00
subject=/CN=cos-oc-vcops.eng.vmware.com
issuer=/DC=com/DC=vmware/CN=VMware CA
MIIFWTCCBEGgAwIBAgIKSJGT5gACAAAwKjANBgkqhkiG9w0BAQUFADBBMRMwEQYK
CZImiZPyLGQBGRYDY29tMRYwFAYKCZImiZPyLGQBGRYGdm13YXJlMRIwEAYDVQQD
EwlWTXdhcmUgQ0EwHhcNMTQwMjA1MTg1OTM2WhcNMTYwMjA1MTg1OTM2WjAmMSQw
VMware, Inc. 733

vRealize Operations Manager Certificates

vRealize Operations Manager includes a central page where you can review authentication
certificate contents. Certificates allow the vRealize Operations Manager cluster nodes to
authenticate each other.
How the Certificates Page Works

The Certificates page lets you examine certificate contents without the need to open the
certificate outside of vRealize Operations Manager.
Where You Find Certificates

In the menu, click Administration, and then in the left pane, click Management > Certificates.
Certificate Tabs
The certificate tab describes columns of exceptions tabs.
Note The CRL tab is enabled only when you select the Enable Standard Certificate Validation
under Global Settings.
Table 4-215. Certificate Tabs

Tabs Description
Exceptions Lists the certificate that is accepted by the vRealize

Operations Manager administrator but is not certified by
the Certificate Authority (CA).
CRL A Certificate Revocation List (CRL) is a list of digital

certificates that have been revoked by the issuing
Certificate Authority (CA) before their scheduled expiration
date and should no longer be trusted. Click the Add icon to
upload the certificates.
Certificate Options
The options include a data grid for examining certificate contents.
Table 4-216. Certificate Options

Option Description
Certificate Thumbprint Unique alphanumeric string associated with the certificate
Issued By Content associated with the issuer of the certificate, such

as organization name and location
Issued To Typically, content associated with the issuer, plus the

certificate object Identifier (OID)
Expires The date after which the certificate cannot be used for
successful authentication
VMware, Inc. 734

Add a Custom Certificate to vRealize Operations Manager

If you did not add your own SSL/TLS certificate when configuring the vRealize Operations
Manager primary node, you can still add a certificate after vRealize Operations Manager is
installed.
Prerequisites
Procedure

https://node-FQDN-or-ip-address/admin.
2 Log in with the admin username and password.
3 At the upper right, click the yellow certificate icon.
4 In the certificate window, click Install New Certificate.
5 Click Browse for certificate.
6 Locate the certificate .pem file, and click Open to load the file in the Certificate Information
text box.
7 Click Install.
Removing an Adapter Certificate

If you want to delete an old or expired certificate associated with an adapter, perform the
following steps:
Procedure

https://node-FQDN-or-ip-address/ui.
2 Log in with the administrator username and password.
3 In the menu, click Administration, and in the left pane click Management > Certificates.
4 In the certificate window, select the certificate that has to be removed.
5 Click the x to remove the certificate.
6 If the certificate is being used by the adapter, then the following message comes up:
A certificate can be configured for one or more adapters if it is the same destination system.
VMware, Inc. 735

7 If you delete a certificate which is already being used by another adapter, the adapter fails to
connect or start. As a workaround, perform the following steps:
a On the left pane, click Solutions.
b Select the particular adapter and click the Configure button on the toolbar.
c Click Test Connection.
d A prompt comes up asking the user to import the associated certificate. Click OK.
e Restart the adapter from the Solutions page.
Modifying Global Settings

The global settings control the system settings for vRealize Operations Manager, including data
retention and system timeout settings. You can modify one or more of the settings to monitor
your environment better. These settings affect all your users.
The global settings do not affect metric interactions, color indicators, or other object
management behaviors. These behaviors are configured in your policies.
Settings related to managing objects with vRealize Operations Manager are available on the
Inventory page.
You can view tooltips for each option in the Edit Global Settings dialog box.
Global Settings Best Practices

Most of the settings pertain to how long vRealize Operations Manager retains collected and
process data.
The default values are common retention periods. You might need to adjust the time periods
based on your local policies or disk space.
List of Global Settings

The global settings determine how vRealize Operations Manager retains data, keeps connection
sessions open, and other settings. These are system settings that affect all users.
VMware, Inc. 736

Table 4-217. Global Setting Default Values and Descriptions

Default
Setting Value Description
Action History 30 days Number of days to retain the recent task data for actions.
The data is purged from the system after the specified number
of days.
Deleted Objects 168 hours Number of hours to retain objects that are deleted from an
adapter data source or server before deleting them from
An object deleted from an adapter data source is identified by
vRealize Operations Manager as not existing and vRealize
Operations Manager can no longer collect data about the
object. Whether vRealize Operations Manager identifies deleted
objects as not existing depends on the adapter. This feature is
not implemented in some adapters.
For example, if the retention time is 360 hours and a virtual
machine is deleted from a vCenter Server instance, the virtual
machine remains as an object in vRealize Operations Manager
for 15 days before it is deleted.
This setting applies to objects deleted from the data source or
server, not to any objects you delete from vRealize Operations
Manager on the Inventory page.
A value of -1 deletes objects immediately.
You can define the number of hours per object type to retain
objects that no longer exist and check for object type overrides.
To add individual object types and set up their values, click the
Object Deletion Scheduling icon. You can also edit or delete
these object types.
Deletion Schedule Interval 24 hours Determines the frequency to schedule deletion of resources.
This setting works with the Deleted Objects setting to remove
objects that no longer exist in the environment. vRealize
Operations Manager transparently marks objects for removal
that have not existed for the length of time specified under
Deleted Objects. vRealize Operations Manager then removes
the marked objects at the frequency specified under Deletion
Scheduling Interval.
Object History 90 days Number of days to retain the history of the object configuration,
relationship, and property data.
The configuration data is the collected data from the monitored
objects on which the metrics are based. The collected data
includes changes to the configuration of the object.
The data is purged from the system after the specified number
of days.
Session Timeout 30 minutes If your connection to vRealize Operations Manager is idle for the
specified amount of time, you are logged out of the application.
You must provide credentials to log back in.
Symptoms/Alerts 45 days Number of days to retain canceled alerts and symptoms.

The alerts and symptoms are either canceled by the system or
by a user.
VMware, Inc. 737

Table 4-217. Global Setting Default Values and Descriptions (continued)

Default
Time Series Data Retention 6 months Number of months that you want to retain the collected and
calculated metric data for the monitored objects. This setting is
set to 6 months by default for 5 minutes interval data retention.
Additional Time Series Data Retention 36 months The number of months that the roll-up data extends beyond the
regular period. The roll-up data is available starting from the
end of the regular period and until the end of the roll-up data
retention period. If you specify 0 as the value, then this will
effectively disable the Additional Time Series Data Retention
time and only data specified in Time Series Retention is stored.
This setting ensures that after 6 months of normal retention for
5 minutes, the seventh month data is rolled up into a one Hour
roll up. You can set up this option up to 120 months for data roll
ups.
Deleted Users 100 days You can specify the number of days to keep custom content
created by a user who has been removed from vRealize
Operations Manager or by the automatic synchronization of
LDAP. For example, the custom dashboards created by a user.
External Event Based Active disabled The number of days to retain the external event-based active
Symptoms symptoms.
Maintain Relationship History You can maintain a history of all the relationships of all the
monitored objects in vRealize Operations Manager.
Dynamic Threshold Calculation enabled Determines whether to calculate normal levels of threshold
violation for all objects.
If the setting is disabled, the following area of vRealize
Operations Manager does not work or are not displayed:
n Alert symptom definitions based on dynamic thresholds will
not work
n Metric charts that display normal behavior are not present
Disable this setting only if you have no alternative options for
managing resource constraints for your vRealize Operations
Manager system.
Cost Calculation The host time at which cost calculations are run.
Customer Experience Improvement enabled Determines whether to participate in the Customer Experience
Program Improvement Program by having vRealize Operations Manager
send anonymous usage data to https://vmware.com.
Allow vCenter users to log in to Determine how users of vCenter Server login to vRealize
individual vCenters using the vRealize Operations Manager.
Operations Manager UI n In the vRealize Operations Manager user interface, vCenter
Server users can log in to individual vCenter Server
instances. Disabled by default.
n vCenter Server users can log in from vCenter Server clients.
Enabled by default.
n In the vRealize Operations Manager user interface, vCenter
Server users can log in to all vCenter Server instances.
Enabled by default.
VMware, Inc. 738

Table 4-217. Global Setting Default Values and Descriptions (continued)

Default
Allow vCenter users to log in from enabled Allows vCenter users to log in from the vCenter clients.
vCenter clients
Allow vCenter users to log in to all enabled Allows vCenter users to log in to all vCenters using the vRealize
vCenters using the vRealize Operations Operations Manager UI.
Manager UI
Automated Actions enabled or Determines whether to allow vRealize Operations Manager to

disabled automate actions. When an alert triggered, the alert provides
recommendations for remediation. You can automate an action
to remediate an alert when the recommendation is the first
priority for that alert. You enable actionable alerts in your
policies.
Enable Standard Certification This option enables certificate verification to Test Connection in
Validation the Create or Modify AI screen, using a standard verification
flow.
The option checks CA authority.
n Certificate Subject DN
n Subject alternative name
n Certificate validity period
n Revocation list
This option also presents dialogs to user if one of those checks
fail. It is up to the adapter implementation on how the adapter
checks source certificate validity during a normal collection
cycle. On a usual scenario, adapters just perform a thumb-print
verification. However, in case this flag is enabled, Test
connection validates certificates in full scale and accepts
certificates that are matching all criteria without any user
dialogs.
Concurrent UI login sessions enabled Allows concurrent UI login sessions per user. Once changed,
this setting affects the subsequent login sessions.
Allow non-imported vIDM user access enabled Allows non-imported VMware Identity Manager users to be
created automatically as read-only users upon first access. If
disabled, only VMware Identity Manager imported users or
users belonging to imported VMware Identity Manager groups
will be granted access.
Currency You can specify the currency unit that is used for all the cost
calculations. You can select the type of currency from the list of
currency types by clicking Choose Currency. From the Set
Currency, select the required currency and confirm your action
by clicking the check box, and set the currency.
Global Settings
To manage how vRealize Operations Manager retains data, keeps connection sessions open, and
other settings, you can modify the values for the global settings. These system settings affect all
users.
VMware, Inc. 739

You can also choose to participate in the customer experience improvement program. For more
information on accessing Global settings, see Access Global Settings.
Access Global Settings

With global settings, you set times to delete objects, set timeouts, store historical data, use
dynamic threshold and capacity calculations, and determine how vCenter Server users log in. For
automated actions, you can select whether to allow actions to be triggered from alert
recommendations automatically.
Procedure
1 In the menu, click Administration, and then in the left pane click Management > Global
Settings.
2 To edit the global settings, click the setting you want to edit.
Note Editable global settings have a hidden Edit icon next to their values. To see the icon,
point to the global setting.
Table 4-218. Global Settings Options

Option Description
Edit Global Settings Click the global setting you want to edit to activate the
edit mode and modify the setting values. To edit non-
switchable settings, select a value and then click Save.
To edit switchable settings, select a value and then click
Enable or Disable to change the setting. Click Cancel to
discard all changes and exit the edit mode.
Setting Setting name.
Value Current value for the setting.

To change the setting value, click Edit Global Settings.
Description Information about the setting. Point to the setting to

display additional information about the setting.
The Customer Experience Improvement Program

This product participates in VMware's Customer Experience Improvement Program (CEIP). The
CEIP provides VMware with information that enables VMware to improve its products and
services, to fix problems, and to advise you on how best to deploy and use our products. You
can choose to join or leave the CEIP for vRealize Operations Manager at any time.
Details regarding the data collected through CEIP and the purposes for which it is used by
VMware are set forth at the Trust & Assurance Center at http://www.vmware.com/trustvmware/
ceip.html .
Join or Leave the Customer Experience Improvement Program for vRealize Operations Manager
You can join or leave the Customer Experience Improvement Program (CEIP) for vRealize
Operations Manager at any time.
VMware, Inc. 740

vRealize Operations Manager gives you the opportunity to join the Customer Experience
Improvement Program (CEIP) when you initially install and configure the product. After
installation, you can join or leave the CEIP by following these steps.
Procedure
1 In the menu, click Administration, and then in the left pane, click Management > Global
Settings.
2 From the toolbar, click the Edit icon.
3 Select or clear the Customer Experience Improvement Program option.
This option activates the program and sends data to www.vmware.com.
4 Click OK.
Transfer Ownership of Dashboards and Report Schedules

When a user is deleted from vRealize Operations Manager, the report schedules and dashboards
created by the user are stored as orphaned content. As an admin user, you can transfer
ownership of dashboards and report schedules created by deleted users.
From Where You Can Transfer Ownership of Dashboards and Report Schedules
In the menu, click Administration. From the left pane, select Management > Orphaned Content.
Orphaned Content Page

You can view a list of deleted users from the Deleted Users panel in the left pane of the
Orphaned Content page. Based on your selection in the Deleted Users panel, the dashboards
and report schedules for the deleted user are displayed under the Dashboard and Report
Schedules tabs in the Orphaned Content page.
As an admin user, you can take ownership, assign ownership, or discard orphaned dashboards
and report schedules, from the Actions menu in the Dashboards and Report Schedules tabs.
Enter the name or part of the name of a dashboard or report schedule in the Filter option and
click Enter. The relevant dashboard or report schedule is displayed.
Table 4-219. Actions Menu Options

Actions Options
Take Ownership You can take ownership of the selected dashboards or

report schedules.
Assign Ownership You can assign a new owner for the selected dashboards
or report schedules. You can select a target user from the
Transfer Dashboards/Report Schedule dialog box.
Discard You can permanently delete the dashboards or report

schedules.
vRealize Operations Manager Logs for Product UI
VMware, Inc. 741

How vRealize Operations Manager Logs Work

For troubleshooting in the product UI, the product provides an expandable tree of vRealize
Operations Manager log files that you can browse and load for review. You can also edit the log
file folders, limit the retained log size, and set logging levels.
vRealize Operations Manager logs are categorized by cluster node, and log type.
Where You Find vRealize Operations Manager Logs

In the menu, click Administration, and in the left pane click Support > Logs.
Log Viewer Options

Use the toolbar options to control the tree of items and the viewer.
1 Click Node and select any component that is listed under the node.
2 Click the gear icon, enter the logging levels and log size.
3 Click OK.
Note Not all components have relevant syslog information. Therefore, not all nodes have the
configuration option enabled.
Figure 4-1. Logs
Figure 4-2. Log Options
Table 4-220. Log Viewer Toolbar Options

Option Description
Group By Organizes the tree by cluster node or log type.
Collapse All Closes the view of the tree to show only the high-level folders.
Edit Properties For the selected folder, you can limit the log size and set logging levels.
Delete Selected File Deletes the log file.
VMware, Inc. 742

Table 4-220. Log Viewer Toolbar Options (continued)

Option Description
Starting Line Indicates the starting line of the file .

0 is for the first line. -1 or no value indicates that the file has to be
displayed from the end.
Number of Lines Specifies the number of lines to be displayed in the search result.
For example:
If you want to see the first 10 occurrences of a particular chunk of text,
enter the number of lines as 10 and the starting line as 0.
Min Log Level If you specify the minimum log level, the logs for that particular log level
and higher are shown.
For example:
If you select warning, the logs having the same log level (warning) and
higher are shown .
Text to Find Enter the specific text that you want to search in the logs. Add the
following filters for search, if required:
n Case Sensitive
n Regular Expression
You can perform the search at various levels:
n On a single file: Use this option if you want to search a single log file .
n On all the log files of an entity: Use this option if you want to search all
the log files of an entity such as a log type or folder.
n On all the log files of a node: Use this option if you want to search all
the log files that are grouped under a node.
The last modified time for any file is found by placing the pointer on the
file in the tree.
Set Timerange If you specify a time range, the logs for that particular time range are
shown in the search results.
Word Wrap If you select this option, the part of the line that does not fit on the screen
is moved to the next line. If you do not select this option, a scroll bar is
provided to see the complete line.
Create a vRealize Operations Manager Support Bundle

You create a vRealize Operations Manager support bundle to gather log and configuration files
for analysis when troubleshooting a vRealize Operations Manager issue.
When you create a support bundle, vRealize Operations Manager gathers files from cluster
nodes into ZIP files for convenience.
Procedure
1 In the menu, click Administration, and then in the left pane, click Support > Supoort Bundles.
2 From the toolbar, click the Create a Support Bundle icon.
3 Select the option to create a Light or Full support bundle.
VMware, Inc. 743

4 Select the cluster nodes that need to be evaluated for support.
Only logs from the selected nodes are included in the support bundle.
5 Click OK, and click OK to confirm support bundle creation.
Depending on the size of the logs and number of nodes, it might take time for vRealize
Operations Manager to create the support bundle.
What to do next
Use the toolbar to download the support bundle ZIP files for analysis. For security, vRealize
Operations Manager prompts you for credentials when you download a support bundle.
You can review the log files for error messages or, if you need troubleshooting assistance, send
the diagnostic data to VMware Technical Support. When you resolve or close the issue, use the
toolbar to delete the outdated support bundle to save disk space.
vRealize Operations Manager Support Bundles

vRealize Operations Manager support bundles contain log and configuration files that help
troubleshoot a vRealize Operations Manager issue.
How Support Bundles Work

Support bundles require that you select nodes or the entire cluster, and the level of logging that
you want to collect. After vRealize Operations Manager creates the support bundle, you
download it in ZIP format for analysis.
Where You Find Support Bundles

In the menu, click Administration, and then in the left pane, select Support > Support Bundles.
Support Bundle Options

Use the toolbar options to add, download, or remove items.
Table 4-221. Support Bundle Toolbar Options

Option Description
Add Open a dialog box that guides you through the process of
creating a support bundle.
Delete Remove the selected support bundle.
Download Download the support bundle in ZIP format.
Reload Support Bundles Refresh the list of support bundles.
VMware, Inc. 744

Table 4-222. Support Bundle Data Grid Options

Option Description
Bundle System-generated identifier for the support bundle
Bundle Type n Light. Include 24 hours of logs

n Full. Include all available logs and configuration files
Date and Time Created Time when support bundle creation began
Status Progress of support bundle creation
vRealize Operations Manager Dynamic Thresholds

A threshold marks the boundary between normal and abnormal behavior for a metric. In addition
to fixed thresholds, vRealize Operations Manager supports dynamic thresholds for a metric,
calculated based on historical and incoming data.
How Dynamic Thresholds Work

By default, dynamic thresholds are refreshed on a regular schedule, but you can recalculate
dynamic thresholds outside of the schedule if you want to capture the most recent data.
Where You Find Dynamic Thresholds

In the menu, click Administration, and then in the left pane, select Support > Dynamic
Thresholds.
Dynamic Threshold Options

The dynamic threshold feature includes options to start or stop the calculation process and to
review associated values.
Table 4-223. Dynamic Threshold Options

Option Description
Start Run the dynamic threshold calculation process now,

outside of its normal schedule
Stop Stop the dynamic threshold calculation currently in

progress
Calculation progress Percentage completion of the current dynamic threshold

calculation
Calculation times and Count Timestamps and metric counts associated with the last
dynamic threshold calculation, as well as the time for the
next scheduled calculation
vRealize Operations Manager Adapter Redescribe

When vRealize Operations Manager redescribes an adapter, vRealize Operations Manager finds
the adapter files, gathers information about the abilities of the adapter, and updates the user
interface with information about the adapter.
VMware, Inc. 745

How Adapter Redescribe Works

After installing or updating an adapter, capture the adapter information by having vRealize
Operations Manager redescribe its adapters.
Where You Find Adapter Redescribe

In the menu, click Administration, and then in left pane, click Support > Redescribe.
Adapter Redescribe Options

The feature includes an option to start the adapter describe process.
Table 4-224. Adapter Redescribe Options

Option Description
Redescribe Start the adapter describe process
vRealize Operations Manager provides adapter-specific details from the redescribe process.
Table 4-225. Adapter Redescribe Details

Option Description
Name Adapter to which the redescribe process applies
Status Success, failure, or other condition related to the last

redescribe process
Describe Version Version of describe.xml against which the last redescribe

process ran
Adapter Version Version of the adapter against which the last redescribe
process ran
Message Additional details about the last redescribe process
Customizing Icons
Every object or adapter in your environment has an icon representation. You can customize how
the icon appears.
vRealize Operations Manager assigns a default icon to each object type and adapter type . Taken
collectively, object types and adapter types are known as objects in your environment. Icons
represent objects in the UI and help you to identify the type of object. For example, in the
Topology Graph widget on a dashboard, labeled icons show how objects are connected to one
other. You can quickly identify the type of object from the icon.
If you want to differentiate objects, you can change the icon. For example, a virtual machine icon
is generic. If you want to pictorially distinguish the data that a vSphere virtual machine provides
from the data that a Hypervisor virtual machine provides, you can assign a different icon to each.
VMware, Inc. 746

Customize an Object Type Icon

You can use the default icons that vRealize Operations Manager provides, or you can upload
your own graphics file for an object type. When you change an icon, your changes take effect for
all users.
Prerequisites
If you plan to use your own icon files, verify that each image is in PNG format and has the same
height and width. For best results, use a 256x256 pixel image size.
Procedure
1 In the menu, click Administration, and then in the left pane, click Configuration > Icons.
2 Click the Object Type Icons tab.
3 Assign the Object Type icon.
a Select the object type in the list with the icon to change.
By default, object types for all adapter types are listed. To limit the selection to the object
types that are valid for a single adapter type, select the adapter type from the drop-
down menu.
b Click the Upload icon.
c Browse to and select the file to use and click Done.
4 (Optional) To return to the default icon, select the object type and click the Assign Default
Icons icon.
The original default icon appears.
Object Type Icons Tab

vRealize Operations Managerobtains data from different sources. Data sources are classified by
the type of object or object type. In UI locations where metric data appears for objects, vRealize
Operations Manager includes an icon to show the object type. To graphically distinguish the
different types of objects, you can customize the icon.
Where You Customize Object Type Icons
In the menu, click Administration, and then in the left pane, click Configuration > Icons > Object
Type Icons.
VMware, Inc. 747

Table 4-226. Object Type Icons Options

Option Description
Adapter Type Icons for all adapters are listed by default. To list a subset
of the object types that are valid for one type of adapter,
select the adapter type.
Toolbar options Manages the selected icon.

n Upload uploads a PNG file to uniquely identify the
object type.
n Assign Default icons returns the selection to the
original icon.
Search Search for objects with a particular name to narrow the

selection of object types displayed.
Object Type Name of the type of object.
Icon Pictorial representation of the type of object.
Customize an Adapter Type Icon

You can use the default icons that vRealize Operations Manager provides, or you can upload
your own graphics file for an adapter type. When you change an icon, your changes take effect
for all users.
Prerequisites
If you plan to use your own icon files, verify that each image is in PNG format and has the same
height and width. For best results, use a 256x256 pixel image size.
Procedure
1 In the menu, click Administration, and then in the left pane, click Configuration > Icons.
2 Click Adapter Type Icons tab.
3 Assign the Adapter Type icon.
a Select the adapter type in the list with the icon to change.
b Click the Upload icon.
c Browse to and select the file to use and click Done.
4 (Optional) To return to the default icon, select the adapter type and click the Assign Default
Icons icon.
The original default icon appears.
Adapter Type Icons Tab

Adapters collect and provide data tovRealize Operations Manager. Adapters are classified by the
type of adapter or adapter kind. To graphically distinguish the different types of adapters, you
can customize the icon.
VMware, Inc. 748

Where You Customize Adapter Type Icons

In the menu, click Administration, and then in the left pane, click Configuration > Icons > Adapter
Type Icons.
Table 4-227. Adapter Type Icons Options

Option Description
Toolbar options Manages the selected icon.

n Upload uploads a PNG file to uniquely identify the
adapter type.
n Assign Default icons returns the selection to the
original icon.
Name Name of the type of adapter.
Icon Pictorial representation of the type of adapter.
Allocate More Virtual Memory to vRealize Operations Manager

You might need to add virtual memory to keep the vRealize Operations Manager process
running.
When the vRealize Operations Manager virtual machine requests more memory than is available,
the Linux kernel might kill the vcops-analytics process, and the product might become
unresponsive. If that happens, use the reservation feature in vSphere to specify the guaranteed
minimum memory allocation for vRealize Operations Manager virtual machines.
Procedure
1 In the vSphere Client inventory, right-click the vRealize Operations Manager virtual machine
and select Edit Settings.
2 Click the Resources tab, and select Memory.
3 Use the Reservation option to allocate more memory.
About the vRealize Operations Manager Administration

Interface
The vRealize Operations Manager administration interface provides access to selected
maintenance functions beyond what the product interface supports.
Use the vRealize Operations Manager administration interface instead of the product interface
under the following conditions. You can access the administration interface login page from any
node in the vRealize Operations Manager analytics cluster by appending /admin to the node IP
address or FQDN when you enter the URL in your browser.
n Enable or disable high availability (HA).
n Upload and install vRealize Operations Manager software update PAK files.
VMware, Inc. 749

n The product interface is inaccessible, and you need to correct the problem by bringing nodes
online, or by restarting nodes or the cluster.
n vRealize Operations Manager needs to be restarted for any reason.
There is some overlap between the administration interface and product interface in terms of
access to logs, support bundles, and some of the node maintenance activities that do not involve
restarting the cluster, such as adding nodes.
vRealize Operations Manager Cluster Management

vRealize Operations Manager includes a central page where you can monitor and manage the
nodes in your vRealize Operations Manager cluster and the adapters that are installed on the
nodes.
How Cluster Management Works

You can view and change the online or offline state of the overall vRealize Operations Manager
cluster or the individual nodes. In addition, you can enable or disable high availability (HA) and
view statistics related to the adapters that are installed on the nodes.
Where You Find Cluster Management

or-ip-address/admin.
Cluster Management Options

The options include cluster-level monitoring and management features.
Table 4-228. Initial Setup Status Details

Option Description
Cluster Status Displays the online, offline, or unknown state of the

vRealize Operations Manager cluster and provides an
option to take the cluster online or offline.
If a cluster fails to go offline, click the Force Take Offline
button to take the cluster offline.
Note The Force Take Offline button appears only when

the Bring Cluster offline operation fails.
You can select to display the reason for taking the cluster
offline. Select the Show reason on maintenance page
check box in the Take Cluster Offline dialog box. When
you log in to vRealize Operations Manager when the cluster
is offline, the reason for taking the cluster offline is
displayed.
High Availability Indicates whether HA is enabled, disabled, or degraded

and provides an option to change that setting.
vRealize Operations Manager provides node-level information as well as a toolbar for taking
nodes online or offline.
VMware, Inc. 750


Option Description
Generate Passphrase Generate a passphrase that can be used instead of the

administrator credentials to add a node to this cluster.
Take Node Online/Offline You can select the required node and bring it online or
offline. You are required to understand the risk involved
and provide a valid reason for the action performed when
you bring a node online or offline.
Reload Nodes You can fetch data from the nodes.
Shrink Cluster This option provides a mechanism to remove a node

without having to lose any data. The shrink cluster removes
nodes by migrating data from one node to any other node.
All the historical data is either moved to the primary node
or any other node, which has sufficient disk space.
If HA is enabled and you have selected the replica node for
removal, then you are asked to select another replica node.
vRealize Operations Manager provides a list of nodes that
be a possible candidate to become a replica node.
vRealize Operations Manager stops collecting data from
the removed nodes. However, the data that is available in
the removed node is migrated to an existing node. Once
the migration is complete, then the removed nodes are
deleted with the cluster state as offline.
For remote collectors, if any adapters are on the collectors
of the removed nodes, then such nodes are migrated as
well.
Note vRealize Operations Manager cannot move pinned

adapters. The adapter instances which were pinned on
removed nodes do not move to another collector
automatically. You must change the collector before
starting the shrink cluster process.

Option Description
Node Name Machine name of the node.

The node that you are logged into displays a dot next to
the name.
Node Address Internet protocol (IP) address of the node. Primary and
replica nodes require static IP addresses. Data nodes may
use DHCP or static IP.
Cluster Role Type of vRealize Operations Manager node: primary, data,

replica, or remote collector.
State Powered on, powered off, unknown, or other condition of

the node.
Status Online, offline, unknown, or other condition of the node.
VMware, Inc. 751

Table 4-230. Nodes in the vRealize Operations Manager Cluster (continued)

Option Description
Objects Total environment objects that the node currently

monitors.
Metrics Total metrics that the node has collected since being
added to the cluster.
Build vRealize Operations Manager software build number

Version vRealize Operations Manager software version installed on

the node.
Deployment Type Type of machine on which the node is running: vApp
SSH Status Enable or disable the SSH Status.
In addition, there are adapter statistics for the selected node.
Table 4-231. Adapters on Server

Option Description
Name Name that the installing user gave to the adapter.
Status Indication of whether the adapter is collecting data or not.
Objects Total environment objects that the adapter currently

monitors.
Metrics Total metrics that the adapter has collected since being
Last Collection Time Date and time of the most recent data collection by the
adapter.
Added On Date and time when the adapter was installed on the node.
vRealize Operations Manager Logs for Admin UI

For troubleshooting in the Admin UI, the product provides an expandable tree of vRealize
Operations Manager log files that you can browse and load for review.
How vRealize Operations Manager Logs Work

vRealize Operations Manager logs are categorized by cluster node, and functional area or log
type.
Where You Find vRealize Operations Manager Logs

1 Log in to the vRealize Operations Manager administration interface at https://master-node-
name-or-ip-address/admin.
2 In the menu, click Administration, and in the left pane click Support > Logs.
VMware, Inc. 752

Log Viewer Options

Use the toolbar options to control the tree of items and the viewer.
Table 4-232. Log Viewer Toolbar Options

Option Description
Starting Line Specifies the starting line of the file to be displayed.

Note: 0 is for the first line. -1 or no value indicates that the
file has to be displayed from the end.
Number of Lines Specifies the number of lines to be displayed from the file.
For example:
If you want to see the first 10 lines of the required text,
specify the number of lines as 10 and the starting line as 0.
Word Wrap If you select this option, the extra part of the line that does
not fit on the screen is moved to the next line. If you do not
select this option, a scroll bar is provided to see the
complete line.
vRealize Operations Manager Support Bundles

vRealize Operations Manager support bundles contain log and configuration files that help
troubleshoot a vRealize Operations Manager issue.
How Support Bundles Work

Support bundles require that you select nodes or the entire cluster, and the level of logging that
you want to collect. After vRealize Operations Manager creates the support bundle, you
download it in ZIP format for analysis.
Where You Find Support Bundles

or-ip-address/admin.
Support Bundle Options

Use the toolbar options to add, download, or remove items.
Table 4-233. Support Bundle Toolbar Options

Option Description
Add Open a dialog box that guides you through the process of
creating a support bundle.
Delete Remove the selected support bundle.
Download Download the support bundle in ZIP format.
Reload Refresh the list of support bundles.
VMware, Inc. 753

Table 4-234. Support Bundle Data Grid Options

Option Description
Bundle System-generated identifier for the support bundle
Bundle Type n Light. Include 24 hours of logs

n Full. Include all available logs and configuration files
Date and Time Created Time when support bundle creation began
Status Progress of support bundle creation
Update the Reference Database for vRealize Operations Manager

You can update the reference database to have the most updated version of the reference
library. The reference database supplies default values for cost calculations.
Procedure
1 In the menu, click Administration and in the left pane click Support > Cost Reference
Database.
The existing version of the reference database along with the date is displayed.
2 Click Download Here.
The latest version of the reference database is downloaded to the default location.
3 Click Upload Reference Database and select the reference database from the default
download location.
Results
Note that the updated reference library values are reflected in the cost drivers only after the cost
calculation process runs as per the schedule.
Configuring and Using Workload Optimization

Workload Optimization provides for moving virtual compute resources and their file systems
dynamically across datastore clusters within a data center or custom data center.
Using Workload Optimization, you can rebalance virtual machines and storage across clusters,
relieving demand on an overloaded individual cluster and maintaining or improving cluster
performance. You can also set your automated rebalancing policies to emphasize VM
consolidation, which potentially frees up hosts and reduces resource demand.
Workload Optimization further enables you potentially to automate a significant portion of your
data center compute and storage optimization efforts. With properly defined policies
determining the threshold at which resource contention automatically runs an action, a data
center performs at optimum.
VMware, Inc. 754

vRealize Automation Integration

When you add an instance to a vRealize Automation adapter or solution pack as well as to a
vCenter Server adapter instance that is connected to the vRealize Automation server, using
vRealize Automation-managed resources, vRealize Operations Manager automatically adds a
custom data center for the vCenter Server, using vRealize Automation-managed resources.
On the vRealize Operations Manager side, to get the day2 chain configured, you must make the
following initial configurations:
1 In vCenter Server, Administration -> Solutions and then add the VMware vSphere adapter
instance for the vCenter Server that is configured as an endpoint in vRealize Automation
Server.
2 In vCenter Server, Administration -> Solutions and then add the VMware vRealize
Automation adapter instance for the server that will appear in the vRealize Operations
Manager and vRealize Automation integration day2 chain.
vRealize Operations Manager can manage workload placement and optimization for the custom
data centers that reside in vRealize Automation-managed clusters.
However, vRealize Operations Manager is not permitted to set tag policies for the custom data
center. (At the Workload Optimization screen, the Business Intent window is not operational for
vRealize Automation custom data centers.) When rebalancing a vRealize Automation custom
data center, vRealize Operations Manager uses all applicable policies and placement principles
from both systems: vRealize Automation and vRealize Operations Manager. For more information
on configuring vRealize Automation to work with vRealize Operations Manager, see vRealize
Automation Solution For complete information on creating and managing vRealize Automation
custom data centers that are managed by vRealize Operations Manager, see the vRealize
Automation documentation.
Configuring Workload Optimization

Workload Optimization offers you the potential to automate fully a significant portion of your
cluster workload rebalancing tasks. The tasks to accomplish workload automation are as follows:
1 Configure the Workload Automation Details. See Workload Automation Details.
2 Tag VMs for cluster placement. See Business Intent - Host-Based Virtual Machine Placement
and Business Intent: Tag-Based VM Placement in Clusters.
3 If you do not use the AUTOMATE function in the Optimization Recommendation pane at the
Workload Automation screen, configure the two Workload Optimization alerts to be
triggered when cluster CPU/memory limits are breached, and configure them as automated.
When the alerts are automated, the actions calculated by Workload Optimization are run
automatically. See Configuring Workload Optimization Alerts
VMware, Inc. 755

Prerequisites
Workload Optimization acts on objects associated with the VMware vSphere Solution that
connects vRealize Operations Manager to one or more vCenter Server instances. The virtual
objects in this environment include a vCenter Server, data centers and custom data centers,
cluster compute and storage resources, host systems, and virtual machines. Specific
requirements:
n A vCenter Adapter configured with the actions enabled for each vCenter Server instance.
n A vCenter Server instance with at least two datastore clusters with sDRS enabled and fully
automated.
n Any non-datastore clusters must have DRS enabled and fully automated
n Storage vMotion must be set to ON at Workload Automation Details. The default is On.
n You must have permission to access all objects in the environment.
Design Considerations
The following rules constrain the possible computer and storage resource moves that can be
performed.
Note When vRealize Operations Manager suggests that you optimize clusters in a data center,
the system does not guarantee it can run an optimization action. vRealize Operations Manager
analytics can determine that optimization is desirable and can create a rebalancing plan.
However, the system cannot automatically identify all the architectural constraints that may be
present. Such constraints may prevent an optimization action, or cause an action in progress to
fail.
n Moving compute and storage resources is allowed only within, not across data centers or
custom data centers.
n Storage resources cannot be moved across non-datastore clusters. Storage can move only
across datastore clusters that have sDRS fully automated.
n Compute-resource-only moves are permitted through shared storage.
n Virtual machines defined with affinity rules or anti-affinity rules are not to be moved.
n Virtual machines cannot be moved when residing on a local datastore, unless a storage swap
exists on the local datastore.
n Virtual machines cannot be moved if they have data residing across multiple datastore
clusters. Compute-only moves with similar shared storage are not permitted.
n A virtual machine cannot have data that resides across different storage types. For example,
if a virtual machine has a VM disk on a datastore and a second VM disk on a datastore
cluster, the virtual machine does not move, even when the datastore is shared with the
destination or has swap on it.
VMware, Inc. 756

n A virtual machine can use RDM so long as the destination datastore cluster can access the
RDM LUN.
n A virtual machine can implement VM disks on multiple datastores inside a single datastore
cluster.
n Workload Optimization may suggest moving virtual machines that are protected by vSphere
Replication or Array Based Replication. You must ensure that all the clusters within a selected
data center or custom data center have replication available. You can set up DRS affinity
rules on virtual machines that you do not want moving across clusters.
Business Intent: Tag-Based VM Placement in Clusters

You can use vCenter Server tagging to tag VMs and associated clusters, respectively, with
specific tags. These tags define - for a given cluster - the set of VMs that is placed with that
cluster and remains within the cluster. When the system runs an optimization action, it uses VM-
to-cluster tag matching to ensure that VMs are moved to - or stay with - the appropriate cluster.
To edit Business Intent values, you must have privileges for Administration -> Configuration ->
Workload Placement Settings -> Edit.
Using Tags for Cluster Flexibility

When configuring custom data centers and clusters without tags, you configure CDCs as
relatively homogeneous. All cluster resources must support, for example, the same OS or the
same security requirements so that optimization actions do not place VMs in the wrong cluster.
The tagging approach enables you to define zones of infrastructure within cluster boundaries.
For example, you can ensure that during workload optimization actions, Windows VMs are
moved only to Windows-licensed clusters and Oracle VMs are moved only to Oracle-licensed
clusters. Similarly, you can enable tiers of service in an application, where "Tier 1" VMs are moved
only to Tier 1 clusters running business-critical applications. Other examples include separating
VMs according to OS, or creating network boundaries.
VMs and clusters can be tagged with more than one tag. VMs with multiple tags are placed only
on clusters with all matching tags.
Note VM-to-cluster tagging is not the same as host-based VM tagging. See Business Intent -
Host-Based Virtual Machine Placement .
vCenter Server tags are implemented as key:value labels that enable operators to add meta-data
to vCenter Server objects. In vCenter Server terminology, the key is the tag category and the
value is the tag name.
Using this construct, the tag OS: Linux can indicate a cluster or VM that is assigned to the
category OS with a tag name of Linux. For complete information on vCenter Server tagging
capabilities, refer to the vCenter Server and Host Management guide.
The system provides several preset categories at the Business Intent Workspace:
n Operating System
VMware, Inc. 757

n Environment
n Tier
n Network
n Other
These categories represent potential business intent in gathering VMs into various associations.
You are free to remove a category or add a new one that works for your environment.
Using this construct, the tag OS: Linux can indicate a cluster or VM that is assigned to the
category OS with a tag name of Linux. For complete information on vCenter Server tagging
capabilities, refer to the vCenter Server and Host Management guide.
In vRealize Operations Manager, you assign category and name tags in Policies, at the Business
Intent workspace.
Tagging Considerations
n You can choose either cluster-tag-based placement or host-based placement in the same
data center or custom data center, but not both. If you select cluster-tag-based placement,
host tags are ignored. Conversely, if you choose host-tag-based placement, cluster tags are
ignored.
n If a VM is tagless, the system attempts to move it to a tagless cluster.
Tag Implementation Example: Cluster Zones of Service and Licensing

The following example shows how an administrator assigned tags to clusters and VMs to create
zones within a data center:
Gold Silver Oracle
Production 1 2 3 4 5
Staging 6 7 8 9 10
Dev 11 12 13 14 15
Clusters
Data Center A
Using vCenter Server, the administrator sets up these tag categories and associated tag names:
n Environment: Production, Staging, Dev
VMware, Inc. 758

n Service Tier: Gold, Silver
n Licensing: Oracle
Data Center A includes 15 clusters. The administrator tags the clusters and VMs in those clusters
as follows:
Cluster Environment Service Tier Licensing
1 Production Gold
2, 3 Production Silver
4, 5 Production Oracle
6 Staging Gold
7, 8 Staging Silver
9, 10 Staging Oracle
11 Dev Gold
12, 13 Dev Silver
14, 15 Dev Oracle
Opening the vRealize Operations Manager policies to Tag-Based VM Placement in the Business
Intent window, the administrator prioritizes the Environment: Production and Service Tier: Gold
category-tag combinations. Because the Optimization policies emphasize balance, clusters with
those tags are balanced first.
Business Intent - Host-Based Virtual Machine Placement

Use host-based VM placement to tie your VMs more closely to your infrastructure. By using
vCenter Server to tag hosts and VMs with specific tags, you make certain that when the system
runs an optimization, it uses VM-to-host tag matching to ensure that VMs are moved to - or stay
with - the appropriate host.
Using Tags to Enhance Structure

When configuring data centers or custom data centers without tags, you configure clusters and
their hosts as relatively homogenous. All cluster resources must support, for example, the same
OS or the same security requirements so that optimization actions do not place VMs in the wrong
cluster.
The tagging approach enables you to define zones of infrastructure within cluster boundaries.
VM-to-cluster tagging, for example, allows you to tag VMs and clusters to assure that Windows
VMs are moved only to Windows-licensed clusters and Oracle VMs are moved only to Oracle-
licensed clusters.
With host-based VM placement (VM-to-host tagging), you bind your VMs to individual hosts
rather than clusters.
VMware, Inc. 759

vCenter Server tags are implemented as key:value labels that enable operators to add meta-data
to vCenter Server objects. In vCenter Server terminology, the key is the tag category and the
value is the tag name. You can define many keys and values in vCenter Server, but choose a
subset to be considered in the Business Intent pane of the Workload Optimization screen (Home
-> Optimize Performance -> Workload Optimization).
Note If you choose host-based placement in the Business Intent pane, the system - after getting
confirmation from you - disables conflicting user-created affinity rules. Then, as you define host-
VM tagging relationships in the Business Intent pane, vRealize Operations Manager automatically
creates the required affinity rules, saving you the manual effort. So, for example, suppose you
configure a tag in the Business Intent pane that requires VM1 to remain with Host1. If there exists
a user-configured affinity rule keeping VM1 with Host2, the system disables the rule. However, if
another user-configured affinity rule dictates that VM2 remains with Host2, the system does not
change that rule.
Additional Considerations
n You are not permitted to employ both VM-to-cluster tagging and VM-to-host tagging in the
same data center or custom data center - only one tagging method or the other. If you select
host-based VM placement, any cluster tags are ignored.
n With host-based VM placement, only one category and one tag per VM is allowed per VM.
n A tagless VM can be sent to any host, even a tagged host.
n A host with multiple tags is treated as tagless.
n Even if all workloads are balanced, if there is also a tag violation, the system is by definition
not optimized.
n The system does not consider any tags of storage - that is, datastores or datastore clusters.
Business Intent Workspace

You can use vCenter Server tagging to tag VMs, hosts, and/or clusters with specific tags.
vRealize Operations Manager can be configured to leverage tags to define business-related
placement constraints: VMs can only be placed on hosts/clusters with matching tags.
Where You Find Business Intent

From the Home page, click the chevron next to Optimize Performance on the left. Click Workload
Optimization, select a data center or custom data center from the top row, and click Edit in the
Business Intent window.
To edit Business Intent values, you must have privileges for Administration -> Configuration ->
Workload Placement Settings -> Edit.
VMware, Inc. 760

Establishing Business Intent

Tags are implemented in vCenter Server as key:value labels that enable operators to add meta-
data to vCenter Server objects. In vCenter Server terminology, the key is the tag category and
the value is the tag name. Using this construct, the tag OS: Linux can indicate a cluster or VM that
is assigned to the category OS with a tag name of Linux. For complete information on vCenter
Server tagging capabilities, refer to the vCenter Server and Host Management guide.
To specify tags considered for placement, first select the radio button for the type of object you
want to associate with VMs in this business intent session: Clusters or Hosts.
The system provides several suggested categories. These categories are only suggestions. You
must specify the actual categories in vCenter Server after you expand the section for a
suggested category . For example, in section "Tier", you can specify the actual vCenter Server
tag category that represents tier semantics, for instance, "service level".
n Operating System
n Environment
n Tier
n Network
n Other
Any actual categories you specify must first be created in vCenter Server.
Then you can associate tagged VMs with clusters or hosts, based on the rules for each type of
tagging.
1 Click the chevron to the left of the first suggested category. A tag category field appears.
2 Click the drop-down menu indicator and choose a category from the list defined in vCenter
Server.
3 Click the drop-down menu indicator in the Tag Name (Optional) field and choose a tag name
from the list defined in vCenter Server.
4 Click Include Tag. All VMs with that tag are associated with the category.
Rules for Host-Based Placement

To set host level placement constraints, vRealize Operations Manager automatically creates and
manages DRS rules. All conflicting user-created DRS rules are DISABLED.
These rules include the following:
n Any VM-VM affinity and anti-affinity rules.
n Any VM-Host affinity and anti-affinity rules.
You must check the selection box next to the statement, "I understand that vRealize Operations
will disable all my current and future DRS rules".
See also Business Intent - Host-Based Virtual Machine Placement .
VMware, Inc. 761

Rules for Cluster-Based Placement

See Business Intent: Tag-Based VM Placement in Clusters.
Configuring Workload Optimization Alerts

vRealize Operations Manager provides two preconfigured alerts designed to work with the
Workload Optimization feature. You must take additional action in the Policies area to turn on the
alerts and automate them so that predetermined actions are run when the alerts fire.
The following preconfigured alerts are designed to work with the Workload Optimization feature:
n Data center performance can potentially be optimized in one or more clusters.
n Custom data center performance can potentially be optimized in one or more clusters.
The preconfigured alerts fire only if the AUTOMATE function is not turned on at the Workload
Optimization screen. (Home -> Optimize Performance -> Workload Optimization).
Prerequisites
Ensure that you have all required permissions to access the Workload Optimization UI pages and
manage vCenter Server objects.
Procedure
1 Select Administration from the menu, then Policies from the left pane.
2 Click Policy Library and select the policy that includes settings for the relevant data centers
and custom data centers, for example, vSphere Solution’s Default Policy.
3 Click Edit.
4 Click #6 on the lower left, Alert/Symptom Definitions.
5 Search on "can potentially be optimized" to locate the two alerts you want.
6 The alerts are turned ON by default/inheritance (see the State column).
7 The alerts are not automated by default/inheritance (see the Automate column). To automate
the alerts, click the menu symbol to the right of the inherited value and select the green
check mark.
Results
Workload Optimization is fully automated for your environment.
What to do next
To confirm that actions are taken automatically, monitor rebalance activity at the Workload
Optimization screen.
VMware, Inc. 762

Using Workload Optimization

Use the Workload Optimization UI pages to monitor optimizing moves in a fully automated
system. If your system is not fully automated, you can use the UI to conduct research and run
actions directly.
vRealize Operations Manager monitors virtual objects and collects and analyzes related data that
is presented to you in graphical form at the Workload Optimization screen. Depending on what
appears on the screen, you might use optimization functions to distribute a workload differently
in a data center or custom data center. Or you may decide to perform more research, including
checking the Alerts page to determine if any alerts have been generated for objects of interest.
For comprehensive general instructions on responding to alerts and analyzing problems related
to objects in your environment, see Chapter 5 Monitoring Objects in Your Managed Environment
by Using vRealize Operations Manager.
The following examples demonstrate the primary ways you can use Workload Optimization to
keep your data centers balanced and performing their best.
Example: Run Workload Optimization

As a virtual infrastructure administrator or other IT professional, you use Workload Optimization
functions to identify points of resource contention or imbalance. In this example, you manually
run an optimization action to consolidate demand.
When you log into vRealize Operations Manager, you see the Quick Start page. In the left-most
column, Optimize Performance, is the alert 3 DATA CENTERS REQUIRING OPTIMIZATION.
Prerequisites
Ensure that you have all required permissions to access the Workload Optimization UI and
Procedure
1 Click Workload Optimization in the Optimize Performance column.
The Workload Optimization page appears. Data centers are grouped by Criticality, with the
three troubled data centers appearing in a carousel across the top of the page: DC-
Bangalore-18, DC-Bangalore-19, DC-Bangalore-20. A Not Optimized badge appears in the
lower right corner of each graphic.
2 If no data center is preselected, select DC-Bangalore-18 from the carousel.
Comprehensive data about the state of the data center follows.
3 Based on the available data, you determine an optimization action is required.
CPU workloads can be consolidated such that a host in Cluster 3 can be freed up.
VMware, Inc. 763

Table 4-235. Panes and Widgets

Pane Contents
Workload Optimization Status shows as Not Optimized. A system message says,

"You can consolidate workloads to maximize usage and
potentially free up 1 host."
The message reflects that you have set policies to
emphasize consolidation as a goal in optimization moves.
The system is saying you can free up a host through
consolidation.
Settings The current policy is Consolidate. The system advises:

Avoid Performance Issues, Consolidate Workloads.
Cluster Workloads Cluster 1 CPU Workload is 16%. Cluster 2 CPU Workload

is 29%. Cluster 3 CPU Workload is 14%. Cluster 4 CPU
Workload is 22%.
4 Click OPTIMIZE NOW in the Workload Optimization pane.
The system creates an optimization plan, which depicts BEFORE and (projected) AFTER
workload statistics for the optimization action.
5 If you are satisfied with the projected results of the optimization action, click NEXT.
The dialog box updates to show the planned moves.
6 Review the optimization moves, then click BEGIN ACTION.
The system runs the compute and storage resource moves.
Results
The optimization action moved compute and storage resources from some clusters to other
clusters in the data center, and so freed up a host on one cluster.
Note The Workload Optimization page refreshes every five minutes. Depending on when you
run an optimization action, the system might not reflect the result for up to five minutes, or longer
when longer-running actions extend the processing time.
VMware, Inc. 764

What to do next
To confirm that your optimization action was completed, go to the Recent Tasks page by
selecting Administration on the top menu, and clicking History > Recent Tasks in the left pane. In
the Recent Tasks page, use the Status function on the menu bar to locate your action by its
status. You can also search using a range of filters. For example, first filter on Starting Time and
scroll to the time when you began the action, then select the Object Name filter. Finally, enter the
name of one of the VMs in the rebalance plan.
Note Sometimes an optimizing action may be suggested, for example to consolidate two hosts,
but when you run the optimization, the generated placement plan does not show any potential
consolidation. The seeming inconsistency results from the fact that suggested optimization
actions are based on current conditions, whereas the placement plan logic includes forecasting. If
forecasting predicts that consolidation might incur stress in the future, then consolidation is not
suggested.
Example: Schedule a Repeating Optimization Action

As a virtual infrastructure administrator or other IT professional, you determine that compute and
storage resources in a given data center are volatile and a regularly scheduled optimization
action can address the problem.
vRealize Operations Manager monitors virtual objects and collects and analyzes related data that
is presented to you in graphical form at the Workload Optimization page. Depending on what
appears, you may determine that you must schedule optimization functions to distribute a
workload more evenly in a data center or custom data center.
Prerequisites
Ensure that you have all required permissions to access the Workload Optimization UI and
Procedure
1 From the Home screen, click Optimize Performance > Workload Optimization in the left
pane.
2 From the carousel of data centers across the top of the page, select a data center for which
you want to schedule repeated optimization actions.
3 In the Workload Optimization pane, click SCHEDULE.
4 Give the schedule a name and choose a time zone.
5 Determine how often you want to repeat the optimization action and click the relevant radio
button under Recurrence.
Depending on your selection under Recurrence, additional options appear to the right. In this
instance, you choose to repeat the optimization daily.
VMware, Inc. 765

6 Leave the current date and time.
7 Select the Repeat every day radio button.
8 Select the Expire after radio button and tick the counter up to 6.
9 Click Save.
Results
The optimization action repeats for six days, then stops.
At the Workload Optimization page, the Scheduled button appears in the upper right of the
Workload Optimization pane if optimization actions are scheduled for the selected data center. If
you want to edit or delete a schedule, click the Scheduled button. The Optimization Schedules
page appears, where you can perform those actions.
Note If you schedule a number of optimization actions close together, and the optimization
plans of two or more actions include overlapping functions, that is, they impact the same set of
resources, the system shifts the actions into a queue. As a result, some actions may complete
later than expected, with longer running actions and other potential system constraints extending
the lag time. Optimization actions that do not overlap can run concurrently.
What to do next
To confirm that your optimization action was finished, go to the Recent Tasks screen by selecting
Administration on the top menu, and clicking History > Recent Task in the left pane. In the
Recent Tasks screen, use the Status function on the menu bar to locate your action by its status.
You can also search using a range of filters. For example, filter on Event Source and enter the
name of the scheduled optimization plan.
Note Because real-time data center resource contention is dynamic, the system calculates a
new optimization plan each time the scheduled optimization action starts, but before it runs. The
system does not run the action if the system determines that the data center container is
balanced at this moment. On the Recent Tasks page, the name of the affected data center
appears in the Object Name column, and the Message “The optimization of the selected
container cannot be improved” appears under Details. Another possibility is that a scheduled
optimization plan is attempted, but does not go forward. In this event - which is not the same as a
"failed" action - the name of the affected data center also appears in the Object Name column.
Example: Run Workload Optimization from Recommended Actions

From the Home screen, click Recommendations under Optimize Performance - first column on
the left. The Recommended Actions screen appears, with data center and custom data center
errors highlighted. If a suggested optimization action is available, it appears in the bottom third of
the screen, with details.
To run the action, click the blue Run Action arrow.
VMware, Inc. 766

Prerequisites
Ensure that you have all required permissions for accessing the Workload Optimization UI and
managing vCenter Server objects.
Results
The system runs the proposed rebalancing action.
What to do next
The Workload Optimization screen appears, where you can review the results of the rebalancing
actions. Additional information is available at the Recent Tasks page: in the menu, select
Administration, then click History > Recent Tasks in the left pane. Choose the Event Source filter
and enter part of the alert name, then search. If the action succeeded, the Event Source column
shows Alert: <alert name>.
Workload Optimization Page

Workload Optimization enables you to optimize virtual machines and storage across datastore
clusters to reduce resource contention and maintain optimum system performance.
Where You Find Workload Optimization

From the Home screen, select Workload Optimization under Optimize Performance in the left
pane. From the Quick Start screen, select Workload Optimization in the left-most column.
Workload Optimization Page Options

In the Workload Optimization page, you see a list of data centers in a carousel, listed under three
categories:
n Critical
n Normal
n Unknown
VMware, Inc. 767

After you select a data center, you see the ALL DATACENTERS button on the upper right. Click
ALL DATACENTERS when you want to switch the view to a filtered list of all data centers. Click X
to return to a carousel view of data centers.
Table 4-236. Workload Optimization Page Options

Option Description
View: Filter results to include data centers, custom data centers,

vRA-managed custom data centers, or all three. (Option
appears if you select ALL DATACENTERS on the upper
right.)
Group By: Filter results by criticality (most out of balance data

centers/custom data centers listed first) or by the vCenter
Server to which each data center belongs. (Option appears
if you select ALL DATACENTERS on the upper right.)
Sort By: Options (Options appear if you select ALL DATACENTERS

on the upper right):
n Alarm clock graphic - list data centers/custom data
centers by time remaining.
n Dollar sign - list data centers/custom data centers by
potential cost savings with capacity optimization.
n Scales graphic - Optimized.
Select data center or ADD NEW CUSTOM DATACENTER Options (Options appear if you select ALL DATACENTERS
on the upper right):
n Select a data center from the carousel across the top of
the page. All data following refreshes with information
for the selected object.
n Select ADD NEW CUSTOM DATACENTER to display a
screen that enables you to define a custom data
center.
Data Center Options

After you select a data center from the carousel, you see the following information and options.
Note If you point your cursor to the lower right of a data center graphic, a tooltip may appear to
let you know that the data center is using automated optimization.
VMware, Inc. 768

Table 4-237. Data Center Options

Option Description
Optimization Status/Optimization Appears when you select a data center or custom data center from the top
Recommendation of the screen.
Status:
n Optimized - indicates that workloads are optimized based on the
settings you entered in the neighboring Operational Intent window, with
no tag violations based on the settings you entered in the Business
Intent window.
n Not Optimized - indicates that one of the following conditions is true:
workloads are not optimized based on the settings you entered in the
neighboring Operational Intent window AND/OR there are tag violations
based on the settings you entered in the Business Intent window. In the
event of tag violations, the offending tags are listed.
Four major Workload Optimization functions are accessed here:
n OPTIMIZE NOW - runs optimizing actions based on the settings you
entered in your Operational and Business Intent settings.
n SCHEDULE - displays a dialog box enabling you to schedule one or more
optimization actions. If schedules are currently set for data center or
custom data center optimization, a check mark appears next to the data
center or custom data center name.
n AUTOMATE - continually seeks optimizing opportunities for data center
or custom data center, based on the settings in the neighboring
Operational Intent window or Business Intent windows. Scheduled
optimizations are turned off while automatic optimization is on. Also,
automated alerts are not operational when automatic optimization is on.
Once you confirm automation, the system displays message, for
example, 1) "Workload Optimization is looking for opportunities to
automate," 2) "Your workloads are optimized according to your
settings." or 3) "No eligible moves were found within the max number of
compatibility checks allowed."
Note To initiate Automation, you must have privileges for Environment -

> Action -> Schedule Optimize Container.
n TURN OFF AUTOMATION - stops automatic optimization. Any
scheduled optimizations come back online.
n Check the History tab above the Recent Tasks under Administration to
see what optimization actions have been taken.
Note Sometimes an optimizing action may be recommended, for example

to consolidate two hosts, but when you run the optimization, the generated
placement plan does not show any potential consolidation. The seeming
inconsistency results from the fact that recommended optimization actions
are based on current conditions, whereas the placement plan logic includes
forecasting. If forecasting predicts that consolidation can incur stress in the
future, then consolidation is not recommended.
History Displays a graphical depiction of executed manual and automated

optimizations for clusters in the selected data center or custom data center,
based on parameters you provide.
n Selected WLP process - the optimization action whose details you want
to display.
VMware, Inc. 769

Table 4-237. Data Center Options (continued)

Option Description
n Last n hours - select the time parameter: last 6, 12, 24 hours or last 7
days.
n Quick filter - choose a cluster name to search on.
n Squares graphic - toggle between viewing processes in icon or circle
form.
n Circle - toggle between viewing processes presented in a circle or on a
straight line.
n Back arrow - reset action.
If you point your cursor to a specific cluster as displayed on the screen, the
details of the cluster appear in a tool tip. Click the note card icon on the
lower right of the tool tip to go to the Details screen for the cluster. When
displayed in the circle format, rings in the circle indicate how much CPU and
how much memory was used at any given time. For example, if memory
usage was higher than recommended based on your policy settings, the
memory circle appears red.
Note the timeline across the bottom of the screen. When you choose
parameters, for example, WLP process name, time parameter and cluster
name, indicators appear along the timeline, showing when processes were
initiated.
To zero in on a specific event, choose a process from the drop-down menu.
You can also click points on the marker floating above the timeline, which
causes a descriptive tool tip to appear, then double-click the 'Double-click to
zoom' icon on the lower right.
If the event you choose includes an actual movement of VMs, you see a blue
ball containing the number of VMs moved and showing the direction of the
move and starting and ending clusters.
Operational Intent Utilization Objective: indicates the main attribute of your current
automation policy settings. Values are moderate, consolidate, or balance.
EDIT - displays the Workload Automation Policy Settings, where you can
adjust settings for optimization and cluster headroom.
Business Intent Allows you to define zones of infrastructure within cluster boundaries. For
example, you can ensure that during workload optimization actions,
Windows VMs are moved only to Windows-licensed clusters and Oracle
VMs are moved only to Oracle-licensed clusters. Alternatively, you can
create categories and tags based on VM-to-host relationships.
To edit Business Intent values, you must have privileges for Administration -
> Configuration -> Workload Placement Settings -> Edit.
EDIT - displays a workspace where you can select criteria for placement of
VMs.
VMware, Inc. 770

Table 4-237. Data Center Options (continued)

Option Description
Are your clusters meeting your utilization Displays a table which presents data in the following columns:
objective? n Name
n CPU Workload
n Memory Workload
n DRS Settings
n Migration Threshold
n Violated Tags
n VM Name
Migration thresholds are based on DRS priority levels, and are computed
based on the workload imbalance metric for the cluster. The violated tags
shows which clusters or host groups are breaching the business intent. The
VM Name column shows the name of the VMs and tag value due to which
tag violation is happening.
Provides the option to set the DRS automation level for individual objects.
VIEW DRS SUMMARY Select a cluster in the list, then click this link to display a page containing
metrics for DRS performance and cluster balance in the selected data
center.
SET DRS AUTOMATION Select a cluster in the list, then click this link to set the level of the DRS
automation for the cluster. Note that clusters must be fully automated in
order for workload optimization alerts to run actions set in the policies.
See also Example: Run Workload Optimization
Rightsizing
Use this screen to alter the number of CPUs and amount of memory in oversized and undersized
virtual machines.
Where You Find Rightsizing

From the Home screen, select Rightsizing under Optimize Capacity in the left pane.
Note Click on a data center graphic to display the details for the data center.
How Rightsizing Works

The Capacity Optimization, Reclaim, and Rightsizing features are tightly integrated functions that
enable you to assess workload status and resource usage in data centers across your
environment. You can determine time remaining until CPU, memory, or storage resources run
out, and realize cost savings when underutilized VMs can be reclaimed and deployed where
needed. With this function, you can change CPU size and memory values for oversized and
undersized virtual machines to achieve optimum system performance.
VMware, Inc. 771

When you open the page, graphical representations of all the data centers and custom data
centers in your environment appear. By default, they are shown in order of time remaining,
beginning from the upper left, where the most constrained data centers appear. To identify
possible oversized and undersized VMs in a data center, click its graphic. The area following
refreshes to display details about the selected data center.
"Oversized VMs" displays the number of VMs determined to be oversized based on policies
previously set. A chart details suggested reductions in the overall number of CPUs and GBs of
memory and shows the percentage of total resources the reductions represent. Similarly,
"Undersized VMs" indicates the number of VMs considered to be undersized, with a chart listing
suggested increases in CPU and memory.
The table at the bottom of the page provides important information about the VMs. Table
headings are Oversized VMs and Undersized VMs. VMs under each heading are grouped by
cluster. Click the chevron to the left of a cluster name to list all the oversized or undersized VMs,
respectively, in that cluster. You can check the box next to one or more VM names and click the
EXCLUDE VM(S) button to prevent those VMs from being included in a resizing action. You can
also select individual VMs to resize before clicking the RESIZE VM(S) button.
Run a Rightsize Action on Oversized VMs

Run the action as follows:
1 In the table headings, Select Oversized VMs.
2 Select the boxes next to VMs you want to exclude from the action, if any.
3 Click EXCLUDE VM(S), if required. In the confirmation dialog box, click EXCLUDE VM(S).
4 Select the boxes next to VMs you want to include in the resizing action, or Select the box
next to VM Name to include all VMs.
5 Click RESIZE VM(S). The Resize VM(S) workspace appears. The table displays suggested
reductions for vCPU and memory. Click the edit icons to accomplish to changes you wish.
6 Select the box at the bottom of the screen to indicate your understanding that, because
workloads must restart to accommodate resizing, some work may be interrupted.
Run a Rightsize Action on Undersized VMs

Run the action as follows:
1 In the table headings, Select Undersized VMs.
2 Select the boxes next to VMs you want to exclude from the action, if any.
3 Click EXCLUDE VM(S), if required. In the confirmation dialog box, click EXCLUDE VM(S).
4 Select the boxes next to VMs you want to include in the resizing action, or Select the box
next to VM Name to include all VMs.
5 Click RESIZE VM(S). The Resize VM(S) workspace appears. The table displays suggested
increases for vCPU and memory. Click the edit icons to accomplish to changes you wish.
VMware, Inc. 772

6 Select the box at the bottom of the screen to indicate your understanding that, because
workloads must restart to accommodate resizing, some work may be interrupted.
Table 4-238. Rightsize Options

Option Description
Select a data center. Select a data center from the carousel across the top of the page. All data
refreshes with information for the selected object.
ALL DATACENTERS | X Toggle: click ALL DATACENTERS on the upper right when you want to
switch the view to a filtered list of all data centers. Click X to return to a
carousel view of data centers.
View: Filter results to include data centers, custom data centers, or both. Option
appears when you select ALL DATACENTERS on the upper right.
Group BY: Filter results by criticality (least time remaining data centers/custom data
centers listed first) or by the vCenter Server to which each data center
belongs. Option appears when you select ALL DATACENTERS on the upper
right.
Sort by: Options (Options appear when you select ALL DATACENTERS on the upper
right):
n Alarm clock graphic - list data centers/custom data centers by time
remaining.
n Dollar sign - list data centers/custom data centers by potential cost
savings.
n Scales graphic - list data centers/custom data centers by level of
optimization.
Select data center or ADD NEW CUSTOM Options (Options appear when you select ALL DATACENTERS on the upper
DATACENTER. right):
n Select a data center from the carousel across the top of the page. All
data refreshes with information for the selected object.
n Select ADD NEW CUSTOM DATACENTER to display a dialog box that
enables you to define a custom data center.
Oversized VMs display Displays the number of VMs identified as oversized, with suggested
reductions for vCPU and memory size.
VMware, Inc. 773

Table 4-238. Rightsize Options (continued)

Option Description
Undersized VMs display Displays the number of VMs identified as undersized, with suggested
increases for vCPU and memory size.
Table of Oversized and Undersized VMs Tabular representation of the Oversized and Undersized VMs in the
selected data center.
Click one of the headings - Oversized VMs or Undersized VMs - to refresh
the table with data for that heading. The table lists the relevant VMs. To see
the VMs hosted in a given cluster, click the chevron to the left of the cluster
name.
Click the check box next to the VMs you want to act on, or click the check
box next to the column heading VM Name to act on all the VMs.
Once you select a VM or VMs, the dimmed options above the table become
visible, as follows.
Exclude VM(s): the selected VMs are excluded from your subsequent
action. Excluding VMs from a reclamation action can reduce the potential
cost savings.
For Oversized VMs:
n RESIZE VM(s): the system displays a dialog box with suggestions for
reducing vCPUs and memory. Click the edit icons to change resource
size.
For Underseized VMs::
n RESIZE VM(s): the system displays a dialog box with suggestions for
increasing vCPUs and memory. Click the edit icons to change resource
size.
SHOW|HIDE EXCLUDED VMS: toggle displays or hides the list of VMs you
previously excluded.
INCLUDE VM(s): include the selected VMs in the actionable list.
Manage Optimization Schedules

Enables you to set up a regular schedule for optimizing a selected container.
Where You Find Manage Optimization Schedules

At the Workload Optimization screen, select SCHEDULE from the pane: Optimization
Recommendation
Option Description
Schedule Name Meaningful name for the schedule
Time Zone Choose the time zone for the action
Recurrence Indicate how often you want the optimize action to run.
Complex schedules can be defined, for example, select the
Monthly option and choose to run the action on Tuesdays
and every other Thursday, beginning on the fifth of the
month.
Start on: Day to start the optimization schedule.
Start at: Time to start the optimization schedule.
VMware, Inc. 774

Expire after: Designate a set number of scheduled runs.
Expire on: Designate an exact date for the actions to end.
See also Example: Schedule a Repeating Optimization Action
Workload Automation Policy Settings

Provides options for refining policy settings specifically for Workload Optimization.
Where You Find Workload Automation Settings

Access this screen through the Policies pages:
Select Administration from the menu, then select Policies from the left pane.
Click Policy Library, then click either the Add New Policy icon or the Edit Selected Policy icon. In
the Add or Edit Monitoring policy workspace, on the left click Workload Automation.
Refer to Workload Automation Details .
View DRS Summary

The View DRS Summary page provides insight and perspective into the actions DRS is taking to
balance a cluster. You can view DRS settings for the cluster and cluster balance metrics, and
determine if recent vMotions are DRS- or user-initiated.
Where You Find the View DRS Summary Page

From the Home screen, select Workload Optimization under Optimize Performance in the left
pane. Then select a cluster name in the Current Workloads pane. The dimmed View DRS
Summary and Set DRS Automation links turn live. Click the link to display the DRS summary
information.
Table 4-239. DRS Summary Values

Pane/fields Value
<cluster name> Name of the selected cluster
Automation Level Enabled/Disabled. DRS is running or not.
Migration Threshold Aggressive/Default/Moderate
Active Memory Used False/ nn%
Cluster Balance Shows the variations in the DRS cluster balance metric over time as
DRS runs. The graph shows how DRS reacts to and clears any cluster
imbalance each time it runs.
Cluster Imbalance The range of potential imbalance values, as expressed in vCenter

DRS metrics.
Total Imbalance The level of imbalance in a cluster, as measured by vCenter DRS

metrics.
Tolerable Threshold The upper limit of what is tolerable in cluster imbalance. Designated
by a green dotted line, this is a vCenter DRS metric.
VMware, Inc. 775

Table 4-239. DRS Summary Values (continued)

Pane/fields Value
VM Happiness A bar graph summarizing the total happy and unhappy VMs in the
cluster. For individual VMs, there is a presentation of performance
metrics related to its happiness, such as %CPU ready time and
memory swapped.
Happy VMs Total of happy VMs are shown in green. Click in the green zone to
show a list of these VMs in the Happy/Unhappy VMs pane to the
right.
Unhappy VMs Total of unhappy VMs is shown in red. To show a list of these VMs in
the Happy/Unhappy VMs pane to the right, click in the red zone .
Happy/Unhappy VMs Lists by name all the VMs in the zone you clicked in the VM
Happiness pane.
VM Metrics Shows the trend in VM happiness or unhappiness
Recent vMotions The number of recent vMotions, plotted against time.
vMotion Details Shows the number of DRS-initiated and user (non-DRS) initiated
vMotions over time. You can choose which type you want to view.
Date/VM Date of a given vMotion.
Source/Destination Source and destination of moved VMs.
Type DRS-initiated or user initiated.
Optimization Schedules
Use the Optimization Schedules page to edit or delete optimization schedules that you set up in
the Manage Optimization Schedule Dialog Box at the Workload Optimization main screen.
Where You Find Optimization Schedules

n From the Home screen, select Administration > Configuration > Optimization Schedules.
n At the Workload Optimization Page page, select in the data center whose optimization
schedule you want to edit or delete. Then click SCHEDULE in the Optimization
Recommendation pane.
Table 4-240. Optimize Schedules Options

Option Description
Edit icon Select a schedule from the list, then click the Edit icon.
The Manage Optimization Schedules appears, with the data for the
selected schedule filled in.
Delete icon Select a schedule from the list, then click the Delete icon.
The selected schedule is deleted and does not run.
See also Example: Run Workload Optimization
VMware, Inc. 776

Optimize Placement
A two-page dialog that provides information about optimizing the workload of a selected
container.
First page: The current workload ("before," for example, CPU 105%) and projected results
("after," for example storage utilization 45%) for a possible optimizing action.
Second page: The exact moves planned for compute and storage resources.
Where You Find Optimize Placement

At the Workload Optimization screen, select OPTIMIZE NOW in the Optimization
Recommendation pane.
Table 4-241. Optimize Clusters Options

Option Description
Compare Cluster Balance If you are satisfied with the before and after numbers (First page, above), click NEXT.
Review Optimization Moves If you are satisfied with the moves planned (Second page, above), click BEGIN ACTION.
See also Example: Run Workload Optimization.
VMware, Inc. 777

Monitoring Objects in Your
Managed Environment by Using
vRealize Operations Manager
5
You can use vRealize Operations Manager to resolve problems that your customers raise,
respond to alerts that identify problems before your customers report problems, and generally
monitor your environment.
When your customers experience performance problems and call you to resolve the problem,
the data that vRealize Operations Manager collects and processes is presented to you in
graphical forms. You can then compare and contrast objects, understand the relationship
between objects, and determine the root cause of problems.
A generated alert notifies you when objects in your environment are experiencing problems. If
you resolve the problem based on the alert before your customers notice, then you avoid service
interruptions.
You can investigate the problems that generate alerts or that result in calls by using the Alerts,
Events, Details, and Environment tabs. If you find the root cause of the problem, you might be
able to resolve the problem by running an action. The actions change objects in the target
system, for example, the VMware vCenter Server® system, from vRealize Operations Manager.
n Enhanced Search Capability
n What to Do When...
n Monitoring and Responding to Alerts
n Monitoring and Responding to Problems
n Running Actions from vRealize Operations Manager
n Viewing Your Inventory
Enhanced Search Capability

The search function on the upper right supports locating named objects, dashboards, alerts, and
so on, in the system. The search function attempts to match or partially match any string you
enter; additional capabilities enable you to go swiftly to the item you want. The system presents
the item in the Edit context.
VMware, Inc. 778

Where you Find Search

The search function appears on all the pages of the VMware vRealize Operations Manager in the
top menu. Click the magnifying glass icon to open the search bar. Optionally, you can press the
Ctrl, Shift and Spacebar keys on your keyboard to open the search bar.
How Search Works

You start your search by typing in the search bar. VMware vRealize Operations Manager displays
matching objects types and objects.
The search function supports several common categories you can employ to find the item you
seek quickly, as follows:
n Dashboard
n Object
n Supermetric
n Alert definition
n Symptom definition
n View
n Report
n Notification
n I.P. Address
What this means is that in addition to entering a traditional search phrase, for example, a simple
string - "VM" - you can also enter one of the listed categories followed by a string or a name. You
can then search for objects within the category. For the Object, View and Dashboard categories,
the system displays the object in view mode.
If you want quickly to locate a specific dashboard, for example, start typing "dash..." into the
search field. The system offers the search term Dashboards. Select the term using the cursor and
then enter the dashboard name or part of the name and press Enter. The system finds the
dashboard you want, with editing functions available.
Similarly, you can type "alert" or simply "a" in the search field and the system offers Alert
Definition. Select the term and enter part of an alert message, for example, "unbalanced." The
system returns the alert, "Cluster has an unbalanced workload," presented in the Alert Definition
Workspace where you can edit it.
Note You can type virtual machine in the search bar to list all the virtual machines associated
with the host.
VMware, Inc. 779

What to Do When...
As a virtual infrastructure administrator, network operations center engineer, or other IT
professional, use vRealize Operations Manager to monitor objects in your environment. Using
vRealize Operations Manager, you can ensure that your customers experience the best possible
service, and resolve any problems that occur.
Your vRealize Operations Manager administrator has configured vRealize Operations Manager to
manage two vCenter Server instances that manage multiple hosts and virtual machines. It is your
first day using vRealize Operations Manager to manage your environment.
n User Scenario: A User Calls with a Problem

The vice president of sales telephones tech support reporting that a virtual machine,
VPSALES4632, is running slowly. The VP is working on sales reports for an upcoming
meeting and is running behind schedule because of the slow performance of the virtual
machine.
n User Scenario: An Alert Arrives in Your Inbox

You return from lunch to find an alert notification in your inbox. You can use vRealize
Operations Manager to investigate and resolve the alert.
n User Scenario: You See Problems as You Monitor the State of Your Objects
As you investigate your objects in the context of this scenario, vRealize Operations Manager
provides details to help you resolve the problems. You analyze the state of your
environment, examine current problems, investigate solutions, and act to resolve the
problems.
User Scenario: A User Calls with a Problem

The vice president of sales telephones tech support reporting that a virtual machine,
VPSALES4632, is running slowly. The VP is working on sales reports for an upcoming meeting
and is running behind schedule because of the slow performance of the virtual machine.
As an operations engineer, you reviewed the morning alerts and did not see problems with that
virtual machine, so you begin troubleshooting the problem.
Procedure
1 Search for a Specific Object

As a network operations engineer, you must locate the customer's virtual machine in
vRealize Operations Manager so that you can begin troubleshooting the reported problem.
2 Review Alerts Related to Reported Problems

The sales vice president reports degraded performance in a virtual machine. To determine if
the virtual machine has any alerts indicating the cause, review alerts for the virtual machine.
VMware, Inc. 780

3 Use Troubleshooting to Investigate a Reported Problem

To troubleshoot problems with the VPSALES4632 virtual machine, consider evaluating
symptoms, examining time line information and events, and creating metric charts to find the
root cause.
Search for a Specific Object

As a network operations engineer, you must locate the customer's virtual machine in vRealize
Operations Manager so that you can begin troubleshooting the reported problem.
You use vRealize Operations Manager to monitor three vCenter Server instances with a total of
360 hosts and 18,000 virtual machines. The easiest way to locate a particular virtual machine is to
search for it.
Procedure
1 In the Search text box on the vRealize Operations Manager title bar, enter the name of the
virtual machine.
The Search text box displays all the objects that contain the string you enter in the text box.
If your customer knows that the virtual machine name contains SALES, enter the string and
the virtual machine is included in the list.
2 Select the object in the list.
Results
The main pane displays the object name and the Summary tab. The left pane displays and the
related objects, including the host system and vCenter Server instance.
What to do next
Look for alerts related to the reported problem for the object. See Review Alerts Related to
Reported Problems.
Review Alerts Related to Reported Problems

The sales vice president reports degraded performance in a virtual machine. To determine if the
virtual machine has any alerts indicating the cause, review alerts for the virtual machine.
Alerts on an object can give you an insight into problems beyond the specific problem reported
by the user.
Prerequisites
Locate the customer's virtual machine so that you can review related alerts. See Search for a
Specific Object.
Procedure
1 Click the Summary tab for the object generating alerts.
The Summary tab displays active alerts for the object.
VMware, Inc. 781

2 Review the top alerts for Health, Risk, and Efficiency.
Top alerts identify the primary contributors to the current state of the object. Do any of them
appear to contribute to the slow response time? For example, any ballooning or swapping
alerts indicate that you must add memory to the virtual machine. Are any alerts related to
memory contention? Contention can be an indicator that you must add memory to the host.
3 If the Summary tab does not include top problems that appear to explain the reported
problem, click the Alerts tab.
The Alerts tab displays all active alerts for the current object.
4 Review the alerts for problems that are similar to or contribute to the reported problem.
a To view the active and canceled alerts, click Status: Active to clear the filter and display
active and inactive alerts.
The canceled alerts might provide information about the problem.
b So that you can locate alerts generated on or before the time when your customer
reported the problem, click the Created On column to sort the alerts.
c To view alerts for the parent objects in the same list with the alert for the virtual machine,
click View From, then select, for example, Host System under Parents.
The system adds these object types to the list so that you can determine if alerts among
the parent objects are contributing to the reported problem.
5 If you locate an alert that appears to explain the reported problem, click the alert name in the
alerts list.
6 On the Alert > Symptoms tabs, review the triggered symptoms and recommendations to
determine if the alert indicates the root cause of the reported problem.
What to do next
n If the alert appears to indicate the source of the problem, follow the recommendations and
verify the resolution with your customer. For an example, see Run a Recommendation on a
Datastore to Resolve an Alert.
n If you cannot locate the cause of the reported problem among the alerts, begin more in-
depth troubleshooting. See Use Troubleshooting to Investigate a Reported Problem.
Use Troubleshooting to Investigate a Reported Problem

To troubleshoot problems with the VPSALES4632 virtual machine, consider evaluating
symptoms, examining time line information and events, and creating metric charts to find the root
cause.
If a review of the alerts did not help you identify the cause of the problem reported for the virtual
machine, use the following tabs: Alert > Symptoms, Event > Timeline, and All Metrics to
troubleshoot the virtual machine history and current state.
VMware, Inc. 782

Prerequisites
n Locate the object for which the problem was reported. See Search for a Specific Object.
n Review the alerts for the virtual machine to determine if the problem is already identified and
recommendations made. See Review Alerts Related to Reported Problems.
Procedure
1 In the menu, click Environment, then click Inventory and select VPSALES4632 from the tree.
The main pane updates to display the object Summary tab.
2 Click the Alerts tab, click the Symptoms tab, and review the symptoms to determine if one of
the symptoms is related to the reported problem.
Depending on how your alerts are configured, some symptoms might be triggered but not
sufficient to generate an alert.
a Review symptom names to determine if one or more symptoms are related to the
reported problem.
The Information column provides the triggering condition, trend, and current value. What
are the most common symptoms that affect response time? Do you see any symptoms
related to CPU or memory use?
b Sort by the Created On date so that you can focus on the time frame in which your
customer reported that the problem.
c Click the Status: Active filter button to disable the filter so that you can review active and
inactive symptoms.
It appears the problem is related to CPU or memory use. But you do not know if the problem
is with the virtual machine or with the host.
3 Click the Events > Timeline tabs and review the alerts, symptoms, and change events that
might help identify common trends that are contributing to the reported problem.
a To determine if other virtual machines had symptoms triggered and alerts generated at
the same time as your reported problem, click View From > Peer.
Other virtual machine alerts are added to the time line. If you see that multiple virtual
machines triggered symptoms in the same time frame, then you can investigate parent
objects.
b Click View From and select Host System from the Parent list.
The alerts and symptoms that are associated with the host on which the virtual machine is
deployed are added to the time line. Use the information to determine if a correlation
exists between the reported problem and the alerts on the host.
VMware, Inc. 783

4 Click the Events > Events tab to view changes in the collected metrics for the problematic
virtual machine. Metrics might direct you toward the cause of the reported problem.
a Manipulate the Date Controls to identify the approximate time when your customer
reported the problem.
b Use the Filters to filter on event criticality and status. Select Symptoms if you want to
include the filters in your analysis.
c Click an Event to view the details about the event.
d Click View From, select Host System under Parents, and repeat the analysis.
Comparing events on the virtual machine and the host, and evaluating those results, indicates
that CPU or memory problems are the likely cause of the problem.
5 If the problem relates to CPU or memory use, click All Metrics and create metric charts to
identify whether it is CPU, memory, or both.
a If the host is still the focus, begin by working with host metrics.
b In the metric list, double-click the CPU Usage (%) and the Memory Usage (%) metrics to
add them to the workspace on the right.
c In the map, click the VPSALES4632 object.
The metric list now displays the virtual machine metrics.
d In the metric list, double-click the CPU Usage (%) and the Memory Usage (%) metrics to
add them to the workspace on the right.
e Review the host and virtual machine charts to see if you can identify a pattern that
indicates the cause of the reported problem.
Comparing the four charts shows normal CPU use on both the host and the virtual machine,
and normal memory use on the virtual machine. However, memory use on the host is
consistently elevated three days before the reported problem on VPSALES4632.
Results
The host memory is consistently elevated, which impacts virtual machine response time. The
number of running virtual machines is well within the supported number. The cause might be
many intensive process applications on the virtual machines. Move some of the virtual machines
to other hosts, distribute the workload, or power off idle virtual machines.
What to do next
n In this example, use vRealize Operations Manager to power off virtual machines on the host
so that you can improve performance in the running virtual machines. See Run Actions from
Toolbars in vRealize Operations Manager.
n If you want to use the combination of charts that you created on the All Metrics tab again,
click Generate Dashboard.
VMware, Inc. 784

User Scenario: An Alert Arrives in Your Inbox

You return from lunch to find an alert notification in your inbox. You can use vRealize Operations
Manager to investigate and resolve the alert.
As a network operations engineer, you are responsible for several hosts and their datastores and
virtual machines. You receive emails when an alert is generated for your monitored objects. In
addition to alerting you to problems in your environment, alerts can provide viable
recommendations to resolve those problems. As you investigate this alert, you are evaluating the
data to determine if one or more of the recommendations can resolve the problem.
This scenario assumes that you configured the outbound alerts to send standard email using
SMTP. It also assumes that you configured notifications to send you alert notifications using the
Standard Email Plug-In. When outbound alerts and notifications are configured, vRealize
Operations Manager sends messages when an alert is generated so that you can respond
quickly.
Prerequisites
n Verify that outbound alerts are configured for standard email alerts. See Add a Standard
Email Plug-In for vRealize Operations Manager Outbound Alerts.
n Verify that the notifications are configured to send messages to your users for the alert
definition. For an example of how to create an alert notification, see User Scenario: Create a
vRealize Operations Manager Email Alert Notification .
Procedure
1 Respond to an Alert in Your Email

As a network operations engineer, you receive an email message from vRealize Operations
Manager about a datastore for which you are responsible. The email notification informs you
about the problem even when you are not presently working in vRealize Operations
Manager.
2 Evaluate Other Triggered Symptoms for the Affected Datastore

Because you need more information about the datastore before you decide on the best
response, you examine the Symptoms tab to see other triggered symptoms for the
datastore.
3 Compare Alerts and Events Over Time in Response to a Datastore Alert

To evaluate an alert over time, compare the current alert and symptoms to other alerts and
symptoms, other events, other objects, and over time.
4 View the Affected Datastore in Relation to Other Objects

To view the object for which the alert was generated as it relates to other objects, use the
topological map on the Relationships tab.
VMware, Inc. 785

5 Construct Metric Charts to Investigate the Cause of the Datastore Alert

To analyze the capacity metrics related to the generated alert, you create charts that
compare different metrics. These comparisons help identify when something changed in
your environment and what effect it had on the datastore.
6 Run a Recommendation on a Datastore to Resolve an Alert

As a network operations engineer, you investigated the alert regarding datastore disk space
and determined that the provided recommendations can solve the problem. The
recommendation to delete unused snapshots is especially useful. Use vRealize Operations
Manager to delete the snapshots.
Respond to an Alert in Your Email

As a network operations engineer, you receive an email message from vRealize Operations
Manager about a datastore for which you are responsible. The email notification informs you
about the problem even when you are not presently working in vRealize Operations Manager.
In your email client, you receive an alert similar to the following message.
Alert was updated at Tue Jul 01 16:34:04 MDT:

Info: datastore1 Datastore is acting abnormally from Mon Jun 30 10:21:07 MDT and was last updated at
Tue Jul 01 16:34:04 MDT
Alert Definition Name: Datastore is running out of disk space

Alert Definition Description: Datastore is running out of disk space
Object Name: datastore1
Object Type: Datastore
Alert Impact: risk
Alert State: critical
Alert Type: Storage
Alert Sub-Type: Capacity
Object Health State: info
Object Risk State: critical
Object Efficiency State: info
Symptoms:
SYMPTOM SET - self
Symptom Name | Object Name | Object ID | Metric | Message Info
Datastore space use reaching limit datastore1 | b0885859-e0c5-4126-8eba-6a21c895fe1b |
Capacity|Used Space | HT above 99.20800922575977 > 95
Recommendations:
- Storage vMotion some virtual machines to a different datastore
- Delete unused snapshots of virtual machines
- Add more capacity to the datastore
Notification Rule Name: All alerts - datastores
Notification Rule Description:
Alert ID: a9d6cf35-a332-4028-90f0-d1876459032b
Operations Manager Server - 192.0.2.0
Alert details
VMware, Inc. 786

Prerequisites
n Verify that outbound alerts are configured for standard email alerts. See Add a Standard
Email Plug-In for vRealize Operations Manager Outbound Alerts.
n Verify that the notifications are configured to send messages to your users for the alert
definition. For an example of how to create an alert notification, see User Scenario: Create a
vRealize Operations Manager Email Alert Notification .
Procedure
1 In your email client, review the message so that you understand the state of the affected
objects and determine if you must begin investigating immediately.
Look for the alert name, the alert state to determine the current level of criticality, and the
affected objects.
2 In the email message, click Alert Details.
vRealize Operations Manager opens on the Summary tab in the alert details for the
generated alert and affected object.
3 Review the Summary tab information.
Option Evaluation Process
Alert name and Review the name and description and verify that you are evaluating the alert for which
description you received an email message.
Recommendations Review the top recommendation, and if available, other recommendations, to understand
the steps that you must take to resolve the problem. If implemented, do the prioritized
recommendations resolve the problem?
What is Causing the Which symptoms were triggered? Which were not triggered? What effect does this
Problem? evaluation have on your investigation? In this example, the alert that the datastore is
running out of space is configured so that the criticality is symptom-based. If you
received a critical alert, then it is likely that the symptoms are already at a critical level,
having moved up from Warning and Immediate. Look at the sparkline or metric graph
chart for each symptom to determine when the problem escalated on the datastore
object.
What to do next
n If you determine that the recommendations might resolve the problem, implement them. See
Run a Recommendation on a Datastore to Resolve an Alert.
n If you need more information about the affected objects, continue your investigation. Begin
by looking at other triggered symptoms for the datastore. See Evaluate Other Triggered
Symptoms for the Affected Datastore.
Evaluate Other Triggered Symptoms for the Affected Datastore

Because you need more information about the datastore before you decide on the best
response, you examine the Symptoms tab to see other triggered symptoms for the datastore.
VMware, Inc. 787

If other symptoms are triggered for the object besides the symptom included in the alert,
evaluate them as well. Determine what the symptoms reflect about the state of the object to
decide whether the related recommendations might resolve the problem.
Prerequisites
Verify that you are addressing the alert for which you received an alert message in your email.
See Respond to an Alert in Your Email.
Procedure
1 In the menu, click Alerts and select the alert name in the data grid.
The center pane view changes to display the alert detail tabs.
2 Click View additional metrics > Alerts > Symptoms and review the active symptoms.
Criticality Are other symptoms of similar criticality present that are affecting the object?
Symptom Are any of the triggered symptoms related to the symptoms that triggered the current alert?
Symptoms that might indicate storage problems?
Created On Do the date and time stamps for the symptoms indicate that they were triggered before the alert you
are investigating, indicating that it might be a related symptom? Were the symptoms triggered after
the alert was generated, indicating that the alert symptoms contributed to these other symptoms?
Information Can you identify a correlation between the alert symptoms and the other symptoms based on the
triggering metric values?
What to do next
n If your review of the symptoms and the provided information clearly indicates that the
recommendations can solve the problem, implement one or more of the recommendations.
For an example of implementing one of the recommendations, see Run a Recommendation
on a Datastore to Resolve an Alert.
n If your review of the symptoms did not convince you that the recommendations can resolve
the problem or provide you with enough information to identify the root cause, continue your
investigation using the Events > Timeline tab. See Compare Alerts and Events Over Time in
Response to a Datastore Alert.
Compare Alerts and Events Over Time in Response to a Datastore Alert

To evaluate an alert over time, compare the current alert and symptoms to other alerts and
symptoms, other events, other objects, and over time.
As a network operations engineer, you use the Events > Timeline tab to compare this alert to
other alerts and events in your environment. This way, you can determine if you can resolve the
problem of the datastore running out of disk space by applying one or more alert
recommendations.
VMware, Inc. 788

Prerequisites
Verify that you are addressing the alert for which you received an alert message in your email.
See Respond to an Alert in Your Email.
Procedure
1 In the menu, click Alerts and select the alert name in the data grid.
The alert details appear to the right.
2 Click View Events > Timeline.
The Timeline tab displays the generated alert and the triggered symptoms for the affected
object in a scrollable timeline format, starting when the alert was generated.
3 Scroll through the timeline using the week timeline at the bottom.
4 To view events that might contribute to the alert, click Event Filters and click the check box
for each event type.
Events related to the object are added to the timeline. You add the events to your evaluation
of the current state of the object and determine whether the recommendations can resolve
the problem.
5 Click View From and select Host under Parents.
Because the alert is related to disk space, adding the host to the timeline enables you to see
what alerts and symptoms are generated for the host. As you scroll through the timeline, ask:
when did some of the related alerts begin? When are they no longer on the timeline? What
was the effect on the state of the datastore object?
6 Click View From and select Peer under Parents.
If other datastores have alerts related to the alert you are currently investigating, seeing
when the alerts for the other datastores were generated can help you determine what
resource problems you are experiencing.
7 To remove canceled alerts from your timeline, click Filters and deselect the Canceled check
box.
Removing the canceled alerts and symptoms from the timeline clears the view and enables
you to focus on current alerts.
What to do next
n If your evaluation of alerts in the timeline indicated that one or more of the recommendations
to resolve the alert are valid, implement the recommendations. See Run a Recommendation
on a Datastore to Resolve an Alert.
n If you need more information about the affected object, continue your investigation. See
View the Affected Datastore in Relation to Other Objects.
VMware, Inc. 789

View the Affected Datastore in Relation to Other Objects

To view the object for which the alert was generated as it relates to other objects, use the
topological map on the Relationships tab.
As a network operations engineer, you view a datastore and the related objects in a map to
further your understanding of the problem. The map view helps determine if implementing the
alert recommendations can resolve the problem.
Prerequisites
Evaluate the alert over time and in comparison to related objects. See Compare Alerts and
Events Over Time in Response to a Datastore Alert.
Procedure
1 In the menu, click Alerts, select the alert name in the data grid, and click View additional
metrics > All Metrics.
2 Click Show Object Relationships.
The Relationships tab displays the datastore in a map with the related objects. By default,
the badge that this alert affects is selected only on the toolbar. Objects in the tree show a
colored square to indicate the current state of the badge.
3 To view the alert status of the objects for the other badges, click the Health button and then
the Efficiency button.
As you click each badge button, the squares on each object indicate whether an alert is
generated and the criticality of the alert.
4 To view alerts for an object, select the object and click Alerts.
The alert list dialog box appears, enabling you to search and sort for alerts for the object.
5 To view a list of the child objects for an object in the map, click the object.
A list of the number of children by object type appears at the bottom of the center pane.
6 Use the options to evaluate the datastore.
For example, what does the map tell you about the number of virtual machines that are
associated with the datastore? If many virtual machines are associated with a datastore,
moving them might free datastore disk space.
What to do next
n If your review of the map provided enough information to indicate that one or more of the
recommendations to resolve the alert are valid, implement the recommendations. See Run a
Recommendation on a Datastore to Resolve an Alert.
n If you need more information about the affected object, continue your investigation. See
Construct Metric Charts to Investigate the Cause of the Datastore Alert.
VMware, Inc. 790

Construct Metric Charts to Investigate the Cause of the Datastore Alert

To analyze the capacity metrics related to the generated alert, you create charts that compare
different metrics. These comparisons help identify when something changed in your environment
and what effect it had on the datastore.
As a network operations engineer, you create custom charts so that you can further investigate
the problem, and to determine if implementing the alert recommendations can resolve the
problem that the alert identifies.
Prerequisites
View the topological map for the datastore to determine if related objects are contributing to the
alert or if triggering symptoms indicate that the datastore is contributing to other problems in
your environment. See View the Affected Datastore in Relation to Other Objects.
Procedure
1 In the menu, click Alerts, select the alert name in the data grid, and click View additional
metrics > All Metrics.
The Metric Charts tab does not include charts. You must add the charts to compare.
2 To analyze the first recommendation, Add more capacity to the Datastore Storage, add
related charts to the workspace.
a Enter capacity in the metric list search text box.
The list displays metrics that contain the search term.
b Double-click the following metrics to add the following charts to the workspace:
n Capacity | Used Space (GB)
n Disk Space | Capacity (GB)
n Summary | Number of Capacity Consumers
c Compare the charts.
For example, the Capacity | Used Space (%) chart might show an increase in used space,
without the Disk Space | Capacity (GB) increasing or the Summary | Number of Capacity
Consumers increasing. Then adding capacity can be a solution, but it does not address
the root cause.
VMware, Inc. 791

3 To analyze the second recommendation, vMotion some Virtual Machines to a different

Datastore, add related charts to the workspace.
a Enter vm in the metric list search text box.
b Double-click the Summary | Total Number of VMs metric to add it to the workspace
c Compare the four charts.
For example, the Summary | Total Number of VMs chart might show that the number of
virtual machines did not increase enough to affect the datastore negatively. That result
might make moving some of the virtual machines seem the best solution, but it does not
address the root cause.
4 To analyze the third recommendation, Delete unused snapshots of virtual machines, add
related charts to the workspace.
a Enter snapshot in the metric list search text box.
b Double-click the following metrics to add the charts to the workspace:
n Disk Space | Snapshot Space (GB)
n Disk Space Reclaimable | Snapshot Space | Waste Value (GB)
c Compare the charts.
For example, say the amount of Disk Space | Snapshot Space (GB) increases. At the same
time, the Disk Space Reclaimable | Snapshot Space | Waste Value (GB) indicates an area
where space can be reclaimed. Then deleting unused snapshots positively affects the
datastore disk space problem and resolves the alert.
5 If this datastore is a problematic one that you must continue to monitor, create a dashboard.
a Click the Generate Dashboard button on the workspace toolbar.
b Enter a name for the dashboard and click OK.
In this example, use a name like Datastore disk space.
The dashboard is added to your available dashboards.
Results
You compared metric charts to determine if the recommendations are valid and which
recommendation to implement first. In this example, the recommendation to Delete unused
snapshots of Virtual Machines appears to be the most likely way to resolve the alert.
What to do next
Implement the alert recommendations. See Run a Recommendation on a Datastore to Resolve an

Alert.
VMware, Inc. 792

Run a Recommendation on a Datastore to Resolve an Alert

As a network operations engineer, you investigated the alert regarding datastore disk space and
determined that the provided recommendations can solve the problem. The recommendation to
delete unused snapshots is especially useful. Use vRealize Operations Manager to delete the
snapshots.
If you have not enabled actions in the vCenter adapter, you can manually delete the snapshots
on your vCenter Server instance.
Prerequisites
n Compare the metric charts to identify the likely root cause of the alert. See Compare Alerts
and Events Over Time in Response to a Datastore Alert .
Procedure
1 In the menu, click Alerts and select the alert name in the data grid. The alerts detail
information appears on the right.
2 Review the Recommendations.
Recommendations include the Storage vMotion some virtual machines to a different

datastore recommendation and the Delete unused snapshots for virtual machines
recommendation. The delete unused snapshot recommendation includes an action button.
3 Click Delete Unused Snapshots for Datastore.
4 In the Days Old text box, select or enter the number of days old the snapshot must be to be
retrieved for deletions and click OK.
For example, enter 30 to retrieve all snapshots on the datastore that are 30 days old or
older.
5 In the Delete Unused Snapshots for Datastore dialog box, review the Snapshot Space,
Snapshot Create Time, and the VM Name. Determine which snapshots to delete and select
the check box for each one to delete.
6 Click OK.
The dialog box that appears provides a link to Recent Tasks and a link to the task.
7 To verify that the task ran successfully, click Recent Tasks.
The Recent Tasks page appears. The Delete Unused Snapshots action includes two tasks,
one to retrieve the snapshots and one to delete the snapshots.
8 Select the Delete Unused Snapshot task that has the more recent finish time.
This task deletes the snapshots. The status is Completed.
Results
In this example, you ran an action on the datastore in vCenter Server. The other
recommendations might also be valid.
VMware, Inc. 793

What to do next
n Verify that the recommendations resolve the alert. Run a few collection cycles after you run
the action and verify that the alert is canceled. Alerts are canceled when the conditions that
generated them are no longer true.
n Implement the other recommendations. The other recommendations for this alert require you
to use other applications. You cannot implement the recommendations from vRealize
Operations Manager.
User Scenario: You See Problems as You Monitor the State of Your
Objects
As you investigate your objects in the context of this scenario, vRealize Operations Manager
provides details to help you resolve the problems. You analyze the state of your environment,
examine current problems, investigate solutions, and act to resolve the problems.
As a virtual infrastructure administrator, you regularly browse through vRealize Operations

Manager at various levels so that you know the general state of the objects in your managed
environment. Although no one has called or emailed, and you do not see any new alerts, you are
starting to see that your cluster is running out of capacity.
This scenario refers to objects that are associated with the VMware vSphere Solution, which
connects vRealize Operations Manager to one or more vCenter Server instances. The objects in
your environment include multiple vCenter Server instances, data centers, clusters (cluster
compute resources), host systems, resource pools, and virtual machines.
As you perform the steps in this scenario, and progress through the stages of troubleshooting,
you learn how to use vRealize Operations Manager to help you resolve problems. You analyze
the state of the objects in your environment, examine current problems, investigate solutions,
and act to resolve the problems.
This scenario shows you how to evaluate the problems that occur on your objects, and how to
resolve problems.
n Using the Events tab, you examine the symptoms that triggered on the objects, determine
when the problems that triggered those symptoms occurred, identify the events associated
with those problems, and examine the metric values involved.
n On the Details tab, you investigate the metric activity as a graph, list, or distribution chart,
and view the heat maps to examine the criticality levels of your objects.
n With the Environment tab, you evaluate the health, risk, and efficiency of various objects as
they relate to your overall object hierarchy. You view the object relationships to determine
how an object that is in a critical state might be affecting other objects.
To support future troubleshooting and ongoing maintenance, you can create an alert definition,
and create a dashboard and one or more views. To enforce the rules used to monitor your
objects, you can create and customize operational policies.
VMware, Inc. 794

Prerequisites
Verify that you are monitoring one or more vCenter Server instances.
Procedure
1 Troubleshoot Problems with a Host System

Use the Troubleshooting tabs to identify the root cause of problems that the system does
not resolve by alert recommendations or simple analysis.
2 Examine the Environment Details

Examine the status of your objects in the views and heat maps so that you can identify the
trends and spikes that are occurring with the resources on your cluster and objects. To
determine whether any deviations have occurred, you can display overall summaries for an
object, such as for the cluster disk space usage breakdown.
3 Examine the Environment Relationships

Use the Environment tab to examine the status of the three badges as they relate to the
objects in your environment hierarchy. You can then determine which objects are in a critical
state for a particular badge. To view the relationships between your objects to determine
whether an ancestor object that has a critical problem might be causing problems with the
descendants of the object, use All Metrics > Show Object Relationship.
4 Fix the Problem

Use the troubleshooting features of vRealize Operations Manager to examine problems that
put your objects in a critical state, and identify solutions. To resolve the resource and time
remaining problems, use the Capacity Optimization function.
5 Create Dashboards and Views

To help you investigate and troubleshoot problems with your cluster and host systems that
might occur in the future, you can create dashboards and views. These tools apply the
troubleshooting solutions that you used to research and solve the problems with your host
system, and make the troubleshooting tools and solutions available for future use.
Troubleshoot Problems with a Host System

Use the Troubleshooting tabs to identify the root cause of problems that the system does not
resolve by alert recommendations or simple analysis.
To troubleshoot the symptoms of the capacity problems that are occurring on the cluster and
host system, and determine when those problems occurred, use the Troubleshooting tabs to
investigate the memory problem.
Procedure
1 In the menu, click Environment, then in the left pane click vSphere Hosts and Clusters and
select the object. For example, USA-Cluster.
VMware, Inc. 795

2 Click the Alerts tab and review the symptoms.
The Symptoms tab displays the symptoms that triggered on the selected cluster. You notice
that several critical symptoms exist.
n Cluster Compute Resource Time Remaining with committed projects is critically

low
n Cluster Compute Resource Time Remaining is critically low
n Capacity remaining is critically low
3 Investigate the critical symptoms.
a Point to each critical symptom to identify the metric used.
b To view only the symptoms that affect the cluster, enter cluster in the quick filter text
box.
When you point to Cluster Compute Resource Time Remaining is critically low, the metric
Capacity|Time Remaining appears. You notice that its value is less than or equal to zero,
which caused the capacity symptom to trigger and generate an alert on the USA-Cluster.
4 Click the Events > Timeline tab to review the triggered symptoms, alerts, and events that
occurred on the USA-Cluster over time, and identify when the problems occurred.
a Click the calendar and select Last 7 Days as the range.
Several events appear in red.
b Point to each event to view the details.
c To display the events that occurred on the cluster's data center, click View From, and
select Datacenter.
Warning events for the data center appear in yellow.
d Point to the warning events.
You notice that a hard threshold violation occurred on the data center late in the evening.
The hard threshold violation shows that the Badge|Workload metric value was under the
acceptable value, and that the violation triggered.
e To view the affected child objects, click View From and select Host System.
5 Click the Events tab to examine the changes that occurred on the USA-Cluster, and
determine whether a change occurred that contributed to the root cause of the alert or other
problems with the cluster.
a Review the graph.
By reviewing the graph, you can determine whether a reoccurring event has caused the
errors. Each event indicates that the guest file system is out of disk space. The affected
objects appear in the pane following the graph.
b Click each red triangle to identify the affected object and highlight it in that pane.
VMware, Inc. 796

6 Click the Capacity tab to evaluate details of capacity and time remaining.
7 Click the All Metrics tab to evaluate the objects in their context in the environment topology
to help identify the possible cause of a problem.
a In the top view, select USA-Cluster.
b In the metrics pane, expand All Metrics > Capacity Analyltics Generated and double-click
Capacity Remaining (%).
The Capacity Remaining (%) calculation appears on the right pane.
c In the metrics pane, expand All Metrics > Badge and double-click Workload (%). The
Workload (%) calculation appears on the right pane.
d On the toolbar, click Date Controls and select Last 7 Days.
The metric chart indicates that the capacity for the cluster remained at a steady level for
the past week, but that the Badge|Workload (%) calculation displays workload extremes.
Results
You have analyzed the symptoms, timeline, events, and metrics related to the problems on your
cluster. Through your analysis, you have determined that the heavy workload on the cluster has
caused the cluster to start running out of capacity.
What to do next
Examine the Details views and heat maps to interpret the properties, metrics, and alerts. Also,
look for trends and spikes that occur in the resources for your objects, the distributions of
resources across your objects, and data maps. You can examine the use of various object types
across your objects.
Examine the Environment Details

Examine the status of your objects in the views and heat maps so that you can identify the
trends and spikes that are occurring with the resources on your cluster and objects. To
determine whether any deviations have occurred, you can display overall summaries for an
object, such as for the cluster disk space usage breakdown.
To examine the problems with your USA-Cluster further, use the Details views to display the
metrics and collected capacity data for your cluster. Each view includes specific metrics data
collected from your objects. For example, trend views use data collected from objects over time
to generate trends and forecasts for resources such as memory, CPU, disk space.
Use the heat maps to examine the capacity levels on the cluster, host systems, and virtual
machines. The block sizes and colors are based on the metrics selected in the heat map
configuration.
Prerequisites
Use the Troubleshooting tabs to look for root causes. See Troubleshoot Problems with a Host
System.
VMware, Inc. 797

Procedure
1 Click Environment > vSphere Hosts and Clusters > USA-Cluster.
2 Examine the detailed information about the USA-Cluster in the views.
a Click the Details tab and click Views.
The views provide multiple ways to look at different types of collected data by using
trends, lists, distributions, and summaries.
b In the search text box, enter capacity.
The list filters and displays the capacity views for clusters and other objects.
c Click the view named Cluster Capacity Overview, and examine the number of virtual
machines listed for the USA-Cluster in the lower pane.
Even though the USA-Cluster has two host systems and 30 virtual machines, no capacity
exists.
3 Examine the host systems in the cluster, and reclaim capacity from the descendant virtual
machines.
a Click the Capacity tab.
b In the inventory tree, expand USA-Cluster, and click each of the host systems in turn.
c The host system w2-vcopsqe2-009 is in a critical state, with no capacity remaining.
d Click the Details tab, then click Views, and click Cluster Configuration View.
e To reclaim capacity from several virtual machines, select the cluster name
f Click the gear icon, and select Set CPU Count and Memory for VM.
g In the workspace that appears, click the Current CPU column title to sort the list
according to the highest number of CPUs.
Based on the actual use of the virtual machines listed, the New CPU column suggests
fewer CPUs for each virtual machine.
h Click the check box next to each virtual machine that has a suggested lower CPU count,
and click Begin Action. A confirmation message indicates that the action is underway and
provides the task ID that you use to track the action in the Recent Tasks section under
Administration. Click OK.
By reducing the number of CPUs for each virtual machine, you free up capacity on your
host system, and improve the USA-Cluster capacity and workload.
4 Examine the heat maps for the host system and virtual machine objects in the USA-Cluster.
a In the inventory tree, click the USA-Cluster.
b Click Details, click Heatmaps, and click through the list of heat map views.
VMware, Inc. 798

c Click Which VMs currently have the highest CPU demand and contention?
The heat map displays blocks that represent the objects in the USA-Cluster. The block for
a virtual machine appears in red, which indicates that it has a critical problem.
d Point to the red block and examine the details.
The cluster, host system, and virtual machine names appear, with links to more
information about the object.
e Click Show Sparkline to display the activity trend on the virtual machine.
f Click each of the Details links to display more information.
Results
To verify that freeing up memory on the virtual machines has improved the workload of the host
system and the cluster, you can now examine the status of the host system and cluster.
You used views and heat maps to evaluate the status of your objects and identify trends and
spikes, and free up capacity for your host system and the USA-Cluster. To further narrow in on
problems, you can examine the other views and heat maps. You can also create your own views
and heat maps.
What to do next
Examine the status for the objects in your environment hierarchy to determine which objects are
in a critical state. Then examine the object relationships to determine whether a problem on one
object is affecting one or more other objects.
Examine the Environment Relationships

Use the Environment tab to examine the status of the three badges as they relate to the objects
in your environment hierarchy. You can then determine which objects are in a critical state for a
particular badge. To view the relationships between your objects to determine whether an
ancestor object that has a critical problem might be causing problems with the descendants of
the object, use All Metrics > Show Object Relationship.
As you click each of the badges in the Environment tab, you see that several objects are
experiencing critical problems with health. Others are reporting critical risk status.
Several objects are experiencing stress. You notice that you can reclaim capacity from multiple
virtual machines and a host system, but the overall efficiency status for your environment
displays no problems.
Prerequisites
Examine the status of your objects in views and heat maps. See Examine the Environment
Details.
Procedure
1 Click Environment > vSphere Hosts and Clusters > USA-Cluster.
VMware, Inc. 799

2 Examine the USA-Cluster environment overview to evaluate the badge states of the objects
in a hierarchical view.
a In the inventory tree, click USA-Cluster, and click the Environment tab.
b On the Badge toolbar, click through the three badges - Health, Risk, and Efficiency - and
look for red icons to identify critical problems.
As you click through the badges, you notice that your vCenter Server and other top-level
objects appear to be healthy. However, you see that a host system and several virtual
machines are in a critical state for health, risk, and efficiency.
c Point to the red icon for the host system to display the IP address.
d Enter the IP address in the search text box, and click the link that appears.
The host system is highlighted in the inventory tree. You can then look for
recommendations or alerts for the host system on the Summary tab.
3 Examine the environment list and view the badge status for your objects to determine which
objects are in a critical state.
a Click the Environment tab.
b Examine the badge states for the objects in USA-Cluster.
c Many of the objects display critical states for risk and health. You notice that multiple
virtual machines and a host system named w2-vropsqe2-009 are critically affected.
Because the host system is experiencing the most critical problems, and is likely affecting
other objects, you must focus on resolving the problems with the host system.
d Click the host system named w2-vropsqe2-009, which is in a critical state, to locate it in
the inventory tree.
e Click w2-vropsqe2-009 in the inventory tree, and click the Summary tab to look for
recommendations and alerts to act on.
4 Examine the relationship map.
a Click All Metrics > Show Object Relationship.
b In the inventory tree, click USA-Cluster, and view the map of related objects.
In the relationship map, you can see that the USA-Cluster has an ancestor data center,
one descendant resource pool, and two descendant host systems.
c Click the host system named w2-vropsqe2-009.
The types and numbers of descendant objects for this host system appear in the list
following. Use the descendant object list identify all the objects related to the host system
that might be experiencing problems.
What to do next
Use the user interface to resolve the problems.
VMware, Inc. 800

Fix the Problem

Use the troubleshooting features of vRealize Operations Manager to examine problems that put
your objects in a critical state, and identify solutions. To resolve the resource and time remaining
problems, use the Capacity Optimization function.
You have used the Alerts, Details, All Metrics, and Environment areas of the user interface to
examine critical problems such as resource contention and time remaining issues that occur on
your objects. To resolve those problems, you can use the Capacity Optimization function.
Prerequisites
Examine the environment relationships. See Examine the Environment Relationships.
Procedure
1 In the menu, click Home, then click Overview under Optimize Capacity in the left pane. The
Capacity Overview screen appears.
2 Select the data center - DC-Denver-19 - that contains the problem objects.
The data in the lower half of the screen refreshes to display time remaining information and
reclaim recommendations for selected data center DC-Chicago-12. NOTE: Double-clicking the
data center graphic displays the Object Details page for that data center.
3 At the graph, select Most Constrained from the Sort By: choices and CPU from CPU|Memory|
Disk Space above the graph.
The graph refreshes to show the usage value almost touching 100% and the timeline/
projection value nearly intersecting the usage value. The data center is almost out of CPU.
4 Scroll down the page to the Recommendations below the graph.
Option 1 lists total resources (CPU, memory, disk space) that can be reclaimed. Option 2 lists
the hardware to purchase to increase time remaining to 150 days.
5 Click RECLAIM RESOURCES.
The Reclaim screen appears, displaying data for DC-Chicago-12. The "How much can you
save?" pane shows that $4140/month can potentially be saved. Looking to the top of the
table, you see that the $4140 sum appears next to Oversized VMs.
6 Click Oversized VMs. Then click the chevron next to a cluster name on the left of the table.
All the VMs in the cluster are listed.
7 Select the check box next to VM Name in the table heading.
All the VMs in the cluster are checked.
8 Click RESIZE VM(s).
The Resize VMs page appears, showing the 20 VMs available for resizing.
VMware, Inc. 801

9 Leave the recommendation as is, without editing the target reductions, then select the "I
understand that workloads may be interrupted..." check box and click RESIZE VM(s).
The system runs the resize action.
Results
You have used Capacity Optimization to resolve problems on a host system that is experiencing
critical problems. The data center does not run out of CPU, and instead realizes projected cost
savings of nearly $50,000 annually.
What to do next
To become aware of critical problems on your objects before they adversely affect the
performance of other objects and your environment, configure the Workload Optimization alerts
to be automated. See Configuring Workload Optimization Alerts.
Create Dashboards and Views

To help you investigate and troubleshoot problems with your cluster and host systems that might
occur in the future, you can create dashboards and views. These tools apply the troubleshooting
solutions that you used to research and solve the problems with your host system, and make the
troubleshooting tools and solutions available for future use.
To view the status of your cluster and host systems when your CIO asks you about their health,
you can use the decision support dashboards on the vRealize Operations Manager Home page.
For example, you can:
n Use the Cluster Utilization dashboard to view the use index, CPU demand, and memory use
for your clusters. This dashboard also tracks Internet use and disk I/O operations.
n Use the Capacity Summary dashboard to track total environment capacity, system-wide
capacity and time remaining, and capacity remaining by CPU, memory, and storage. The
dashboard also includes Top 10 lists for clusters running out of CPU, memory, and storage,
respectively. Additional details are available.
n Use the Capacity Optimization dashboard to examine the provisioned capacity levels for CPU,
disk, and memory and to review potential reclaimable capacity from CPUs, data centers,
snapshot waste, and virtual memory.
Or, you might need to create your own dashboards to track the status of your clusters and host
systems.
If you work in a Network Operations Center environment and have multiple monitors, you can run
multiple instances of vRealize Operations Manager. By running the many instances, you can
dedicate a monitor to each dashboard and visually track the status of your objects.
Procedure
1 In the menu, click Dashboards and look through the list of existing dashboards to determine
whether you can use the cluster and host system dashboards to track your clusters and host
systems.
VMware, Inc. 802

2 Click the Self Troubleshooting dashboard, and review the widgets included on it: Object
Type, Select Objects, Metric Picker, and Metric Chart.
By adding the Object List, Alert List, Heatmap, and Top-N widgets, you can easily peruse the
status of the host systems that you select in the Object List widget. Configure widget
interaction so that the object you select in the Object List widget is the object for which the
other widgets display data.
3 Create and configure a new dashboard that has widgets to monitor the health of your host
systems and generate alerts.
a Above the dashboard view, click Actions and select Create Dashboard.
b In the New Dashboard workspace, for the Dashboard Name, enter System Health, and
leave the other default settings.
c In the Widget List workspace, add the Object List widget and configure it to display host
system objects.
d Add the Alert List widget to the dashboard, and configure it to display capacity alerts
when the capacity of your host systems becomes an immediate risk.
e Add the Heatmap and Top_N widgets.
f In the Widget Interactions workspace, for each widget listed, select the Object List widget
as the provider to drive the data to the other widgets, and click Apply Interactions.
g In the Dashboard Navigation workspace, select the dashboards that receive data from
the selected widgets, and click Apply Navigations.
After vRealize Operations Manager collects data, if a problem occurs with the capacity of
your host systems, the Alert List widget on your new dashboard displays the alerts that are
configured for your host systems.
What to do next
Prepare to share information with others, plan for growth and new projects, and use policies to
monitor continuously all the objects in your environment. See Reports, Chapter 6 Capacity
Optimization for Your Managed Environment , and Policies .
Monitoring and Responding to Alerts

Alerts indicate a problem in your environment. Alerts are generated when the collected data for
an object is compared to alert definitions for that object type and the defined symptoms are true.
When an alert is generated, you are presented with the triggering symptoms, so that you can
evaluate the object in your environment, and with recommendations for how to resolve the alert.
Alerts notify you when an object or group of objects are exhibiting symptoms that are
unfavorable for your environment. By monitoring and responding to alerts, you stay aware of
problems and can react to them in a timely fashion.
Generated alerts drive the status of the top-level badges, Health, Risk, and Efficiency.
VMware, Inc. 803

In addition to responding to alerts, you can generally respond to the status of badges for objects
in your environment.
You cannot assign alerts to vRealize Operations Manager users. Your users must take ownership
of an alert.
Monitoring Alerts in vRealize Operations Manager

You can monitor your environment for generated alerts in several areas in vRealize Operations
Manager. The alerts are generated when the symptoms in the alert definition are triggered,
letting you know when the objects in your environment are not operating within the parameters
you defined as acceptable.
Generated alerts appear in many areas of vRealize Operations Manager so that you can monitor
and respond to problems in your environment.
Alerts
Alerts are classified as Health, Risk, or Efficiency. Health alerts indicate problems that require
immediate attention. Risk alerts indicate problems that must be addressed shortly, before the
problems become immediate health problems. Efficiency alerts indicate areas where you can
reclaim wasted space or improve the performance of objects in your environment.
You can monitor the alerts for your environment in the following locations.
n Alerts
n Health
n Risk
n Efficiency
You can monitor alerts for a selected object in the following locations.
n Alert Details, including the Summary, Timeline, and Metric Charts tabs
n Summary tab
n Alerts tab
n Events tab
n Custom dashboards
n Alert notifications
Working with Alerts

Alerts indicate a problem that must be resolved so that triggering conditions no longer exist and
the alert is canceled. Suggested resolutions are provided as recommendations so that you can
approach the problem with solutions.
As you monitor alerts, you can take ownership, suspend, or manually cancel alerts.
VMware, Inc. 804

When you cancel an alert, the alert and any symptoms of type message event, or metric event
are canceled. You cannot manually cancel other types of symptoms. If a message event
symptom or metric event symptom triggered the event, then the alert is effectively canceled. If a
metric symptom or property symptom triggered the alert, a new alert might be created for the
same conditions in the next few minutes.
The correct way to remove an alert is to address the underlying conditions that triggered the
symptoms and generated the alert.
Migrated Alerts
If you migrated alerts from a previous version of vRealize Operations Manager, the alerts are
listed in the overview with a canceled status, but alert details are not available.
User Scenario: Monitor and Process Alerts in vRealize Operations Manager

Alerts in vRealize Operations Manager notify you when objects in your environment have a
problem. This scenario illustrates one way that you can monitor and process alerts for the objects
for which you are responsible.
An alert is generated when one or more of the alert symptoms are triggered. Depending on how
the alert is configured, the alert is generated when one symptom is triggered or when all the
symptoms are triggered.
As the alerts are generated, you must process the alerts based on the negative affect they have
on objects in your environment. To do the processing, you start with Health alerts, and process
them based on criticality.
As a virtual infrastructure administrator, you review the alerts at least twice a day. As part of your
evaluation process in this scenario, you encounter the following alerts:
n Virtual machine has unexpected high CPU workload.
n Host has memory contention that a few virtual machines cause.
n Cluster has many virtual machines that have memory contention because of memory
compression, ballooning, or swapping.
Procedure
2 Select Time in the Group By filter and the click the down arrow in the Created On column, so
the most recent alerts are listed first .
3 In All Filters, select Criticality > Warning
You have listed all the Warning alerts in order of when they fired, with the most recent alerts
appearing first.
VMware, Inc. 805

4 Review the alerts by name, the object on which it was triggered, the object type, and the
time at which the alert was generated.
For example, do you recognize any of the objects as objects that you are responsible for
managing? Do you know that the fix that you will implement in the next hour will fix any of
the alerts that are affecting the Health status of the object? Do you know that some of your
alerts cannot be resolved currently because of resource constraints?
5 To indicate to other administrators or engineers that you are taking ownership of the Virtual
machine has unexpected high CPU workload alerts, click the selected alerts, click Actions
on the menu bar, and click Take Ownership.
The Assigned to: field in Alert Details updates with your user name. You can only take
ownership of alerts, you cannot assign them to other users.
6 To take ownership and temporarily exclude the alert from affecting the state of the object,
select the Host has memory contention caused by a few virtual machines alert in the list.
Then click Actions on the menu bar and click Suspend.
a To suspend the alert for an hour, enter 60.
b Click OK.
The alert is suspended for 60 minutes and you are listed as the owner in the alert list. If it is
not resolved in an hour, it returns to an active state.
7 Select the row that contains the Cluster has many Virtual Machines that have memory
contention due to memory compression, ballooning or swapping alert. Then click
Actions on the menu bar and click Cancel Alert to remove the alert from the list.
This alert is a known problem that you cannot resolve until the new hardware arrives.
The alert is removed from the alert list, but this action does not resolve the underlying
condition. The symptoms in this alert are based on metrics, so the alert will be generated
during the next collection and analysis cycle. This pattern continues until you resolve the
underlying hardware and workload distribution issues.
Results
You processed the critical health alerts and took ownership of the ones to resolve or
troubleshoot further.
What to do next
Respond to an alert. See User Scenario: Respond to an Alert in the Health Alert List.
User Scenario: Respond to an Alert in the Health Alert List
In this scenario, you investigate and resolve the Virtual machine has an unexpected high CPU
workload alert. The alert might be generated for more than one virtual machine.
VMware, Inc. 806

Prerequisites
Generated alerts in vRealize Operations Manager appear in the alert lists. You use the alert lists to
investigate, resolve, and begin troubleshooting problems in your environment.
n Process and take ownership of the alerts you troubleshoot and resolve. See User Scenario:
Monitor and Process Alerts in vRealize Operations Manager.
n Review information about how the Power Off Allowed setting works when you run actions.
See Working with Actions That Use Power Off Allowed.
Procedure
2 To limit the list to virtual machine alerts, click All Filters on the toolbar.
a Select Object Type in the drop-down menu.
b Enter virtual machine in the text box.
c Click Enter.
The alerts list displays only alerts based on virtual machines.
3 To locate the alerts by name, enter high CPU workload in the Quick filter (Alert) text box.
4 In the list, click the Virtual machine has an unexpected high CPU workload alert name.
5 Review the information. To show the recommendations, click Alert Settings >
Recommendations in the left pane .
Alert Description Review the description so that you better understand the alert.
Recommendations Do you think that implementing one or more of the recommendations can
resolve the alert?
What is Causing the Issue? Do the triggered symptoms support the recommendations? Do the other
triggered symptoms contradict the recommendation, indicating that you
must investigate further?
In this example, the triggered symptoms indicate that the virtual machine
CPU demand is at a critical level and that the virtual machine anomaly is
starting to get high.
Non-Triggered Symptoms Some alerts are generated only when all the symptoms are triggered.
Others are configured to generate an alert when any one of the symptoms
are triggered. If you have non-triggered symptoms, evaluate them in the
context of the triggered alerts.
Do the non-triggered symptoms support the recommendations? Do the non-
triggered symptoms indicate that recommendations are not valid and that
you must investigate further?
VMware, Inc. 807

6 To resolve the alert based on the recommendation to check the guest applications to
determine whether a high CPU workload is an expected behavior, click the Action menu on
the center pane toolbar and select Open Virtual Machine in vSphere Client.
a Log in to the vCenter Server instance using your vSphere credentials.
b Start the console for the virtual machine and identify which guest applications are
consuming CPU resources.
7 To resolve the alert based on the recommendation to add more CPU capacity to this virtual
machine, click Set CPU Count for VM.
a Enter a new value in the New CPU text box.
The value that appears is the calculated suggested size. If vRealize Operations Manager
was monitoring the virtual machine for six or more hours, depending on your
environment, the value that appears is the CPU recommended size metric.
b To allow power off or to create a snapshot, depending on how your virtual machines are
configured, select the following options.
Option Description
Power Off Allowed Shuts down or powers off the virtual machine before modifying the value.
If VMware Tools is installed and running, the virtual machine is shut down.
If VMware Tools is not installed or not running, the virtual machine is
powered off without any regard for the state of the operating system.
In addition to the question whether the action shuts down or powers off
a virtual machine, you must also consider whether the object is powered
on and what settings are applied.
Snapshot Creates a snapshot of the virtual machine before you add CPUs.
If the CPU is changed with CPU Hot Plug enabled, then the snapshot is
taken with the virtual machine running, which consumes more disk space.
c Click OK.
The action adds the suggested number of CPUs to the target virtual machine.
8 Allow several collection cycles to run after implementing the suggested changes and check
the alert list.
What to do next
If the alert does not reappear after several collection cycles, it is resolved. If it reappears, further
troubleshooting is required. For an alternative scenario for troubleshooting alerts, see User
Scenario: An Alert Arrives in Your Inbox.
Monitoring and Responding to Problems

The organization of the tabs and options in vRealize Operations Manager provides a built-in
workflow that you can use when you work with objects in your environment.
VMware, Inc. 808

The tabs, Summary, Alerts, Capacity, and so on, provide a progressive level of detail about the
selected object. As you work through the tabs, starting with the high level Summary and Alerts
tabs, you see the general state of an object. The data provided in the Events tabs is useful when
you are investigating the root cause of a problem. The Details tabs are specific data views and
the Environment tabs show object relationships.
As you monitor objects in your environment, you discover which tabs provide the information
that you need when you are investigating problems.
Evaluating Object Information Using Badge Alerts and the Summary

Tab
The Summary tab that is associated with the other object tabs summarizes Heath, Risk, and
Efficiency badge alerts for the selected object and displays the top alerts that lead to the current
state.
Use this tab as an overview of alerts for an object, object group, or application - to evaluate the
effect that alerts are having on an object and to begin troubleshooting problems. For more detail
on the badge Alerts, click Badge Alerts, further to the right on the tool bar.
Badge Alert Types

The Health, Risk, and Efficiency badge states are based on the number and criticality of the
generated alerts for the selected object.
n Health alerts indicate problems that affect the health of your environment and require
immediate attention to ensure that service to your customers is not affected.
n Risk alerts indicate problems that are not immediate threats but must be addressed shortly.
n Efficiency alerts tell you where you can improve performance or reclaim resources.
Alerts for an Object or an Object Group

For a single object, the Top alerts are the alerts generated for the object. The Top Alerts for
Children are the alerts generated for any child or other descendant objects in the currently
selected navigation hierarchy. For example, if you are working with a host object in the vSphere
Host and Clusters navigation hierarchy, children can include virtual machines and datastores.
Object groups can include one object type, such as hosts, or multiple objects types, such as
hosts, virtual machines, and datastores. When you are working with object groups, all the group
member objects are children of the group container. The most critical generated alerts for the
member objects appear as Top Alerts for Children.
For an object group, the only Top Alerts that might be generated are the predefined group
population alerts. If the average health is above the Warning, Immediate, or Critical threshold, a
group population alert considers the health of all group members and is triggered. If a group
population alert is generated, the alert affects the badge score and color. If a group population
alert is not generated, then the badges are green. This behavior is because an object group is a
container for other objects.
VMware, Inc. 809

Summary Tab and Related Hierarchies

The alerts that appear on the Summary tab for an object can vary depending on the currently
selected hierarchy in the Related Hierarchies in the left pane.
Depending on the selected hierarchy, you see different alerts and relationships on the Summary
tab for an object. The current focus object name is on the center pane title bar, but the children
alerts depend on the relationships that the highlighted hierarchy defined in the Related
Hierarchies list in the upper left pane. For example, if you are working with a host object relative
to virtual machines in the vSphere Hosts and Clusters hierarchy, then children commonly include
virtual machines and datastores. But if you are working with the same host as a member of an
object group, then any alerts on virtual machines that are also members of the group do not
appear. The alerts do not appear because the host and the virtual machines are considered
children of the group and peers among each other. In this example, the focus of the Summary
tab is the host in the context of the group, not the vSphere Hosts and Clusters hierarchy.
Summary Tab Evaluation Techniques

You can evaluate the state of objects, starting with the Summary tab, by using one or more of
the following techniques.
n Select an object or object group, click the alerts on the Summary tab, and resolve the
problems that the alert indicates.
n Select an object, review the alerts on the Summary > Alerts tab, and select other objects,
comparing the volume and types of alerts generated for different objects.
User Scenario: Evaluate the Badge Alerts for Objects for a vRealize Operations
Manager Object Group
In vRealize Operations Manager, you use alerts on a group to review the summary alert
information for hosts and virtual machine descendant objects. Using this method, you can see
how the state of one object type can affect the state of the other.
As a network operations center engineer, you are responsible for monitoring a group of hosts
and virtual machines for the sales department. As part of your daily tasks, you check the state of
the objects in the group to determine if there are any immediate problems or any upcoming
problems based on generated alerts. You start with your group of objects, particularly the host
systems in the group, and review the information in the Summary tab.
In this example, the group includes the following object alerts.
n Health alert:Host has memory contention caused by a few virtual machines.
n Risk alert:Virtual Machine has a chronic high memory workload.
n Risk alert:Virtual Machine is demanding more CPU than the configured limit.
n Efficiency alert:Virtual Machine has large disk snapshots.
VMware, Inc. 810

The following method of evaluating alerts on the Summary tab is provided as an example for
using vRealize Operations Manager and is not definitive. Your troubleshooting skills and your
knowledge of the particulars of your environment determine which methods work for you.
Prerequisites
n Create a group that includes virtual machines and the hosts on which they run. For example,
Sales Dept VMs and Hosts. For an example of how to create a similar group, see Create a
Custom Accounting Department Group.
n Review how the Summary tab works with object groups and related hierarchies. See
Evaluating Object Information Using Badge Alerts and the Summary Tab.
Procedure
2 Click the Custom Groups tab and click, for example, your Sales Dept VMs and Hosts group.
3 To view the alerts for a host and the associated child virtual machines, in the left pane, click,
for example, Host System and click the host name in the lower left pane.
The Summary tab displays the Health, Risk, and Efficiency badges.
4 To view the Summary tab for the host so that you can also work with the child virtual
machines, click the right arrow to the right of the host name in the lower left pane.
5 Select the vSphere Hosts and Clusters, located in the upper part of the left pane.
To work with alerts for child virtual machines, the host in the vSphere Hosts and Clusters
hierarchy must be the focus of the Summary tab rather than the host as a member of the
object group.
6 To view the alert details for an alert in the list, click the alert name.
When multiple objects are affected, and you click the alert link to view the details, the Health
Issues dialog box appears. If there is only one object affected, the Alerts tab for the object is
displayed.
7 On the Alerts tab, begin evaluating the recommendations and triggered symptoms.
In this scenario, a recommendation for this generated alert is to move some virtual machines
with a high memory workload from this host to a host with more available memory.
8 To return to the object Summary tab so that you can review alerts for any child virtual
machines, click the back button located in the left pane.
The host is again the focus of the object Summary tab. Generated alerts for the child virtual
machines appear in the following table.
VMware, Inc. 811

9 Click each virtual machine alert and evaluate the information provided on the Alerts tab.
Virtual Machine Alert Evaluation
Virtual Machine has a The recommendation is to add more memory to this virtual machine.
chronic high memory If one or more virtual machines are experiencing high workload, this situation is probably
workload. contributing to the host memory contention alert. These virtual machines are candidates for
moving to a host with more available memory. Moving the virtual machines can resolve the
host memory contention alert and the virtual machine alert.
Virtual Machine is The recommendations include increasing or removing the CPU limits on this virtual machine.
demanding more CPU If one or more virtual machines are demanding more CPU than is configured, and the host is
than the configured experiencing memory contention, then you cannot add CPU resources to the virtual
limit. machine without further stressing the host. These virtual machines are candidates for
moving to a host with more available memory. Moving the virtual machines can allow you to
increase the CPU count and resolve the virtual machine alert, and might resolve the host
memory contention alert.
10 Take the suggested actions.
Results
Your actions might resolve the virtual machine and host alerts.
What to do next
After a few collection cycles, look again at your Sales VMs and Hosts group to determine if the
alerts are canceled and no longer appear in the object Summary tab. If the alerts are still present,
see User Scenario: Investigate the Root Cause of a Problem by Using the Troubleshooting Tab
Options for an example troubleshooting workflow.
Summary Tab
The Summary tab provides an overview of the state of the selected object, group, or application.
Use this tab to evaluate the impact that alerts are having on the object and use the information to
begin troubleshooting problems.
How the Summary Tab Works
Based on the object selected, the following summary tabs are displayed:
n VM Summary Tab
n Datastore Summary Tab
n Host Summary Tab
n Cluster Summary Tab
n Custom Group and Container Summary Tab

Where to Find the Summary Tab
n In the menu, click Environment, then select a group, custom data center, application, or
inventory object.
VMware, Inc. 812

n In the menu, select Alerts to display the All Alerts screen. Click an alert to display the alert
details on the right. Then click View Additional Metrics to see more information about the
alert and the object that triggered the alert. Click the Summary tab.
Understanding the Summary Tab
Table 5-1. Summary Tab Options

Option Description
Recommended Actions This widget displays the health status for the selected
object and its descendants. It also displays suggestions to
solve problems in an instance.
The badges provide a visual indicator of the alert status for
the following alert types.
n Health alerts that usually require immediate attention.
n Risk alerts indicating that you must look into any
problems shortly.
n Efficiency alerts indicating that you can reclaim
resources.
To see the alerts for the object, click the badge .
About Me This widget displays the summary of metrics and

properties of the selected object for review.
Performance Gives data for CPU demand, memory usage and

contention, I/O, and disk latency.
Select Parent Host or Datastore Select the parent host or datastore associated with this
object. You can then use the Neighbors on Selected Parent
Host or Datastore .... pane to explore the health of objects
related to the selected object.
VMware, Inc. 813

Table 5-1. Summary Tab Options (continued)

Option Description
What does my week look like? Gives a historical view of the hourly workload pattern of
the object. Provides a preview of any trouble areas that
might create issues.
Capacity Remaining This widget displays a score indicating the remaining

computing resources as a percent of the total consumer
capacity for the most constrained resource.
Datastore Summary Tab

The Datastore Summary tab provides an overview of the state of the selected datastore. For the
selected object, the Datastore Summary tab displays the alerts and metrics as they affect the
health, risk, or efficiency. Use this tab to evaluate the impact that alerts are having on the
datastore and use the information to begin troubleshooting problems.
Understanding the Datastore Summary Tab
VMware, Inc. 814

Table 5-2. Datastore Summary Tab Options

Option Description
object and its descendants. It also displays
recommendations to solve problems in an instance.
problems shortly.
resources.
About Me This widget displays the key metrics and properties of the
selected object.
Inventory This widget displays the number of hosts and VMs

associated with the datastore.
Capacity This widget displays a visual summary of the capacity and

workload resources used by the objects in your
environment. It displays the latest value and a trend line of
the various key indicators in a color that indicates its health
based on the symptom associated with the metrics.
Double-click each metric to see the expanded chart.
Performance This widget displays the summary metrics about the overall
performance of the object. It displays the latest value and a
trend line of the various key performance indicators in a
color that indicates its health based on the symptom
associated with the metrics. Double-click each metric to
see the expanded chart.
Child VMs distribution by Disk IO, Disk Latency As per the configuration that you choose from the list, this
widget displays heat maps to show the distribution of the
child VMs based on the Disk IO and Disk latency metrics. It
helps to evaluate quickly the status of all the VMs using the
same datastore. It also helps to check if there are problems
that impact all the VMs or if a group of VMs is the source of
a problem.
Host Summary Tab

The Host Summary tab provides an overview of the state of the selected host. For the selected
object, the Host Summary tab displays the alerts and metrics as they affect the health, risk, or
efficiency. Use this tab to evaluate the impact that alerts are having on the host and use the
information to begin troubleshooting problems.
Understanding the Host Summary Tab
VMware, Inc. 815

Table 5-3. Host Summary Tab Options

Option Description
problems soon.
resources.
selected object.
Inventory This widget displays the number of running VMs and

Datastores associated with the selected host.

Double-click each metric to see the detailed chart.
VMware, Inc. 816

Table 5-3. Host Summary Tab Options (continued)

Option Description
Child VMs Distribution by CPU, Memory As per the configuration that you select from the list, this
widget displays the heat maps showing the distribution of
the child VMs based on CPU and Memory metrics. It also
helps to identify the noisy VMs in the host.
VM Summary Tab
The VM Summary tab provides an overview of the state of the selected VM. For the selected
object, the VM Summary tab displays the alerts and metrics as they affect the health, risk, or
efficiency. Use this tab to evaluate the impact that alerts are having on the VM and use the
information to begin troubleshooting problems.
Understanding the VM Summary Tab
VMware, Inc. 817

Table 5-4. VM Summary Tab Options

Option Description
problems shortly.
resources.
To see the alerts for the object, click the badge.
selected object.
VMware, Inc. 818

Table 5-4. VM Summary Tab Options (continued)

Option Description

Double-click each metric to see the expanded chart.
What does my week look like? This widget displays a quick view of the hourly workload
pattern that the VM went through in the last week per day.
Select Parent Host or Datastore This widget display the status of the parent host or
datastore of the selected VM. This input controls the data
displayed in the heat map.
Neighbors on Selected Parent Host or Datastore by CPU, As per the configuration that you choose from the list, this
Memory, Disk IO widget displays heat maps showing the distribution of the
neighbors on selected parent host or datastore by CPU,
Memory, and Disk IO. It helps to identify the noisy
neighbors using the same infrastructure.
Cluster Summary Tab

The Cluster Summary tab provides an overview of the state of the selected cluster. For the
selected object, the Cluster Summary tab displays the alerts and metrics as they affect the
health, risk, or efficiency. Use this tab to evaluate the impact that alerts are having on the cluster
and use the information to begin troubleshooting problems.
Understanding the Cluster Summary Tab
VMware, Inc. 819

Table 5-5. Cluster Summary Tab Options

Option Description
problems shortly.
resources.
selected object.
Inventory This widget displays the number of running hosts, running

VMs, and datastores associated with the cluster.
Utilization This widget provides a summary of the use of the cluster

by CPU/Memory and IO. It displays a trend line for the last
24 hours and the latest value in the color associated with
its health based on the symptom associated with this
metric.
Performance This widget displays the trend line of maximum KPI values
for any of the VMs running on the cluster for the last 24
hours. It also displays the latest value in a color that
represents its health based on the symptom associated
with this metric. Click each metric to see a detailed view of
the chart.
VMware, Inc. 820

Table 5-5. Cluster Summary Tab Options (continued)

Option Description
Child Hosts Distribution by CPU, Memory As per the configuration that you choose from the list, the
heat map shows the distribution of the child hosts based
on CPU and memory. It helps to identify quickly the VMs
with high demand and VMs with latency problems.
Child VMs Distribution by CPU, Memory, Latency As per the configuration that you choose from the list, the
heat map shows the distribution of the child VMs based on
CPU, memory, and latency. This heat map helps to identify
hosts with high workloads.
Custom Group and Container Summary Tab

The Custom Group and Container Summary tab provides an overview of the state of the selected
group or a container. For the selected object, the Custom Group and Container Summary tab
displays the alerts and metrics as they affect the health, risk, or efficiency. Use this tab to
evaluate the impact that alerts are having on the group or a container and use the information to
troubleshoot the problems.
Understanding the Custom Group and Container Summary Tab
VMware, Inc. 821

Table 5-6. Customer Group and Container Summary Tab Options

Option Description
problems shortly.
resources.
To see the alerts for the object, click the badge.
vSAN Cluster Summary Tab

The vSAN cluster summary tab provides details about Disk Groups, Capacity Disks, Cache Disks,
Total Capacity, and Alerts associated with the vSAN cluster.
Where To View vSAN Cluster Summary Page
On the menu, click Environment > VMware vSAN > vSAN and Storage Devices > vSAN Cluster.
You can also view relationship details and heat map details for the selected vSAN cluster. The
relationship section provides information about the relationship between the objects in your
vSAN cluster. The heat map helps you to identify potential problems for the objects in your vSAN
cluster.
vSAN Cluster Fault Domain Summary Tab

The vSAN cluster fault domain summary tab provides details about CPU, CPU Cores, Memory,
Disc Space and Alerts associated with the fault domain of the vSAN cluster.
Where To View vSAN Cluster Fault Domain Summary
On the menu, click Environment > VMware vSAN > vSAN and Storage Devices > vSAN Cluster >
Fault Domain.
You can also view relationship details and heat map details for the selected vSAN fault domain.
The relationship section provides information about the relationship between the objects in your
fault domain.
vSAN Cluster Disk Group Summary Tab

The vSAN cluster disk group summary tab provides details about Disc Capacity, Write Buffers,
Read Cache and Alerts associated with the disk group of the vSAN cluster.
Where To View vSAN Cluster Disk Group Summary
On the menu, click Environment > VMware vSAN > vSAN and Storage Devices > vSAN Cluster >
Host System > Disk Group.
VMware, Inc. 822

You can also view relationship details and heat map details for the selected vSAN disk group. The
relationship section provides information about the relationship between the objects in your
disk group.
Investigating Object Alerts

The Alerts tab provides a list of generated alerts for the currently selected object. When you are
working with objects, reviewing and responding to generated alerts on the Alert tab helps you
manage problems in your environment.
The alerts notify you when a problem occurs in your environment based on configured alert
definitions. Object alerts are useful to you as an investigative tool in two ways. They can provide
you with early notification about problems in your environment before a user calls you to report
a problem. As well, object alerts can provide information about the object that you can use when
troubleshooting general or reported problems.
As you review the Alerts tab, you can add ancestors and descendants to the list to broaden your
view of the alerts. You can see if alerts on the current object affect other objects. Conversely,
you can examine how problems reflected in alerts on other objects affect the current object.
Depending on the practices and workflows of your infrastructure operations team, you can use
the object Alerts tab to manage generated alerts on individual objects.
n Take ownership of alerts so that your team knows that you are working to resolve the
problem.
n Suspend an alert so that is temporarily excluded from affecting the Health, Risk, or Efficiency
state of the object while you investigate the problem.
n Cancel alerts that you know are a result of a deliberate action. For example, a network card is
removed from a host for replacement. Also cancel alerts that are known issues that you
cannot resolve currently because of resource constraints. Canceling an alert that is generated
because of only message event or metric event symptoms cancels the alert permanently. If
the underlying metric or property condition remains true, canceling an alert that is generated
because of metric, super metric, or property symptoms can result in the alert being
regenerated . It is only effective to cancel alerts generated because of message event or
metric event symptoms.
Investigating and resolving alerts helps you provide the best possible environment to your
customers.
User Scenario: Respond to Alerts on the Alerts Tab for Problem Virtual Machines
You respond to alerts for objects so that you can bring the affected objects back to the required
level of configuration or performance. Based on the information in the alert and using other
information provided in vRealize Operations Manager, you evaluate the alert, identify the most
likely solution, and resolve the problem.
VMware, Inc. 823

As a virtual infrastructure administrator or operations manager, you troubleshoot problems with

objects. Reviewing and responding to the generated alerts for objects is part of any
troubleshooting process. In this example, you want to resolve workload problems for a virtual
machine. As part of that process, you review the Alerts tab to determine what alerts might
indicate or contribute to the identified problem.
The problem virtual machine is db-01-kyoto, which you use as a database server.
The following method of responding to alerts is provided as an example for using vRealize
Operations Manager and is not definitive. Your troubleshooting skills and your knowledge of the
particulars of your environment determine which methods work for you.
Prerequisites
n Verify that the vCenter Adapter has been configured for the actions in each vCenter Server
instance.
n Verify that you understand how to use the power-off-allowed option if you are running Set
CPU Count, Set Memory, and Set CPU Count and Memory actions. See Working with Actions
That Use Power Off Allowed.
Procedure
1 Enter the name of the object, db-01-kyoto, in the Search text box and select the virtual
machine in the list.
The object Summary tab appears. The Top Alerts panes display important active alerts for
the object.
2 Click the All Metrics tab.
The All Metrics > Badge > Workload % generates a graph in the right pane that shows the
workload is heavy.
3 Click the Alerts tab.
In this example, the alert list includes the follow alerts that might be related to the problem
you are investigating.
n Virtual machine has unexpected high CPU workload.
n Virtual machine has unexpected high memory workload.
VMware, Inc. 824

4 In the upper left pane, select the vSphere Hosts and Clusters related hierarchy and select
ancestor or descendant alerts to add to the list.
You want to check for possible alerts on ancestor or descendant objects in the context of the
selected hierarchy.
a On the toolbar, click Show Ancestor Alerts and select the Host System and Resource
Pool check boxes.
Any alerts for the host system or resource pool related to this virtual machine are added
to the list.
b Click Show Descendant Alerts and select Datastore.
Any alerts for the datastore are added to the list.
In this example, there are no additional alerts for the host, resource pool, or datastore, so you
begin addressing the virtual machine alerts.
5 Click the Virtual machine has unexpected high CPU workload alert name.
The Alert Details Summary tab appears.
6 Review the recommendations to determine if one or more suggested recommendations can

fix the problem.
This example includes the following common recommendations:
n Check the guest applications to determine whether high CPU workload is

expected behavior.
n Add more CPU capacity for this virtual machine.
7 To follow the Check the guest applications to determine whether high CPU workload is
expected behavior recommendation, click Actions on the title bar and select Open Virtual
Machine in vSphere Client.
The vSphere Web Client Summary tab appears so that you can open the virtual machine in
the console and check which applications are contributing to the reported high CPU
workload.
8 To follow the Add more CPU Capacity for this virtual machine recommendation, click Set CPU
Count for VM .
a Enter a value in the New CPU text box.
The default value that appears before you provide a value is a suggested value based on
analytics.
b To allow the action to power off the virtual machine before running the action if Hot Add
for CPU is not enabled, select the Power Off Allowed check box.
c To create a snapshot before changing the virtual machine CPU configuration, select the
Snapshot check box.
VMware, Inc. 825

d Click OK.
e Click the Task ID link and verify that the task ran successfully.
The specified number of CPUs are added to the virtual machine.
What to do next
After a few collection cycles, return to the object Alerts tab. If the alert no longer appears, then
your actions resolved the alert. If the problem is not resolved, see User Scenario: Investigate the
Root Cause of a Problem by Using the Troubleshooting Tab Options for an example
troubleshooting workflow.
Alerts Tab
The Alerts tab is a list of all the alerts generated for the selected object, group, or application.
Use the alerts list to evaluate the number of generated alerts for the object so that you can begin
resolving them.
How the Alerts Tab Works
All the active alerts for the selected object appear in the list. By default, the system groups the
alerts by Time. You can select multiple rows in the list using Shift+click, Control+click. Modify the
filter if you want to see inactive alerts.
Manage the alerts in the list using the toolbar options. Click the alert name to see the alert details
for the affected object. The alert details appear on the right, including the symptoms triggered
with the alert. The system offers recommendations for addressing the alert and links to additional
information. A Run Action button might appear in the details. Point to the button to learn what
recommendation is performed if you click the button. To return to the list view, click the X at the
top right of the alert details.
To see the object details, click the Summary Tab.

Where You Find the Alerts Tab
inventory object. Click the object to display the object's Summary tab. Click the Alerts >
Alerts tabs.
n In the menu, select Search and locate the object of interest. Click the object to display the
object's Summary tab. Click the Alerts > Alerts tabs.
Alerts Tab Options
The alert options include toolbar and data grid options. Use the toolbar options to sort the alert
list and to cancel, suspend, or manage ownership. Additional toolbar options enable you to
review parent and child alerts related to the alert you are reviewing. Use the data grid to view
the alerts and alert details.
VMware, Inc. 826

Table 5-7. Actions Menu

Option Description
Actions menu Select an alert from the list to turn on the Actions menu,
then select an option from the menu.
Menu Options:
from the list.
Delete Canceled Alerts Delete cancelled (inactive) alerts by making a group

selection or by individually selecting alerts. You cannot
delete active alerts.

owner.
alert.
ownership.
Go to Alert Definition Switches to the Alert Definitions page, with the definition
for the previously selected alert displayed.
Disable... Offers two options for disabling the alert:

Disable the alert in all policies: this disables the alert for all
objects for all the policies.
Disable Alert in Selected Policies: this disables the alert for
objects having the selected policy. This method works only
for objects with alerts.
Open an external application Actions you can run on the selected object.
VMware, Inc. 827

Table 5-8. View From Menu

Options Description
Self The selected object.
Parents <options> Displays the alerts for the ancestors of the selected object.
Parents in this instance include the parents, grandparents,
and so on, of the object. For example, the parents of a host
are a folder, storage pod, cluster, data center, and vCenter
Server instance.
Children <options> Displays the alerts for the descendants of the selected
object.
Children in this instance include the children and
grandchildren of the object. For example, the descendants
of a host are datastores, resources pools, and virtual
machines.

Option Description
Time Group alerts by time triggered. The default.
"All Alerts Data Grid Options" table, below.

together.
Table 5-10. Alerts Data Grid

Option Description



VMware, Inc. 828

Table 5-10. Alerts Data Grid (continued)

Option Description

Table 5-11. All Filters

Filtering options Limit the list of alerts to those matching the filters you
choose.
For example, you might have chosen the Time option in the
Group By menu. Now you can choose Status -> Active in
the all Filters menu, and the All Alerts page displays only
the active alerts, ordered by the time they were triggered.
Selected Options (see also the Group By and Alerts Data Grid tables for more filter definitions:)
Owner Name of operator who owns the alert.
Impact Alert badge affected by the alert. The affected badge,

health, risk, or efficiency, indicates the level of urgency for
the identified problem.
the object.
include:
assigned to a user.
VMware, Inc. 829

Table 5-11. All Filters (continued)

occurs:
canceled.
following reasons:
deleted.
Table 5-12. Alert Details Tab

Section Description
Recommendations View recommendations for the alert. To resolve the alert,

click the Run Action button if it appears.
Other Recommendations Collapse the section to view additional recommendations.

See the links in the Need More Information? section to
view additional metrics, events, or other details that appear
as a link.
If a VM is configured to send data to Wavefront, click View
App Metrics in Wavefront to view the metrics in
Wavefront.
Symptoms View the symptoms that triggered the alert. Collapse each
symptom to view additional information.
Alert Information View information such as the start time, update time, and
status of the alert.
Close Click the X icon to close the alert details tab.
Evaluating Metric Information

The All Metrics tab provides a relationship map and user-defined metric charts. The topological
map helps you evaluate objects in the context of their place in your environment topology. The
metric charts are based on the metrics for the selected object that you think helps identify the
possible cause of a problem in your environment.
VMware, Inc. 830

Although you might be investigating problems with a single object, for example, a host system,
the relationship map allows you to see the host in the context of parent and child objects. It also
works as a hierarchical navigation system. If you double-click an object in the map, that object
becomes the focus of the map. The available metrics for the object become active in the lower-
left pane.
You can also build your own set of metric charts. You select the objects and metrics that provide
you with a detailed view of changes to different metrics for a single object, or for related objects
over time.
Where available, the All Metrics tab provides pre-defined sets of metrics to help you when
looking at a specific aspect of an object. For example, if you have a problem with a host, access
the most relevant information about the host by looking at the metrics displayed in the pre-
defined lists. You can edit these groups of metrics, and create additional groups, by dragging
and dropping metrics and properties from the All Metrics and All Properties lists.
For more information about the metrics, refer to Chapter 7 Metric, Property, and Alert Definitions.
Where You Find the All Metrics Tab

inventory object.
n Alternatively, click Environment, then use the hierarchies in the left pane to quickly drill down
to the objects that you want.
Create Metric Charts When You Troubleshoot a Virtual Machine Problem

You create a custom group of metric charts when you troubleshoot a problem with a virtual
machine so that you can compare different metrics. The level of detail that you can create using
the All Metrics tab, can contribute significantly to your effort to find the root cause of a problem.
VMware, Inc. 831

As an administrator investigating a performance problem with a virtual machine, you determined

that you must see detailed charts about the following reported symptoms.
n Guest file system overall disk space usage reaching critical limit
n Guest partition disk space usage
The following method of evaluating problems using the All Metrics tab is provided as an example
for using vRealize Operations Manager and is not definitive. Your troubleshooting skills and your
Procedure
1 Enter the name of the virtual machine in the Search text box on the menu bar.
In this example, the virtual machine name is sales-10-dk.
2 Click the All Metrics tab.
3 In the relationship topology map, click the virtual machine, dk-new-10.
The metrics list, located in the left of the center pane, displays virtual machine metrics.
4 On the chart toolbar, click Date Control and select a time that is on or before the symptoms
were triggered.
5 Add metric charts to the display area for the virtual machine.
a In the metric list, select Guest Files System Stats > Total Guest File System Free (GB)
and double-click the metric name.
b To add the guest partition, for example, C:\, select Guest Files System Stats > C:\ > Guest
File System Free (GB) and double-click the metric name.
c To add disk space for comparison, select Disk Space > Capacity Remaining (%) and
double-click the metric name.
6 Compare the charts.
You can see a decrease in the file system free space, and that the virtual machine disk space
capacity remaining is decreasing at a steady rate. You determine that you must add disk
space to the virtual machine. However, you do not know if the datastore can support the
change to the virtual machine.
7 Add the datastore capacity chart to the charts.
a In the topology map, double-click the host.
The topology map refreshes with the host as the focus object.
b Click the datastore.
c In the metric list, which is updated to display datastore metrics, select Capacity >
Available Space (GB) and double-click the metric name.
8 To determine if sufficient capacity is available on the datastore to support increasing the disk
space on the virtual machine, review the datastore capacity chart.
VMware, Inc. 832

Results
You know that you must increase the size of the virtual disk on the virtual machine.
What to do next
Expand the virtual disk on the virtual machine and assign it to stressed partitions. Click Actions,
on the object title bar, and view the virtual machine in the vSphere Web Client.
Troubleshooting with the All Metrics Tab

The All Metrics tab provides a relationship graph and metric charts. The relationship graph helps
you evaluate objects in the context of their place in your environment topology. Metric charts are
based on the metrics for the active map object that you think can help you identify the cause of a
problem.
How All Metrics Works

You can double-click any object in the graph and view the specific parent-child objects for the
focus object. If you point to an object icon, you can see the health, risk, and efficiency details.
You can also click the Alerts link for the number of generated alerts. Click the purple icon to view
the child relationships of the object. If you double-click an object icon, the selected object
becomes the focus of the map. The graph is updated for the selected object, and the metrics list
shows only the metrics for the selected object.
Using the metrics list, you create charts based on metrics that you think can help you investigate
problems. You customize the charts to evaluate the data in detail. To save the configured charts,
you create a dashboard using the toolbar option.
Where available, the metrics list also displays pre-defined groups of metrics that contain the
most relevant metrics for the selected object. You can edit these groups, and create your own
customized groups of metrics by dragging and dropping metrics and properties from the All
Metrics and All Properties lists.
Where You Find All Metrics

inventory object.
n Alternatively, click Environment, then use the hierarchies in the left pane to locate the objects
that you want.
All Metrics Options

The options include the graph toolbar, the metric selector options, the metric charts toolbar, and
the toolbar on each chart.
VMware, Inc. 833

Table 5-13. Relationship Map

Option Description
Reset to initial object Returns the map to original object if you double-clicked on
an icon to examine another object.
Vertical/Horizontal Displays a vertical or horizontal view of the graph or tree

view.
Hide Text/Show Text Hides or displays the object names.
Standard View/Fit View The Standard View option fixes the view to a specific
zoom level.
The Fit View option adjusts the graph or tree view to fit the
screen.
Group Items/Ungroup Items Groups by objects types. You can view further details by
double-clicking on the object. You can also choose to
display the graph or tree view without grouping the object
types.
Path Exploration Displays the relative relationship path between two

selected objects on the graph or tree view. To highlight the
path, click the Path Exploration icon and then select the
two objects from the graph or tree view.
The chart options are used to limit the metric list.
Table 5-14. Metric Chart Selector

Option Description
Show collecting metrics Updates the list to display only the currently collected
metrics for the object.
Show previewable super metrics Updates the list to display super metrics for the object.
Note The super metrics only appear if the super metric is

associated with the object, see Create a Super Metric.
Actions Click the Actions icon to configure metric groups. Verify

that you hold the PowerUser or administrator role.
n Add Group. To add metrics or properties to the group,
expand any of the metric groups, and drag one or more
metrics to the group.
n Remove Group(s). To remove one or more groups.
n Rename Group. To enter a new name for the group.
n Remove Metric(s) from Group(s). To remove one or
more metrics or properties from one or more groups,
hold down the Ctrl key, and select the metrics or
properties that you want to remove.
in the list.
VMware, Inc. 834

Table 5-14. Metric Chart Selector (continued)

Option Description
Time Range Filters the metrics to show only the ones that have
received data in the selected time range.
Metric list Double-click a metric to populate the chart window. To

populate the chart window with a separate chart for each
of the metrics in the group, double-click a metric group.
To visualize the specific metric data over time, and compare the results for different metrics,
select different combinations of options.
Table 5-15. Metric Chart Toolbar

Option Description
Split Charts Displays each metric in a separate chart.
Stacked Chart Consolidates all charts into one chart. This chart is
useful for seeing how the total or sum of the metric
values vary over time. To view the stacked chart,
ensure that the split chart option is turned off.
Y Axis Shows or hides the Y-axis scale.
Metric Chart Shows or hides the line that connects the data points
on the chart.
Trend Line Shows or hides the line and data points that
represents the metric trend. The trend line filters out
metric noise along the timeline by plotting each data
point relative to the average of its adjoining data
points.
Dynamic Thresholds Shows or hides the calculated dynamic threshold

values for a 24-hour period.
Show Entire Period Dynamic Thresholds Shows or hides dynamic thresholds for the entire
time period of the graph.
Anomalies Shows or hides anomalies. Time periods when the

metric violates a threshold are shaded. Anomalies
are generated when a metric crosses a dynamic or
static threshold, either above or below.
Show Data Point Tips Shows or hides the data point tooltips when you
hover the mouse over a data point in the chart.
Zoom All Charts Resizes all the charts that are open in the chart pane
based on the area captured when you use the range
selector.
You can switch between this option and Zoom the
View.
Zoom the View Resizes the current chart when you use the range
selector.
Pan When you are in zoom mode, allows you to drag the
enlarged section of the chart so that you can view
higher or lower, earlier or later values for the metric.
VMware, Inc. 835

Table 5-15. Metric Chart Toolbar (continued)

Option Description
Show Data Values Enables the data point tooltips if you switched to a
zoom or pan option. Show Data Point Tips must be
enabled.
Refresh Charts Reloads the charts with current data.
Date Controls Opens the date selector.

Use the date selector to limit the data that appears in
each chart to the time period you are examining.
Generate Dashboard Saves the current charts as a dashboard.
Remove All Removes all the charts from the chart pane, allowing
to you begin constructing a new set of charts.
Manage individual charts with the toolbar options.
Table 5-16. Individual Metric Charts Toolbar

Option Description
Navigation If an adapter includes the ability to link to another

button to access a link to the application.
Correlation Runs metric correlation using the following options:

All self-metrics: Runs metric correlation on all metrics for
the same object, to find metrics of similar, or opposite
behavioral change for the same time period.
Selected metric of all peers: Runs metric correlation on the
same metrics for all peer objects, to find the same metrics
with behavioral changes within peer objects. Peer objects
are the direct child objects of the parent for the selected
objects. The child objects have the same object type.
Note The correlation results only appears if there are at

least 11 data points and the time range is within the three
months period to run the metric correlation.
After you run the correlation, the results are displayed in

the Correlation window. By default, only the first 10 results
for correlated metrics are displayed. To view the full list,
click Show More.
You can zoom in to view the correlated metrics and also
pin them so that they appear in the preview section of the
All Metrics tab.
Note During the correlation process, some metrics are left

out. For example, the badge and vRealize Operations
Manager generated metrics. By default, the instanced
metrics are omitted, except those in the Aggregate of all
instances group.
Save a Snapshot Creates a PNG file of the current chart. The image is the
size that appears on you screen.
VMware, Inc. 836

Table 5-16. Individual Metric Charts Toolbar (continued)

Option Description
Save a Full Screen Snapshot Downloads the current graph image as a full-page PNG file,
which you can display or save.
Download comma-separated data Creates a CSV file that includes the data in the current
chart.
Scales You can choose a scale for a stacked chart.

n Select Linear to view a chart in which the Y axis scale
increases in a linear manner. For example, the Y axis
can have ranges from 0 to 100, 100 to 200, 200 to
300, and so on.
n Select Logarithmic to view a chart in which the Y axis
scale increases in a logarithmic manner. For example,
the Y axis can have ranges from 10 to 20, 20 to 300,
300 to 4000, and so on. This scale gives a better
visibility of minimum and maximum values in the chart
when you have a large range of metric values.
Note If you select a logarithmic scale, the chart does

not display data points for metric values less than or
equal to 0, which leads to gaps in the graph.
n Select Combined to view overlapping graphs for the
metrics. The chart uses individual scales for each graph
instead of using a relative scale, and displays a
combined view of the graphs.
n Select Combined by Unit to view a chart that groups
the graphs for similar metric units together. The chart
uses a common scale for the combined graphs.
Move Down Moves the chart down one position.
Move Up Moves the chart up one position.
Vertical resize Resizes the height of a graph in the chart.
Remove icon next to each metric name in a stacked chart Removes the graph for the metric from the chart.
Capacity Tab Overview

Use the Capacity tab to assess workload status and resource contention in the selected object.
You can determine time, capacity and VM remaining until CPU, memory, or storage resources run
out. With robust capacity planning and optimization, you can manage your production capacity
effectively as your organization addresses changing requirements.
VMware, Inc. 837

Capacity Tab
The Capacity tab provides Time Remaining and Capacity Remaining data for the selected object.
Virtual Machine Remaining data is available for Clusters, Datacenters, CDC, and VC based on the
average profile, or when you enable one or more custom profiles in the policy.
Where You Find the Capacity Tab

inventory object. The Object details screen appears. Click the Capacity tab.
n In the menu, select Alerts to display the All Alerts screen. Click an alert to show the alert
details on the right, then click View Additional Metrics to see more information about the
alert and the object that triggered the alert. Click the Capacity tab.
Understanding the Capacity Tab

For the selected object, the Capacity tab lists two panes with the Time Remaining and Capacity
information. These panes display the value of the resources remaining till they run out.
Below the Time Remaining and Capacity panes, the time and capacity utilization metric for CPU,
memory, and disk space are displayed in three panes. By default, the most constrained resource
is selected. Click CPU, Memory, or Disk Space to change the views to these resources. These
panes display the resource information based on the Demand model (default) or Allocation
model (if configured).
Time Remaining Pane
When you select the Time Remaining pane and click one of the resource types, the utilization
graph displays the historical value of the utilization metric and its forecast plotted against
time, projecting how swiftly resource utilization is approaching the usable capacity.
Capacity Pane
The Capacity Remaining pane indicates the unused capacity of your virtual environment to
accommodate new virtual machines. vRealize Operations Manager calculates the Capacity
Remaining as a percentage of the remaining capacity, compared to the total. Capacity
Remaining is calculated as the utilization metric forecast 3 days from now subtracted from the
Usable Capacity. vRealize Operations Manager calculates the average profile and always
computes the virtual machine remaining number based on the average profile. vRealize
Operations Manager calculates virtual machine remaining numbers when you enable one or
more custom profiles from the policy. The overall virtual machine remaining is based on the
most constrained profile.
When you select Capacity and click one of the resource types, a bar chart and a table of
values based on the Demand and Allocation model (if configured) appears. The bar chart
displays total usable resource, the percentage used, and the percentage remaining based on
the Demand and Allocation models (if configured).
VMware, Inc. 838

The table displays the following information for each resource type:
n Total: The total usable capacity for each resource type based on the Demand model or
Allocation model (if configured). The difference in Total capacity and Usable capacity is
set in the HA (admission control) that is set in the clusters in vSphere.
n Usable: The total usable capacity for each resource type based on the Demand model or
Allocation model (if configured).
n Used: Approximate value how much utilization do you have now. Shows the forecast
value of utilization metric in 3 days from now. If Capacity Remaining is greater than zero,
then Used = Usable - Capacity Remaining.
n Recommended Size:The Total Capacity that must be available for a green level of Time
Remaining. The slider in the policy controls the Time Remaining green zone, and the
default value is 150 days.
n Remaining: The Capacity Remaining metric value and also the percentage. The value of
Capacity Remaining metric is calculated by forecasting the utilization metric 3 days from
now and subtracting it from Usable capacity.
The Capacity tab is a subset of the Capacity optimization capability. For additional details, refer
to Capacity Overview.
Using Troubleshooting Tools to Resolve Problems

The data provided in the Alerts, Symptoms, Timeline, Events, and All Metrics tabs help you
identify the root cause of a complex problem.
You can use the troubleshooting tabs individually or as part of a workflow to resolve problems.
Each of the tabs displays the collected data in a different way. Sometimes, as you are
troubleshooting problems, you move directly from the Alerts tab to the All Metrics tab. Under
other circumstances, the Timeline tab might provide the information that you need.
Symptoms Tab Overview

You can view a list of triggered symptoms for the selected object. You use the symptoms when
you are troubleshooting problems with an object.
The Symptoms tab displays all the triggered symptoms for the currently selected object. A
review of the triggered symptoms provides you with a list of the problems that the currently
selected object is experiencing. To understand which symptoms are associated with currently
generated alerts, go to the Alerts tab for the object.
As you evaluate the triggered symptoms, consider the time at which they were created and the
configuration information and trend charts, where applicable.
Symptoms Tab
The symptoms tab includes all the symptoms triggered for the current object. Use the symptom
list to identify problems with an object so that you can resolve alerts generated for the object.
VMware, Inc. 839

How the Symptoms Work

The list is the active triggered symptoms for an object, either as part of a generated alert or as a
triggered symptom that is not included in an alert. This complete symptom list is useful for
identifying problems that occur on an object but are not currently included in your alert
definitions.
Click a symptom in the list to display the symptom details. An arrow in each column heading
enables you to order the list in ascending or descending order. You can select multiple rows in
the list using Shift+click, Control+click.
Where You Find the Symptoms Tab
n In the menu, select Environment, then select a group, application, or inventory object. Click
the object to display the object's Summary tab. Click the Alerts > Symptoms tabs.
object's Summary tab. Click the Alerts > Symptoms tabs.
Table 5-17. Symptoms Data Grid

Option Description
Criticality Criticality is the level of importance of a symptom in your

environment.
The level is based on the same level assigned when the
symptom was created. The possible values include:
n Critical
n Immediate
n Warning
n Information
Symptom Name of the triggered symptom.
Status Current state of the symptom.

Possible values are Active or Inactive.
Canceled On Date and time when the symptom was canceled.
Information Information about the triggering condition for the

symptom, including the trend and current value.
The sparkline displays a range of data that includes six
hours before the symptom update time and one hour after
the update time.
VMware, Inc. 840

Table 5-18. Filters
Filtering options Limits the list of symptoms to those matching the filter you
select. Some filters are similar to data grid headings:
Symptom, Status, Criticality, Created on, Canceled on.
Triggered On Name of the object for which the symptom was generated.
the object.
Timeline Tab Overview

The timeline provides a view of the triggered symptoms, generated alerts, and events for an
object over time. Use the timeline to identify common trends over time that are contributing to
the status of objects in your environment.
The timeline provides a three-tier scrolling mechanism that you can use to move quickly through
large spans of time, or slowly and minutely through individual hours when you are focusing on a
particular period. To ensure that you have the data that you need, configure the Date Controls to
encompass the problem you are investigating.
It is not always effective to investigate a problem on an individual object by looking only at the
object. Use the parent, children, and peer options to examine the object in a broader
environmental context. This context often reveals unexpected influences or consequences for
the problem.
The timeline is a tool that provides you a graphical view of patterns. If the system triggers a
symptom and then cancels it at various intervals over time, you can compare the event to other
changes to the object or to the related objects. These changes might be the root cause of the
problem.
Events Timeline Tab

The generated alerts, triggered symptoms, and change events for the current object over time
appear on the Timeline tab. You use the timeline to identify common trends over time that are
contributing to the status of objects in your environment.
How the Events Timeline Works
The timeline view includes alerts, symptoms, and events for the selected object for the last 6
hours. To view the data for a particular time, click the timeline in one of the three tiers. Then
move your mouse to the left to see data from the past or to the right to move back to the
present.
The view is limited to approximately 50 alerts, symptoms, and events. If your timeline includes
more than this number, you can use the toolbar options to remove data from the timeline until it
contains data that you find useful for your investigation.
VMware, Inc. 841

Where You Find the Events Timeline

inventory object. Click the object to display the object's Summary tab. Click the Events >
Timeline tabs.
object's Summary tab. Click the Events > Timeline tabs.
Table 5-19. View From Menu

Option Description
Self Shows or hides events for the current object.
Peer Shows or hides events for objects like the impacted object.
Parents <options> Shows or hides events for the parent, grandparent, and so
on, objects of the current object.
Children <options> Shows or hides the events for the descendants of the
impacted object.
Table 5-20. Alert Filters

Option Description
Criticality <options> Limits the alerts to those matching the selected criticality
level. If no criticality is selected, all alerts are displayed.
Status <options> Limits the alerts in the chart to the canceled or active
alerts. If no status is selected, all alerts are displayed.
This option applies only to alerts, not to fault and change
events. Change events and active faults are always
displayed in the chart.
Alert Type <options> Select one or more alert types. The types are assigned
when the alert is defined. If no type is selected, all alerts
are displayed.
Table 5-21. Event Filters

Option Description
Dynamic Threshold Violation vRealize Operations Manager calculates dynamic

thresholds for each metric that is collected for an object
based on policies set.
Hard Threshold Violation Events that represent a hard threshold violation, based on
policies set. The system analyses the number of metrics
that are violating their hard thresholds to determine trends.
Data Availability Events reflecting datastore performance. Data availability is

the capacity to provide data on demand to users and
applications.
System Degradation Events that reflect negative impacts on system

performance.
Environment Events indicating a change in the environment.
VMware, Inc. 842

Table 5-21. Event Filters (continued)

Option Description
Change Shows or hides the change events. Change events are

changes to the object that might or might not result in an
alert.
Notification Routine notification events.
Fault Events indicating any observed behavior that differs from

the expected one.
Table 5-22. Date Controls, Data Values, Events Chart

Option Description
Date Controls Limits the data in the chart to the selected time frame.
Data Values When you click a data point, the event is highlighted in the
event data grid.
Events chart Shows the events and alerts over time by criticality, and
other data options you select in the toolbar.
Events Tab Overview

Events are changes in vRealize Operations Manager metrics that reflect changes that occurred
on managed objects because of user actions, system actions, triggered symptoms, or generated
alerts on an object. Use the Events tab to compare the occurrence of events with the generated
alerts. These comparisons can help determine if a change on your managed object contributed
to the root cause of the alert or other problems with the object.
Events can occur on any object, not just the one listed.
The following vCenter Server activities are some of the activities that generate vRealize
Operations Manager events:
n Powering a virtual machine on or off
n Creating a virtual machine
n Installing VMware Tools on the guest OS of a virtual machine
n Adding a newly configured ESX/ESXi system to a vCenter Server system
Depending on alert definitions, these events might generate alerts.
You might monitor the same virtual machines with other applications that provide information to
vRealize Operations Manager, with the adapters for those applications configured to provide
change events. In this instance, the Events tab includes certain change events that occur on the
monitored objects. These change events might provide further insight into the cause of problems
that you are investigating.
VMware, Inc. 843

Events Tab
An event is any change to an object defined by a change in the metrics for that object. You can
compare changes to an object with symptoms and other data to identify a possible cause for a
generated alert.
How the Events Tab Works
If you arrive at the Events tab from the Alerts page or tab, the Events tab opens with the timeline
centered on the moment the alert occurred for the selected object.
You can configure the chart to display various combinations of data, allowing you to identify
events that contribute to the alert you are investigating. Use the range selectors to shift the
larger time frame in the timeline, then click and drag on the graph area to zoom in on a specific
period. Click the data points on the graph to see pop-up descriptions of the various events.
Click the Actions menu to open an external application, for example, vSphere Client.
Where You Find the Events Tab
inventory object. Click the object to display the object's Summary tab. Click the Events >
Events tabs.
object's Summary tab. Click the Events > Events tabs.
n In the menu, click Alerts, then click an alert of interest to display the alert details on the right.
Click View events. The object that triggered the alert is displayed with associated events.
Table 5-23. View From

Option Description
Self Shows or hides events for the current object.
Peer Shows or hides events for objects like the impacted object.
Parents <options> Shows or hides events for the parent, grandparent, and so
on, objects of the current object.
Children <options> Shows or hides the events for the descendants of the
impacted object.
VMware, Inc. 844

Table 5-24. Alert Filters

Option Description
Criticality <options> Limits the alerts to those matching the selected criticality
level. If no criticality is selected, all alerts are displayed.
Status <options> Limits the alerts in the chart to the canceled or active
alerts. If no status is selected, all alerts are displayed.
This option applies only to alerts, not to fault and change
events. Change events and active faults are always
displayed in the chart.
Alert Type <options> Select one or more alert types. The types are assigned
when the alert is defined. If no type is selected, all alerts
are displayed.
Table 5-25. Event Filters

Option Description
Dynamic Threshold Violation vRealize Operations Manager calculates dynamic

thresholds for each metric that is collected for an object
based on policies set.
Hard Threshold Violation Events that represent a hard threshold violation, based on
policies set. The system analyses the number of metrics
that are violating their hard thresholds to determine trends.
Data Availability Events reflecting datastore performance. Data availability is

the capacity to provide data on demand to users and
applications.
System Degradation Events that reflect negative impacts on system

performance.
Environment Events indicating a change in the environment.
Change Shows or hides the change events. Change events are

changes to the object that might or might not result in an
alert.
Notification Routine notification events.
Fault Events indicating any observed behavior that differs from

the expected one.
VMware, Inc. 845

Table 5-26. Date Controls, Events Chart, Events Data Grid

Option Description
Date Controls Limits the data in the chart to the selected time frame.
Events chart Shows the events and alerts over time by criticality, and
other data options you select in the toolbar.
Events data grid Shows a list of events when you select at least one of the
following display options:
n Self
n Parent
n Child
n Peer
Creating and Using Object Details

The views and heat map details provide you with specific data about the object. You use this
information to evaluate problems in more detail. If the current views or heat maps do not provide
the information that you need, you can create one to use as a tool as you investigate your
specific problem.
Details Views Tab

The Views tab is divided into two panels. The bottom panel updates, depending on what you
select on the top panel.
In the top panel you can create, edit, delete, clone, export, and import views. The views list
depends on the object you select from the environment. Each view is associated with an object.
For example, the predefined VM inventory - Memory list view is available when you select a host.
You can limit the views list by adding a filter from the right side of the panel. Each of the provided
filter groups limits the list by the word you type. For example, if you select Description and type
my view, the listed views are all views that are applicable for the selected object and contain my
view in the description.
Table 5-27. Views List Table Columns

Column Description
Name Name of the view.
Type Type of the view. A view type is the way the collected
information for the object is presented.
Description Description of the view as it is defined when the view is

created.
Subject Object type with which a view is associated.
Owner Owner of the view is the user, who created it or edited it

for the last time.
VMware, Inc. 846

In the bottom panel of the Views tab, you can see the data of the object, calculated by a
selected view from the top panel. Say, for example, the selected object is a host and you select
Virtual Machine Configuration Summary List View. The result is a list of all the virtual machines on
that host, and their data calculated by the view.
For Trend views, you can select a parent object and see the data of the associated child objects
and metrics in the bottom panel of the Views tab.
For Distribution views, you can click on a section of the pie chart or on one of the bars in the bar
chart to view the list of objects filtered by the selected segment, in the bottom panel of the
Views tab.
Where You Find the Details View Tab

inventory object. Click the Details tab, then select the Views button.
n Alternatively, click Environment, then use the hierarchies in the left pane to locate quickly the
object you want.
Working with Heat Maps

With the vRealize Operations Manager heat map feature, you can locate trouble areas based on
the metric values for objects in your virtual infrastructure. vRealize Operations Manager uses
analytics algorithms that you can use to compare the performance of objects across the virtual
infrastructure in production using heat maps.
You can use predefined heat maps or create your own custom heat maps to compare the metric
values of objects in your virtual environment. vRealize Operations Manager has predefined heat
maps on the Details tab that you can use to compare commonly used metrics. You can use this
data to plan to reduce waste and increase capacity in the virtual infrastructure.
What a Heat Map Shows

A heat map contains rectangles of different sizes and colors, and each rectangle represents an
object in your virtual environment. The color of the rectangle represents the value of one metric,
and the size of the rectangle represents the value of another metric. For example, one heat map
shows the total memory and percentage of memory use for each virtual machine. Larger
rectangles are virtual machines with more total memory, green indicates low memory use, and
red indicates high use.
vRealize Operations Manager updates the heat maps automatically as new values are collected
for each object and metric. The colored bar below the heat map is the legend. The legend
identifies the values that the endpoints represent and the midpoint of the color range.
Heat map objects group by parent. For example, a heat map that shows virtual machine
performance, groups the virtual machines by the ESX hosts on which they run.
VMware, Inc. 847

Create a Custom Heat Map

You can define an unlimited number of custom heat maps to analyze exactly the metrics that you
need.
Procedure
2 Select an object to inspect from an inventory tree.
3 Click the Heat Maps tab under the Details tab.
4 Select the tag to use for first-level grouping of the objects from the Group By drop-down
menu.
If a selected object does not have a value for this tag, it appears in a group called Other
Groups.
5 Select the tag to use to separate the objects into subgroups from the Then By drop-down
menu.
If a selected object does not have a value for this tag, it appears in a subgroup called Other
Groups.
6 Select a Mode option.
Option Description
Instance Track all instances of a metric for an object with a separate rectangle for
each metric.
General Pick a specific instance of a metric for each object and track only that metric.
7 If you selected General mode, select the attribute to use to set the size of the rectangle for
each resource in the Size By list. Also select the attribute to use to determine the color of the
rectangle for each object in the Color By list.
Objects that have higher values for the Size By attribute have larger areas in the heat map
display. You can also select fixed-size rectangles. The color varies between the colors you set
based on the value of the Color By attribute.
In most cases, the attribute lists include only metrics that vRealize Operations Manager
generates. If you select an object type, the list shows all the attributes that are defined for
that object type.
a To track metrics only for objects of a particular kind, select the object type from the
Object Type drop-down menu.
8 If you selected Instance mode, select an attribute kind from the Attribute Kind list.
The attribute kind determines the color of the rectangle for each object.
VMware, Inc. 848

9 Configure colors for the heat map.
a Click each of the small blocks under the color bar to set the color for low, middle, and
high values.
The bar shows the color range for intermediate values. You can also set the values to
match the high and low end of the color range.
b (Optional) Enter minimum and maximum color values in the Min Value and Max Value text
boxes.
If you leave the text boxes blank, vRealize Operations Manager maps the highest and
lowest values for the Color By metric to the end colors. If you set a minimum or maximum
value, any metric at or beyond that value appears in the end color.
10 Click Save to save the configuration.
The custom heat map you created appears in the list of heat maps on the Heat Maps tab.
Find the Best or Worst Performing Objects for a Metric

You can use heat maps to find the objects with the highest or lowest values for a particular
metric.
Prerequisites
If the combination of metrics that you want to compare is not available in the list of defined heat
maps, you must define a custom heat map first. See Create a Custom Heat Map.
Procedure
1 In the menu, click Environment and select an object from an inventory tree.
All metric heat maps related to the selected resource appear in the list of predefined heat
maps.
3 In the list of heat maps, click the map to view.
The name and metrics values for each object shown on the heat map appear in the list below
the heat map.
4 Click the column header for the metric you are interested in to change the sort order, so that
the best or worst performing objects appear at the top of the column.
Compare Available Resources to Balance the Load Across the Infrastructure

A heat map can be used to compare the performance of selected metrics across the virtual
infrastructure. You can use this information to balance the load across ESX hosts and virtual
machines.
VMware, Inc. 849

Prerequisites
If the combination of metrics to compare is not available in the list of defined heat maps, you
must define a custom heat map first. See Create a Custom Heat Map.
Procedure
2 Select an object to inspect from an inventory tree.
4 In the list of heat maps, click the one to view.
The heat map of the selected metrics appears, sized and grouped according to your
selection.
5 Use the heat map to compare objects and click resources and metric values for all objects in
your virtual environment.
The list of names and metric values for all objects shown on the heat map appear in the list
below the heat map. You can click column headers to sort the list by column. If you sort the
list by a metric column, you can see the highest or lowest values for that metric on top.
6 (Optional) To see more information about an object in the heat map, click the rectangle that
represents this object or click the pop-up window for more details.
What to do next
Based on your findings, you can reorganize the objects in your virtual environment to balance the
load between ESX hosts, clusters, or datastores.
Heat Maps Tab
With the vRealize Operations Manager heat map feature, you can locate trouble areas based on
the metric values for objects in your virtual infrastructure. vRealize Operations Manager uses
analytics algorithms that you can use to compare the performance of objects across the virtual
infrastructure using heat maps.
How Heat Maps Work
You can use predefined heat maps or create your own custom heat maps to compare the metric
values of objects in your virtual environment. vRealize Operations Manager has predefined heat
maps on the Details tab that you can use to compare commonly used metrics.
Where You Find Heat Maps
inventory object. Click the Details tab, then select the Heat Maps button.
n Alternatively, click Environment, then use the hierarchies in the left pane to locate quickly the
object you want.
VMware, Inc. 850

The Heat Maps tab is divided into two panels and the heat map appears between the panels. In
the top panel you can create, edit, delete, or clone heat maps. The heap map display depends on
the object you select from the environment and the heat map you select.
Table 5-28. Heat Map List Table Columns

Column Description
Name Name of the heat map.
Group By First-level grouping of the objects in the heat map.
Color By Determines the color of the rectangle for each object.
Size By An attribute to set the size of the rectangle for each object.
Object Type Type of object.
The bottom panel updates, depending on what you select on the top panel. In the bottom panel
of the Heat Map tab, you can see the data of the object, calculated by a selected view from the
top panel. For example, if the selected object is a host, the result is a list of all the objects on that
host.
The Heat Map Display
A heat map displays rectangles of different sizes and colors, and each rectangle represents an
object in your virtual environment. The color of the rectangle represents the value of one metric,
and the size of the rectangle represents the value of another metric.
vRealize Operations Manager updates the heat maps automatically as new values are collected
for each object and metric. The colored bar below the heat map is the legend. The legend
identifies the values that the endpoints represent and the midpoint of the color range.
Click a link in the pop-up window for an object to see more details.
Heat Map Configuration Options Workspace
If no predefined heat map shows the information that you want to see, you can define a custom
heat map. You can select the objects and metrics it tracks, the colors it uses, and the end points
for its value range.
Where You Find the Heat Map Configuration Workspace
Select Environment in the left pane and select an object from an inventory tree. On the Details
tab, select Heat Maps. On the Heat Maps tab, click the plus sign to create a custom heat map.
Table 5-29. Heat Map Configuration Options

Option Description
Configurations n Add a configuration.

n Edit a custom configuration.
n Delete selected configuration.
n Clone selected configuration.
Description Meaningful description of the heat map.
Group by First-level grouping of the objects in the heat map.
Then by Subgroups of the first-level object groups in the heat map.
VMware, Inc. 851

Table 5-29. Heat Map Configuration Options (continued)

Option Description
Mode General Mode The heat map shows a colored rectangle for each
selected object. The size of the rectangle indicates
the value of one selected attribute. The color of
the rectangle indicates the value of another
selected attribute.
Instance Mode Each rectangle represents a single instance of the

selected metric for an object. A resource can have
multiple instances of the same metric. The
rectangles are all the same size. The color of the
rectangles varies based on the instance value. You
can use instance mode only if you select a single
object kind.
Size by Attribute to set the size of the rectangle for each object. Objects that have higher
values for the Size by attribute have larger areas of the heat map display. You can
also select fixed-size rectangles. In most cases, the attribute lists include only metrics
that vRealize Operations Manager generates. If you select an object kind, the list
shows all the attributes that are defined for the object type.
Color by Determines the color of the rectangle for each object.
Color Shows the color range for high, intermediate, and low values. You can set each color
and type minimum and maximum color values in the Min Value and Max Value text
boxes.
If you leave the text boxes blank, vRealize Operations Manager maps the highest and
lowest values for the Color By metric to the end colors. If you set a minimum or
maximum value, any metric at or beyond that value appears in the end color.
Using Heat Maps to Analyze Data for Capacity Risk

Planning for possible capacity risk involves analyzing data to determine how much capacity is
available and whether you make efficient use of the infrastructure.
Identify Clusters That Have Enough Space for Virtual Machines
Identify the clusters in a data center that have enough space for your next set of virtual
machines.
Procedure
1 In the left pane of vRealize Operations Manager, click Environment.
2 Select vSphere World.
3 Click the Heat Map tab under the Details tab.
4 Select the Which clusters have the most free capacity and least stress? heat map.
5 In the heat map, point to each cluster area to view the percentage of remaining capacity.
A color other than green indicates a potential problem.
6 To examine the resources for the cluster or data center, click Details in the pop-up window .
VMware, Inc. 852

What to do next
Identify the green clusters with the most capacity to store virtual machines.
Examine Abnormal Host Health
Identifying the source of a performance problem with a host involves examining its workload.
Procedure
4 Select the Which hosts currently have the most abnormal workload? heat map.
5 In the heat map, point to the cluster area to view the percentage of remaining capacity.
A color other than green indicates a potential problem.
6 Click Details for the ESX host in the pop-up window to examine the resources for the host.
What to do next
Adjust workloads to balance resources as necessary.

Identify Datastores with Enough Space for Virtual Machines
Identify the datastores that have the most space for your next set of virtual machines.
Procedure
4 Select the Which datastores have the highest disk space overcommitment and the lowest
time remaining? heat map.
5 In the heat map, point to each data center area to view the space statistics.
6 If a color other than green indicates a potential problem, click Details in the pop-up window
to investigate the disk space and disk I/O resources.
What to do next
Identify the datastores with the largest amount of available space for virtual machines.
Identify Datastores with Wasted Space
To improve the efficiency of your virtual infrastructure, identify datastores with the highest
amount of wasted space that you can reclaim.
Procedure
VMware, Inc. 853

4 Select the Which datastores have the most wasted space and total space storage? heat
map.
5 In the heat map, point to each data center area to view the waste statistics.
6 If a color other than green indicates a potential problem, click Details in the pop-up window
to investigate the disk space and disk I/O resources.
What to do next
Identify the red, orange, or yellow datastores with the highest amount of wasted space.
Identify the Virtual Machines with Resource Waste Across Datastores
Identify the virtual machines that waste resources because of idle, oversized, or powered-off
virtual machine states or because of snapshots.
Procedure
4 Select the For each datastore, which VMs have the most wasted disk space? heat map.
5 In the heat map, point to each virtual machine to view the waste statistics.
6 If a color other than green indicates a potential problem, click Details for the virtual machine
in the pop-up window and investigate the disk space and I/O resources.
What to do next
Identify the red, orange, or yellow virtual machines with the highest amount of wasted space.
Workload Tab
Workload metrics measure an object's demand for resources versus the actual capacity that the
object can access. Use Workload values as an investigative tool when you are researching
capacity constraints or evaluating the general state of objects in your environment.
Object Workload
The Workload tab present data about a single object as follows:
n The Business Week Workload - this measure reflects the system's calculation of how much
capacity an object demands over a time period. The analysis compares an object's overall
average workload against its capacity for a six-week period, hour by hour. Results are color-
coded to show different demand levels. See the color key that follows these descriptions.
n Workload Breakdown - Data is given for the individual resources of the workload, for
example, CPU and memory. The values are recalculated every five minutes.
VMware, Inc. 854

Custom Group Workload

The Workload tab presents information for a custom group, for example vSphere World,
differently from how it presents object data:
n Current Workload Breakdown - the system presents workload constraints in several formats:
pie chart, badges, bar chart, and grid. See the color key that follows these descriptions.
Table 5-30. Custom Workload Breakdown

Format Content
Pie Chart Each slice of the pie represents the percentage of total workload being occupied by objects
in a given state: normal, warning, critical, and so on. Point to a slice to make the percentage
appear as a tool tip.
Badges Each colored badge represents a state and includes the number of objects in a given state,
for example, immediate (attention needed). You can toggle the data between the number of
objects in a given state and the percentage of objects in a given state. A caption notes the
total number of objects in the group.
Bar chart A visual presentation of the percentage of all objects experiencing workload issues during
that past four weeks.
Grid All objects in the group are listed by name, object type, current level of criticality, and general
issue description. You can click any object name to view the details for that object, including
its Object Workload details.
Object State Color Key

Table 5-31. Object Workload States
Badge Color Description User Action
Workload on the object is not excessive. No attention required.
Object is experiencing some high-resource Check and take appropriate action.

workloads.
Workload on the object is approaching its Check and take appropriate action as soon
capacity in at least one area. as possible.
Workload on the object is at or over its capacity Act immediately to avoid or correct
in one or more areas. problems.
No data is available.
Object is offline.
Here is a list of metrics by which the data in the Workload Tab is represented, for all interested
object types.
VMware, Inc. 855

Table 5-32. vCenter Server

Data Metric Name
CPU-Capacity CPU|Total Capacity
CPU-Demand CPU|Demand Without Overhead
CPU-Usage CPU|VM CPU usage
CPU-Reserved CPU|Reserved Capacity
CPU-Overhead CPU|Overhead
Memory-Capacity Memory|Total Capacity
Memory-Demand Memory|Machine Demand
Memory-Usage Memory|Host Usage
Memory-Reserved Memory|Reserved Capacity
Memory-Overhead Memory|ESX System Usage
Memory-Entitlement Memory|Usable Capacity
Table 5-33. Datacenter

Data Metric Name
CPU-Entitlement CPU|Usable Capacity
Table 5-34. Cluster Compute Resource

Data Metric Name
CPU-Entitlement CPU|Usable Capacity
VMware, Inc. 856

Table 5-34. Cluster Compute Resource (continued)

Data Metric Name
Table 5-35. Host System

Data Metric Name
Table 5-36. Virtual Machine

Data Metric Name
CPU-Demand CPU|Demand
CPU-Usage CPU|Usage
CPU-Limit CPU|Effective limit
Memory-Demand Memory|Utilization
Memory-Usage Memory|Guest Usage
Memory-Reserved Memory|Reservation Used
Memory-Limit Memory|Effective limit
VMware, Inc. 857

Table 5-37. Resource Pool

Data Metric Name
CPU-Demand CPU|Usage
CPU-Usage CPU|Usage
CPU-Reserved CPU|Reservation Used
Memory-Demand Memory|Guest Demand
Memory-Usage Memory|Consumed
Memory-Reserved Memory|Reservation Used
Examining Relationships in Your Environment

Most objects in an environment are related to other objects in that environment. The
Environment tab shows how objects in your environment are related. You use this display to
troubleshoot problems that might not be about the object that you originally chose to examine.
For example, a problem alert on a host might be because a virtual machine related to the host
lacks capacity.
Environment Tab
When you select an object from the inventory of your environment and display the Object Details
screen, you can display an overview of the related objects by clicking the Environment tab. The
tab shows all the objects in your environment that are related to the selected object, with a
status badge for each object. Use the Environment tab to identify related objects in your
environment with health, risk, or efficiency problems.
Example: Use the Environment Tab to Find Problems

Suppose that you are trying to investigate the reason for slow performance in the environment.
You can select key objects such as host systems to see if any related objects such as virtual
machines indicate problems.
Procedure
1 In the menu, click Environment, then click vSphere Hosts and Clusters in the left pane and
select the vSphere World object.
2 Select the Environment tab.
The system displays health badges for all objects in the vSphere World.
3 Click each of the host system badges.
The health badge of the virtual machines that belong to the host are highlighted. A host that
displays a good health badge, may have virtual machines that display a warning status.
VMware, Inc. 858

What to do next
Now you can investigate the reason for the problem. For example, once it is determined whether
the problem is chronic or temporary, you can decide how to address it. See Using
Troubleshooting Tools to Resolve Problems.
Environment Objects Tab

vRealize Operations Manager collects data for all objects in your environment. You can compare
the status of an object with the status of all related objects to determine the possible cause for a
problem in your environment.
How the Environment Objects Tab Works
When you select an object in your inventory, vRealize Operations Manager highlights badges for
the object and all its related objects. Point to a badge to display current key conditions for an
object.
Where You Find the Environment Objects Tab
n In the menu, click Environment, then click a group, custom data center, application, or
inventory object to display the Object Summary screen. Click the Environment tab.
n Alternatively, click Environment, then use the hierarchies in the left pane to click down to the
object you want. Click the object to display the Object Summary screen, then click the
Environment tab.
Table 5-38. Environment Objects Overview Options

Option Description
Badge Displays the selected badge with the color appropriate to

the state of the badge.
Status All statuses appear by default. Select a status to toggle off

the display of badges.
Power State Options Toggle on to display badges for objects in the On, Off,
Standby, or Unknown power states. Selections are additive.
For example, you can display objects in both the on and off
states. Actions depend on the power state of the object.
Use the display to help determine why an action for an
object might not be available. See List of vRealize
Operations Manager Actions.
Sort Changes the order in which the objects are listed.

Alphabetical sort is by object name.
User Scenario: Investigate the Root Cause of a Problem by Using the

Troubleshooting Tab Options
One of your customers reports poor performance for a virtual machine, including slowness and
fails. This scenario provides one way that you can use vRealize Operations Manager to
investigate the problem based on information available in the Troubleshooting tabs.
VMware, Inc. 859

As a virtual infrastructure administrator, you respond to a help ticket in which one of your
customers reports problems with a virtual machine, sales-10-dk. The reported conditions are poor
application performance, including slow load times and slow boot, some applications are taking
longer and longer to load, and files are taking longer to save. Today applications started to fail
and an update failed to install.
When you look at the Alerts tab for the virtual machine, you see an alert for chronic high
memory workload leading to memory stress. The triggered symptoms indicate memory stress
and the recommendation is to add more memory.
Based on experience, you are not convinced that this alert indicates the root cause, so you
review the Capacity tab. The Capacity tab indicates memory and disk space problems, and Time
Remaining, which has 0 days remaining for memory and disk space.
From this initial review, you know that problems exist in addition to the memory alert, so you use
the Events tabs to do a more thorough investigation.
Review the Triggered Symptoms When You Troubleshoot a Virtual Machine

Problem
As a virtual infrastructure administrator, you respond to customer complaints and alerts, and
identify problems that occur on the objects in your environment. You use the information on the
Symptoms tab to help determine whether the triggered symptoms indicate conditions that
contribute to the reported or identified problem.
You must research a problem of poor performance on one of your virtual machines, as reported
by one of your customers. When you view the Alerts tab for the virtual machine, the only alert
that appears is named Virtual Machine is Violating Risk Profile 1 in vSphere Hardening
Guide.
When you reviewed the Capacity tab for the virtual machine, you identified that problems were
occurring with memory and disk space. Now, you focus your attention to the triggered
symptoms on the virtual machine.
The following method of using the Symptoms tab to evaluate problems is provided as an
example for using vRealize Operations Manager, and is not definitive. Your troubleshooting skills
and your knowledge of the particular aspects of your environment determine which methods
work for you.
Procedure
1 In the menu, click Dashboards, then click Troubleshoot a VM in the left pane.
2 Search for a virtual machine to troubleshoot.
In this example, the virtual machine name is named sales-10-dk.
3 With the virtual machine selected, click the Alerts tab, and click the Symptoms tab.
VMware, Inc. 860

4 Review and evaluate the triggered symptoms.
Symptom Are any of the triggered symptoms related to the critical states you see for memory or disk space?
Status Are the symptoms active or inactive? Even inactive symptoms can provide information about the past
state of the object. To add any inactive symptoms, click Status: Active on the toolbar to remove the
filter.
Created On When did the symptoms trigger? How does the time of the triggered symptom compare with the other
symptoms?
Information Can you identify a correlation between the triggered symptoms and the state of the Time Remaining
and Capacity Remaining badges?
Results
From your review, you determine that some of the triggered symptoms are associated with
compliance alerts for the virtual machine as defined in the vSphere Hardening Guide. The violated
symptoms triggered for the alert named vSphere Hardening Guide, which is one of several
compliance risk profiles provided with vRealize Operations Manager.
The following symptoms triggered in the compliance alert named Virtual Machine is
Violating Risk Profile 1 in vSphere Hardening Guide:
n Independent nonpersistent disks are being used
n Autologon feature is enabled
n Copy/paste operations are enabled
n Users and processes without privileges can remove, connect and modify devices
n Guests can receive host information
Other symptoms also triggered, which are related to memory and time remaining.
n Guest file system overall disk space usage reaching critical limit
n Virtual machine disk space time remaining is low
n Virtual machine CPU time remaining is low
n Guest partition disk space usage
n Virtual machine memory time remaining is low
What to do next
Review the symptoms for the object on a timeline. See Compare Symptoms on a Timeline When
You Troubleshoot a Virtual Machine Problem.

guides.html.
VMware, Inc. 861

Compare Symptoms on a Timeline When You Troubleshoot a Virtual Machine

Problem
Looking at the triggered symptoms for an object over time enables you to compare triggered
symptoms, alerts, and events when you are troubleshooting problems with objects in your
environment. The Timeline tab in vRealize Operations Manager provides a visual chart on which
to see triggered symptoms that you can use to investigate problems in your environment.
After you identify the following symptoms as possible indicators of the root cause of the
reported performance problems on the sales-10-dk virtual machine, you compare them to each
other over time. Look for unusual or common patterns.
n Guest file system overall disk space use reaching critical limit.
n Virtual machine disk space time remaining low.
n Virtual machine CPU time remaining low.
n Guest partition disk space use.
n Virtual machine memory time remaining is low.
The following method of evaluating problems using the Timeline tab is provided as an example
for using vRealize Operations Manager and only one method. Your troubleshooting skills and
your knowledge of the specifics of your environment determine which methods work for you.
Prerequisites
Review the triggered object symptoms. See Review the Triggered Symptoms When You
Troubleshoot a Virtual Machine Problem.
Procedure
1 Enter the name of the virtual machine in the Search text box on the main title bar.
2 Click the Events tab and click the Timeline tab.
3 On the Timeline toolbar, click Date Controls and select a time that is on or before the
reference symptoms were triggered.
The default time range is the last 6 hours. For a broader view of the virtual machine over
time, configure a range that includes triggered symptoms and generated alerts.
4 To view the point at which the symptoms were triggered and to identify which line represents
which symptom, drag the timeline week, day, or hour section left and right across the page.
5 Click Event Filters and select all the event types.
Consider whether events correspond to triggered symptoms or generated alerts.
6 In the Related Hierarchies list in the upper left pane, click vSphere Hosts and Clusters.
The available ancestors and descendant objects depend on the selected hierarchy.
VMware, Inc. 862

7 To see if the host is experiencing a contributing problems, click View From and select Host
System under Parent.
Consider whether the host has symptoms, alerts, or events that provide you with more
information about memory or disk space problems.
Results
Comparing virtual machine symptoms to host symptoms, and looking at the symptoms over time
indicates the following trends:
n The host resource use, host disk use, and host CPU use symptoms are triggered for about 10
minutes approximately every 4 hours.
n The virtual machine guest-file system out-of-space symptom is triggered and canceled over
time. Sometimes the symptom is active for an hour and canceled. Sometimes it is active for
two hours. But no more than 30 minutes occur between cancellation and the next triggering
of the symptom.
What to do next
Look at events in the context of the badges and alerts. See Identify Influential Events When You
Troubleshoot a Virtual Machine Problem.
Identify Influential Events When You Troubleshoot a Virtual Machine Problem

Events are changes to objects in your environment that are based on changes to metrics,
properties, or information about the object. Examining the events for the problematic virtual
machine in the context of alerts can provide visual clues to the root cause of a problem.
As a virtual infrastructure administrator investigating a reported performance problem with a

virtual machine, you compared symptoms on the timeline. You identified odd behavior related to
a guest file system that you want to examine in the context of other metrics. This investigation
can determine whether you find the root cause of the problem.
The following method of evaluating problems using the Events tab is provided as an example for
using vRealize Operations Manager and is not definitive. Your troubleshooting skills and your
Prerequisites
Examine triggered symptoms, alerts, and events over time. See Compare Symptoms on a
Timeline When You Troubleshoot a Virtual Machine Problem.
Procedure
1 Enter the name of the virtual machine in the Search text box, on the main title bar.
2 Click the Events tab and select the Events button.
VMware, Inc. 863

3 On the Events toolbar, click Date Controls and select a time that is on or before the
symptoms were triggered.
4 Click Event Filters and select all the event types.
Consider whether any changes correspond to other events.
5 Click View From > Parent > Select All and click through the alerts in the timeline to review
events.
Consider whether any of the events, which are listed in the data grid below the chart,
correspond to problems with the host that might contribute to the reported problem.
6 Click View From > Child > Select All and click through the alerts to review the events.
Consider whether any of the events show problems with the datastore.
Results
Your evaluation shows no particular correlation between the workload and the time at which the
guest file system out-of-space symptom was triggered each time.
Running Actions from vRealize Operations Manager

The actions available in vRealize Operations Manager allow you to modify the state or
configuration of selected objects in vCenter Server from vRealize Operations Manager. For
example, you might need to modify the configuration of an object to address a problematic
resource issue or to redistribute resources to optimize your virtual infrastructure.
The most common use of the actions is to solve problems. You can run them as part of your
troubleshooting procedures or add them as a resolution recommendation for alerts.
When you grant a user access to actions in vRealize Operations Manager, that user can take the
granted action on any object that vRealize Operations Manager manages.
When you are troubleshooting problems, you can run the actions from the center pane Actions
menu. Alternatively, you can run them from the toolbar on list views that contain the supported
objects.
When an alert is triggered, and you determine that the suggested action is the most likely way to
resolve the problem, you can run the action on one or more objects.
Run Actions from Toolbars in vRealize Operations Manager

When you run actions in vRealize Operations Manager, you change the state of vCenter Server
objects. You run one or more actions when you encounter objects where the configuration or
state of the object is affecting your environment. These actions allow you to reclaim wasted
space, adjust memory, or conserve resources.
VMware, Inc. 864

This procedure for running actions is based on the vRealize Operations Manager Actions menus
and is commonly used when you are troubleshooting problems. The available actions depend on
the type of objects with which you are working. You can also run actions as alert
recommendations.
Prerequisites
n Verify that the vCenter Adapter is configured to run actions for each vCenter Server instance.
See Configure a vCenter Adapter Instance in vRealize Operations Manager.
n Ensure that you understand how to use the power-off-allowed option if you are running Set
CPU Count, Set Memory, and Set CPU Count and Memory actions. See Working with Actions
That Use Power Off Allowed.
Procedure
1 Select the object in the Environment page inventory trees or select one or more objects it in a
list view.
2 Click Actions on the main toolbar or in an embedded view.
3 Select one of the actions.
If you are working with a virtual machine, only the virtual machine is included in the dialog
box. If you are working with clusters, hosts, or datastores, the dialog box that appears
includes all objects.
4 To run the action on the object, select the check box and click OK.
The action runs and a dialog box appears that displays the task ID.
5 To view the status of the job and verify that the job finished, click Recent Tasks or click OK to
close the dialog box.
The Recent Tasks list appears, which includes the task you just started.
What to do next
To verify that the job completed, click Environment in the menu and click History >Recent Tasks.
Find the task name or task ID in the list and verify that the status is finished. See Monitor Recent
Task Status.
Rebalance Container Action

When the workload in your environment becomes imbalanced, you can move the workload
across your objects to rebalance the overall workload. The container for the rebalance action can
be a data center or a custom data center, and the objects that are moved are the virtual
machines in the suggested list provided by the action.
DRS Must be Enabled on Clusters

Your vCenter Server instance must have a cluster that passes a DRS-enabled check for the
Rebalance Container action to appear in the Actions drop-down menu.
VMware, Inc. 865

To get the Rebalance Container action from a custom data center or data center, and the related
alerts, you must have the following:
n A vCenter Adapter configured with the actions enabled for each vCenter Server instance
n A vCenter Server instance with at least one cluster that is DRS-enabled.
If your cluster does not have DRS fully automated, the Rebalance Container action notifies you
that one or more clusters under the selected container do not have DRS set to fully automated.
To ensure that the Rebalance Container action is available in your environment, you must add
DRS. Then, wait one collection cycle for the Rebalance Container action to appear.
You Must Have Access to All Objects in the Container

If you have access to all objects in a cluster, data center, or custom data center, you can run the
Rebalance Container action to move virtual machines to other clusters. When you do not have
access to all of the objects in the container, the Rebalance Container action is not available.
How the Rebalance Container Action Works

If two data centers are experiencing extreme differences in workload - one high and one low -
use the Rebalance Container action to balance the workload across those objects. For example, if
the CPU demand on a host in one data center exceeds its available CPU capacity, critical
pressure occurs on the host. To identify the cause of stress, monitor the CPU demand. Some
virtual machines on each host might be experiencing high CPU demand, whereas others might be
experiencing a low demand.
The Rebalance Container action moves all affected objects in the suggested list provided by the
action to balance the workload. If you do not want to act on the entire set of objects to resolve
the problem with workload, you can use the Move VM action to move an individual object.
Important Do not attempt to move virtual machines that are members of a vApp, because the
vApp can become nonfunctional. Instead, add affinity rules for these virtual machines to keep
them together so that the Move VM and Rebalance Container actions will ignore them.
When workloads become imbalanced, the following alerts can trigger on data centers and
custom data centers. These alerts are disabled by default in the policies.
n Custom data center has unbalanced workload
n Data center has unbalanced workload
When the workloads on hosts in a data center or custom data center differ significantly, click
Home > Alerts and verify whether the alert triggered. For example, to verify whether the alert
triggered on a custom data center, check the alert named Custom data center has unbalanced
workload. You can click the alert to view the causes of the alert and identify the source of the
imbalance problem on the Summary tab.
VMware, Inc. 866

To display the recommendations about the objects to move so that you can rebalance the
workload, click the Rebalance Container action on the Summary tab. The recommendations
indicate that you move one or more virtual machines to another host. When you click OK, a pop-
up message provides a link to track the status of the action in Recent Tasks.
The action moves the virtual machines identified in the recommendation to the host machine that
has a low workload or stress. You can view the status of the action in the list of recent tasks in
Administration > Recent Tasks. You can also use the vSphere Web Client to view the status of
the action and the performance for the host.
After the action runs and vRealize Operations Manager performs several collection cycles, view
the workload on the data center to confirm that the workload was rebalanced and that the alert
is gone.
Where You Run the Action

You can run the Rebalance Container action from the Actions menu for a data center or custom
data center, or you can provide it as a suggested action on an alert.
For the supported objects and object levels, this action is available in the following locations in
vRealize Operations Manager:
n On the toolbar when you click Environment in the menu, select an object, click the Details
tab, click Views, and select a view of type List.
n On the toolbar when you click Environment in the menu, select an object, click the
Environment tab, and select an object in the list view.
n In the Inventory list when you click Administration in the menu, click Inventory, then click the
List tab, and select an object in the list.
n In configured alert recommendations.
n In the Object List and Topology Graph dashboard widgets.
Action Recommendations
Review the following information about the hosts and virtual machines to ensure that you are
submitting the action for the correct objects.
Option Description
Virtual Machine Name of the virtual machine on the host that is experiencing an excessive workload.
Source Cluster Name of the cluster on which the virtual machine is running.
Datastores Datastore associated with the virtual machine.
Destination Cluster Cluster where the virtual machine is to be moved. DRS selects the host automatically.
Reason Describes the action to be taken and the reason why the move is suggested. For example, the
recommendation is to move part of the workload on the cluster to another cluster to reduce the
imbalance in CPU demand.
Parent vCenter Identifies the vCenter vCenter Serveradapter associated with the affected cluster.
After you click OK, the next dialog box provides the task ID and a link to the task list.
VMware, Inc. 867

Table 5-39. Task ID Dialog Box

Option Description
Recent Tasks To view the status of the job and verify that the job
finished, click Recent Tasks.
OK To close the dialog box without further action, click OK.
Delete Idle VM Action

The Delete Idle VM action in vRealize Operations Manager removes from your vCenter Server
instances those selected virtual machines that are in an idle state. Use this action to reclaim
redundant resources.
How the Action Works

The Delete Idle VM action removes from your vCenter Server instances those virtual machines
that are powered on, but that are in an idle state.
n Embedded just below the top menu.
tab and click Views.
n In the Inventory list click Administration in the menu, then click Inventory, then click the List
tab, and select an object in the list.
Action Menu Items

Review the following information about the virtual machines to ensure that you are submitting
the action for the correct objects.
Menu Items Description
Name Name of the virtual machine as it appears in the environment inventory.
Host Name of the host on which the virtual machine is running.
Parent vCenter Parent vCenter Server instance where the virtual machine resides.
After you click Begin Action, the next dialog box provides the task ID and a link to the task list.
VMware, Inc. 868


Option Description
Set DRS Automation Action

You can monitor and configure the vSphere Distributed Resource Scheduler (DRS) automation
rules from vRealize Operations Manager. DRS monitors and allocates the resources in your
environment, and balances the computing capacity across your hosts and virtual machines.

The Set DRS Automation action monitors and configures DRS automation rules. With the Set DRS
Automation action, you can enable and disable DRS.
If vRealize Automation manages any of the virtual machines in your environment, the Set DRS
Automation action is not available for that object.

Action Menu Items

To ensure that you are submitting the correct action for the correct objects, review the following
information about the clusters.
Name Name of the cluster in the vCenter Server instance.
Automation Level Level of DRS automation. When DRS is fully automated on the selected cluster, you can run the Set
DRS Automation action.
VMware, Inc. 869

Migration Threshold Recommendations for the migration level of virtual machines. Migration thresholds are based on
DRS priority levels, and are computed based on the workload imbalance metric for the cluster.
Parent vCenter Parent vCenter Server instance where the cluster resides.
After you click Begin Action, the next dialog box provides the task ID and a link to the task list.

Option Description
Move Virtual Machine Action

You can use the Move VM action to move virtual machines from one host and datastore to
another host and datastore to balance the workload in your environment.

When you initiate this action, the Move VM wizard opens and scopes the possible destinations.
You select the destination host and datastore from the list of available destinations.
To see all destinations, you must have view access to the following object types:
n Scope object, which includes a vCenter Server, data center, custom data center, or cluster.
n Host in the scope object.
n Datastore in the host.
The destinations include combinations of objects for the move, such as a specific host and
datastore, or a different host with the same datastore. You select one of the available
combinations. If your environment includes many destination objects, such as many hosts or
datastores, enter text in the filter text box to search for specific destination objects.
vRealize Operations Manager uses vSphere DRS rules that you define in vCenter Server to help
determine good placement decisions for your virtual machines in the move action. The Affinity
Rules column indicates whether those rules are violated by the Move VM action.
Important Do not attempt to move virtual machines that are members of a vApp, because the
vApp can become nonfunctional. Instead, add affinity rules for these virtual machines to keep
them together so that the Move VM and Rebalance Container actions will ignore them.
To initiate the action, you click the Begin Action button.
When you finish the wizard, vRealize Operations Manager displays a dialog box to indicate that
the action has started. To track the status of the action, click the link in the dialog box and view
the state of the action in Administration > Recent Tasks.
VMware, Inc. 870

Moving Virtual Machines is Not Allowed Across Data Centers

When you attempt to use the Move VM action to move a virtual machine across data centers,
vRealize Operations Manager must be able to identify the matching network and storage objects
for the destination data center. Network objects include VMware virtual switches and distributed
virtual switches. Storage objects include datastores and datastore clusters.
Moving a virtual machine across data centers requires vRealize Operations Manager to move the
virtual machine files and change the virtual machine network configuration. vRealize Operations
Manager does not currently move the virtual machine files across datastores, nor does it change
the virtual machine network configuration. As a result, vRealize Operations Manager does not
allow you to move virtual machines across data centers.
When you use the Move VM action, be aware of the following behavior:
n If you select a single virtual machine, vRealize Operations Manager displays the data center
where the virtual machine resides.
n If you select multiple virtual machines, but those virtual machines do not share a common
data center, the Move VM action does not display the data centers, and the Move VM action
does not appear in the actions menu.

Action Options
Option Description
Priority Indicates the priority of the proposed move destination. When the action is automated, the
proposed destination with priority of 1 is automatically selected.
Destination Host Name of the host to which the virtual machine will be moved.
Current CPU Amount of CPU in GHz available on the host.

Workload
VMware, Inc. 871

Option Description
Current Memory Amount of memory in GB available on the host.

Workload
Destination Datastore Datastore to which the virtual machines storage will be moved.
Current Disk Space Amount of disk space available on the datastore.

Workload
Will it fit Calculated estimation of whether the virtual machine fits on the selected destination.
VM Power Off When set to No, the action does not power off the virtual machine before the move. When set to
Required Yes, the action powers off the virtual machine before the move takes place, and powers on the
virtual machine after the move is complete. If VMware Tools is installed, a guest OS shutdown is
used to power off the virtual machine.
Affinity Rules Indicates whether vSphere DRS rules exist, as defined in vCenter Server. For example, a rule
might exist to keep virtual machines together, and another rule might exist to separate virtual
machines.
This column indicates the following status.
n Empty. vSphere DRS rules are not defined.
n Green check mark. The move of virtual machines does not violate affinity rules.
n Red circle with bar. The move of virtual machines does break affinity rules. If you choose to
break the affinity rules, you must resolve any problems manually.
Affinity Rule Details Identifies the virtual machine and the vSphere DRS rule name as defined in vCenter Server.

Option Description
Power Off Virtual Machine Action

The Power Off VM action in vRealize Operations Manager stops one or more selected virtual
machines that are in a powered on state. You power off a virtual machine when you are
managing resources and reclaiming wasted space.

The Power Off VM action turns off the virtual machine. If VMware Tools is installed and running,
the guest operating system is shut down before the machine is powered off. If VMware Tools is
not installed and running, the virtual machine is powered off regardless of the state of the guest
operating system. In this case, use this action only when you are powering off virtual machines
where stopping the guest operating system does not adversely affect the installed applications.
If the target virtual machine is already powered off, the recent task status reports success on the
machine, even though the state of the virtual machine did not change.
VMware, Inc. 872


Action Options
Option Description
Selected objects Check box indicates whether the action is applied to the object. To not run the action on one or
more objects, deselect the associated check boxes. This option is available when two or more
objects are selected.
Power State Indicates whether the virtual machine is powered on or powered off.
Idle VM Indicates whether the virtual machine is considered to be in the idle state based on the configured
idle virtual machine metric.
Possible values include:
n false. The virtual machine is active.
n true. The virtual machine is idle.
n unknown. vRealize Operations Manager does not have the data required to calculate the idle
metric.
Idle VM Percentage Calculated threshold of the idle virtual machine percentage based on the configured reclaimable
wasted space policy.
CPU Usage Calculated threshold of the virtual machine CPU percentage based on the metric named cpu |
Percentage usage_average.
Adapter Instance Name of the VMware Adapter as it is configured in vRealize Operations Manager. The adapter
manages the communication with the vCenter Server instance.
VMware, Inc. 873


Option Description
Shut Down Guest Operating System for Virtual Machine Action

The Shut Down Guest OS for VM action shuts down the guest operating system and powers off
the virtual machine. You shut down a virtual machine when you are managing resources and
reclaiming wasted space.

The Shut Down Guest OS for VM action checks that VMware Tools, which is required, is installed
on the target virtual machines, then shuts down the guest operating system and powers off the
virtual machine. If VMware Tools is not installed or installed but not running, the action does not
run and the job is reported as failed in Recent Tasks.
If the target virtual machine is already powered off, the recent task status reports success on the
machine, even though the state of the virtual machine did not change.

tab, and click Views.
Action Options
Review the following so you can be sure you are taking the right action.
Option Description
Selected objects Check box indicates whether the action is applied to the object. To not run the action on one or
more objects, deselect the associated check boxes. This option is available when two or more
objects are selected.
VMware, Inc. 874

Option Description
Idle VM Indicates whether the virtual machine is considered to be in the idle state based on the configured
idle virtual machine metric.
Possible values include:
n false. The virtual machine is active.
n true. The virtual machine is idle.
n unknown. vRealize Operations Manager does not have the data required to calculate the idle
metric.
Idle VM Percentage Calculated threshold of the idle virtual machine percentage based on the configured reclaimable
wasted space policy.

Option Description
Power on Virtual Machine Action

To start one or more virtual machines that are in a powered off state, use the Power On VM
action. You power on a virtual machine so that you can shift resources. For example, power on a
machine so that you can use it, run applications, or verify that actions that were run on already
powered down machines contribute to improved performance.

The Power On VM action powers on virtual machines that are powered off. The action does not
affect virtual machines that are currently powered on.
If the target virtual machine is already powered on, the task status reports success for the
machine even though the state of the virtual machine did not change.

VMware, Inc. 875

Action Options
To ensure that you are taking the right action, review the following information .
Option Description
Selected objects Check box indicates whether the action is applied to the object. To not run the action on one or more
objects, deselect the associated check boxes. This option is available when two or more objects are
selected.

Option Description
Delete Powered Off Virtual Machine Action

The Delete Powered Off VM action in vRealize Operations Manager removes selected virtual
machines that are in a powered off state from your vCenter Server instances. Use this action to
reclaim redundant resources.

The Delete Powered Off VM action removes virtual machines from the vCenter Server instances.
If the virtual machine is powered on, the action does not delete the virtual machine.

VMware, Inc. 876

n In the Inventory list when you click Administration in the menu, click Inventory , then click the
Action Options
To ensure that you are submitting the action for the right objects, review the following
information.
Option Description
Selected objects Check box indicates whether the action is applied to the object. To not run the action on one or more
objects, deselect the associated check boxes. This option is available when two or more objects are
selected.
Disk Space Amount of disk space currently consumed by the virtual machine.
Snapshot Space Amount of disk space currently consumed by the virtual machine snapshots.
Memory (MB) Amount of memory allocated to the virtual machine.
CPU Count Number of CPUs currently configured for the virtual machine.

Option Description
Set Memory for Virtual Machine Action

The Set Memory for VM action in vRealize Operations Manager is used to add or remove memory
on virtual machines. You increase the memory to address performance problems or decrease the
memory to reclaim resources.
VMware, Inc. 877


The Set Memory for VM action perform several tasks. The action determines the power state of
the target virtual machines, takes a snapshot when you request it and powers off the machine if
necessary and you request it. As well, the action changes the memory to the new value, and
returns the virtual machines their original power states.
An alternative form of the Set Memory for Virtual Machine action is available for automation. This
action can run when the virtual machine is powered on or off.
Use this version of the action if the automated action has permission to power off the virtual
machine, and hot add of memory is not enabled on the virtual machine. With hot add enabled,
you can add memory, but you cannot remove it.
This version of the action would be required if a virtual machine is powered on and the amount of
memory must be reduced.
This version of the action has the Power Off Allowed flag set to true. You can select this Power
Off Allowed version of the action when you create or edit alerts and associate the alert with a
recommendation. When the Power Off Allowed version of this action is automated, you do not
select this version of the action.
If Hot Plug is enabled on the virtual machines, then power off is not required. If power off is
required and VMware Tools is installed, then the virtual machines are shut down before they are
powered off.

Action Options
information.
VMware, Inc. 878

Option Description
Selected Check box indicates whether the action is applied to the object. To not run the action on one or more
objects objects, deselect the associated check boxes. This option is available when two or more objects are
selected.
If you modify a value, the check box is selected. The check box must be selected to enable the OK
button.
New (MB) Requested amount of memory in megabytes. The value must be a multiple of 4, and must not be less
than 4. If the value is less than 4 or is not a multiple of 4, the amount of memory does not change, and
Recent Tasks displays the action as failed.
n When the virtual machine power state is PoweredOn, the memory hot plug configuration limits of the
virtual machine are factored into the requested amount and might result in a different configured
memory than requested.
n If the memory hot plug is not enabled, the request fails unless you also select Power Off Allowed.
n If the memory hot plug is enabled, the configured memory is adjusted to be a multiple of the virtual
machine hot plug memory increment. The adjustment makes sure that the configured memory is at
least that increment more than the current virtual machine memory configuration. The adjusted
memory configuration must also be no more than the hot plug memory limit.
If the memory hot plug constraints of the virtual machine cannot be satisfied, the amount of memory
does not change, and Recent Tasks displays the action as failed unless you also select Power Off
Allowed. If Power Off Allowed is selected, the action first attempts to satisfy the memory reconfiguration
request without powering off the virtual machine. The action only powers off the virtual machine if it is
necessary to reconfigure the memory.
Current (MB) Amount of memory in megabytes that is configured on the virtual machine.
Power Off If selected, the action shuts down or powers off the virtual machine before modifying the value. If
Allowed VMware Tools is installed and running, the virtual machine is shut down. If VMware Tools is not installed
or not running, the virtual machine is powered off without regard for the state of the operating system.
In addition to whether the action shuts down or powers off a virtual machine, you must consider whether
the object is powered on and what settings are applied.
Snapshot Creates a snapshot of the virtual machine before modifying the memory. Use this option if you need a
snapshot to which you can revert the virtual machine if the action does not produce the expected results.
The name of the snapshot is supplied in the Recent Tasks messages for the action.
If the memory is changed with Memory Hot Plug enabled, then the snapshot is taken with the virtual
machine is running, which consumes more disk space.
Adapter Name of the VMware Adapter as it is configured in vRealize Operations Manager. The adapter manages
Instance the communication with the vCenter Server instance.

Option Description
VMware, Inc. 879

Set Memory Resources for Virtual Machine Action

The Set Memory Resources for VM action is used to modify the memory reservation and memory
limit on virtual machines. You modify the memory reservation and limit to manage resources in
your environment, either to reclaim unused resources or to ensure that your virtual machines
have the resources they need to run efficiently.

The Set Memory Resources for VM action determines how memory resources are allocated to
the virtual machine. The reservation value is the minimum amount of guaranteed memory
allocated for the virtual machine. The limit is the maximum amount of memory that the virtual
machine can consume.
The reservation and limit values in vCenter Server are set in megabytes. vRealize Operations
Manager calculates and reports on memory in kilobytes. When you run this action, the values are
presented in kilobytes so that you can implement recommendations from vRealize Operations
Manager.
To run the action, all options must be configured in the dialog box for the objects on which your
are running the action. If you are changing one option to a new value, but not another option,
ensure that the option that you do not want to change is configured with the current value.

Action Options
information.
VMware, Inc. 880

Option Description
selected.
button.
New Resv (KB) Amount of memory in kilobytes reserved for the virtual machine when the action is finished. The new
reservation value must be less than or equal to the new limit value unless your new limit is unlimited (-1).
The reservation supports the following possible values:
n If you set the value to 0, the virtual machine is allocated only the currently configured amount of
RAM.
n If you add or remove reserved memory, the value must be evenly divisible by 1024.
Current Resv Amount of memory in kilobytes that is configured as the guaranteed memory for the virtual machine.
(KB)
New Limit (KB) Maximum amount of memory in kilobytes that the virtual machine can consume when the action is
completed.
The limit supports the following possible values:
n If you set the value to 0, then the maximum memory is no greater than the allocated reservation
amount.
n If you set the value to -1, then the virtual machine memory is unlimited.
n It you increase or decrease the limit, the value must be evenly divisible by 1024.
Current Limit Maximum amount of memory that the virtual machine is currently allowed to consume.
(KB)
Adapter Name of the VMware Adapter as it is configured in vRealize Operations Manager. The adapter
Instance manages the communication with the vCenter Server instance.

Option Description
Set CPU Count for Virtual Machine Action

The Set CPU action modifies the number of vCPUs on a virtual machine. You increase the number
of CPUs to address performance problems or decrease the number of CPU to reclaim resources.

The Set CPU Count action shuts down or powers off the target virtual machines. If you are
decreasing the CPU count, the action is required. This action creates a snapshot if you request it,
changes the number of vCPUs based on the new CPU count you provided, and returns the virtual
machines to their original power states.
VMware, Inc. 881

An alternative form of the Set CPU Count for Virtual Machine action is available for automation.
This action can run when the virtual machine is powered on or off.
Use this version of the action if the automated action has permission to power off the virtual
machine, and hot add of memory is not enabled on the virtual machine. With hot add enabled,
you can add CPUs, but you cannot remove them.
This version of the action is required if a virtual machine is powered on and the number of CPUs
must be reduced.
This version of the action has the Power Off Allowed flag set to true. You can select this Power
Off Allowed version of the action when you create or edit alerts and associate the alert with a
recommendation. When the Power Off Allowed version of this action is automated, you do not
select this version of the action.
required and VMware Tools are installed, then the vurtual machines are shut down before they
are powered off.
Set CPU Count for a Virtual Machine

bctid=ref:video_set_cpu_count_for_vm)

Action Options
VMware, Inc. 882

Option Description
selected.
button.
New CPU Number of CPUs when the action is completed. If the value is less than 1 or a value not supported for the
virtual machine in vCenter Server, and the virtual machine is powered on and Hot Add is not enabled, the
number of CPUs does not change and Recent Tasks shows the action as failed. If the virtual machine is
powered off when you submit an unsupported value, the task reports success, but the virtual machine
will fail when you run a power on action.
The value that appears is the calculated suggested size. If the target virtual machine is new or offline, this
value is the current number of CPUs. If vRealize Operations Manager has been monitoring the virtual
machine for six or more hours, depending on your environment, the value that appears is the CPU
Recommended Size metric.
Current CPU Number of configured CPUs.
Snapshot Creates a snapshot before changing the number of CPUs. Use this option if you need a snapshot to
which you can revert the virtual machine if the action does not produce the expected results.
The name of the snapshot is supplied in the Recent Tasks messages for the action.
If the CPU is changed with CPU Hot Plug enabled, then the snapshot is taken with the virtual machine is
running, which consumes more disk space.

Option Description
Set CPU Resources for Virtual Machine Action

The Set CPU Resources for VM action is used to modify the CPU reservation and CPU limit on
virtual machines. You modify the CPU reservation and limit to manage workload demands in your
environment.
VMware, Inc. 883


The Set CPU Resources for VM action determines how CPU resources can be allocated to the
virtual machines. The reservation limit is the minimum amount of guaranteed CPU resources
allocated to the virtual machine. The limit is the maximum amount of CPU resources that the
virtual machine can consume.
To run the action, all options where you configure a value must contain a value for the objects
that you want to change. If you are changing one option to a new value, but not another option,
ensure that the option that you are not changing is configure with the current value.

Action Options
information.
Option Description
selected.
button.
New Resv Amount of CPU resources in megahertz reserved for the virtual machine when the action is finished.
(MHz) The new reservation value must be less than or equal to the new limit value unless your new limit is
unlimited (-1).
The reservation supports the following possible values:
n If you set the value to 0, the virtual machine is allocated only the configured CPU consumption level.
n If you add or removed reserved CPU consumption, supply a positive integer unless you set the
value to 0.
Current Resv Amount of CPU resources that is configured as the guaranteed CPU resources for the virtual machine.
(MHz)
VMware, Inc. 884

Option Description
New Limit Maximum amount of CPU consumption in megahertz that the virtual machine can consume when the
(MHz) action is completed.
The limit supports the following possible values:
n If you set the value to 0, the maximum CPU consumption is not greater than the allocated
reservation amount.
n If you set the value to -1, then the virtual machine CPU consumption is unlimited.
n If you add or remove CPU consumption limits, supply a positive integer, unless you set the value to
0 or -1.
Current Limit Maximum amount of CPU that the virtual machine can consume.
(MHz)

Option Description
Set CPU Count and Memory for Virtual Machine Action

The Set CPU Count and Memory for VM action is used to add or remove CPUs and memory on
virtual machines with only one power off of the virtual machines to perform the combined
actions. You modify the CPU and memory to address performance problems or to reclaim
resources.

The Set CPU Count and Memory action powers off the target virtual machines. The action also
creates a snapshot when requested and changes the number of vCPUs and memory based on
the new CPU count and memory values you provided. As well, the action returns the virtual
machines their original power states.
An alternative form of the Set CPU Count and Memory for Virtual Machine action is available for
automation. This version of the action has the Power Off Allowed flag set to true so that the
action is available for automation and can run when the virtual machine is in the powered on
state. You can select the Power Off Allowed version of the action when you create or edit alerts
and associate the alert with a recommendation. When the Power Off Allowed version of this
action is automated, you do not select this version of the action.
required and VMware Tools are installed, then the virtual machines are shut down before they
are powered off.
VMware, Inc. 885

To run the action, all options where you configure a value must contain a value for the objects
that you want to change. If you are changing one option to a new value, but not another option,
ensure that the option that you are not changing is configure with the current value.

Action Options
information.
Option Description
selected.
button.
New CPU Number of CPUs when the action is completed. If the value is less than 1 or a value not supported for the
virtual machine in vCenter Server, and the virtual machine is powered on and Hot Add is not enabled, the
number of CPUs does not change and Recent Tasks shows the action as failed. If the virtual machine is
powered off when you submit an unsupported value, the task reports success, but the virtual machine
will fail when you run a power on action.
value is the current number of CPUs. If vRealize Operations Manager has been monitoring the virtual
machine for six or more hours, depending on your environment, the value that appears is the CPU
Current CPU Number of configured CPUs.
VMware, Inc. 886

Option Description
New (MB) Amount of memory in megabytes when the action is completed. The value must be a multiple of 4, and
not less than 4. If the value is less that 4 or is not a multiple of 4, and the virtual machine is powered on
and Hot Add is not enabled, the amount of memory does not change and the Recent Tasks shows the
action as failed. If the virtual machine is powered off when you submit an unsupported value, the task
reports success, but the virtual machine fails when you run a power on action.
value is the currently configured memory. If vRealize Operations Manager has been monitoring the virtual
machine for six or more hours, depending on your environment, the value that appears is the Memory
Current (MB) Amount of memory in megabytes that is configured on the virtual machine.
Snapshot If selected, the action creates a snapshot of the virtual machine before modifying the CPU count and the
memory.
Use this option if you need a snapshot to which you can revert the virtual machine if the action does not
produce the expected results.
the communication with the vCenter Server instance.

Option Description
Delete Unused Snapshots for Virtual Machine Action

The Delete Unused Snapshots for Virtual Machines action in vRealize Operations Manager deletes
snapshots that are older than the specified age from your datastores. Deleting unused snapshots
reclaims wasted space in your environment.

The Delete Unused Snapshots for Virtual Machine action comprises two dialog boxes. The first
dialog box allows you to select the snapshot age criteria, which must be greater than one day.
The second step allows you to select the snapshots to delete, and runs the Delete Unused
Snapshots for Virtual Machine action.
VMware, Inc. 887

The number of days that you specify for each virtual machine is the age of the snapshots based
on the creation date. The Delete Unused Snapshots for Virtual Machine action retrieves the
snapshot and displays the snapshot name, space consumed, and location so that you can
evaluate the snapshots before you delete them.
When you click Begin Action, vRealize Operations Manager displays a dialog box to indicate that

n In the Inventory list when you click Administration in the menu, click Inventory , then click the
Action Options
information.
You first retrieve snapshots based on age, then select the snapshots to delete.
Table 5-52. Retrieve Snapshots

Option Description
Name Name of the virtual machine on which you are running the Delete Unused Snapshots for
VM action.
Days Old Age of the snapshots to be deleted. This action retrieves snapshots for the virtual machine
that are older than one day.
Host Name of the host with which the virtual machine is associated.
Parent vCenter Name of the VMware Adapter as it is configured in vRealize Operations Manager. The
adapter manages the communication with the vCenter Server instance.
Select the snapshots to delete.
VMware, Inc. 888

Table 5-53. Delete Snapshots

Option Description
Selected objects Check box indicates whether the action is applied to the object. To not run the action on one
or more objects, deselect the associated check boxes. This option is available when two or
more objects are selected.
VM Name Name of the virtual machine from which the snapshot was created.
Snapshot Name Name of the snapshot in the datastore.
Snapshot Space (MB) Number of megabytes consumed by the snapshot.
Snapshot Create Time Date and time when the snapshot was created.
Snapshot Age Age of the snapshot in days.
Datacenter Name Name of the data center with which the datastore is associated.
Datastore Name Name of the datastore where the snapshot is managed.
Host Name Name of the host with which the datastore is associated.

Option Description
The Delete Unused Snapshots action creates a job for the retrieve snapshots action, and a job for
the delete snapshots action.
Delete Unused Snapshots for Datastore Action

The Delete Unused Snapshots for Datastore action in vRealize Operations Manager deletes
snapshots that are older than the specified age from your datastores. Deleting unused snapshots
reclaims wasted space in your environment.

The Delete Unused Snapshots for Datastore action comprises two dialog boxes. The first dialog
box allows you to select the snapshot age criteria, which must be greater than one day. The
second step allows you to select the snapshots to delete, and runs the Delete Unused Snapshots
for Datastore action.
The number of days that you specify for each datastore is the age of the snapshots based on the
creation date. The Delete Unused Snapshots dialog box provides details regarding snapshot
name, space consumed, and location so that you can evaluate the snapshots before you delete
them.
When you click Begin Action, vRealize Operations Manager displays a dialog box to indicate that
VMware, Inc. 889


Action Options
information.
You first retrieve snapshots based on age, then select the snapshots to delete.
Table 5-55. Retrieve Snapshots

Option Description
Name Name of the datastore on which you are running the delete snapshot action.
Days Old Age of the snapshots to be deleted. This action retrieves snapshots for the datastore
that are older than one day.
Host Name of the host with which the datastore is associated.
Parent vCenter Name of the VMware Adapter as it is configured in vRealize Operations Manager. The
adapter manages the communication with the vCenter Server instance.
Select the snapshots to delete.
Table 5-56. Delete Snapshots

Option Description
Selected objects Check box indicates whether the action is applied to the object. To not run the action on one
or more objects, deselect the associated check boxes. This option is available when two or
more objects are selected.
Datastore Name Name of the datastore where the snapshot is managed.
Snapshot Name Name of the snapshot in the datastore.
Snapshot Space (MB) Number of megabytes consumed by the snapshot.
Snapshot Create Time Date and time when the snapshot was created.
Snapshot Age Age of the snapshot in days.
Datacenter Name Name of the data center with which the datastore is associated.
VMware, Inc. 890

Table 5-56. Delete Snapshots (continued)

Option Description
Host Name Name of the host with which the datastore is associated.
VM Name Name of the virtual machine from which the snapshot was created.

Option Description
The Delete Unused Snapshots action creates a job for the retrieve snapshots action, and a job for
the delete snapshots action.
Open Virtual Machine in Wavefront

The Open Virtual Machine in Wavefront action allows you to view data sent to Wavefront.

The Open Virtual Machine in Wavefront action allows you to view data in Wavefront if the VM is
configured to send data to Wavefront. The link takes you to the configured Wavefront URL.

For supported objects and object levels, this action is available from the Actions menu just below
the top menu in vRealize Operations Manager.
Troubleshoot Actions in vRealize Operations Manager

If you are missing data or cannot run actions from vRealize Operations Manager, review the
troubleshooting options.
Verify that your vCenter Adapter is configured to connect to the correct vCenter Server instance,
and configured to run actions. See Configure a vCenter Adapter Instance in vRealize Operations
Manager.
n Actions Do Not Appear on Object

An action might not appear on an object, such as a host or virtual machine, because vRealize
Automation is managing that object.
n Missing Column Data in Actions Dialog Boxes

Data is missing for one or more objects in an Actions dialog box, making it difficult to
determine if you want to run the action.
VMware, Inc. 891

n Missing Column Data in the Set Memory for VM Dialog Box

The read-only data columns do not display the current values, which makes it difficult to
specify properly a new memory value.
n Host Name Does Not Appear in Action Dialog Box

When you run an action on a virtual machine, the host name is blank in the action dialog box.
Actions Do Not Appear on Object

An action might not appear on an object, such as a host or virtual machine, because vRealize
Automation is managing that object.
Problem
Actions such as Rebalance Container might not appear in the drop-down menu when you view
the actions for your data center.
n If a data center is managed by vRealize Automation, actions do not appear.
n If a data center is not managed by vRealize Automation, you can act on the virtual machines
that vRealize Automation is not managing.
Cause
When vRealize Automation manages the child objects of a data center or custom data center
container, the actions that are normally available on those objects do not appear. They are not
available because the action framework excludes actions on objects that vRealize Automation
manages. You cannot turn on or turn off the exclusion of actions on objects that vRealize
Automation manages. This behavior is normal.
If you removed the vRealize Automation adapter instance, but did not select the Remove related
objects check box, the actions are still disabled.
Make actions available on the objects in your data center or custom data center in one of two
ways. Either confirm that vRealize Automation is not managing the objects, or perform the steps
in this procedure to remove the vRealize Automation adapter instance.
Solution
1 To allow actions on an object, go to your vRealize Automation instance.
2 Perform the action in vRealize Automation, such as to move a virtual machine.
Missing Column Data in Actions Dialog Boxes

Data is missing for one or more objects in an Actions dialog box, making it difficult to determine if
you want to run the action.
Problem
When you run an action one or more objects, some of the fields are empty.
VMware, Inc. 892

Cause
There are two possible causes: 1) the VMware vSphere adapter has not collected the data from
the vCenter Server instance that manages the object. 2) the current vRealize Operations Manager
user does not have privileges to view the collected data for the object.
Solution
1 Verify that vRealize Operations Manager is configured to collect the data.
2 Verify that you have the privileges necessary to view the data.
Missing Column Data in the Set Memory for VM Dialog Box

The read-only data columns do not display the current values, which makes it difficult to specify
properly a new memory value.
Problem
Current (MB) and Power State columns do not display the current values, which are collected for
the managed object.
Cause
The adapter responsible for collecting data from the vCenter Server on which the target virtual
machine is running has not run a collection cycle and collected the data. This omission can occur
when you recently created an VMware adapter instance for the target vCenter Server and
initiated an action. The VMware vSphere adapter has a five-minute collection cycle.
Solution
1 After you create a VMware adapter instance, wait an extra five minutes.
2 Rerun the Set Memory for VM action.
The current memory value and the current power state appear in the dialog box.
Host Name Does Not Appear in Action Dialog Box

When you run an action on a virtual machine, the host name is blank in the action dialog box.
Problem
When you select virtual machine on which to run an action, and click the Action button, the
dialog box appears, but the Host column is empty.
Cause
Although your user role is configured to run action on the virtual machines, you do not have a
user roll that provides you with access to the host. You can see the virtual machines and run
actions on them, but you cannot see the host data for the virtual machines. vRealize Operations
Manager cannot retrieve data that you do not have permission to access.
VMware, Inc. 893

Solution
You can run the action, but you cannot see the host name in the action dialog boxes.
Monitor Recent Task Status

The Recent Task status includes all the tasks initiated from vRealize Operations Manager. You use
the task status information to verify that your tasks finished successfully or to determine the
current state of tasks.
You can monitor the status of tasks that are started when you run actions, and investigate
whether a task finished successfully.
Prerequisites
You ran at least one action as part of an alert recommendation or from one of the toolbars. See
Run Actions from Toolbars in vRealize Operations Manager.
Procedure
1 In the menu, click Administration, then select History from the left pane.
2 Click Recent Tasks.
3 To determine if you have tasks that are not finished, click the Status column and sort the
results.
Option Description
In Progress Indicates running tasks.
Completed Indicates finished tasks.
Failed Indicates incomplete tasks on at least one object when started on multiple
objects.
Maximum Time Reached Indicates timed out tasks.
4 To evaluate a task process, select the task in the list and review the information in the Details
of Task Selected pane.
The details appear in the Messages pane. If the information message includes No action
taken, the task finished because the object was already in the requested state.
5 To view the messages for an object when the task included several objects, select the object
in the Associated Objects list.
To clear the object selection so that you can view all the messages, press the space bar.
What to do next
Troubleshoot tasks with a status of Maximum Time Reached or Failed to determine why a task
did not run successfully. See Troubleshoot Failed Tasks.
VMware, Inc. 894

Recent Tasks in vRealize Operations Manager

The status of the tasks that were recently initiated from vRealize Operations Manager appears in
the Recent Task list. You can determine whether a task is finished, still in process, or failed.
How Recent Tasks Work

The Recent Tasks page reports on logged task events, and the log entries appear in the
messages area so that you can troubleshoot failed tasks.
Where You View Recent Tasks

In the menu, select Administration, then select History from the left pane and click Recent Tasks.
Recent Task Options

Review the information in the task list to determine if a task is completed or if you must
troubleshoot a failed task. To see the details about a task, select the task in the list and review
the associated objects and task messages.
Table 5-58. Task List

Option Description
Export Exports the selected task to an XML file.

The exported information, which includes the messages, is
useful when you are troubleshooting a problem.
Edit Properties Determines how long the recent task data is retained in your
system.
Set the number of days that vRealize Operations Manager
keeps the data, after which it is purged from the system.
The default value is 90 days.
Status drop-down menu Filters the list based on the status value.
All Filters Filters the list based the selected column and the provided
values.
Filter (Object Name) Limits the tasks in the list to those that match the entered
string.
The search is based on a partial entry. For example, if you
enter vm, objects such as vm001 and acctvm_east are
included.
Task Name of the task.

For example, Set CPU Count for VM.
VMware, Inc. 895

Table 5-58. Task List (continued)

Option Description
Status State of the task.

Possible states include the following values:
n Completed. Task completed successfully on the target
objects.
n In Progress. Task is running on the target objects.
n Failed. Task failed to run on the target objects. If the
task started, the reasons for failure might include a
faulty script, a script timed out, or actions are not taken.
If the task did not start and immediately reports as
failed, the reasons might include that the task was not
able to start or the script was not found. If the task was
not initiated on the target object, it might have failed
because of communication or authentication errors.
n Maximum Time Reached. Task is running past the
amount of time that is the default or configured value.
To determine the status, you must troubleshoot the
initiated action.
n Not Dispatched. The action adapter was not found.
n Started. Task is initiated on the object.
n Unknown. An error occurred while running the action,
but the error was not captured in the task logs. To
investigate this status further, check the vRealize
Operations Manager support logs for the vCenter
Adapter, available in the Administration area, and check
the target system.
Started Time Date and time when the task started.
Completed Time Date and time when the task finished.

A completed date does not appear if the task failed or if the
maximum timeout is reached.
Automated Indicates whether the action in the task list is automated,

indicated by Yes or No.
Object Name Object on which the task was started.
Object Type Type of object on which the task was started.
Alert Alert that triggered the action automatically. When an alert

is triggered that is associated to the recommendation, it
triggers the action without user intervention.
You can automate Alert recommendations that have an
associated action. Automation is disabled by default. You
configure automation in the Override Alert / Symptom
Definitions area of a policy when you create or edit the
policy in Administration > Policies.
An administrator who has the Automation role has
permission to automate actions in the Override Alert /
Symptom Definitions area of the policy workspace.
Source Type Authentication source that the user who started the task
used when accessing vRealize Operations Manager.
VMware, Inc. 896

Table 5-58. Task List (continued)

Option Description
Submitted By Name of the user who initiated the task. This column
displays the automationAdmin user account for automated
actions that are triggered by alerts.
Task ID ID generated when the task, which included one or more

actions, was started.
The task ID is unique for the task for each adapter. If a task
includes tasks that ran using two adapters, you see two task
IDs.
If the task is a delete snapshot action, two task IDs are
generated. One ID is for the retrieve snapshots based on
date task, and the other ID is for the delete selected
snapshots task.
The Associated Objects are the objects on which the selected task ran.
Table 5-59. Associated Objects for Selected Task Details

Option Description
Object Name Detailed list of objects that are included in the task
selected in the task list.
If the task ran on only one object, the list includes one
object. If the task ran on multiple objects, each object is
listed on a separate row.
Object Type Type of object for each object name.
Status Current state of the task.
The Messages are the log of the task as it ran. If the task does not finish successfully, use the logs
to identify problems.
Table 5-60. Messages for Selected Task Details
Severity drop-down menu Limits the messages based on the Severity value.
Filter (Message) Limits the message in the list to those that match the
entered string.
The search is based on a partial entry. For example, if you
enter id, then messages that contain Task ID and the
phrase did not complete are included.
Severity Message level in the logs.

The severity includes the following values:
n Information. Messages added to logs as the task is
processed.
n Error. Messages generated during a task failure.
VMware, Inc. 897

Table 5-60. Messages for Selected Task Details (continued)
Time Date and time the entry was added to the log.
Message Text of the log entry.

Use the information in the message to determine why a
task failed, and to begin to troubleshoot and resolve the
failure.
The messages appear with the most recent entry at the
top of the list if you do not sort the columns.
Troubleshoot Failed Tasks

If tasks fail to run in vRealize Operations Manager, review the Recent Tasks page and
troubleshoot the task to determine why it failed.
This information is a general procedure for using the information in Recent Tasks to troubleshoot
problems identified in the tasks.
n Determine If a Recent Task Failed

The Recent Tasks provide the status of action tasks initiated from vRealize Operations
Manager. If you do not see the expected results, review the tasks to determine if your task
failed.
n Troubleshooting Maximum Time Reached Task Status

An action task has a Maximum Time Reached status and you do not know the status of the
task.
n Troubleshooting Set CPU or Set Memory Failed Tasks

An action task for Set CPU Count or Set Memory for VM has a Failed status in the recent
task list because power off is not allowed.
n Troubleshooting Set CPU Count or Set Memory with Powered Off Allowed
A Set CPU Count, Set Memory, or a Set CPU Count and Set Memory action indicates that the
action failed in Recent Tasks.
n Troubleshooting Set CPU Count and Memory When Values Not Supported
If you run the Set CPU Count or Set Memory actions with an unsupported value on a virtual
machine, the virtual machine might be left in an unusable state. That outcome requires you
to resolve the problem in vCenter Server.
n Troubleshooting Set CPU Resources or Set Memory Resources When the Value Is Not
Supported
If you run the Set CPU Resources action with an unsupported value on a virtual machine, the
task fails and an error appears in the Recent Task messages.
VMware, Inc. 898

n Troubleshooting Set CPU Resources or Set Memory Resources When the Value Is Too High
You run the Set CPU Resources or Set Memory Resources action and the task fails with an
error appearing in the Recent Tasks messages. The reason might be that you entered a
value that is greater than the value that your vCenter Server instance supports.
n Troubleshooting Set Memory Resources When the Value Is Not Evenly Divisible by 1024
If you run the Set Memory Resources action with a value that cannot convert from kilobytes
to megabytes, the task fails and an error appears in the Recent Task messages.
n Troubleshooting Failed Shut Down VM Action Status

A shutdown VM action task has a Failed status in the Recent Task list.
n Troubleshooting VMware Tools Not Running for a Shutdown VM Action Status

A Shutdown VM action task has a Failed status in the Recent Task list and the Message
indicates that VMware Tools were required.
n Troubleshooting Failed Delete Unused Snapshots Action Status

A Delete Unused Snapshots action task has a Failed status in the Recent Task list.
Determine If a Recent Task Failed

The Recent Tasks provide the status of action tasks initiated from vRealize Operations Manager.
If you do not see the expected results, review the tasks to determine if your task failed.
Procedure
1 In the menu, click Administration, then click History in the left pane.
3 Select the failed task in the task list.
4 In the Messages list, locate the occurrences of Script Return Result: Failure and review
the information between this value and <-- Executing:[script name] on {object type}.
Script Return Result is the end of action run and <-- Executing indicates the beginning.
The information provided includes the parameters that are passed, the target object, and
unexpected exceptions that you can use to identify the problem.
Troubleshooting Maximum Time Reached Task Status

An action task has a Maximum Time Reached status and you do not know the status of the task.
Problem
The Recent Tasks list indicates that a task had a status of Maximum Time Reached.
The task is running past the amount of time that is the default or configured value. To determine
the latest status, you must troubleshoot the initiated action.
VMware, Inc. 899

Cause
The task is running past the amount of time that is the default or configured value for one of the
following reasons:
n The action is exceptionally long running and did not finish before the threshold timeout was
reached.
n The action adapter did not receive a response from the target system before reaching the
timeout. The action might have completed successfully, but the completion status was not
returned to vRealize Operations Manager.
n The action did not start correctly.
n The action adapter might have an error and be unable to report the status.
Solution
To determine whether the action completed successfully, check the state of the target object. If it
did not complete, continue investigating to find the root cause.
Troubleshooting Set CPU or Set Memory Failed Tasks

An action task for Set CPU Count or Set Memory for VM has a Failed status in the recent task list
because power off is not allowed.
Problem
The Recent Tasks list indicates that a Set CPU Count, Set Memory, or Set CPU and Memory task
has a status of Failed. When you evaluate the Messages list for the selected task, you see this
message.
Unable to perform action. Virtual Machine found

powered on, power off not allowed.
When you increase the memory or CPU count, you see this message.
Virtual Machine found powered on, power off not allowed, if hot add is
enabled the hotPlugLimit is exceeded.
Cause
You submitted the action to increase or decrease the CPU or memory value without selecting the
Allow Power Off option. When you ran the action where a target object is powered on and
where Memory Hot Plug is not enabled for the target object in vCenter Server, the action fails.
Solution
1 Either enable Memory Hot Plug on your target virtual machines in vCenter Server or select
Allow Power Off when you run the Set CPU Count, Set Memory, or Set CPU and Memory
actions.
2 Check your hot plug limit in vCenter Server.
VMware, Inc. 900

Troubleshooting Set CPU Count or Set Memory with Powered Off Allowed
A Set CPU Count, Set Memory, or a Set CPU Count and Set Memory action indicates that the
action failed in Recent Tasks.
Problem
When you run an action that changes the CPU count, the memory, or both, the action fails. It fails
even though Power Off Allowed was selected, the virtual machine is running, and the VMware
Tools are installed and running.
Cause
The virtual machine must shut down the guest operating system before it powers off the virtual
machine to make the requested changes. The shutdown process waits 120 seconds for a
response from the target virtual machine, and fails without changing the virtual machine.
Solution
1 To determine if it has jobs running that are delaying the implementation of the action, check
the target virtual machine in vCenter Server.
2 Retry the action from vRealize Operations Manager.
Troubleshooting Set CPU Count and Memory When Values Not Supported
If you run the Set CPU Count or Set Memory actions with an unsupported value on a virtual
machine, the virtual machine might be left in an unusable state. That outcome requires you to
resolve the problem in vCenter Server.
Problem
You cannot power on a virtual machine after you successfully run the Set CPU Count or Set
Memory actions. When you review the messages in Recent Tasks for the failed Power On VM
action, you see messages stating that the host does not support the new CPU count or new
memory value.
Cause
Because of the way that vCenter Server validates changes in the CPU and memory values, you
can use the vRealize Operations Manager actions to change the value to an unsupported amount.
This change can happen when you run the action when the virtual machine is powered off.
If the object was powered on, the task fails, but rolls back any value changes and powers the
machine back on. If the object was powered off, the task succeeds and the value is changed in
vCenter Server. However, the target object is left in a state where you cannot power it on using
either actions or the vCenter Server without manually changing the CPU or memory to a
supported value.
Solution
1 In the menu, click Administration, then select History from the left pane.
VMware, Inc. 901

3 In the task list, locate your failed Power On VM action, and review the messages associated
with the task.
4 Look for a message that indicates why the task failed.
For example, if you ran a Set CPU Count action on a powered off virtual machine to increase
the CPU count from 2 to 4, but the host does not support 4 CPUs. The Set CPU tasks
reported that it completed successfully in recent tasks. However, when you attempt to power
on the virtual machine, the tasks fails. In this example, the message is Virtual machine
requires 4 CPUs to operate, but the host hardware only provides 2.
5 Click the object name in the Recent Task list.
The main pane updates to display the object details for the selected object.
6 Click the Actions menu on the toolbar and click Open Virtual Machine in vSphere Client.
The vSphere Web Client opens with the virtual machine as the current object.
7 In the vSphere Web Client, click the Manage tab and click VM Hardware.
8 Click Edit.
9 In the Edit Settings dialog box, change the CPU count or memory to a supported value and
click OK.
You can now power on the virtual machine from the Web client or from vRealize Operations
Manager.
Troubleshooting Set CPU Resources or Set Memory Resources When the Value
Is Not Supported
If you run the Set CPU Resources action with an unsupported value on a virtual machine, the task
fails and an error appears in the Recent Task messages.
Problem
The Recent Tasks list indicates that a Set CPU Resource or Set Memory Resource action has a
state of Failed. When you evaluate the Messages list for the selected task, you see a message
similar to the following examples.
RuntimeFault exception, message:[A specified parameter was not correct.

spec.cpuAllocation.reservation]
RuntimeFault exception, message:[A specified parameter was not correct. spec.cpuAllocation.limits]
Cause
You submitted the action to increase or decrease the CPU or memory reservation or limit value
with an unsupported value. For example, if you supplied a negative integer other than -1, which
sets the value to unlimited, vCenter Server cannot make the change and the action failed.
VMware, Inc. 902

Solution
u Run the action with a supported value.
The supported values for reservation include 0 or a value greater than 0. The supported
values for limit include -1, 0, or a value greater than 0.
Troubleshooting Set CPU Resources or Set Memory Resources When the Value
Is Too High
You run the Set CPU Resources or Set Memory Resources action and the task fails with an error
appearing in the Recent Tasks messages. The reason might be that you entered a value that is
greater than the value that your vCenter Server instance supports.
Problem
The Recent Tasks list indicates that a Set CPU Resource or Set Memory Resource action has a
state of Failed. When you evaluate the Messages list for the selected task, you see messages
similar to the following examples.
If you are working with Set CPU Resources, the information message is similar to the following
example, where 1000000000 is the supplied reservation value.
Reconfiguring the Virtual Machine Reservation to:[1000000000] Mhz
The error message for this action is similar to this example.
RuntimeFault exception, message:[A specified parameter was not correct: reservation]
If you are working with Set Memory Resources, the information message is similar to the
following example, where 1000000000 is the supplied reservation value.
Reconfiguring the Virtual Machine Reservation to:[1000000000] (MB)
The error message for this action is similar to this example.
RuntimeFault exception, message:[A specified parameter was not correct.

spec.memoryAllocation.reservation]
Cause
You submitted the action to change the CPU or memory reservation or limit value to a value
greater than the value supported by vCenter Server, or the submitted reservation value is
greater than the limit.
Solution
u Run the action using a lower value.
VMware, Inc. 903

Troubleshooting Set Memory Resources When the Value Is Not Evenly Divisible
by 1024
If you run the Set Memory Resources action with a value that cannot convert from kilobytes to
megabytes, the task fails and an error appears in the Recent Task messages.
Problem
The Recent Tasks list indicates that a Set Memory Resource action has a state of Failed. When
you evaluate the Messages list for the selected task, you see a message similar to the following
example.
Parameter validation;[newLimitKB] failed conversion to (MB, (KB)[2000] not evenly divisible by 1024.
Cause
Because vCenter Server manages memory reservations and limit values in megabytes, but
vRealize Operations Manager calculates and reports on memory in kilobytes, you must provide a
value in kilobytes that is directly convertible to megabytes. To do that, the value must be evenly
divisible by 1024.
Solution
u Run the action where the reservation and limit values are configured with supported values.
The supported values for reservation include 0 or a value greater than 0 that is evenly
divisible by 1024. The supported values for a limit include -1, 0, or a value greater than 0 that
is evenly divisible by 1024.
Troubleshooting Failed Shut Down VM Action Status

A shutdown VM action task has a Failed status in the Recent Task list.
Problem
The Shut Down VM action did not run successfully.
The Recent Tasks list indicates that a Shut Down VM action has a task status of Failed. When
you evaluate the Messages list for the selected job, you see Failure: Shut down confirmation
timeout.
Cause
The shutdown process involves shutting down the guest operating system and powering off the
virtual machine. The wait time is 120 seconds to shut down the guest operating system. If the
guest operating system does not shut down in this time, the action fails because the shutdown
action is not confirmed.
Solution
u To determine why the guest operating system did not shut down in the allotted time, check
its status in vCenter Server.
VMware, Inc. 904

Troubleshooting VMware Tools Not Running for a Shutdown VM Action Status

A Shutdown VM action task has a Failed status in the Recent Task list and the Message indicates
that VMware Tools were required.
Problem
The Shutdown VM action did not run successfully.
The Recent Tasks list indicates that a Shutdown VM action has a tasks status of Failed. When
you evaluate the Messages list for the selected job, you see VMware Tools: Not running (Not
installed).
Cause
The Shutdown VM action requires that VMware Tools is installed and running on the target virtual
machines. If you ran the action on more than one object, then VMware Tools was not installed, or
installed but not running, on at least one of the virtual machines.
Solution
u In the vCenter Server instance that manages the virtual machine that failed to run the action,
install and start VMware Tools on the affected virtual machines.
Troubleshooting Failed Delete Unused Snapshots Action Status

A Delete Unused Snapshots action task has a Failed status in the Recent Task list.
Problem
The Delete Unused Snapshots action did not run successfully.
The Recent Tasks list indicates that a Delete Unused Snapshots action has a task status of
Failed. When you evaluate the Messages list for the selected job, you see this message.
Remove snapshot failed, response wait expired after:[120] seconds,

unable to confirm removal.
Cause
The delete snapshot process involves waiting for access to datastores. The wait time is 600
seconds to access the datastore and delete the snapshot. If the delete request is not passed to
the datastore in that time, the action does not finish the delete snapshot action.
Solution
1 To determine if the snapshot was deleted, check its status in vCenter Server .
2 If it was not, submit the delete snapshot request at a different time.
VMware, Inc. 905

Viewing Your Inventory

vRealize Operations Manager collects data from all the objects in your environment and displays
a health, risk, and efficiency status for each object.
Survey your entire inventory to get a quick idea of the state of any object or click an object name
for more detailed information. See Evaluating Object Information Using Badge Alerts and the
Summary Tab.
Inventory Tab
The tab displays the state of each object in your environment. Objects are members of groups
and applications that you define.
Where You Find Inventory

In the menu, click Environment, then select the Inventory tab.
Use the toolbar options to manage objects.
Table 5-61. Inventory Toolbar Options

Option Description
Action An action on the selected object. Depends on the object

type. For example, Power on VM applies to the selected
virtual machine. See List of vRealize Operations Manager
Actions.
Open in external application If an adapter includes the ability to link to another

command to access a link to the application. For example,
Open Virtual Machine in a vSphere Client or Search for VM
logs in vRealize Log Insight.
Filter Limit the list to objects matching the filter.
Table 5-62. Inventory Data Grid Options

Option Description
Object Name Displays a summary of the object.
Summary Criticality of the health, risk, and efficiency of any object.
VMware, Inc. 906

Capacity Optimization for Your
Managed Environment 6
Capacity Optimization in vRealize Operations Manager is achieved using powerful integrated
functions - capacity overview, workload balancing and optimization, repurposing of underutilized
resources, and what-if predictive scenarios - to reach optimal system performance.
Capacity planners must assess whether physical capacity is sufficient to meet current or
forecasted demand. With robust capacity planning and optimization, you can manage your
production capacity effectively as your organization addresses changing requirements. The
objective of strategic capacity optimization is to reach an optimal level where production
capabilities meet ongoing demand.
vRealize Operations Manager analytics provide precise tracking, measuring and forecasting of
data center capacity, usage, and trends to help manage and optimize resource use, system
tuning, and cost recovery. The system monitors stress thresholds and alerts you before potential
issues can affect performance. Multiple pre-set reports are available. You can plan capacity
based on historical usage, and run what-if scenarios as your requirements expand.
How Capacity Optimization Works

The Capacity Optimization provides four integrated functions - Overview, Reclaim, Workload
Optimization, and What-If Scenarios - that give an overview of the status of all data center
activity and trending. You can conduct on-the-spot analysis, including drilling down into further
detail on any object to identity possible performance problems or anomalies. You can rebalance
and optimize compute resources. The system further identifies underutilized workloads (virtual
machines) and calculates the potential cost savings that can accrue when these resources are
reclaimed to be deployed more effectively. You can interact with and manipulate data and
outcomes based on your requirements.
Use the Capacity Optimization and Reclaim features to assess workload status and resource
contention in data centers across your environment. You can determine time remaining until CPU,
memory, or storage resources run out and realize cost savings when underutilized VMs can be
reclaimed and deployed where needed.
VMware, Inc. 907

Workload Optimization provides for moving virtual workloads and their file systems dynamically
across datastore clusters within a data center or custom data center. You can potentially
automate a significant portion of your data center compute and storage optimization efforts.
With properly defined policies determining the threshold at which resource contention triggers
an alert and automatically runs an action, a data center performs at optimum.
In addition, the What-If Analysis function- can run scenarios that help determine where additional
system resources can be brought online.
Note You may see a data center or cluster labeled as optimized when it has few or no days
remaining before CPU, memory, or storage is predicted to run out. That is because these are two
different measures of data center and cluster health. A data center can be running at optimum
based on policy settings for balance and consolidation, yet be almost out of resources. It is
important to consider both measures when managing your environment.
n Capacity Analytics
n Example: Excluding VMs from Reclaim Action
n What-If Analysis: Modeling Workload, Capacity, or Migration Planning
n Example: Run a What-If Scenario
n Example: Import Workload from an Existing VM Scenario
n Allocation Model
n Capacity Overview
n Reclaim
n Reclamation Settings
n What-If Analysis - Workload
n What-If Analysis - Physical Infrastructure
n What-If-Analysis - Migration Planning
n What-If-Analysis - Hyperconverged Infrastructure
n Custom Profiles in VMware vRealize Operations Manager
n Custom Data Centers in VMware vRealize Operations Manager
Capacity Analytics
Capacity analytics helps you assess the utilization and capacity remaining in objects across your
environment. An evaluation of the historical utilization of resources generates a projection of the
future workload. You can plan for infrastructure procurement or migrations based on the
projection and avoid the risk of capacity shortage and high infrastructure costs.
VMware, Inc. 908

Capacity analytics uses the capacity engine to assess historical trends, which include utilization
peaks. The engine chooses an appropriate projection model to predict the future workload. The
amount of historical data that is considered depends on the amount of historical utilization data.
Capacity Engine and Calculations

The capacity engine analyzes historical utilization and projects future workload by using real-time
predictive capacity analytics, which is based on an industry-standard statistical analysis model of
demand behavior. The engine takes the Demand and Usable Capacity metrics as input and
generates the output metrics, which are Time Remaining, Capacity Remaining, Recommended
Size, and Recommended Total Capacity, as shown in the following figure.
Time Remaining
Resource
Utilization / Demand Capacity Remaining
Capacity Engine
Usable Capacity Recommended Size
Recommended
Total Capacity
The projection window for the capacity engine is 1 year into the future. The engine consumes
data points every 5 minutes to ensure real-time calculation of output metrics.
The capacity engine projects the future workload in a projected utilization range. The range
includes an upper bound projection and a lower bound projection. Capacity calculations are
based on the time remaining risk level. The engine considers the upper bound projection for a
conservative risk level and the mean of the upper bound projection and lower bound projection
for an aggressive risk level. For more information about setting risk levels, see Analysis Settings
Details.
The capacity engine calculates the time remaining, capacity remaining, recommended size, and
recommended total capacity.
Time Remaining
The number of days remaining till the projected utilization crosses the threshold for the
usable capacity. The usable capacity is the total capacity excluding the HA settings.
Capacity Remaining
The largest difference between the usable capacity and the projected utilization between
now and 3 days into the future. If the projected utilization is above 100% of the usable
capacity, the capacity remaining is 0.
Recommended Size
VMware, Inc. 909

The maximum projected utilization for the projection period from the current time to 30 days
after the warning threshold value for time remaining. The warning threshold is the period
during which the time remaining is green. The recommended size excludes HA settings.
If the warning threshold value for time remaining is 120 days, which is the default value, the
recommended size is the maximum projected utilization 150 days into the future.
vRealize Operations Manager caps the recommended size that is generated by the capacity
engine to keep the recommendations conservative.
n vRealize Operations Manager caps an oversized recommended size at 50% of the

currently allocated resources.
For example, a virtual machine that is configured with 8 vCPUs has never used more than
10% CPU historically. Instead of recommending a reclaim of 7 vCPUs, the recommendation
is capped to reclaiming 4 vCPUs.
n vRealize Operations Manager caps an undersized recommended size at 100% of the

currently allocated resources.
For example, a virtual machine that is configured with 4 vCPUs has been constantly
running very hot historically. Instead of recommending the addition of 8 vCPUs, the
recommendation is capped at adding 4 vCPUs.
Recommended Total Capacity
The maximum projected utilization for the projection period from the current time to 30 days
after the warning threshold value for time remaining. The recommended total capacity
includes HA settings.
For example, if the warning threshold value for time remaining is 120 days, which is the
default value, the recommended size is the maximum projected utilization including HA
values, 150 days into the future.
Note Recommended total capacity is not available for objects.
The following figure shows the capacity calculations for a conservative risk level.
VMware, Inc. 910

Utilization
Recommended Size
Upper Bound Projection
Time Remaining
Usable Capacity Mean Projection
Capacity
Remaining Lower Bound
Projection
Time Remaining
Current Time Current Time + 3 Days Green + 30 Days
Time
Historical Utilization Projected Utilization
The following figure shows the capacity calculations for an aggressive risk level.
Utilization
Upper Bound Projection

Recommended Size
Mean Projection
Time Remaining
Usable Capacity
Lower Bound
Capacity
Projection
Remaining
Time Remaining
Current Time Current Time + 3 Days Green + 30 Days
Time
Historical Utilization Projected Utilization
Utilization Peaks
The historical utilization of resources can have peaks, which are periods of maximum utilization.
The projection of future workload depends on the types of peaks. According to the frequency of
peaks, they can be momentary, sustained, or periodic.
Momentary Peaks
Short-lived peaks that are a one-time occurrence. The peaks are not significant enough to
require additional capacity, so they do not impact capacity planning and projection.
Sustained Peaks
VMware, Inc. 911

Peaks that last for a longer time and impact projections. If a sustained peak is not periodic,
the impact on the projection lessens over time because of exponential decay.
Periodic Peaks
Peaks that exhibit cyclical patterns or waves. The peaks can be hourly, daily, weekly,
monthly, during the last day of the month, and so on. The capacity engine also detects
multiple overlapping cyclical patterns.
Projection Models
The capacity engine uses projection models to generate projections. The engine constantly
modifies projections and chooses the model that best fits the pattern of historical data. The
projection range predicts the general usage pattern that covers 90% of the future data points.
Projection models can be linear or periodic.
Linear Models
Models that have a steadily increasing or decreasing trend. Multiple linear models run in
parallel and the capacity engine chooses the best model.
Examples of linear models are linear regression and autoregressive moving average (ARMA).
Periodic Models
Models that discover periodicity of various lengths, such as hours, days, weeks, months, or
the last day of the week or month. Periodic models detect square waves that represent batch
jobs and handle data streams that contain multiple overlapping periodic patterns. These
models ignore random noise.
Examples of periodic models are fast Fourier transforms (FFTs), pulses (edge detection), and
wavelets.
Historical Data Window

The capacity engine captures historical data over a period of time depending on the historical
data window. The historical data window that the engine uses is an exponential decay window.
The exponential decay window is a window of unlimited size in which the capacity engine gives
more importance to the most recent data points. Beginning from the projection calculation start
point, the engine consumes all the historical data points and weighs them exponentially, based
on how far back in time they are.
Example: Excluding VMs from Reclaim Action

In this example, an administrator starts the UI, chooses the Reclaim function on the Quick Start
page, and identifies a data center with an excessive number of snapshots. The administrator
wants to run the action for reclaiming resources, but chooses to exclude some VMs from the
action.
The administrator is reviewing system resources at the start of the shift.
VMware, Inc. 912

Prerequisites
The administrator must have credentials for operating vRealize Operations Manager and
Procedure
1 At the Home screen, clicks Reclaim in the Optimize Capacity column.
The Reclaim screen appears. In reviewing the status of data centers across the network, the
administrator sees that data center DC-Evanston-6 has 3 days of time remaining.
2 The administrator clicks the DC-Evanston-6 graphic.
The data in the lower half of the screen refreshes to display total reclaimable capacity and
cost savings potential for recommendations for selected data center DC-Denver-19. (NOTE:
Double-clicking the DC-Evanston-6 graphic at this point displays the Object Details page for
that data center.)
3 At the table, selects Snapshots from the header row.
The table refreshes to list clusters with excess snapshots.
4 The administrator clicks the chevron next to a cluster name on the left in the table.
All the VMs in the cluster are listed.
5 The administrator wants to keep snapshots for some VMs in the cluster, so selects two VMs
and clicks EXCLUDE VM(s).
A dialog box appears asking for confirmation.
6 Clicks EXCLUDE VM(s) to confirm.
The excluded VMs disappear from view and the potential cost savings drops.
7 Back at the table, with the VMs selected whose snapshots are to be deleted, the
administrator clicks DELETE SNAPSHOT(s).
The Delete Snapshots confirmation dialog box appears, showing how many snapshots are to
be deleted and the monthly savings in cost and disk space.
8 Clicks DELETE SNAPSHOT(s) to confirm.
The system deletes the snapshots.
Results
Excessive snapshots are deleted and cost savings are realized.
What to do next
Under Optimize Capacity in the left menu, click Overview to display the Capacity Overview
screen. Confirm that DC-Evanston-6 now has 15 days of time remaining.
VMware, Inc. 913

What-If Analysis: Modeling Workload, Capacity, or Migration

Planning
Using the what-if tool, you can plan for an increase or decrease in workload or capacity
requirements in your virtual infrastructure. To evaluate the demand and supply for capacity on
your system objects, and to assess the potential risk to your current capacity, you can create
scenarios for adding and removing workloads. You can also determine how much capacity you
require to make a migration work. You can run one scenario or group scenarios and run them
cumulatively.
Why Create a Scenario

A scenario is a detailed estimation of the resources you must have available in your environment
to incorporate upcoming changes. You define scenarios that can potentially add resources to
actual data centers. VMware vRealize Operations Manager models the scenario and calculates
whether your desired workload can fit in the targeted data center. You can save multiple
scenarios for comparison or review.
Where You Find What-If Analysis

From the Home screen, select What-If Analysis under Optimize Capacity in the left pane. The
Overview tab of the What-If analysis page has four panes. Each pane lets you run What-If
scenarios to optimize capacity based on workload, physical infrastructure HCI nodes, or migration
to the cloud.
How What-If Analysis Works

You can run What-If scenarios to see how much capacity will remain after you add or remove
VMs or hosts and add hyperconverged infrastructure (HCI) nodes. Migration planning shows you
the capacity and cost information after migrating to cloud based infrastructure.
Scenarios that you save for later are displayed as a list in the Saved Scenarios tab. You can run,
edit or delete the saved scenarios. You can select more than one compatible scenarios and run
them together. For example, you can create a scenario to remove hosts using the Physical
Infrastructure Planning pane, because your organization has hardware that will soon become
obsolete. You can create another scenario to add hosts to your physical infrastructure to account
for new hardware that will replace the obsolete ones. You can run both these scenarios together
to see the capacity after removing old hardware and adding new hardware.
You can only combine scenarios that pertain to the same object. Use the filters in the Saved
Scenarios tab to narrow down the list based on scenario name, type, data center, or cluster.
You can select the following combinations of scenarios and run them together:
Workload Planning and Physical Infrastructure Planning
n Add VMs
n Remove VMs
VMware, Inc. 914

n Add Hosts
n Remove Hosts
The Scenario Summary page displays the results of running one or more saved scenarios. To add
or remove saved scenarios and run them again cumulatively, click Edit in the Scenario Summary
page .
Example: Run a What-If Scenario

In this example, an IT administrator at a financial data center must plan for an increase in
workloads as tax season approaches. To evaluate whether additional workloads can be added to
existing virtual infrastructure, the administrator runs a what-if scenario.
Prerequisites
Procedure
1 The administrator clicks Home > Optimize Capacity > What-If Analysis.
The What-If Analysis screen appears.
2 Clicks Add VMS in the Workload Planning pane.
The Workload Planning screen appears.
3 Enters Workload Tax 2018 in the SCENARIO NAME field, then selects DC-Chicago-16
(vc_10.27.83.19) from the list under LOCATION - WHERE WOULD YOU LIKE TO ADD YOUR
WORKLOAD?
The field to the right populates with the words, Any cluster. The administrator selects Cluster
- Mich2long from the list.
4 The administrator clicks the Configure radio button.
5 For the CPU row, the administrator increments the count to 4. For the Memory row, enters 18.
For the Disk Space row, enters 65. Enters 45% in the Expected Utilization column. For number
of VMs, enters 20.
The configuration is nearly complete.
6 The administrator clicks SAVE
The Saved Scenarios screen appears. The data entered on the previous screen appears
under Saved Scenarios.
7 The administrator researches the time period for which the workload is needed online.
The administrator identifies the start and end dates.
VMware, Inc. 915

8 Back at the What-If Analysis screen, the administrator selects Workload Tax 2018 in the list
under Saved Scenarios and clicks EDIT in the command bar.
The Workload Planning screen appears with the data filled in for the requested scenario.
9 In the DATE area, the administrator selects 3/25/18 and 5/30/18 as the start and end dates,
respectively, then clicks RUN SCENARIO.
The scenario runs and the results appear. To the administrator's surprise, the workload does
not fit.
10 At the top right of the screen, the administrator selects a different cluster: Cluster -
Mich3long. Then clicks the RUN SCENARIO button to the right of the list.
The scenario runs and the results appear. This time the workload fits. It is projected to cost
$84/month to run in the VMware hybrid cloud.
Results
The administrator identifies a location in the virtual infrastructure where the required workload
can reside and support the coming increase in production requirements.
What to do next
Assuming this plan is the best of the scenarios the administrator has run, it can be implemented
in time to support the added workload. The administrator can monitor the workload performance
using the Using Workload Optimization and Chapter 6 Capacity Optimization for Your Managed
Environment features.
Example: Import Workload from an Existing VM Scenario

In this example, an IT administrator at a data center must plan for an increase in workloads as
more staff is hired. To evaluate whether additional workloads can be added to existing virtual
infrastructure, the administrator runs a what-if scenario using an actual VM as the workload.
Prerequisites
Procedure
1 The administrator clicks Home > Optimize Capacity > What-If Analysis.
The What-If Analysis screen appears.
2 Clicks Add VMS in the Workload Planning pane.
The Workload Planning screen appears.
VMware, Inc. 916

3 Enters Workload Staff Hire in the SCENARIO NAME field, then selects DC-Boston-16
(vc_10.27.83.18) from the list under LOCATION - WHERE WOULD YOU LIKE TO ADD YOUR
WORKLOAD?
The field to the right populates with the words, Any cluster. The administrator selects Cluster
- 1860 from the list.
4 The administrator clicks the Import from existing VM radio button in the APPLICATION
PROFILE field, then clicks SELECT VMs.
The Select VMs dialog box appears.
5 In the column on the left, double-click the name of each VM whose attributes you want use in
this scenario. The VM names appear in a SELECTED column on the right.
6 Click OK.
The Workload Planning screen appears. The data entered on the previous screen appears in
the APPLICATION PROFILE field.
7 At the Workload Planning screen, under APPLICATION PROFILE, in the SELECTED VMS table,
enter in the Quantity column the number of copies you want of each VM you selected.
The scenario is almost ready to run.
8 In the DATE area, the administrator selects 3/25/18 and 6/30/18 as the start and end dates,
respectively, then clicks RUN SCENARIO
The scenario is successful: the workload will fit. By default, vRealize Operations Manager
compares the cost of running the workload on two providers, typically Hybrid Cloud
(VMware) and AWS. The corresponding cost details are updated for your private cloud and
public cloud providers. The planning scenario also provides a public cloud comparison
between Hybrid Cloud and VMware Cloud on AWS. You can see that the monthly cost is
displayed for each of the public clouds.
VMware Cloud on AWS Hybrid Cloud
Shows the number of hosts required on VMare Cloud on AWS for the migration to Shows the allocated cost
accommodate the selected workload, considering the minimum purchase of four hosts. for a month.
The actual utilized capacity of each host, with balanced workload distribution. Displays the utilization of
CPU, memory, and
storage. Provides overall
requirement of hosts for
the given capacity.
Total purchase cost is derived by multiplying the effective monthly purchase cost for
each host by the number of required hosts.
Total Utilized Cost per month is computed based on utilized CPU and RAM, allocated
storage, this indicates how well all three resources are being utilized as a fraction of
the purchase cost.
Required CPU and memory are calculated based on utilization.
Required storage is calculated based on allocated storage capacity in your private

cloud.
VMware, Inc. 917

VMware Cloud on AWS Hybrid Cloud
Shows on-demand, one and three-year subscription cost.
Shows the cost for a selected AWS region and its equivalent resources required for
the selected region.
Results
In the Public Cloud text box, the system displays the monthly cost of running the workload on the
VMware Hybrid Cloud versus the AWS Public Cloud.
What to do next
Assuming this plan is the best of the scenarios the administrator has run, it can be implemented
in time to support the added workload. The administrator can monitor the workload performance
using the Using Workload Optimization and Chapter 6 Capacity Optimization for Your Managed
Environment features.
Allocation Model
The allocation model determines how much compute, memory, and storage resources are
allocated to object types. You define the allocation values by modifying the policy which is
applied to the objects. The allocation values, also known as overcommit ratios, affect
performance and cost.
The allocation model works alongside the demand model. Unlike the demand model which
always affects the capacity calculations, the allocation model can be turned on or off in the policy
setting. You can control the ratio by which vRealize Operations Manager overcommits either the
CPU, memory, or disk space. By specifying the allocation values in the policy, you can choose
whether you want to overcommit your resources or not. Overcommitting helps you measure
utilization of resources in a pay-as-you-go model. When you do not overcommit, the utilization of
your cluster will never exceed 100%. If your resource utilization is over the allocation ratio that
you set, Capacity Remaining becomes zero.
To modify a policy and configure overcommit ratios, see Policy Allocation Model Element.
Capacity Overview
Use the Capacity Overview screen to assess workload status and how much capacity is
remaining in data centers across your environment.
Where You Find Capacity Overview

In the menu, select home and then click Overview under Optimize Capacity in the left pane.
From the Quick Start screen, select Assess Capacity in the second-from-left column.
Note Double-click on a data center graphic to display the object details screen for the data
center.
VMware, Inc. 918

How the Capacity Overview Works

The Capacity Optimization and Reclaim features are tightly integrated functions that enable you
to assess workload status in data centers across your environment. You can determine time
remaining until CPU, memory, or disk space resources run out and realize cost savings when
underutilized VMs can be reclaimed and deployed where needed.
When you open the Capacity Overview page, graphical representations of all the data centers
and custom data centers in your environment appear. VMware Cloud on AWS data centers has a
unique icon to differentiate it from the other data centers.
By default, they are shown in order of time remaining, beginning from the upper left, where the
most constrained data centers appear. To review the status of a data center, click the graphic.
The page refreshes to display the following data:
Time Remaining
Time Remaining specifies which clusters are most constrained and displays the criticality of
the cluster.
Optimization Recommendations
vRealize Operations Manager shows you the number of reclaimable VMs and the associated
cost savings. Click View Reclaimable VMs to navigate to the Reclaim page.
Cluster Utilization
Cluster Utilization displays an interactive graph that shows time remaining by component.
You can explore the demand percentage over time by CPU, memory, and disk space or by
the most constrained component. By default, the data displayed is for the Demand model. If
you have configured the Allocation model then you can also see the CPU, memory, and disk
space time remaining model based on the overcommit ratios that you have set in the policy.
Set the Show History and Show Forecast variables to create the slice of time in which you
want to see time-remaining data. The vertical axis of the graph shows the total capacity
being used by the current amount of CPU, memory, or disk space respectively. The bold,
black line across the top of the graph depicts the historical value of usable capacity. The
horizontal axis is the timeline. Vertical lines in the graph are labeled at the bottom of each
line. The first vertical dotted line on the left marks the projection calculation start point. The
next line is the current date - now. The third vertical marks the date the resource runs out. If a
resource has little time remaining, the current date and the date that time runs out may be
the same.
vRealize Operations Manager can make recommendations for increasing time remaining based
on the data it receives and these recommendations appear at the bottom of the screen. You
might see two options: Option 1 shows what you can achieve by reclaiming resources. Option 2
shows the results of adding capacity.
VMware, Inc. 919

If you choose to reclaim resources, you can run that process immediately by clicking RECLAIM
RESOURCES. To see the details or choose additional options before running a reclaim action,
review the information provided in the Optimization Recommendations pane and then click
VIEW RECLAIMABLE VMS to go to the Reclaim page.
Table 6-1. Capacity Optimization Options

Option Description
Select a datacenter Select a data center from the carousel across the top of the page.
Information about the datacenter is displayed below.
View: Filter results to include data centers, custom data centers, or both. This
option appears if you select ALL DATACENTERS on the upper right.
belongs. This option appears if you select ALL DATACENTERS on the upper
right.
Sort by: Options (Options appear if you select ALL DATACENTERS on the upper
right):
n Alarm clock graphic - lists data centers/custom data centers by time
remaining.
n Dollar sign - lists data centers/custom data centers by potential cost
savings.
n Scales graphic - lists data centers/custom data centers by level of
optimization.
Select datacenter or ADD NEW CUSTOM Options (options appear if you select ALL DATACENTERS on the upper
DATACENTER right):
data following refreshes with information for the selected object.
Time Remaining Appears when you select a data center or custom data center from the top
of the screen.
Gives overview of cluster status, including how many are at:
n Critical
n Medium
n Normal
n Unknown
"Critical" can indicate a resource contention, imbalance, or other stress
condition. Thresholds you set in the policies define what is critical.
Optimization Recommendations Lists potential cost savings by reclaiming unused resources.

Indicates if workloads can be optimized across clusters.
VIEW RECLAIMABLE VMS - displays the Reclaim screen, where you can
research and run potential VM reclamation actions.
VIEW OPTIMIZATION - displays the Workload Optimization screen, where
you can optimize workloads based on your policy settings.
VMware, Inc. 920

Table 6-1. Capacity Optimization Options (continued)

Option Description
Cluster Utilization and Time Remaining Overall view of cluster health in the selected data center. You can select a
cluster from the list to display information about that cluster, or use the
options to sort and filter results. The options you choose dictate the data
displayed in the graph.
Sort by:
n Most Constrained: most constrained element
n CPU (allocation or demand)
n Memory (allocation or demand)
n Disk Space (allocation or demand)
Note Demand model is always on and is the default.
Filter: search field.

Show History for: The period before forecasting begins (does not impact
the forecast calculation).
Show Forecast For: The forecast period.
How is the criticality determined? Displays the criticality threshold you set
for this type of object in the Policies Library.
Time Remaining graph Data shows current and trending resource usage and pinpoints when a
given cluster is projected to run out of CPU, memory, or disk space based
on the allocation or demand model (default).
Recommendations Option 1: Reclaim Resources.

Shows resources that can be reclaimed to increase time remaining for the
selected cluster.
RECLAIM RESOURCES - displays the Reclaim screen, where you can
research and run potential VM reclamation actions.
Option 2: Add Capacity.
Shows resources that can be added to increase time remaining.
Note You may see that a data center or cluster is labeled optimized when it has few or no days
remaining before CPU, memory, or disk space is predicted to run out. The seemingly odd
assessment is due to optimization and time remaining being two different measures of data
center and cluster health. A data center can be running at optimum based on policy settings for
balance and consolidation, yet be almost out of resources. It is important to consider both
measures when managing your environment.
Reclaim
Use the Reclaim screen to identify underutilized workloads and reclaim resources from across
your environment.
VMware, Inc. 921

Where You Find Reclaim

From the Home screen, select Reclaim under Optimize Capacity in the left pane. From the Quick
Start screen, select Reclaim in the second-from-left column.
Note Double-click on a data center graphic to display the object details screen for the data
center.
How Reclaim Works

The Capacity Optimization and Reclaim features are tightly integrated functions that enable you
to assess workload status and resource contention in data centers across your environment. You
can determine time remaining until CPU, memory, or storage resources run out, and realize cost
savings when underutilized VMs can be reclaimed and deployed where needed.
When you open the Reclaim page, graphical representations of all the data centers and custom
data centers in your environment appear. By default, they are shown in order of time remaining,
beginning from the upper left, where the most constrained data centers appear. To review the
status of a data center, click the graphic. The area following refreshes to display details about the
selected data center. The How much you can potentially save pane reflects potential capacity
savings and indicates a possible cost savings once you have reclaimed underused or powered
off VMs. The Total Reclaimable Capacity pane gives details of the reclaimable percentages for
CPU, memory, and disk space.
The table at the bottom of the page provides important information about the VMs that offer the
most cost savings. The VMs are listed by Powered VMs, Idle VMs, Snapshots, and Orphaned
Disks. The highest priority heading is at the far left. You can specify what information is included
in your reclaim action. For example, when you click a column heading, the table lists, by data
center and then by VM, the allocated and reclaimable CPUs and memory, respectively. Then, for
example, you can check the box next to one or more VM names and click the EXCLUDE VM(S)
button to keep those VMs from being included in any reclaim action. You can also select VMs to
resize.
Reclamation Settings
Select the gear icon next to the page heading to customize Reclamation Settings. This affects all
data centers. Using the Reclamation Settings, you can exclude, for example all snapshots from
being included in the reclaim action - by deselecting the Snapshots checkbox. Similarly, you can
include or exclude powered-off VMs, idle VMs, and orphaned disks. For more information, see
Reclamation Settings.
Run a Reclaim Action

Run a reclaim action as follows:
1 In the table headings, Select the types of VMs to reclaim.
2 Click the name of a listed cluster to show its VM list.
VMware, Inc. 922

3 Select each VM or snapshot you want to reclaim.
4 Click Delete VM(s) to reclaim their resources.
Table 6-2. Reclaim Options

Option Description
Select a data center. Select a data center from the carousel across the top of the page. All data
refreshes with information for the selected object.
View: Filter results to include data centers, custom data centers, or both. Option
appears when you select ALL DATACENTERS on the upper right.
belongs. Option appears when you select ALL DATACENTERS on the upper
right.
Sort by: Options (Options appear when you select ALL DATACENTERS on the upper
right):
n Alarm clock graphic - list data centers/custom data centers by time
remaining.
n Dollar sign - list data centers/custom data centers by potential cost
savings.
n Scales graphic - list data centers/custom data centers by level of
optimization.
Select data center or ADD NEW CUSTOM Options (Options appear when you select ALL DATACENTERS on the upper
DATACENTER. right):
data refreshes with information for the selected object.
How much you can potentially save. Appears when you select a data center or custom data center from the top
of the screen. Shows the total calculated potential cost savings when you
accept system reclamation recommendations.
Total Reclaimable Capacity Lists potential cost savings for the selected data center when you reclaim
unused resources.
Resource: CPU, memory, or disk space
Reclaimable Capacity: how much capacity is available to reclaim from idle
resources
% Reclaimable: percentage of total CPU, memory, or storage you can
reclaim.
VMware, Inc. 923

Table 6-2. Reclaim Options (continued)

Option Description
Duration older than: Shows idle or powered off VMs that have been idle or powered off for at
least the selected time period: one week, two weeks, or a month.
Table of Potential Cost Savings Tabular representation of the VMs, Idle VMs, Snapshots and Orphaned disks
in the selected data center from which resources can be reclaimed.
Click one of the elements - powered off VMs, idle VMs, and so on - to
refresh the table with data for that element. The table lists the relevant
clusters. To see the VMs hosted in a given cluster, click the chevron to the
left of the cluster name.
Click the check box next to the VMs you want to act on, or click the check
box next to the column heading VM Name to act on all the VMs.
Once you select a VM or VMs, the dimmed options above the table become
visible, as follows.
Exclude VM(s): the selected VMs are excluded from your subsequent
action. Excluding VMs from a reclamation action can reduce the potential
cost savings.
For powered Off VMs:
n DELETE VM(s): deletes the selected VMs.
n EXCLUDE VM(s): excludes the selected VMs.
For idle VMs:
n DELETE VM(s): deletes the selected VMs.
n POWER OFF: powers off the selected VMs.
n EXCLUDE VM(s): excludes the selected VMs.
For Snapshots:
n DELETE SNAPSHOT(s): deletes the selected snapshots.
n EXCLUDE VM(s): excludes the selected snapshot.
SHOW|HIDE EXCLUDED VMS: toggle displays or hides the list of VMs you
previously excluded.
Note By default, calculations for reclaimable resources are based on the

demand model. But if you turn on the allocation model in the policy settings,
the calculations are based on the allocation model.
For Orphaned Disks:

n EXCLUDE DISK(S): exclude the selected disks in the actionable list.
n EXPORT ALL: exports the list of orphaned disks into a CSV file. You
cannot reclaim orphaned disks from the UI. Instead, export the list into a
CSV file and then reclaim the orphaned disks manually.
Note vRealize Operations Manager reports orphaned VMDKs

conservatively. There might be a false positive situation when the used
VMDK is reported as orphaned, particularly if the VMDK is located on a
datastore which is shared among multiple VCs, while not all the VCs are
monitored by vRealize Operations Manager.
Check the accuracy of the VMDK reported as an orphaned disk, and

then perform a reclamation.
SHOW|HIDE EXCLUDED DISKS: toggle displays or hides the list of disks you
previously excluded. Excluded disks are not listed in the exported CSV file.
VMware, Inc. 924

Reclamation Settings
Displays information about powered off VMs, idle VMs, snapshots and orphaned disks. This
information helps to identify the amount of resources that can be reclaimed and provisioned to
other objects in your environment or amount of potential savings that can be done in each
month.
The types of VMs are ranked in the order of their importance in a reclamation action. A VM
whose attributes match more than one VM type is included with the higher-ranking VM type.
Grouping the VMs this way eliminates duplicates during calculations. As an example, powered-off
VMs are ranked higher than snapshots, so that a powered-off VM that also has a snapshot
appears only in the powered-off VM group.
If you exclude a given type of VM, all VMs matching this type are included with the next lower-
ranked group they match. For example, to list all snapshots regardless of whether their
corresponding VMs are powered-off or idle, deselect the Powered-off VMs and Idle VMs check
boxes.
Further, you can configure how long a given class of VMs must be in the designated state -
powered-off, for example, or idle - to be included in the reclamation exercise. You also can
choose to hide the cost savings calculation.
Table 6-3. Reclamation Settings

Property Description
Show Cost Savings Controls whether to show Cost savings in 'Assess Capacity'
and 'Reclaim' pages.
Powered-Off VMs The total storage capacity used is reclaimable. Total

storage reclaimable cost is computed by multiplying
storage rate with storage utilization. The direct cost of VM
is also attributed.
Idle VMs Total CPU, memory, and storage capacity allocated to the
VMs is reclaimable. Resource level costs are computed by
multiplying resource base rate with utilization levels. VMs
that are running cost past 30 days are considered as idle.
Direct cost of VM is also attributed.
VMware, Inc. 925

Table 6-3. Reclamation Settings (continued)

Property Description
Snapshots Snapshots of a VM use storage space and such storage is

reclaimable. The reclaimable cost is computed by
multiplying storage rate with reclaimable storage value.
Orphaned Disks Orphaned disks are VMDKs which are associated with a VM
which are not in inventory, but still available in a datastore.
You can configure the minimum number of days for which
VMDKs not related to any existing VM will be reported as
orphaned and appear under Orphaned Disks in Reclaim
page.
Note You can navigate to Global Settings under

Administration > Management and change the value of the
Orphaned Disks Collection time. At this time that you set,
vRealize Operations Manager checks for orphaned VMDKs
in vSphere Client instances. The settings for Cost
Calculation and Orphaned Disks Collection are
interrelated. The default value for Cost Calculation is 9:00
PM, and the default for Orphaned Disks Collection is 8:00
PM. It is recommended to schedule Cost Calculation after
Orphaned Disks Collection.
What-If Analysis - Workload

You define scenarios that can potentially add workloads to actual data centers. vRealize
Operations Manager models the scenario and calculates whether your desired workload can fit in
the targeted data center or custom data center. You can also define scenarios that can
potentially remove workloads from data centers. vRealize Operations Manager calculates the
time remaining and capacity remaining on the cluster when workloads are removed from the
cluster.
Where You Find What-If Analysis - Workload

From the Home screen, select What-If Analysis under Optimize Capacity in the left pane. From
the What-If Analysis screen, click Add VMs or Remove VMs in the pane titled Workload Planning.
How What-If Analysis - Add Workload Works

This feature of Capacity Optimization enables you to forecast successfully the impact of adding a
workload to an application. By trying various scenarios, you can arrive at an optimum
configuration. Once you select the Workload Planning screen, you can choose the exact data
center or custom data center where you want to locate the new workload. You can even pick a
specific cluster where the workload is to reside.
VMware, Inc. 926

In choosing the profile of your workload, you have two options:
n Configure the workload manually by specifying vCPUs, memory, storage, and expected use
percentage. You have the further option to click Advanced Configuration and specify more
precise characteristics for your workload.
n Use an existing VM or VMs as templates, importing all the attributes of the selected VMs to
your workload scenario. The system allows you to specify how many copies of each selected
VM you want to add to the proposed workload.
When you have set the profile for the new workload, enter the start and end date for the period
when you want the workload to be active. The default is: starting today and ending one year
from today. The system can project scenarios ending up to one year from the current date.
At this point, you can save the scenario to edit or run later on. A list of saved scenarios is
available on the What-If Analysis main page. Otherwise, run the scenario to get the vRealize
Operations Manager analysis and assessment of your plan.
The system lets you know immediately if the proposed workload fits or does not fit in the
suggested location. If it fits, the results list the prime target cluster and any additional possible
locations. The system also projects time remaining before the workload runs out of resources. If
you select scenario details, the system displays a graphic depiction of resource use. For each
attribute value - vCPU, memory, and storage - the amount by which the workload increases the
percentage of total application capacity used is shown against a time line. The graph shows the
existing percentage used in blue and the total of existing usage and added usage as a
percentage of total capacity in green.
If the proposed workload does not fit, the system announces the outcome and provides the
following information:
n How much the added workload reduces the time remaining for the target cluster, for
example, from one year to zero.
n The discrepancy between the space available in the target cluster and what the proposed
workload requires, for example, 100 GB of memory.
n The cost of the workload on the VMware Hybrid Cloud and on the public cloud.
About Clouds
When you run a scenario in What-If Analysis, you get a recommendation based on cost relative
to workload placement on different clouds. This cost-based recommendation varies for different
clouds.
Private Cloud and VMware Cloud on AWS costs are computed based on resource usage levels.
Public clouds, AWS, IBM Cloud, Google Cloud, Microsoft Azure and user-defined cloud costs are
dependent on the selected configuration, that is, for the allocated resources. These public cloud
instances are selected based on the close proximity rule, with simulated resource allocation
values and in some scenarios, the exact configuration match available in the cloud instance list is
not available. Due to this issue, these public cloud costs can be inherently higher in comparison.
VMware, Inc. 927

How What-If Analysis - Remove Workload Works

This feature of Capacity Optimization enables you to forecast successfully the impact of
removing a workload. By trying various scenarios, you can arrive at an optimum configuration.
Once you select the Workload Planning screen, you can choose VMs from the concrete cluster
data center or from the customer data center from which you want to remove the existing
workload.
While removing workloads, you have two options to define the workload:
n Select existing VMs and use their projected utilization to evaluate the impact of removing
workloads.
n Configure the workload manually by specifying the vCPUs, memory, storage, and expected
use percentage.
Enter the start and end date for the period during which you want the workload to be removed.
By default, the start date is today and the end date is one year from today. The end date is left
empty by default. The system can project scenarios ending up to one year from the current date.
Table 6-4. What-If Analysis Workload Page Options

Option Description
Add/Remove VMs Click Add VMs or Remove VMs to create a scenario for adding or removing
workload. When clicked, the command displays the Add Workload or Remove
Workload screen.
Scenario Name In the heading of the Saved Scenarios table. Selecting the check box next to the
name selects all scenarios in the list and turns on the dimmed Delete button.
Scenario type Name of the scenario type. Values are Add Workload, Remove Workload, Add
Capacity, Remove Capacity, and Migrate.
<scenario_name> Name of a saved scenario. Selecting the check box next to a name turns on the
dimmed Run Scenario,Edit, and Delete buttons.
All Filters Use the filter to search for a specific scenario by name or type.
Show Columns Click the small button on the lower left to display the Show Columns dialog box.
You can select up to four columns to display in the table: Scenario Name, Scenario
Type, Date Created, and Scenario Start and End Date.
Add or Remove Workloads

As part of the What-If Analysis function, Workload Planning is the form you use to fill in the
details of your what-if scenario. You choose where to add or remove the workload, configure it
yourself or use an existing VM as a template, and establish a time frame. You also have an
advanced configuration option that lets you define your configuration more precisely.
VMware, Inc. 928

Where You Find Workload Planning

At the What-If Analysis screen, click Add VMs or Remove VMs in the Workload Planning pane.
Table 6-5. Workload Planning Add Options

Option Description
Scenario Name Name of your scenario
Location Where do you want to add the workload? Select from the list of existing data
centers. You can optionally choose the exact cluster where you want the
workload to reside.
Application Profile/Configure Allows you to configure the virtual compute resource, including vCPU, memory,
and storage.
Application Profile/Import Import Displays the Select VMs dialog box where you can choose one or more existing
from existing VM VMs to use as templates for your workload. Once you have made your
selections, you return to this screen to enter the quantity of each chosen VM
you want to incorporate as templates into your workload.
Choose Your Workload: With the Configure radio button selected, you can size your workload by
n CPU defining values for vCPU, memory, and disk space.
n Memory
n Disk space
Expected Utilization Set the projected percentage of total workload capacity you expect to average.
Advanced Configuration Displays a dialog box where you can configure more details for your workload,
such as thin or thick provisioning.
Number of VMs (optional)/Quantity You can optionally choose how many VMs to spread the workload across.
Start Date/End Date Select from pop-up calendars the start and end date for the workload. The end
date cannot be later than one year from the current date.
Run Scenario Click to run the scenario. The system calculates whether it fits into the location
you chose.
Save Save the scenario.
Cancel Cancel the scenario.
Table 6-6. Workload Planning Remove Options

Option Description
Scenario Name Name of your scenario.
Location From where do you want to remove the workload? Select from the list of existing
data centers. You can optionally choose the exact cluster from where you want to
remove the workload.
Application Profile/Configure Allows you to configure the virtual compute resource, including vCPU, memory, and
storage.
After you have configured the scenario, enter the quantity of custom VMs that you
want to remove.
VMware, Inc. 929

Table 6-6. Workload Planning Remove Options (continued)

Option Description
Application Profile/Import Displays the Select VMs dialog box where you can choose one or more existing VMs.
Existing VMs Once you have made your selections, you return to this screen to enter the quantity
of each chosen VM you want to remove from your workload.
Note The recommended limit is 100 VMs as a maximum for workload removal.
Application Profile / Custom: With the Configure radio button selected, you can size your workload by defining
Choose your workload values for vCPU, memory, and disk space.
n CPU
n Memory
n Disk space
Start Date/End Date Select from pop-up calendars the start and end date for the workload. The end date
cannot be later than one year from the current date. You can also leave the end date
blank.
Run Scenario Click to run the scenario. The system calculates the impact on the cluster (time
remaining and capacity remaining) when removing the workload.
You can see the cost of capacity that was freed up. This matches the potential savings if
reclaimable VMs were selected
Select VMs
Use the Select VMs dialog box to choose the VMs whose attributes you want to copy or remove
for your What-If Analysis - Workload scenario.
Where You Find Select VMs

From the What-If Analysis screen, click Add or Remove. When you have entered a Scenario
Name and Location, click the Import from existing VM/Existing VMs radio button, then click
Select VMS. On the left is a selection box that allows you optionally to choose all VMs. To add a
VM to the selected list on the right, double-click on the VM name. Following are the rest of your
options:
Select VMs
Option Description
All Filters Filter options:

VM Name: name of the VM you want.
vCenter: all VMs in this vCenter.
VM Tag: all VMs with this tag.
Custom Group: all VMs in this custom group.
Select all (nnn). A list of all available VMs from which to import or remove characteristics. Double-click the VMs whose
attributes you want to copy or remove.
VMware, Inc. 930

Option Description
Selected List of VMs you selected from RESULTS.
OK When you have selected the VMs you want, click OK to return to the Add Workload or Remove
Workload screen, where your selected VMs are listed.
At the Add Workload or Remove Workload screen, under Application Profile, in the Selected
VMS tale, enter in the Quantity column the number of copies of each VM you selected to add or
remove.
Advanced Configuration - Workload

The Advanced Configuration workspace allows you to more precisely define the attributes of the
workload you want to use in your what-if analysis.
Where You Find Advanced Configuration

From the What-If Analysis screen, click Add. When you have entered a Scenario Name and
Location, click the Configure radio button, then click Advanced Configuration.
Advanced Configuration Options

Option Description
Resource Amount Enter the number of vCPUS, the amount of memory, and the number of storage GBs to include
in your scenario configuration.
Expected Utilization For CPUs, memory, and storage units, respectively, increment the relevant counter to the
percentage of total potential usage you expect the resource to use.
Disk space provisioning Click the radio button for Thin or Thick provisioning.
What-If Analysis - Physical Infrastructure

You define scenarios that can potentially add capacity to actual data centers or remove capacity
from actual data centers. vRealize Operations Manager models the scenario and calculates
whether your desired workload can fit in the targeted data center or custom data center.
Where You Find What-If Analysis - Physical Infrastructure

the Quick Start screen, select Plan in the second-from-left column. Click Add Hosts or Remove
Hosts in the pane titled Physical Infrastructure Planning.
How What-If Analysis Works

This feature of Capacity Optimization enables you to forecast successfully the impact of adding
capacity to your environment or removing capacity from your environment. By trying various
scenarios, you can arrive at an optimum configuration. Once you select the Physical
Infrastructure Planning screen, you can choose where you want to locate the additional capacity
or from where you can remove the existing capacity.
VMware, Inc. 931

In choosing the profile while removing capacity, you can choose a profile only from server types
that already exist in your cluster.
In choosing the profile while adding capacity, you have two options:
n Select a server type from a list of commercially available servers. You can choose from a list
of 1) server types already in your cluster or 2) all server types approved for purchase.
n Configure a custom server manually by specifying CPU attributes, memory, and cost.
When you have set the profile for the new server, enter the number of servers to purchase or
remove and the start and end date for the period when you want the scenario to be active. The
number of servers that you plan to remove is limited by the number of selected server types
available in the selected cluster. The system can project scenarios ending up to one year from
the current date. By default, the starting date is today and the ending date is one year from
today.
The system displays immediately the impact on cluster size of the additional or lesser amount of
CPU and memory, and shows the total cost of adding or removing the specified capacity. The
system also shows whether adding new capacity or removing capacity extends or shrinks the
time remaining before CPU or memory runs out.
As well, the system displays a graphic depiction of resource use. For each attribute value - CPU
and memory - the amount by which the workload increases or decreases the percentage of total
capacity used is shown against a time line.
Table 6-7. What-If Analysis Page Options

Option Description
Physical Infrastructure Click Add Hosts or Remove Hosts to create a scenario for adding or removing capacity.
Planning When clicked, the command displays the Physical Infrastructure Planning screen.
Scenario Name In the heading of the Saved Scenarios table. Checking the box selects all scenarios in the
list and turns on the dimmed Delete button.
<scenario_name> Name of a saved scenario. Selecting the check box next to a name turns on the dimmed
Run Scenario,, Edit, and Delete buttons.
Scenario type Name of the scenario type. Values are Add Workload, Remove Workload, Add Capacity,
Remove Capacity, and Migrate.
All Filters Use the filter to search by name for a specific scenario name or scenario type.
Show Columns Click the small button on the lower left to display the Show Columns dialog box. You can
choose up to four columns to display in the table: Scenario Name, Scenario Type, Date
Created, and Scenario Start and End Date.
VMware, Inc. 932

Add or Remove Physical Infrastructure

As part of the What-If Analysis function, Add or Remove Physical Infrastructure is the form you
use to fill in the details of your what-if scenario. You choose where to add or remove the
capacity, use an existing server type or configure it yourself (when you add capacity), and
establish a time frame.
Where You Find Physical Infrastructure

At the What-If Analysis screen, click Add Hosts or Remove Hosts in the Physical Infrastructure
pane.
Table 6-8. Add Capacity Options

Option Description
Location Where do you want to add capacity? Select from the list of existing data centers,
then choose the cluster where you want the server(s) to reside.
Server Details Clicking Select Server displays the Select Server Type dialog box, where you can
choose a commercial brand server or configure a custom server.
Number of Servers to add: increment the Quantity counter up to the number of
servers you want.
Start Date/End Date Select from pop-up calendars the start and end date for the what-if scenario.
Run Scenario Click to run the scenario. The system calculates the cost of the scenario and
determines any new time remaining number.
The system displays immediately the impact on cluster size of the additional CPU and memory,
and shows the total cost of adding the specified capacity. The system also shows in graphical
form whether adding the new capacity extends the time remaining before CPU or memory runs
out.
Table 6-9. Remove Capacity Options

Option Description
Location From where do you want to remove capacity? Select from the list of existing data
centers, then choose the cluster from where you want to remove the server(s).
Server Details Clicking Select Server displays the Select Server Type dialog box, where you can
choose only the server types that exist in your selected cluster.
The number of servers that you plan to remove is limited by the number of selected
server types available in the selected cluster.
Start Date/End Date Select from pop-up calendars the start and end date for the what-if scenario. You
can choose to keep the end date blank.
Run Scenario Click to run the scenario. The system determines any new time remaining number.
VMware, Inc. 933

Table 6-9. Remove Capacity Options (continued)

Option Description
The system displays the time remaining and the impact on CPU and memory with reduced
capacity. The system also shows in graphical form whether removing capacity decreases the
time remaining before CPU or memory runs out.
You can also see that the cost is based on the original purchase cost.
What-If-Analysis - Migration Planning

You define scenarios that can potentially migrate workloads to a public clouds or to VMware
Cloud on AWS. Use this scenario to determine where to move the workloads. vRealize
Operations Manager models the scenario and calculates the cost and capacity to fit your desired
workload.
Where You Find What-If Analysis - Migration Planning

the Quick Start screen, select Plan in the second-from-left column. Click Select in the pane titled
Migration Planning.
How What-If Analysis - Migration Planning Works

This feature of Capacity Optimization enables you to forecast successfully the impact of
migrating a workload to a public cloud instance such as AWS, IBM Cloud, Microsoft Azure,
Google Cloud or to VMware Cloud on AWS. Once you select the Migration Planning screen,
choose whether you want to run the scenario against a public cloud or VMware Cloud on AWS.
For a public cloud, choose the region where you want to migrate the workload. If the public
clouds listed out of the box do not suit your needs you can also define your own public cloud
and upload a rate card.
In defining the profile of your workload, you have two options:
n Configure the workload manually by specifying vCPUs, memory, storage, and expected use
percentage.
n Use an existing VM or VMs as templates, importing all the attributes of the selected VMs to
your workload scenario. The system allows you to specify how many copies of each selected
VM you want to add to the proposed workload.
When you have set the profile for the migrating workload, run the scenario to get the vRealize
Operations Manager analysis and assessment of your plan. You can also select up to three public
clouds (but not VMware Cloud on AWS) to compare results. Alternatively, you can save the
scenario to edit or run later on. A list of saved scenarios is available in the Saved Scenarios tab
on the What-If analysis page.
VMware, Inc. 934

For a public cloud target, the system lets you know immediately if the workload proposed for
migration fits or does not fit in the suggested location. For example, if you selected AWS and the
workload fits, the results list the Amazon Web Services Assessment, with details of the VMware
Configuration and the AWS Equivalent. If the proposed workload does not fit, an error message
appears: "Unable to identify a matching configuration instance in target location."
If you selected VMware Cloud on AWS for your scenario, the results list the VMware Cloud on
AWS Assessment, with details of the VMware configuration. The system also displays the
resource-use-level cost and the monthly purchase cost for an on-demand subscription. In
addition, the system displays the resource-use-level cost and monthly purchase cost for one-
year and three-year subscriptions.
About Clouds
The system may provide a recommendation based on the cost of placing the workload on
different clouds. This cost-based recommendation varies for different clouds. You can modify the
costs for public clouds by uploading a new rate card.
For VMware Cloud on AWS, the system displays the resource-use-level cost and the monthly
purchase cost for an on-demand subscription, plus those same costs for one-year and three-year
subscriptions.
Public cloud costs are based on the selected configuration, that is, the allocated resources.
The public instance is selected based on the close proximity rule, with simulated resource
allocation values. In some scenarios, an exact configuration match is not available in the list. Due
to this lack of availability, the public cost can be inherently higher in comparison.
Migration Planning
As part of the What-If Analysis function, Migrate is the form you use to fill in the details of your
what-if scenario. You choose where to migrate the workload, then select the region.
Where You Find Migration Planning

At the What-If Analysis screen, click SELECT in the Migrate pane.
When you run a scenario for What If: Migration for Public Clouds (Not VMC), vRealize Operations
Manager might suggest the Public Cloud Instance suitable for the Workload Configuration
selected by you. vRealize Operations Manager also calculates the cost for that Public Cloud's
instance and displays the same.
VMware, Inc. 935

Table 6-10. Migrate Options

Option Description
SCENARIO NAME Name of your scenario
SELECT CLOUDS Where do you want to migrate the workload?

Options:
n AWS
n VMware Cloud on AWS - You can now select regions for VMware Cloud
on AWS.
n IBM Cloud
n Microsoft Azure
n Google Cloud
Note The cloud providers added in the Add Cloud Provider page are also
included in the list.
You can select a maximum of three public clouds at a time for comparison.
Hold the Shift key to select more than one public cloud provider. You cannot
choose VMware Cloud on AWS with other public clouds for comparison
because it has a host-based pricing model, while other clouds are instance
based.
ADD CLOUD PROVIDERS You can add or edit the cloud providers and also edit the rate card of each
individual cloud provider.
APPLICATION PROFILE/Configure Using the Application Profile you can configure the virtual compute resources,
like vCPU, memory, and storage.
Select Your Workload: With the Configure radio button selected, you can size your migrating
n CPU workload by defining values for vCPU, memory, and storage.
n Memory
n Disc Space
APPLICATION PROFILE/Import from Displays the Select VMs button. When selected, displays the Select VMs
existing VM workspace, where you can choose one or more existing VMs to use as
templates for your workload. You can filter VMs by name, tags, vCenter
Server, or custom group.
Once you have made your selections, you return to this screen to enter the
quantity of each chosen VM you want to incorporate as templates into your
workload.
Number of VMs (OPTIONAL)/Quantity You can optionally choose how many VMs to spread the workload across.
RUN SCENARIO Click to run the scenario. The system calculates whether it fits into the location
you chose.
SAVE SAVE the scenario.
CANCEL CANCEL the scenario.
The scenario results are displayed when you run the scenario. For VMware Cloud on AWS
Assessment, when you can edit the configuration from the results page, the change in Reserved
Capacity CPU, Reserved Memory Capacity, Fault Tolerance and RAID Level values are not saved
to the original configuration after you edit it and run the scenario.
VMware, Inc. 936

What-If-Analysis - Hyperconverged Infrastructure

You can perform infrastructure planning by adding Hyperconveged Infrastructure (HCI) nodes to
vSAN enabled clusters and running What-If scenarios. vRealize Operations Manager displays the
time remaining and capacity remaining for CPU, memory and disk space in the scenario results.
Where You Find What-If Analysis - Hyperconverged Infrastructure

the Quick Start screen, select Hyperconverged Infrastructure. To run a What-If scenario click
Add HCI Nodes.
How What-If Analysis - Hyperconverged Infrastructure Works

You can add hyperconverged infrastructure to your VMware vSAN enabled environment and
evaluate the increase in HCI capacity and cost. You can add up to 64 hosts per vSAN cluster. This
number takes into account existing hosts in the cluster. vRealize Operations Manager only lists
vSAN and vXRail clusters in the location property. You can select existing server types from
these locations and change the number of instances of these servers to add to your scenario.
Add HCI Nodes

As part of the What-If Analysis function, Add HCI Nodes is the form you use to fill in the details of
your What-If scenario. When you add an HCI node, you can select an existing server type from
your vSAN and vXRail enabled data center and change the number of instances of this server to
calculate storage, capacity, and time remaining.
Where You Find Workload Planning

At the What-If Analysis page, click Add HCI Nodes in the Hyperconverged Infrastructure pane.
Table 6-11. Add HCI Nodes Options

Option Description
Scenario Name Name of your scenario.
Location Where do you want to add the HCI node? Select from the list of existing data
centers. You can optionally choose the exact cluster where you want the HCI node
to reside.
Server Details Allows you to select an existing server type to calculate capacity, time and storage
remaining based on the number of instances of the server.
Number of servers to add How many instances of the server do you want to add?
Start Date/End Date Select from pop-up calendars the start and end date for the workload. The end date
cannot be later than one year from the current date.
Run Scenario Click to run the scenario. The system calculates whether it fits into the location you
chose.
VMware, Inc. 937

Table 6-11. Add HCI Nodes Options (continued)

Option Description
Custom Profiles in VMware vRealize Operations Manager

A custom profile defines a specific configuration of an object instance. With profiles, you can
determine how many instances of that object can fit in your environment, depending on the
capacity remaining and the configuration of that object instance.
To determine how many instances of the object can fit in your environment, use custom profiles
with projects and scenarios. Enter the profile numbers or pre-populate the values from specific
VMs. Depending on the available capacity in your environment, you can add one or more
instances of the object that the custom profile capacity requirements represent.
To determine how many instances of the custom profile object you can include on the parent
object, you select the parent object and the Capacity tab. The custom profiles appear on the VM
remaining section and indicate how many instances of the object fit in your environment.
Custom Profiles Details and Related Policies

A custom profile defines a specific configuration of an object instance. With profiles, you can
determine how many instances of that object can fit in your environment, depending on the
capacity available and the configuration of that object instance.
How Custom Profiles Work

As with default profiles, custom profiles define metrics configurations for an object. You can
create as many custom profiles as you need for an object type. For example, you might create
one custom profile for a virtual machine that has a memory demand model of 2 GB. You create
another custom profile that has a memory demand model of 4 GB.
vRealize Operations Manager uses custom profiles of virtual machines to calculate the number of
virtual machines that can fit in your environment. The number of virtual machines is based on the
capacity allocation and demand defined in the profile.
Where You Find Custom Profiles

In the menu, click Administration then Configuration > Custom Profiles in the left pane.
VMware, Inc. 938

Table 6-12. Custom Profiles Options

Option Description
Toolbar options Use the toolbar options to manage custom profiles.

n Add Profile. Add a custom profile for a specific object type.
n Edit Profile. Modify the selected profile.
n Delete Profile. Remove the selected profile.
Filtering options Filter the list to display profiles that match the filter you create. You can sort by name,
description, object type, or adapter type. Or, enter filter text in the Quick filter text box.
Profile Details tab Displays the name, description, adapter, object type, and metrics applied to the custom profile.
Custom Profiles Add and Edit Workspace

You can add a custom profile for an object type to determine how many instances of a specific
object can fit in your environment. In the Custom Profiles workspace, you create a custom profile
for an object and define its capacity configuration.
Where You Create or Edit a Custom Profile

To create a custom profile, click Administration in the menu, then Configuration > Custom
Profiles in the left pane. To create a custom profile, click the plus sign. To edit the selected
profile, click the edit icon.
Table 6-13. Custom Profiles Configuration Options

Option Description
Profile Name Descriptive name of the custom profile.
Profile Description Meaningful description for the custom profile. Provide specific information that other
users must know about this profile.
Object Type Basic object for the profile, such as a virtual machine.
Value and Unit Populate the value and unit for the capacity metrics. You can optionally import the
values for an existing VM by clicking the IMPORT FROM EXISTING VM button.
Custom Data Centers in VMware vRealize Operations

Manager
A custom data center is a user-defined container for a group of objects that includes clusters,
hosts, and virtual machines. Custom data centers provide capacity analytics and capacity badge
computations based on the objects it contains. You can use custom data centers to forecast and
analyze the capacity needs for your environment.
When you create a custom data center, you can include multiple cluster objects that span
multiple vCenter Server instances. For example, you might have a production environment that
spans multiple clusters, and you must monitor and manage the performance and capacity of the
entire production environment.
VMware, Inc. 939

After you create your custom data center, you can select it in the list of custom data centers to
display a summary of its health, risk, and efficiency. To access the list of custom data centers,
click Environment on the top menu.
This view displays the top alerts for the data center. To examine the capacity remaining for the
custom data center, click the Capacity tab.
Custom Datacenters List

You can view the list of custom data centers that exist in your environment, and a summary view
of its health, risk, and efficiency. In this view, you can click a custom data center to display the
top alerts that the objects in the custom data center triggered.
How Custom Datacenters Work

In vSphere, a data center serves as a container for objects that a vCenter Server instance
manages. A custom data center is a container that can include objects from multiple vCenter
Server instances.
Custom data centers can contain vCenter Server instances, data centers, clusters, hosts, virtual
machines, and datastores. You can add vSphere object types to a custom data center.
When you add an object, the hierarchical children of that object become part of the custom data
center. An object can belong to multiple custom data centers.
When you create custom data centers, the system runs capacity analytics on the objects in the
custom data center, even if those objects span multiple vCenter Server instances. For example,
you might need to examine the capacity analytics data across multiple clusters, and the multiple
vCenter Server instances that manage those clusters. You do not have to analyze the capacity of
one cluster or one vCenter Server instance at a time. You can create a custom data center, add
all the clusters to it, and see the capacity analysis in a single location.
Where You Find Custom Datacenters

Select Environment in the menu and click the Custom Datacenters tab.
VMware, Inc. 940

Table 6-14. Custom Datacenters Toolbar and Grid Options

Option Description
Toolbar options Use the toolbar options to manage your custom data centers.
n Add New Custom Datacenter. Add a custom data center.
n Edit Custom Datacenter. Modify the selected custom data center.
n Delete Custom Datacenter. Remove the selected custom data center.
n Clone Custom Datacenter. Create a copy of the selected custom data center and customize it
for your needs.
Filter Limit the list of custom data centers to those data centers that match the text that you enter in the
Filter text box.
Data grid Lists the custom data centers in your environment, and displays the health, risk, and efficiency for
each one.
To view a summary of the custom data center health, risk, and efficiency on the Summary tab,
click the custom data center name. To edit, delete, or clone a custom data center, click to the right
of the custom data center name. Then, click the toolbar option.
Custom Datacenters Add and Edit Workspace

A custom data center is an object type that provides capacity analytics and capacity badge
computations based on the objects it contains. You create a custom datacenter object and add
inventory objects to it.
Where You Create or Edit a Custom Datacenter

To create a custom data center, in the menu click Environment, click the Custom Datacenters
tab, and click the plus sign.
To edit a selected custom data center, click to the right of the custom data center name, and
click the edit icon. To use an existing custom data center as a template, click to the right of the
custom data center name, and click the clone icon.
Table 6-15. Add and Edit Custom Datacenters Configuration Options

Option Description
Name Descriptive name of the custom data center.
Description Meaningful description for the custom data center. Provide specific information that other
users must know about this custom data center.
Objects Lists the objects in your environment. Select the check box for each object to add to the
custom data center.
You can add vCenter Server instances, vSphere data centers, vSphere clusters, and ESXi
hosts.
When you add an object, the hierarchical children of that object become part of the custom
data center. An object can belong to multiple custom data centers.
VMware, Inc. 941

Metric, Property, and Alert
Definitions 7
vRealize Operations Manager provides definitions for the metrics, properties, and alerts defined
on objects in your environment.
n Metric Definitions in vRealize Operations Manager
n Alert Definitions in vRealize Operations Manager
n Property Definitions in vRealize Operations Manager
Metric Definitions in vRealize Operations Manager

Metric definitions provide an overview of how the metric value is calculated or derived. If you
understand the metric, you can better tune vRealize Operations Manager to display results that
help you to manage your environment.
vRealize Operations Manager collects data from objects in your environment. Each piece of data
collected is called a metric observation or value. vRealize Operations Manager uses the VMware
vCenter adapter to collect raw metrics. vRealize Operations Manager uses the vRealize
Operations Manager adapter to collect self-monitoring metrics. In addition to the metrics it
collects, vRealize Operations Manager calculates capacity metrics, badge metrics, and metrics to
monitor the health of your system.
All metric definitions are provided. The metrics reported on your system depend on the objects
in your environment. You can use metrics to help troubleshoot problems. See Troubleshooting
with the All Metrics Tab.
Changes in Metric Availability

The CPU Demand of Recommended (%) metric is no longer available in vRealize Operations
Manager version 6.x. To approximate the metric, create a super metric using the following
calculations, and add it to your Views and Reports as needed.
( (CPU|Stress Free Demand (MHz)) × (CPU|Current Size in Unit(s)) ) ÷ ( (CPU|Recommended Size

(vCPUs)) × (CPU|Current Size (MHz)) )
For more information about super metrics, see Configuring Super Metrics .
VMware, Inc. 942

Metrics for vCenter Server Components

vRealize Operations Manager connects to VMware vCenter Server® instances through the
vCenter adapter to collect metrics for vCenter Server components and uses formulas to derive
statistics from those metrics. You can use metrics to troubleshoot problems in your environment.
vCenter Server components are listed in the describe.xml file for the vCenter adapter. The
following example shows sensor metrics for the host system in the describe.xml file.
<ResourceGroup instanced="false" key="Sensor" nameKey="1350" validation="">

<ResourceGroup instanced="false" key="fan" nameKey="1351" validation="">
<ResourceAttribute key="currentValue" nameKey="1360" dashboardOrder="1" dataType="float"
defaultMonitored="false" isDiscrete="false" isRate="false" maxVal="" minVal="" unit="percent"/>
<ResourceAttribute key="healthState" nameKey="1361" dashboardOrder="1" dataType="float"
defaultMonitored="false" isDiscrete="false" isRate="false" maxVal="" minVal="" />
</ResourceGroup>
<ResourceGroup instanced="false" key="temperature" nameKey="1352" validation="">
<ResourceAttribute key="currentValue" nameKey="1362" dashboardOrder="1" dataType="float"
<ResourceAttribute key="healthState" nameKey="1363" dashboardOrder="1" dataType="float"
</ResourceGroup>
</ResourceGroup>
Each ResourceAttribute element includes the name of a metric that appears in the UI and is
documented as a Metric Key.
Table 7-1. Sensor Metrics for Host System Cooling

Metric Key Metric Name Description
Sensor|fan|currentValue Speed Fan speed.
Sensor|fan|healthState Health State Fan health state.
Sensor|temperature|currentValue Temperature Host system temperature.
Sensor|temperature|healthState Health State Host system health state.
vSphere Metrics
vRealize Operations Manager collects CPU use, disk, memory, network, and summary metrics for
objects in the vSphere world.
Capacity metrics can be calculated for vSphere world objects. See Capacity Analytics Generated
Metrics.
CPU Usage Metrics

CPU usage metrics provide information about CPU use.
VMware, Inc. 943

Metric Name Description
CPU|Capacity usage CPU usages as a percent during the interval.

Key: cpu|capacity_usagepct_average
CPU|CPU contention(%) This metric shows the percentage of time the VMs in the ESXi hosts are
unable to run because they are contending for access to the physical CPUs.
The number shown is the average number for all VMs. This number is lower
than the highest number experienced by the VM most impacted by CPU
contention.
Use this metric to verify if the host can serve all its VMs efficiently. Low
contention means that the VM can access everything it demands to run
smoothly. It means that the infrastructure is providing good service to the
application team.
When using this metric, ensure that the number is within your expectation.
Look at both the relative number and the absolute number. Relative means a
drastic change in value, meaning that the ESXi is unable to serve the VMs.
Absolute means that the real value itself is high. Investigate why the number
is high. One factor that impacts this metric is CPU Power Management. If CPU
Power Management clocks down the CPU speed from 3 GHz to 2 GHz, the
reduction in speed is accounted for because it shows that the VM is not
running at full speed.
This metric is calculated in the following way: cpu|capacity_contention / (200
* summary|number_running_vcpus)
Key: cpu|capacity_contentionPct
CPU|Demand (%) This metric shows the amount of CPU resources a virtual machine might use if
there were no CPU contention or CPU limit. This metric represents the
average active CPU load for the past five minutes.
Keep this number below 100% if you set the power management to
maximum.
This metric is calculated in the following way: ( cpu.demandmhz /
cpu.capacity_provisioned)*100
Key: cpu|demandPct
CPU|Demand (MHz) This metric shows the amount of CPU resources a virtual machine might use if
there were no CPU contention or CPU limit.
Key: cpu|demandmhz
CPU|Demand CPU demand in megahertz.

Key: cpu|demand_average
CPU|IO wait IO wait (ms).

Key: cpu|iowait
CPU|number of CPU Sockets Number of CPU sockets.

Key: cpu|numpackages
CPU|Overall CPU Contention Overall CPU contention in milliseconds.

Key: cpu|capacity_contention
CPU|Provisioned Capacity (MHz) Capacity in MHz of the physical CPU cores.

Key: cpu|capacity_provisioned
CPU|Provisioned vCPU(s) Number of provisioned CPU cores.

Key: cpu|corecount_provisioned
VMware, Inc. 944

CPU|Reserved Capacity (MHz) Total CPU capacity reserved by virtual machines.

Key: cpu|reservedCapacity_average
CPU|Usage (MHz) CPU usages, as measured in megahertz, during the interval.

n VM - Amount of actively used virtual CPU. This is the host's view of the
CPU usage, not the guest operating system view.
n Host - Sum of the actively used CPU of all powered on virtual machines
on a host. The maximum possible value is the frequency of the two
processors multiplied by the number of processors. For example, if you
have a host with four 2 GHz CPUs running a virtual machine that is using
4000 MHz, the host is using two CPUs completely: 400 / (4 2000) = 0.50
Key: cpu|usagemhz_average
CPU|Wait Total CPU time spent in wait state. The wait total includes time spent in the
CPU Idle, CPU Swap Wait, and CPU I/O Wait states.
Key: cpu|wait
CPU|Workload (%) Percent of workload

Key: cpu|workload
Memory Metrics
Memory metrics provide information about memory use and allocation.
mem|Contention (%) This metric shows the percentage of time VMs are waiting to access
swapped memory.
Use this metric to monitor ESXi memory swapping. A high value indicates
that the ESXi is running low on memory, and a large amount of memory is
being swapped.
Key: mem|host_contentionPct
mem|Machine Demand (KB) Host memory demand in kilobytes.

Key: mem|host_demand
mem|Provisioned Memory Provisioned host memory in kilobytes.

Key: mem|host_provisioned
mem|Reserved Capacity (KB) Total amount of memory reservation used by powered-on virtual machines
and vSphere services on the host.
Key: mem|reservedCapacity_average
mem|Usable Memory (KB) Usable host memory in kilobytes.

Key: mem|host_usable
mem|Host Usage (KB) Host memory use in kilobytes.

Key: mem|host_usage
mem|Usage/Usable (%) Memory usage as percentage of total configured or available memory.

Key: mem|host_usagePct
mem|Workload (%) Percent of workload.

Key: mem|workload
VMware, Inc. 945

Network Metrics
Network metrics provide information about network performance.
net|Packets Dropped (%) This metric shows the percentage of received and transmitted packets
dropped in the collection interval.
Use this metric to monitor the reliability and performance of the ESXi
network. A high value indicates that the network is not reliable and
performance decreases.
Key: net|droppedPct
net|Usage Rate (KB per second) Sum of the data transmitted and received for all of the NIC instances of the
host or virtual machine.
Key: net|usage_average
net|Workload (%) Percent of workload.

Key: net|workload
Disk Metrics
Disk metrics provide information about disk use.
disk|Total IOPS Average number of commands issued per second during the collection
cycle.
Key: disk|commandsAveraged_average
disk|Usage Rate (KB per second) Average of the sum of the data read and written for all of the disk instances
of the host or virtual machine.
Key: disk|usage_average
disk|Workload (%) Percent of workload.

Key: disk|workload
Summary Metrics
Summary metrics provide information about overall performance.
VMware, Inc. 946

summary|Number of Running Hosts Number of running hosts.

Key: summary|number_running_hosts
summary|Number of Running VMs This metric shows the number of running VMs at a given point in time. The
data is sampled every five minutes.
A large number of running VMs might be a reason for CPU or memory
spikes because more resources are used in the host. The number of running
VMs gives you a good indicator of how many requests the ESXi host must
juggle. Powered off VMs are not included because they do not impact ESXi
performance. A change in the number of running VMs can contribute to
performance problems. A high number of running VMs in a host also means
a higher concentration risk, because all the VMs fail if the ESXi crashes.
Use this metric to look for a correlation between spikes in the running VMs
and spikes in other metrics such as CPU contention, or memory contention.
Key: summary|number_running_vms
summary|Number of Clusters Total number of clusters.

Key: summary|total_number_clusters
summary|Total Number of Datastores Total number of datastores.

Key: summary|total_number_datastores
summary|Number of Hosts Total number of hosts.

Key: summary|total_number_hosts
summary|Number of VMs Total number of virtual machines.

Key: summary|total_number_vms
summary|Total Number of Datacenters Total number of data centers.

Key: summary|total_number_datacenters
summary|Number VCPUs on Powered on Number of virtual CPUs on powered-on virtual machines.

VMs Key: summary|number_running_vcpus
summary|Average Running VM Count per Average running virtual machine count per running host.
Running Host Key: summary|avg_vm_density
vCenter Server Metrics

vRealize Operations Manager collects CPU use, disk, memory, network, and summary metrics for
vCenter Server system objects.
vCenter Server metrics include capacity and badge metrics. See definitions in:
n Capacity Analytics Generated Metrics
n Badge Metrics
CPU Usage Metrics

VMware, Inc. 947

Capacity Usage (%) Percent capacity used.

CPU Contention (%) Percent CPU contention.

Demand (%) Percent demand.

Key: cpu|demandPct
Demand (MHz) CPU utilization level based on descendant virtual machines utilization.
This Includes reservations, limits, and overhead to run the virtual
machines.
Key: cpu|demandmhz
Demand CPU Demand.

IO Wait (ms) IO wait time in milliseconds.

Key: cpu|iowait
Number of CPU Sockets Number of CPU sockets.

Overall CPU Contention (ms) Overall CPU contention in milliseconds.

Provisioned Capacity (MHz) Provisioned capacity in megahertz.

Provisioned vCPU Number of provisioned virtual CPU cores.

Reserved Capacity (MHz) Sum of the reservation properties of the immediate children of the
host's root resource pool.
Usage (MHz) Average CPU use in megahertz.

Wait (ms) CPU time spent on the idle state.

Key: cpu|wait
Overhead Amount of CPU that is overhead.

Key: cpu|overhead_average
Demand without overhead Value of demand excluding any overhead.

Key: cpu|demand_without_overhead
Provisioned Capacity Provisioned capacity (MHz).

Key: cpu|vm_capacity_provisioned
Total Capacity (MHz) Total CPU resources configured on the descendant ESXi hosts.
Usable Capacity (MHz) The usable CPU resources that are available for the virtual machines
after considering reservations for vSphere High Availability (HA) and
other vSphere services.
Key: cpu|haTotalCapacity_average
VMware, Inc. 948

Datastore Metrics
Datastore metrics provide information about the datastore.
Outstanding IO requests OIO for datastore.

Key: datastore|demand_oio
Read IOPS Average number of read commands issued per second during the
collection interval.
Key: datastore|numberReadAveraged_average
Write IOPS Average number of write commands issued per second during the
Key: datastore|numberWriteAveraged_average
Read Throughput (KBps) Amount of data read in the performance interval.

Key: datastore|read_average
Write Throughput (KBps) Amount of data written to disk in the performance interval.
Key: datastore|write_average
Disk Metrics
Total IOPS Average number of commands issued per second during the collection
cycle.
Total Latency (ms) Average amount of time taken for a command from the perspective of the
guest operating system. This metric is the sum of the Kernel Device
Command Latency and Physical Device Command Latency metrics.
Key: disk|totalLatency_average
Total Throughput (KBps) Average of the sum of the data read and written for all the disk instances
of the host or virtual machine.
Total queued outstanding operations Sum of queued operations and outstanding operations.
Key: disk|sum_queued_oio
Max Observed OIO Max observed IO for a disk.

Key: disk|max_observed
Disk Space Metrics

Disk space metrics provide information about disk space use.
VMware, Inc. 949

Total disk space used (KB) Total disk space used on all datastores visible to this object.
Key: diskspace|total_usage
Total disk space (KB) Total disk space on all datastores visible to this object.
Key: diskspace|total_capacity
Total provisioned disk space (KB) Total provisioned disk space on all datastores visible to this object.
Key: diskspace|total_provisioned
Utilization (GB) Storage space used on the connected vSphere Datastores.

Total Capacity (GB) Total storage space available on the connected vSphere datastores.
Memory Metrics
Contention (%) Percent host memory contention.

Machine Demand (KB) Host memory demand in kilobytes.

ESX System Usage Memory usage by the VMkernel and ESX user-level services.
Key: mem|host_systemUsage
Provisioned Memory (KB) Provisioned host memory in kilobytes.

Reserved Capacity (KB) Sum of the reservation properties of the immediate children of the
host's root resource pool.
Usable Memory (KB) Usable host memory in kilobytes.

Host Usage (KB) Host memory use in kilobytes.

Key: mem|host_usage
Usage/Usable (%) Percent host memory used.

Contention (KB) Host contention in kilobytes.

Key: mem|host_contention
VM Overhead (KB) Memory overhead reported by host.

Key: mem|overhead_average
Utilization (KB) Memory utilization level based on the descendant virtual machines
utilization. Includes reservations, limits, and overhead to run the Virtual
Machines.
Key: mem|total_need
VMware, Inc. 950

Total Capacity (KB) Total physical memory configured on descendant ESXi hosts.
Usable Capacity (KB) The usable memory resources available for the virtual machines after
considering reservations for vSphere HA and other vSphere services.
Key: mem|haTotalCapacity_average
Network Metrics
Packets Dropped (%) Percent network packets dropped.

Key: net|droppedPct
Total Throughput (KBps) Sum of the data transmitted and received for all of the NIC instances of
the host or virtual machine.
Packets Received Number of packets received in the performance interval.

Key: net|packetsRx_summation
Packets Transmitted Number of packets transmitted in the performance interval.

Key: net|packetsTx_summation
Received Packets Dropped Number of received packets dropped in the performance interval.
Key: net|droppedRx_summation
Transmitted Packets Dropped Number of transmitted packets dropped in the performance interval.
Key: net|droppedTx_summation
Data Transmit Rate (KBps) Average amount of data transmitted per second.
Key: net|transmitted_average
Data Receive Rate (KBps) Average amount of data received per second.
Key: net|received_average
Summary Metrics
Number of Running Hosts Number of hosts that are on.

Number of Running VMs Number of virtual machines that are on.

Number of Clusters Total number of clusters.

Total Number of Datastores Total number of datastores.

VMware, Inc. 951

Number of Hosts Total number of hosts.

Number of VMs Total number of virtual machines.

Maximum Number of VMs Maximum number of virtual machines.

Key: summary|max_number_vms
Workload Indicator (%) Percent workload indicator.

Key: summary|workload_indicator
Total Number of data centers Total number of data centers.

Key: summary|total_number_datacenters
Number of Cores on Powered On Hosts Number of cores on powered-on hosts.

Key: summary|number_powered_on_cores
Number VCPUs on Powered on VMs Number of virtual CPUs on powered-on virtual machines.
Key: summary|number_running_vcpus
Average Running VM Count per Running Host Average running virtual machine count per running host.
Key: summary|avg_vm_density
VC Query Time (ms) vCenter Server query time in milliseconds.

Key: summary|vc_query_time
Derived Metrics Computation Time (ms) Derived metrics computation time in milliseconds.
Key: summary|derived_metrics_comp_time
Number of objects Number of objects.

Key: summary|number_objs
Number of VC Events Number of vCenter Server events.

Key: summary|number_vc_events
Number of SMS Metrics Number of SMS metrics.

Key: summary|number_sms_metrics
Collector Memory Usage (MB) Collector memory use in megabytes.

Key: summary|collector_mem_usage
Disabled Metrics
The following metrics are disabled in this version of vRealize Operations Manager. This means
that they do not collect data by default.
You can enable these metrics in the Policy workspace. For more information, see Collect Metrics
and Properties Details.
Max Observed Number of Outstanding IO Maximum observed number of outstanding IO operations.

Operations Key: datastore|maxObserved_OIO
Max Observed Read Rate Max observed rate of reading data from the datastore.
Key: datastore|maxObserved_Read
VMware, Inc. 952

Max Observed Reads per second Max observed average number of read commands issued per second
during the collection interval.
Key: datastore|maxObserved_NumberRead
Max Observed Writes per second Max observed average number of write commands issued per second
Key: datastore|maxObserved_NumberWrite
Max Observed Write Rate Max observed rate of writing data from the datastore.
Key: datastore|maxObserved_Write
Max Observed Throughput (KBps) Max observed rate of network throughput.

Key: net|maxObserved_KBps
Max Observed Transmitted Throughput (KBps) Max observed transmitted rate of network throughput.
Key: net|maxObserved_Tx_KBps
Max Observed Received Throughput (KBps) Max observed received rate of network throughput.
Key: net|maxObserved_Rx_KBps
Virtual Machine Metrics

vRealize Operations Manager collects configuration, CPU use, memory, datastore, disk, virtual
disk, guest file system, network, power, disk space, storage, and summary metrics for virtual
machine objects.
Capacity metrics can be calculated for virtual machine objects. See Capacity Analytics Generated
Metrics.
Configuration Metrics for Virtual Machines

Configuration metrics provide information about virtual machine configuration.
Config|Thin Provisioned Disk Thin Provisioned Disk.

Key: config|hardware|thin_Enabled
Config|Number of CPUs Number of CPUs for a Virtual Machine.

From vRealize Operations Manager 6.7 and onwards,
this metric is measured in vCPUs instead of cores.
Key: config|hardware|num_Cpu
Config|Disk Space Disk space metrics.

Key: config|hardware|disk_Space
CPU Usage Metrics for Virtual Machines

VMware, Inc. 953

CPU|IO Wait (ms) CPU time spent waiting for IO.

Key: cpu|iowait
CPU|Overall CPU Contention (ms) The amount of time the CPU cannot run due to
contention.
CPU|Reservation Used CPU Reservation Used.

Key: cpu|reservation_used
CPU|Effective Limit CPU Effective Limit.

Key: cpu|effective_limit
CPU|IO Wait (%) Percentage IO Wait.

Key: cpu|iowaitPct
CPU|Swap wait (%) Percentage swap wait for CPU.

Key: cpu|swapwaitPct
CPU|Wait (%) Percentage of total CPU time spent in wait state.

Key: cpu|waitPct
CPU|System (%) Percentage CPU time spent on system processes.

Key: cpu|systemSummationPct
CPU|Capacity entitlement (MHz) CPU entitlement for the VM after considering all limits.
Key: cpu|capacity_entitlement
CPU|Capacity Demand Entitlement (% Percent capacity demand entitlement.

Key: cpu|capacity_demandEntitlementPct
CPU|CPU Contention (%) CPU contention as a percentage of 20-second

CPU|Total Capacity Provisioned CPU capacity in megahertz.

CPU|Demand (MHz) Total CPU resources required by the workloads on the

virtual machine.
Key: cpu|demandmhz
CPU|Host demand for aggregation Host demand for aggregation.

Key: cpu|host_demand_for_aggregation
CPU|Demand (ms) The total CPU time that the VM might use if there was
no contention.
CPU|Demand (%) CPU demand as a percentage of the provisioned

capacity.
Key: cpu|demandPct
CPU|Usage (%) This metric indicates the percentage of CPU that was
used out of all the CPU that was allocated to the VM.
CPU usage can indicate when the VM is undersized.
Key: cpu|usage_average
VMware, Inc. 954

CPU|Usage (MHz) CPU use in megahertz.

CPU|System (ms) CPU time spent on system processes.

Key: cpu|system_summation
CPU|Ready (%) This metric indicates the percentage of time in which

the VM was waiting in line to use the CPU on the host.
A large ready time for a VM indicates that the VM
needed CPU resources but the infrastructure was busy
serving other VMs. A large ready time might indicate
that the host is trying to serve too many VMs.
Whenever the CPU ready is larger than 10%, you
should check if the host is overloaded, or if the VM
really needs all the resources that were allocated to it.
Key: cpu|readyPct
CPU|Extra (ms) Extra CPU time in milliseconds.

Key: cpu|extra_summation
CPU|Guaranteed (ms) CPU time that is guaranteed for the virtual machine.
Key: cpu|guaranteed_latest
CPU|Co-stop (%) Percentage of time the VM is ready to run, but is

unable to due to co-scheduling constraints.
Key: cpu|costopPct
CPU|Latency Percentage of time the VM is unable to run because it

is contending for access to the physical CPUs.
Key: cpu|latency_average
CPU|Max Limited Time the VM is ready to run, but is not run due to
maxing out its CPU limit setting.
Key: cpu|maxlimited_summation
CPU|Overlap Time the VM was interrupted to perform system

services on behalf of that VM or other VMs.
Key: cpu|overlap_summation
CPU|Run Time the VM is scheduled to run.

Key: cpu|run_summation
CPU|Entitlement Latest Entitlement Latest.

Key: cpu|entitlement_latest
CPU|Total Capacity (MHz) Total CPU capacity allocated to the virtual machine.
CPU Utilization for Resources Metrics for Virtual Machines

CPU utilization for resources metrics provide information about resource CPU use.
VMware, Inc. 955

rescpu|CPU Active (%) (interval) The average active time (actav) or peak active time
(actpk) for the CPU during various intervals.
Key:
rescpu|actav1_latest
rescpu|actpk1_latest
rescpu|CPU Running (%) (interval) The average runtime (runav) or peak active time
(runpk) for the CPU during various intervals.
Key:
rescpu|runav1_latest
rescpu|runpk1_latest
rescpu|CPU Throttled (%) (interval) Amount of CPU resources over the limit that were
refused, average over various intervals.
Key:
rescpu|maxLimited1_latest
rescpu|Group CPU Sample Count The sample CPU count.

Key: rescpu|sampleCount_latest
rscpu|Group CPU Sample Period (ms) The sample period.

Key: rscpu|samplePeriod_latest
Memory Metrics for Virtual Machines

Mem|Host Active (KB) Host active memory use in kilobytes.

Key: mem|host_active
Mem|Contention (KB) Memory contention in kilobytes.

Mem|Contention (%) Percent memory contention.

Mem|Guest Configured Memory (KB) Guest operating system configured memory in

kilobytes.
Key: mem|guest_provisioned
VMware, Inc. 956

Mem|Guest Active Memory (%) Percent guest operating system active memory.
Key: mem|guest_activePct
Mem|Guest Non Pageable Memory (KB) Guest operating system non-pageable memory in
kilobytes.
Key: mem|guest_nonpageable_estimate
Mem|Reservation Used Memory Reservation Used.

Key: mem|reservation_used
Mem|Effective Limit Memory Effective Limit.

Key: mem|effective_limit
Mem|Demand for aggregation Host demand for aggregation.

Key: mem|host_demand_for_aggregation
Mem|Balloon (%) Percentage of total memory that has been reclaimed

via ballooning.
Key: mem|balloonPct
Mem|Guest Usage (KB) This metric shows the amount of memory the VM uses.
Key: mem|guest_usage
Mem|Guest Demand (KB) Guest operating system demand in kilobytes.

Key: mem|guest_demand
Mem|Guest Non Pageable Memory (KB) Guest operating system non-pageable memory in
kilobytes.
Key: mem|host_nonpageable_estimate
Mem|Host Demand (KB) Memory demand in kilobytes.

Key mem|host_demand
Mem|Host Workload Host Workload (%).

Key: host_workload
Mem|Zero (KB) Amount of memory that is all 0.

Key: mem|zero_average
Mem|Swapped (KB) This metric shows how much memory is being

swapped. Meaning, the amount of unreserved memory
in kilobytes.
Key: mem|swapped_average
Mem|Swap Target (KB) Amount of memory that can be swapped in kilobytes.

Key: mem|swaptarget_average
Mem|Swap In (KB) Swap-in memory in kilobytes.

Key: mem|swapin_average
Mem|Balloon Target (KB) Amount of memory that can be used by the virtual
machine memory control.
Key: mem|vmmemctltarget_average
Mem|Consumed (KB) Amount of host memory consumed by the virtual

machine for guest memory in kilobytes.
Key: mem|consumed_average
VMware, Inc. 957

Mem|Overhead (KB) Memory overhead in kilobytes.

Mem|Swap In Rate (KBps) Rate at which memory is swapped from disk into active
memory during the interval.
Key: mem|swapinRate_average
Mem|Active Write (KB) Active writes in kilobytes.

Key: mem|activewrite_average
Mem|Compressed (KB) Compressed memory in kilobytes.

Key: mem|compressed_average
Mem|Compression Rate (KBps) Compression rate in kilobytes per second.

Key: mem|commpressionRate_average
Mem|Decompression Rate (KBps) Decompression rate in kilobytes per second.

Key: mem|decompressionRate_average
Mem|Overhead Max (KB) Maximum overhead in kilobytes.

Key: mem|overheadMax_average
Mem|Zip Saved (KB) Zip-saved memory in kilobytes.

Key: mem|zipSaved_latest
Mem|Zipped (KB) Zipped memory in kilobytes.

Key: mem|zipped_latest
Mem|Entitlement Amount of host physical memory the VM is entitled to,

as determined by the ESX schedule.
Key: mem|entitlement_average
Mem|Capacity Contention Capacity Contention.

Key: mem|capacity.contention_average
Mem|Swap In Rate from Host Cache Rate at which memory is being swapped from host
cache into active memory.
Key: mem|llSwapInRate_average
Mem|Swap Out Rate to Host Cache Rate at which memory is being swapped to host cache
from active memory.
Key: mem|llSwapOutRate_average
Mem|Swap Space Used in Host Cache Space used for caching swapped pages in the host
cache.
Key: mem|llSwapUsed_average
Mem|Overhead Touched Actively touched overhead memory (KB) reserved for

use as the virtualization overhead for the VM.
Key: mem|overheadTouched_average
Memory|VM Memory Demand (kb) Key: mem|vmMemoryDemand
Memory|Consumed (%) Key: mem|consumedPct
VMware, Inc. 958

Mem|Utilization (KB) Memory used by the virtual machine. Reflects the guest
OS memory required for vSphere and certain VMTools
versions or for virtual machine consumption.
Key: mem|vmMemoryDemand
Mem|Total Capacity (KB) Memory resources allocated to powered on virtual

machine.
Datastore Metrics for Virtual Machines

Datastore metrics provide information about datastore use.
Datastore|Total IOPS Average number of commands issued per second

Key: datastore|commandsAveraged_average
Datastore|Outstanding IO requests OIO for datastore.

Datastore|Number of Outstanding IO Operations Number of outstanding IO operations.

Key: datastore|oio
Datastore|Demand Datastore demand.

Key: datastore|demand
Datastore|Total Latency (ms) The average amount of time taken for a command from
the perspective of a Guest OS. This is the sum of Kernel
Command Latency and Physical Device Command
Latency.
Key: datastore|totalLatency_average
Datastore|Total Throughput (KBps) Usage Average (KBps).

Key: datastore|usage_average
Datastore|Used Space (MB) Used space in megabytes.

Key: datastore|used
Datastore|Not Shared (GB) Space used by VMs that is not shared.

Key: datastore|notshared
Datastore|Read IOPS Average number of read commands issued per second

Datastore|Write IOPS Average number of write commands issued per second

Datastore|Read Throughput (KBps) This metric shows the amount of data that the VM
reads to the datastore per second.
VMware, Inc. 959

Datastore|Read Latency (ms) Average amount of time for a read operation from the
datastore. Total latency = kernel latency + device
latency.
Key: datastore|totalReadLatency_average
Datastore|Write Latency (ms) Average amount of time for a write operation to the
latency.
Key: datastore|totalWriteLatency_average
Datastore|Write Throughput (KBps) This metric shows the amount of data that the VM
writes to the datastore per second.
Datastore|Highest Latency Highest Latency.

Key: datastore|maxTotalLatency_latest
Datastore|Total Latency Max Total Latency Max (ms).

Key: datastore|totalLatency_max
Disk Metrics for Virtual Machines

Disk|Read IOPS Average number of read commands issued per second

Key: disk|numberReadAveraged_average
Disk|Write IOPS Average number of write commands issued per second

Key: disk|numberWriteAveraged_average
Disk|Total IOPS Average number of commands issued per second

Disk|Total Throughput (KBps) Use rate in kilobytes per second.

Disk|I/O Usage Capacity This metric is a function of storage|usage_average and

disk|workload. Storage|usage_average is an average
over all storage devices. This means that disk|
usage_capacity is not specific to the selected VM or the
host of the VM.
Key: disk|usage_capacity
Disk|Number of Outstanding IO Operations Number of outstanding IO operations.

Key: disk|diskoio
Disk|Queued Operations Queued operations.

Key: disk|diskqueued
Disk|Demand (%) Percent demand.

Key: disk|diskdemand
VMware, Inc. 960

Disk |Total Queued Outstanding Operations Sum of Queued Operation and Outstanding Operations.
Key: disk |sum_queued_oio
Disk|Max Observed OIO Max Observed IO for a disk.

Disk|Read Throughput KBps) Amount of data read in the performance interval.

Key: disk|read_average
Disk|Write Throughput (KBps) Amount of data written to disk in the performance

interval.
Key: disk|write_average
Disk|Read Requests Number of times data was read from the disk in the
defined interval.
Key: disk|numberRead_summation
Disk|Write Requests Number of times data was written to the disk in the
defined interval.
Key: disk|numberWrite_summation
Disk|Bus Resets The number of bus resets in the performance interval.

Key: disk|busResets_summation
Disk|Commands Issued The number of disk commands issued in the

performance interval.
Key: disk|commands_summation
Disk|Commands canceled The number of disk commands canceled in the

Key: disk|commandsAborted_summation
Disk|Highest Latency Highest latency.

Key: disk|maxTotalLatency_latest
Disk|SCSI Reservation Conflicts SCSI Reservation Conflicts.

Key: disk|scsiReservationConflicts_summation
Disk|Read Latency (ms) The average amount of time taken for a read from the
perspective of a Guest OS. This is the sum of Kernel
Read Latency and Physical Device Read Latency.
Key: disk|totalReadLatency_average
Disk|Write Latency (ms) The average amount of time taken for a write from the
perspective of a Guest OS. This is the sum of Kernel
Write Latency and Physical Device Write Latency.
Key: disk|totalWriteLatency_average
Disk|Total Latency (ms) The average amount of time taken for a command from
Latency.
Virtual Disk Metrics for Virtual Machines

Virtual disk metrics provide information about virtual disk use.
VMware, Inc. 961

VirtualDisk|Usage Average virtual disk usage as a percentage.

Key: virtualDisk|usage
VirtualDisk|Total Latency Total latency.

Key: virtualDisk|totalLatency
VirtualDisk|Total IOPS Average number of commands per second.

Key: virtualDisk|commandsAveraged_average
VirtualDisk|Read Requests Average number of read commands issued per second

to the virtual disk during the collection interval.
Key: virtualDisk|numberReadAveraged_average
VirtualDisk|Write Requests Average number of write commands issued per second

to the virtual disk during the collection interval.
Key: virtualDisk|numberWriteAveraged_average
VirtualDisk|Read Throughput (KBps) Rate of reading data from the virtual disk in kilobytes
per second.
Key: virtualDisk|read_average
VirtualDisk|Read Latency (ms) Average amount of time for a read operation from the
virtual disk. Total latency = kernel latency + device
latency.
Key: virtualDisk|totalReadLatency_average
VirtualDisk|Write Latency (ms) Average amount of time for a write operation to the
virtual disk. Total latency = kernel latency + device
latency.
Key: virtualDisk|totalWriteLatency_average
VirtualDisk|Write Throughput (KBps) Rate of writing data from the virtual disk in kilobytes per
second.
Key: virtualDisk|write_average
VirtualDisk|Bus Resets The number of bus resets in the performance interval.

Key: virtualDisk|busResets_summation
VirtualDisk|Commands Aborted The number of disk commands canceled in the

Key: virtualDisk|commandsAborted_summation
VirtualDisk|Read Load Storage DRS virtual disk metric read load.

Key: virtualDisk|readLoadMetric_latest
VirtualDisk|Outstanding Read Requests Average number of outstanding read requests to the

virtual disk.
Key: virtualDisk|readOIO_latest
VirtualDisk|Write Load Storage DRS virtual disk write load.

Key: virtualDisk|writeLoadMetric_latest
VirtualDisk|Outstanding Write Requests Average number of outstanding write requests to the

virtual disk.
Key: virtualDisk|writeOIO_latest
VMware, Inc. 962

VirtualDisk|Number of Small Seeks Small Seeks.

Key: virtualDisk|smallSeeks_latest
VirtualDisk|Number of Medium Seeks Medium Seeks.

Key: virtualDisk|mediumSeeks_latest
VirtualDisk|Number of Large Seeks Large Seeks.

Key: virtualDisk|largeSeeks_latest
VirtualDisk|Read Latency (microseconds) Read Latency in microseconds.

Key: virtualDisk|readLatencyUS_latest
VirtualDisk|Write Latency (microseconds) Write Latency in microseconds.

Key: virtualDisk|writeLatencyUS_latest
VirtualDisk|Average Read request size Read IO size.

Key: virtualDisk|readIOSize_latest
VirtualDisk|Average Write request size Write IO size.

Key: virtualDisk|writeIOSize_latest
Virtual Disk|Outstanding IO requests (OIOs) Key: virtualDisk|vDiskOIO
Virtual Disk|Used Disk Space (GB) Key: virtualDisk|actualUsage
Guest File System Metrics for Virtual Machines

Guest file system metrics provide information about guest file system capacity and free space.
The data for these metrics is only displayed when VMware Tools has been installed on the virtual
machines. If VMware Tools is not installed, features dependent on these metrics, including
capacity planning for virtual machine guest storage, will not be available.
Guest file system|Guest File System Capacity (MB) Total capacity on guest file system in megabytes.
Key: guestfilesystem|capacity
Guest file system|Guest File System Free (MB) Total free space on guest file system in megabytes.
Key: guestfilesystem|freespace
Guest file system|Guest File System Usage (%) Percent guest file system.
Key: guestfilesystem|percentage
Guest file system|Guest File System Usage Total usage of guest file system.
From vRealize Operations Manager 6.7 and onwards,
this metric is measured in GBs.
Key: guestfilesystem|usage
Guest file system|Total Guest File System Capacity (GB) This metric displays the amount of disk space allocated
for the VM.
Correlate other metrics with this metric to indicate if
changes occur in the disk space allocation for the VM.
Key: guestfilesystem|capacity_total
VMware, Inc. 963

Guest file system|Total Guest File System Usage (%) This metric displays the amount of display space being
used out of the total allocated disk space.
Use his metric to track if the overall usage is stable, or if
it reaches the limits. You should avoid having VMs with
a disk space usage of >95% since this might impact
your system.
Key: guestfilesystem|percentage_total
Guest file system|Total Guest File System Usage Total usage of guest file system.
Key: guestfilesystem|usage_total
Guest file system|Utilization (GB) Storage space used by the Guest OS file systems. The
disk space is available only if VM tools are installed and
running. If the VM tools are not installed, the disk space
capacity is not applicable.
Key: guestfilesystem|usage_total
Guest file system|Total Capacity (GB) Storage space used by the Guest OS file systems. The
disk space is available only if VM tools are installed and
running. If the VM tools are not installed, the disk space
capacity is not applicable.
Key: guestfilesystem|capacity_total
Network Metrics for Virtual Machines

Net|Total Throughput (KBps) The sum of the data transmitted and received for all the
NIC instances of the host or virtual machine.
Net|Data Transmit Rate (KBps) This metric shows the rate of data being sent by the VM
per second.
Net|Data Receive Rate (KBps) This metric shows the rate of data received by the VM
per second.
Net|Packets per second Number of packets transmitted and received per

second.
Key: net|PacketsPerSec
Net|Packets Received Number of packets received in the performance

interval.
Net|Packets Transmitted Number of packets transmitted in the performance

interval.
VMware, Inc. 964

Net|Transmitted Packets Dropped This metric shows the number of transmitted packets
dropped in the collection interval
Key: net|dropppedTx_summation
Net|Packets Dropped (%) Percentage of packets dropped.

Key: net|droppedPct
Net|Packets Dropped Number of packets dropped in the performance

interval.
Key: net|dropped
Net|Broadcast Packets Transmitted Number of broadcast packets transmitted during the

sampling interval.
Key: net|broadcastTx_summation
Net|Broadcast Packets Received Number of broadcast packets received during the

sampling interval.
Key: net|broadcastRx_summation
Net|Multicast Packets Received Number of multicast packets received.

Key: net|multicastRx_summation
Net|Multicast Packets Transmitted Number of multicast packets transmitted.

Key: net|multicastTx_summation
Net|VM to Host Data Transmit Rate Average amount of data transmitted per second
between VM and host.
Key: net|host_transmitted_average
Net|VM to Host Data Receive Rate Average amount of data received per second between
VM and host.
Key: net|host_received_average
Net|VM to Host Usage Rate The sum of the data transmitted and received for all the
NIC instances between VM and host.
Key: net|host_usage_average
System Metrics for Virtual Machines

System metrics for virtual machines provide general information about the virtual machine, such
as its build number and running state.
Sys|Powered ON Powered on virtual machines. 1 if powered on, 0 if

powered off, -1 if unknown
Key: sys|poweredOn
Sys|OS Uptime Total time elapsed, in seconds, since last operating

system start.
Key: sys|osUptime_latest
Power Metrics for Virtual Machines

Power metrics provide information about power use.
VMware, Inc. 965

Power|Energy (Joule) Energy use in joules.

Key: power|energy_summation
Power|Power (Watt) Average power use in watts.

Key: power|power_average
Disk Space Metrics for Virtual Machines

Diskspace|Provisioned Space (GB) Provisioned space in gigabytes.

Key: diskspace|provisioned
Diskspace|Provisioned Space for VM Provisioned space for VM.

Key: diskspace|provisionedSpace
Diskspace|Snapshot Space (GB) Space used by snapshots.

Key: diskspace|snapshot
Diskspace|Virtual machine used (GB) Space used by virtual machine files in gigabytes.
Key: diskspace|perDsUsed
Diskspace|Active not shared Unshared disk space used by VMs excluding snapshot.
Key: diskspace|activeNotShared
Storage Metrics for Virtual Machines

Storage metrics provide information about storage use.
Storage|Total IOPS Average number of commands issued per second

Key: storage|commandsAveraged_average
Storage|Contention (%) Percent contention.

Key: storage|contention
Storage|Read Throughput (KBps) Read throughput rate in kilobytes per second.

Key: storage|read_average
Storage|Read IOPS Average number of read commands issued per second

Key: storage|numberReadAveraged_average
Storage|Total Latency (ms) Total latency in milliseconds.

Key: storage|totalLatency_average
Storage|Total Usage (KBps) Total throughput rate in kilobytes per second.

Key: storage|usage_average
VMware, Inc. 966

Storage|Write Throughput (KBps) Write throughput rate in kilobytes per second.

Key: storage|write_average
Storage|Write IOPS Average number of write commands issued per second

Key: storage|numberWriteAveraged_average
Summary Metrics for Virtual Machines

Summary|Running Number of running virtual machines.

Key: summary|running
Summary|Desktop Status Horizon view desktop status.

Key: summary|desktop_status
Reclaimable Idle Boolean flag indicating whether VM is considered as

reclaimable because it is in Idle state.
Key: summary|idle
Reclaimable Powered Off Boolean flag indicating whether VM is considered as

reclaimable because it is in powered off state.
Key: summary| poweredOff
Reclaimable Snapshot Space (GB) Reclaimable snapshot space.

Key: summary| snapshotSpace
Cost Metrics for Virtual Machines

Cost metrics provide information about the cost.
Monthly VM OS Labor Cost Month to date operating system labor cost of the virtual
machine.
Key: cost|osLaborTotalCost
Monthly VM Projected Total Cost Virtual machine cost projected for full month.
Key: Cost|monthlyProjectedCost
Monthly VM VI Labor Cost Month to date virtual infrastructure labor cost of the virtual
machine.
Key: cost|viLaborTotalCost
MTD VM Compute Total Cost Total compute cost (including CPU and memory) of the
virtual machine.
Key: cost|compTotalCost
MTD VM CPU Cost Month to Date Virtual Machine CPU Cost. It is based on
utilization. The more the VM uses, the higher its cost.
Key: cost|cpuCost
VMware, Inc. 967

MTD VM Direct Cost Month to date direct cost (comprising of OS labor, VI labor
and any windows desktop instance license) of the virtual
machine. It also comprises of the additional and application
cost of the virtual machine.
Key: cost|vmDirectCost
MTD VM Memory Cost Month to Date Memory Cost of Virtual Machine. It is based
on utilization. The more the VM uses, the higher its cost.
Key: cost|memoryCost
MTD VM Storage Cost Month to date storage cost of the virtual machine.
Key: cost|storageCost
MTD VM Total Cost Month to date total compute cost (including CPU and
memory) of the virtual machine.
Key: cost|monthlyTotalCost
Potential Savings Reclaimable cost of VM for being either idle, powered-off,

or having snapshots.
Key: cost|reclaimableCost
Cost|Allocation|MTD VM CPU Cost (Currency) Month to Date Virtual Machine CPU Cost computed based
on resource overcommit ratio set for its parent cluster in
policy.
cost|allocation|allocationBasedCpuMTDCost
Cost|Allocation|MTD VM Memory Cost (Currency) Month to Date Virtual Machine CPU Memory cost
computed based on resource overcommit ratio set for its
parent cluster in policy.
cost|allocation|allocationBasedMemoryMTDCost
Cost|Allocation|MTD VM Storage Cost (Currency) Month to Date Virtual Machine CPU Storage cost computed
based on resource overcommit ratio set for its parent
cluster (or datastore cluster) in policy.
cost|allocation|allocationBasedStorageMTDCost
Cost|Allocation|MTD VM Total Cost (Currency) Month to Date Virtual Machine Total Cost is the summation
of the CPU Cost, Memory Cost, Storage Cost and Direct
Cost, based on overcommit ratios set in policy for the
parent cluster or datastore cluster.
cost|allocation|allocationBasedTotalCost
Disabled Metrics
CPU|50% of Recommended number of vCPUs to Remove This metric is superseded by the capacity engine.
cpu|numberToRemove50Pct
CPU|Capacity entitlement (mhz) cpu|capacity_entitlement
VMware, Inc. 968

CPU|Co-stop (msec) Use the Co-Stop (%) metric instead of this metric.
cpu|costop_summation
CPU|Demand Over Capacity (mhz) cpu|demandOverCapacity
CPU|Demand Over Limit (mhz) Use Contention (%) metric instead of this metric.
cpu|demandOverLimit
CPU|Dynamic entitlement cpu|dynamic_entitlement
CPU|Estimated entitlement cpu|estimated_entitlement
CPU|Idle (%) cpu|idlePct
CPU|Idle (msec) cpu|idle_summation
CPU|IO Wait (msec) cpu|iowait
CPU|Normalized Co-stop (%) Use the Co-Stop (%) metric instead of this metric.
cpu|perCpuCoStopPct
CPU|Provisioned vCPU(s) (Cores) cpu|corecount_provisioned
CPU|Ready (msec) Choose the Use Ready (%) metric instead of this metric.
cpu|ready_summation
CPU|Recommended Size Reduction (%) cpu|sizePctReduction
CPU|Swap Wait (msec) cpu|swapwait_summation
CPU|Total Wait (msec) cpu|wait
CPU|Used (msec) cpu|used_summation
CPU|Wait (msec) cpu|wait_summation
Datastore I/O|Max Observed Number of Outstanding IO datastore|maxObserved_OIO

Operations
Datastore I/O|Max Observed Read Rate (kbps) datastore|maxObserved_Read
Datastore I/O|Max Observed Reads per second datastore|maxObserved_NumberRead
Datastore I/O|Max Observed Write Rate (kbps) datastore|maxObserved_Write
Datastore I/O|Max Observed Writes per second datastore|maxObserved_NumberWrite
Disk Space|Not Shared (gb) diskspace|notshared
Disk Space|Number of Virtual Disks diskspace|numvmdisk
Disk Space|Shared Used (gb) diskspace|shared
Disk Space|Total disk space used (gb) diskspace|total_usage
Disk Space|Total disk space (gb) diskspace|total_capacity
Disk Space|Virtual Disk Used (gb) diskspace|diskused
Guest File System stats|Total Guest File System Free (gb) guestfilesystem|freespace_total
Guest|Active File Cache Memory (kb) guest|mem.activeFileCache_latest
Guest|Context Swap Rate per second guest|contextSwapRate_latest
Guest|Huge Page Size (kb) guest|hugePage.size_latest
VMware, Inc. 969

Guest|Page Out Rate per second guest|page.outRate_latest
Guest|Total Huge Pages guest|hugePage.total_latest
Memory|50% of Reclaimable Memory Capacity (gb) This metric is superseded by the capacity engine.
mem|wasteValue50PctInGB
Memory|Balloon (kb) mem|vmmemctl_average
Memory|Demand Over Capacity mem|demandOverCapacity
Memory|Demand Over Limit mem|demandOverLimit
Memory|Granted (kb) mem|granted_average
Memory|Guest Active (kb) mem|active_average
Memory|Guest Dynamic Entitlement (kb) mem|guest_dynamic_entitlement
Memory|Guest Workload (%) mem|guest_workload
Memory|Host Demand with Reservation (kb) mem|host_demand_reservation
Memory|Host Dynamic Entitlement (kb) mem|host_dynamic_entitlement
Memory|Host Usage (kb) mem|host_usage
Memory|Host Workload (%) mem|host_workload
Memory|Latency (%) Use the Memory Contention (%) metric instead of this
metric.
mem|latency_average
Memory|Numa Local Latest (kb) mem|numa.local_latest
Memory|Numa Locality Average (%) mem|numa.locality_average
Memory|Numa Migrations Latest mem|numa.migrations_latest
Memory|Numa Remote Latest (kb) mem|numa.remote_latest
Memory|Recommended Size Reduction (%) mem|sizePctReduction
Memory|Shared (kb) mem|shared_average
Memory|Swap Out Rate (kbps) mem|swapoutRate_average
Memory|Usage (%) mem|usage_average
Memory|Estimated entitlement mem|estimated_entitlement
Network I/O|Data Receive Demand Rate (kbps) net|receive_demand_average
Network I/O|Data Transmit Demand Rate (kbps) net|transmit_demand_average
Network I/O|VM to Host Data Receive Rate (kbps) net|host_received_average
Network I/O|VM to Host Data Transmit Rate (kbps) net|host_transmitted_average
Network I/O|VM to Host Max Observed Received Throughput net|host_maxObserved_Rx_KBps

(kbps)
Network I/O|VM to Host Max Observed Throughput (kbps) net|host_maxObserved_KBps
Network I/O|VM to Host Max Observed Transmitted net|host_maxObserved_Tx_KBps

Throughput (kbps)
VMware, Inc. 970

Network I/O|VM to Host Usage Rate (kbps) net|host_usage_average
Network|bytesRx (kbps) net|bytesRx_average
Network|bytesTx (kbps) net|bytesTx_average
Network|Demand (%) Use absolute numbers instead of this metric.

net|demand
Network|I/O Usage Capacity net|usage_capacity
Network|Max Observed Received Throughput (kbps) net|maxObserved_Rx_KBps
Network|Max Observed Throughput (kbps) net|maxObserved_KBps
Network|Max Observed Transmitted Throughput (kbps) net|maxObserved_Tx_KBps
Network|Packets Received per second net|packetsRxPerSec
Network|Packets Transmitted per second net|packetsTxPerSec
Network|Received Packets Dropped net|droppedRx_summation
Storage|Demand (kbps) storage|demandKBps
Storage|Read Latency (msec) storage|totalReadLatency_average
Storage|Write Latency (msec) storage|totalWriteLatency_average
Summary|CPU Shares summary|cpu_shares
Summary|Memory Shares summary|mem_shares
Summary|Number of Datastores summary|number_datastore
Summary|Number of Networks summary|number_network
Summary|Workload Indicator summary|workload_indicator
System|Build Number sys|build
System|Heartbeat sys|heartbeat_summation
System|Product String sys|productString
System|Uptime (sec) sys|uptime_latest
System|vMotion Enabled vMotion should be enabled for all. It is not necessary to

track all VMs every five minutes.
sys|vmotionEnabled
Host System Metrics

vRealize Operations Manager collects many metrics for host systems, including CPU use,
datastore, disk, memory, network, storage, and summary metrics for host system objects.
Capacity metrics can be calculated for host system objects. See Capacity Analytics Generated
Metrics.
Configuration Metrics for Host Systems

Configuration metrics provide information about host system configuration.
VMware, Inc. 971

Configuration|Failover Hosts Failover Hosts.

Key: configuration|dasConfig|admissionControlPolicy|
failoverHost
Hardware Metrics for Host Systems

Hardware metrics provide information about host system hardware.
Hardware|Number of CPUs Number of CPUs for a host.

Key: hardware|cpuinfo|num_CpuCores
CPU Usage Metrics for Host Systems

CPU|Capacity Usage (%) Percent CPU capacity used.

CPU|Usage (%) Average CPU usage as a percentage.

Key: cpu|usage_average
CPU|CPU Contention (%) This metric indicates the percentage of time the virtual
machines in the ESXi hosts are unable to run because they
are contending for access to the physical CPU(s). This is
the average number of all VMs. Naturally, the number will
be lower than the highest number experienced by the
worst hit VM (a VM that suffers the highest CPU
contention).
Use this metric to verify if the host is able to serve all of its
VMs well.
When using this metric, ensure the number is within your
expectation. The metric is affected by several factors so
you need to watch both relative numbers and absolute
numbers. Relative means a drastic change in value. This
indicates that the ESXi is unable to service its VMs.
Absolute means that the real value is high and should be
checked. One factor that impacts the CPU contention
metric is CPU Power Management. If CPU Power
Management clocks down the CPU speed from 3 GHz to 2
GHz that reduction in speed is taken into consideration.
This is because the VM is not running at full speed.
VMware, Inc. 972

CPU|Demand (%) This metric shows the percentage of CPU resources all the
VMs would use if there was no CPU contention or any CPU
limits set.
It represents the average active CPU load for the past five
minutes.
Keep the number of this metric below 100% if you set
Power Management to Maximum.
Key: cpu|demandPct
CPU|Demand (MHz) CPU demand in megahertz. CPU utilization level based on

descendant Virtual Machines utilization. Includes limits and
overhead to run Virtual Machines, but not reservations.
Key: cpu|demandmhz
CPU|IO Wait (ms) IO wait time in milliseconds.

Key: cpu|iowait
CPU|Number of CPU Sockets Number of CPU sockets.

CPU|Overall CPU Contention (ms) Overall CPU contention in milliseconds.

CPU|Provisioned Capacity (MHz) Capacity in MHz of the physical CPU cores.

CPU|Provisioned virtual CPUs Provisioned virtual CPUs.

CPU|Total Wait CPU time spent in idle state.

Key: cpu|wait
CPU|Demand CPU demand.

CPU|Usage (MHz) CPU use in megahertz.

CPU|Reserved Capacity (MHz) The sum of the reservation properties of the (immediate)
children of the host's root resource pool.
CPU|Total Capacity (MHz) Total CPU capacity in megahertz. Amount of CPU

resources configured on the ESXi hosts.
CPU|Overhead (KB) Amount of CPU overhead.

CPU|Demand without overhead Value of demand excluding any overhead.

CPU|Core Utilization (%) Percent core utilization.

Key: cpu|coreUtilization_average
CPU|Utilization(%) Percent CPU utilization.

Key: cpu|utilization_average
VMware, Inc. 973

CPU|Core Utilization (%) Core Utilization.

Key: cpu|coreUtilization_average
CPU|Utilization (%) Utilization.

Key: cpu|utilization_average
CPU|Co-stop (ms) Time the VM is ready to run, but is unable to due to co-
scheduling constraints.
Key: cpu|costop_summation
CPU|Latency (%) Percentage of time the VM is unable to run because it is

contending for access to the physical CPUs.
Key: cpu|latency_average
CPU|Ready (ms) Time spent in ready state.

Key: cpu|ready_summation
CPU|Run (ms) Time the virtual machine is scheduled to run.

Key: cpu|run_summation
CPU|Swap wait (ms) Amount of time waiting for swap space.

Key: cpu|swapwait_summation
CPU|Wait (ms) Total CPU time spent in wait state.

Key: cpu|wait_summation
CPU|Provisioned Capacity Provisioned capacity (MHz).

CPU|Active Host Load For Balance (Long Term) Active Host Load For Balance (Long Term).
Key: cpu|acvmWorkloadDisparityPcttive_longterm_load
CPU|Active Host Load For Balance (Short Term) Active Host Load For Balance (Short Term).
Key: cpu|active_shortterm_load
CPU Utilization for Resources Metrics for Host Systems

CPU utilization for resources metrics provide information about CPU activity.
VMware, Inc. 974

Rescpu|CPU Active (%) (interval) Average active time for the CPU over the past minute, past
five minutes, and at one-minute, five-minute, and 15-minute
peak active times.
Key:
Rescpu|CPU Running (%) (interval) Average run time for the CPU over the past minute, past
five minutes, past 15 minutes, and at one-minute, five-
minute, and 15-minute peak times.
Key:
Rescpu|CPU Throttled (%) (interval) Scheduling limit over the past minute, past five minutes,
and past 15 minutes.
Key:
Rescpu|Group CPU Sample Count Group CPU sample count.

Key: rescpu|sampleCount_latest
Rescpu|Group CPU Sample Period (ms) Group CPU sample period in milliseconds.
Key: rescpu|samplePeriod_latest
Datastore Metrics for Host Systems


Datastore|Commands Averaged Average number of commands issued per second during

the collection interval.
Datastore|Number of Outstanding IO Operations Number of outstanding IO operations.

Key: datastore|oio
VMware, Inc. 975

Datastore|Total Latency (ms) The average amount of time taken for a command from
Latency.
Datastore|Total Throughput (KBps) Usage Average (KBps).

Datastore|Demand Demand.
Datastore|Storage I/O Control aggregated IOPS Aggregate number of IO operations on the datastore.
Key: datastore|datastoreIops_average
Datastore|Read IOPS Average number of read commands issued per second

Datastore|Write IOPS Average number of write commands issued per second

Datastore|Read Throughput (KBps) Rate of reading data from the datastore in kilobytes per
second.
Datastore|Storage I/O Control normalized latency (ms) Normalized latency in microseconds on the datastore.
Data for all virtual machines is combined.
Key: datastore|sizeNormalizedDatastoreLatency_average
Datastore|Read Latency (ms) Average amount of time for a read operation from the
datastore. Total latency = kernel latency + device latency.
datastore. Total latency = kernel latency + device latency.
Datastore|Write Throughput (KBps) Rate of writing data to the datastore in kilobytes per
second.
Datastore|Max Queue Depth Max Queue Depth.

Key: datastore|datastoreMaxQueueDepth_latest
Datastore|Highest Latency Highest Latency.

Key: datastore|maxTotalLatency_latest
Datastore|Total Latency Max Total Latency Max (ms).

Key: datastore|totalLatency_max
Datastore|Read Latency Read Latency.

Key: datastore|datastoreNormalReadLatency_latest
Datastore|Write Latency Write Latency.

Key: datastore|datastoreNormalWriteLatency_latest
VMware, Inc. 976

Datastore|Data Read Data Read.

Key: datastore|datastoreReadBytes_latest
Datastore|Data Read Rate Data Rate.

Key: datastore|datastoreReadIops_latest
Datastore|Read Load Storage DRS metric read load.

Key: datastore|datastoreReadLoadMetric_latest
Datastore|Outstanding Read Requests Outstanding Read Requests.

Key: datastore|datastoreReadOIO_latest
Datastore|Data Written Data Written.

Key: datastore|datastoreWriteBytes_latest
Datastore|Data Write Rate Data Write Rate.

Key: datastore|datastoreWriteIops_latest
Datastore|Write Load Storage DRS metric write load.

Key: datastore|datastoreWriteLoadMetric_latest
Datastore|Outstanding Write Requests Outstanding Write Requests.

Key: datastore|datastoreWriteOIO_latest
Datastore|VM Disk I/O Workload Disparity Percentage Disk I/O workload disparity among the VMs on
the Host.
Key: datastore|vmWorkloadDisparityPc
Disk Metrics for Host Systems

Disk|Total Throughput (KBps) Average of the sum of the data read and written for all of
the disk instances of the host or virtual machine.
disk|usage_average
Disk|I/O Usage Capacity This metric is a function of storage|usage_average and

disk|workload. storage|usage_average is an average over
all storage devices. This means that disk|usage_capacity is
not specific to the selected VM or the host of the VM.
Key: disk|usage_capacity
Disk|Total IOPS Average number of commands issued per second during

Disk|Total Latency (ms) The average amount of time taken for a command from
Latency.
Disk|Read IOPS Average number of read commands issued per second

Key: disk|numberReadAveraged_average
VMware, Inc. 977

Disk|Write IOPS Average number of write commands issued per second

Disk|Read Requests Number of times data was read from the disk in the
defined interval.
Disk|Write Requests Number of times data was written to the disk in the
defined interval.
Disk|Read Throughput (KBps) Amount of data read in the performance interval.

Disk|Write Throughput (KBps) Amount of data written to disk in the performance interval.
Disk|Bus Resets The number of bus resets in the performance interval.

Key: disk|busResets_summation
Disk|Commands Issued The number of disk commands issued in the performance

interval.
Disk|Commands Aborted The number of disk commands stopped in the

Key: disk|commandsAborted_summation
Disk|Physical Device Read Latency (ms) The average time taken to complete a read from the
physical device.
Key: disk|deviceReadLatency_average
Disk|Kernel Disk Read Latency (ms) The average time spent in ESX Server VMKernel per read.
Key: disk|kernelReadLatency_average
Disk|Read Latency (ms) The average amount of time taken for a read from the
perspective of a Guest OS. This is the sum of Kernel Read
Latency and Physical Device Read Latency.
Disk|Queue Read Latency (ms) The average time spent in the ESX Server VMKernel queue
per read.
Key: disk|queueReadLatency_average
Disk|Physical Device Write Latency (ms) The average time taken to complete a write from the
physical device.
Key: disk|deviceWriteLatency_average
Disk|Kernel Disk Write Latency (ms) The average time spent in ESX Server VMKernel per write.
Key: disk|kernelWriteLatency_average
Disk|Write Latency (ms) The average amount of time taken for a write from the
perspective of a Guest OS. This is the sum of Kernel Write
Latency and Physical Device Write Latency.
Key: disk|totalWriteLatency_average
VMware, Inc. 978

Disk|Queue Write Latency (ms) The average time spent in the ESX Server VMKernel queue
per write.
Key: disk|queueWriteLatency_average
Disk|Physical Device Latency (ms) The average time taken to complete a command from the
physical device.
Key: disk|deviceLatency_average
Disk|Kernel Latency (ms) The average time spent in ESX Server VMKernel per
command.
Key: disk|kernelLatency_average
Disk|Queue Latency (ms) The average time spent in the ESX Server VMKernel queue
per command.
Key: disk|queueLatency_average
Disk|Number of Outstanding IO Operations Number of Outstanding IO Operations.

Key: disk|diskoio
Disk|Queued Operations Queued Operations.

Key: disk|diskqueued
Disk|Demand Demand.
Key: disk|diskdemand
Disk|Total Queued Outstanding operations Sum of Queued Operation and Outstanding Operations.
Disk|Max Observed OIO Max Observed IO for a disk.

Disk|Highest Latency Highest Latency.

Key: disk|maxTotalLatency_latest
Disk|Max Queue Depth Maximum queue depth during the collection interval.
Key: disk|maxQueueDepth_average
Disk|SCSI Reservation Conflicts SCSI Reservation Conflicts.

Key: disk|scsiReservationConflicts_summation
Memory Metrics for Host Systems

Mem|Contention (%) This metric is used to monitor ESXi memory usage.

When the value is high, it means the ESXi is using a good
percentage of available memory. You may need to add
more memory to other memory-related metrics.
Mem|Contention (KB) Host contention in kilobytes.

Mem|Host Usage (KB) Machine usage in kilobytes.

Key: mem|host_usage
VMware, Inc. 979

Mem|Machine Demand (KB) Host demand in kilobytes.

Mem|Overall Memory used to run VMs on Host (KB) Overall memory used to run virtual machines on the host
in kilobytes.
Key: mem|host_usageVM
Mem|Provisioned Memory (KB) Provisioned memory in kilobytes.

Mem|Minimum Free Memory (KB) Minimum free memory.

Key: mem|host_minfree
Mem|Reserved Capacity (%) Percent reserved capacity.

Key: mem|reservedCapacityPct
Mem|Usable Memory (KB) Usable memory in kilobytes.

Mem|Usage (%) Memory currently in use as a percentage of total available

memory.
Mem|ESX System Usage Memory usage by the VMkernel and ESX user-level
services.
Mem|Guest Active (KB) Amount of memory that is actively used.

Key: mem|active_average
Mem|Consumed (KB) Amount of host memory consumed by the virtual machine

for guest memory.
Mem|Granted (KB) Amount of memory available for use.

Key: mem|granted_average
Mem|Heap (KB) Amount of memory allocated for heap.

Key: mem|heap_average
Mem|Heap Free (KB) Amount of free space in the heap.

Key: mem|heapfree_average
Mem|VM Overhead (KB) Memory overhead reported by host.

Mem|Reserved Capacity (KB) Reserved capacity in kilobytes.

Mem|Shared (KB) Amount of shared memory in kilobytes.

Key: mem|shared_average
Mem|Shared Common (KB) Amount of shared common memory in kilobytes.

Key: mem|sharedcommon_average
Mem|Swap In (KB) Amount of memory swapped in.

VMware, Inc. 980

Mem|Swap Out KB) Amount of memory swapped out.

Key: mem|swapout_average
Mem|Swap Used (KB) Amount of memory used for swapped space in kilobytes.
Key: mem|swapused_average
Mem|VM kernel Usage (KB) Amount of memory used by the VM kernel.

Key: mem|sysUsage_average
Mem|Unreserved (KB) Amount of unreserved memory in kilobytes.

Key: mem|unreserved_average
Mem|Balloon (KB) This metric shows the total amount of memory currently
used by the VM memory control. This memory was
reclaimed from the respective VMs at some point in the
past, and was not returned.
Use this metric to monitor how much VM memory has
been reclaimed by ESXi through memory ballooning.
The presence of ballooning indicates the ESXi has been
under memory pressure. The ESXi activates ballooning
when consumed memory reaches a certain threshold.
Look for increasing size of ballooning. This indicates that
there has been a shortage of memory more than once.
Look for size fluctuations which indicate the ballooned out
page was actually required by the VM. This translates into
a memory performance problem for the VM requesting
the page, since the page must first be brought back from
the disk.
Key: mem|vmmemctl_average
Mem|Zero (KB) Amount of memory that is all zero.

Mem|State (0-3) Overall state of the memory. The value is an integer

between 0 (high) and 3 (low).
Key: mem|state_latest
Mem|Usage (KB) Host memory use in kilobytes.

Key: mem|host_usage
Mem|Usage (%) Memory currently in use as a percentage of total available

memory.
Key: mem|usage_average
Mem|Swap In Rate (KBps) Rate at which memory is swapped from disk into active
memory during the interval in kilobyte per second.
Mem|Swap Out Rate (KBps) Rate at which memory is being swapped from active
memory to disk during the current interval in kilobytes per
second.
Key: mem|swapoutRate_average
Mem|Active Write (KB) Average active writes in kilobytes.

VMware, Inc. 981

Mem|Compressed (KB) Average memory compression in kilobytes.

Mem|Compression Rate (KBps) Average compression rate in kilobytes per second.

Key: mem|compressionRate_average
Mem|Decompression Rate (KBps) Decompression rate in kilobytes per second.

Mem|Total Capacity (KB) Total capacity in kilobytes. Amount of physical memory

configured on the ESXi hosts.
Mem|Latency Percentage of time the VM is waiting to access swapped

or compressed memory.
Key: mem|latency_average
Mem|Capacity Contention Capacity Contention.

Key: mem|capacity.contention_average
Mem|Swap In Rate from Host Cache Rate at which memory is being swapped from host cache
into active memory.
Key: mem|llSwapInRate_average
Mem|Swap In from Host Cache Amount of memory swapped-in from host cache.
Key: mem|llSwapIn_average
Mem|Swap Out Rate to Host Cache Rate at which memory is being swapped to host cache
from active memory.
Key: mem|llSwapOutRate_average
Mem|Swap Out to Host Cache Amount of memory swapped-out to host cache.

Key: mem|llSwapOut_average
Mem|Swap Space Used in Host Cache Space used for caching swapped pages in the host cache.
Key: mem|llSwapUsed_average
Mem|Low Free Threshold Threshold of free host physical memory below which ESX
begins to reclaim memory from VMs through ballooning
and swapping.
Key: mem|lowfreethreshold_average
Mem|VM Memory Workload Disparity Percentage Memory workload disparity among the VMs
on the Host.
Key: mem|vmWorkloadDisparityPct
Mem|Active Host Load For Balance (Long Term) Active Host Load For Balance (Long Term).
Key: mem|active_longterm_load
Mem|Active Host Load For Balance (Short Term) Active Host Load For Balance (Short Term).
Key: mem|active_shortterm_load
Mem|Utilization Memory utilization level based on descendant Virtual

Machines utilization. Includes reservations, limits and
overhead to run Virtual Machines
Key: mem|total_need
VMware, Inc. 982

Network Metrics for Host Systems

Net|Packets Transmitted per second This metric shows the number of packets transmitted
Key: net|packetsTxPerSec
Net|Packets per second Number of packets transmitted and received per second.
Key: net|packetsPerSec
Net|Total Throughput (KBps) The sum of the data transmitted and received for all the
Net|I/O Usage Capacity I/O Usage Capacity.

Key: net|usage_capacity
Net|Data Transmit Rate (KBps) Average amount of data transmitted per second.
Net|Data Receive Rate (KBps) Average amount of data received per second.
Net|Packets Received Number of packets received in the performance interval.

Net|Packets Transmitted Number of packets transmitted in the performance

interval.
Net|Broadcast Packets Received Number of broadcast packets received during the

sampling interval.
Key: net|broadcastRx_summation
Net|Broadcast Packets Transmitted Number of broadcast packets transmitted during the

sampling interval.
Key: net|broadcastTx_summation
Net|Error Packets Transmitted Number of packets with errors transmitted.

Key: net|errorsTx_summation
Net|Multicast Packets Received Number of multicast packets received.

Key: net|multicastRx_summation
Net|Multicast Packets Transmitted Number of multicast packets transmitted.

Key: net|multicastTx_summation
Net|FT Throughput Usage FT Throughput Usage.

Key: net|throughput.usage.ft_average
Net|HBR Throughput Usage HBR Throughput Usage.

Key: net|throughput.usage.hbr_average
Net|iSCSI Throughput Usage iSCSI Throughput Usage.

Key: net|throughput.usage.iscsi_average
Net|NFS Throughput Usage NFS Throughput Usage.

Key: net|throughput.usage.nfs_average
VMware, Inc. 983

Net|VM Throughput Usage VM Throughput Usage.

Key: net|throughput.usage.vm_average
Net|vMotion Throughput Usage vMotion Throughput Usage.

Key: net|throughput.usage.vmotion_average
Net|Unknown Protocol Frames Received Number of frames with unknown protocol received.
Key: net|unknownProtos_summation
System Metrics for Host Systems

System metrics provide information about the amount of CPU that resources and other
applications use.
Sys|Power On 1 if the host system is powered on, 0 if the host system is

powered off, or -1 if the power state is unknown.
Key: sys|poweredOn
Sys|Uptime (seconds) Number of seconds since the last system startup.

Key: sys|uptime_latest
Sys|Disk Usage (%) Percent disk use.

Key: sys|diskUsage_latest
Sys|Resource CPU Usage (MHz) Amount of CPU that the Service Console and other
applications use.
Key: sys|resourceCpuUsage_average
Sys|Resource CPU Active (1 min. average) Percentage of resource CPU that is active. Average value
during a one-minute period.
Key: sys|resourceCpuAct1_latest
Sys|Resource CPU Active (%) (5 min. average) Percentage of resource CPU that is active. Average value
during a five-minute period.
Key: sys|resourceCpuAct5_latest
Sys|Resource CPU Alloc Max (MHz) Maximum resource CPU allocation in megahertz.
Key: sys|resourceCpuAllocMax_latest
Sys|Resource CPU Alloc Min (MHz) Minimum resource CPU allocation in megahertz.
Key: sys|resourceCpuAllocMin_latest
Sys|Resource CPU Alloc Shares Number of resource CPU allocation shares.

Key: sys|resourceCpuAllocShares_latest
Sys|Resource CPU Max Limited (%) (1 min. average) Percent of resource CPU that is limited to the maximum
amount. Average value during a one-minute period.
Key: sys|resourceCpuMaxLimited1_latest
Sys|Resource CPU Max Limited (%) (5 min. average) Percentage of resource CPU that is limited to the
maximum amount. Average value during a five-minute
period.
Key: sys|resourceCpuMaxLimited5_latest
VMware, Inc. 984

Sys|Resource CPU Run1 (%) Percent resource CPU for Run1.

Key: sys|resourceCpuRun1_latest
Sys|Resource CPU Run5 (%) Percent resource CPU for Run5.

Key: sys|resourceCpuRun5_latest
Sys|Resource Memory Alloc Max (KB) Maximum resource memory allocation in kilobytes.
Key: sys|resourceMemAllocMax_latest
Sys|Resource Memory Alloc Min (KB) Minimum resource memory allocation in kilobytes.
Key: sys|resourceMemAllocMin_latest
Sys|Resource Memory Alloc Shares Number of resource memory shares allocated.

Key: sys|resourceMemAllocShares_latest
Sys|Resource Memory Cow (KB) Cow resource memory in kilobytes.

Key: Sys|resourceMemCow_latest
Sys|Resource Memory Mapped (KB) Mapped resource memory in kilobytes.

Key: ys|resourceMemMapped_latest
Sys|Resource Memory Overhead (KB) Resource memory overhead in kilobytes.

Key: sys|resourceMemOverhead_latest
Sys|Resource Memory Shared (KB) Shared resource memory in kilobytes.

Key: sys|resourceMemShared_latest
Sys|Resource Memory Swapped (KB) Swapped resource memory in kilobytes.

Key: sys|resourceMemSwapped_latest
Sys|Resource Memory Touched (KB) Touched resource memory in kilobytes.

Key: sys|resourceMemTouched_latest
Sys|Resource Memory Zero (KB) Zero resource memory in kilobytes.

Key: sys|resourceMemZero_latest
Sys|Resource Memory Consumed Resource Memory Consumed Latest (KB).

Key: sys|resourceMemConsumed_latest
Sys|Resource File descriptors usage Resource File descriptors usage (KB).

Key: sys|resourceFdUsage_latest
Sys|vMotion Enabled 1 if vMotion is enabled or 0 if vMotion is not enabled.

Key: sys|vmotionEnabled
Sys|Not in Maintenance Not in maintenance.

Key: sys|notInMaintenance
Management Agent Metrics for Host Systems

Management agent metrics provide information about memory use.
VMware, Inc. 985

Management Agent|Memory Used (%) Amount of total configured memory that is available for
use.
Key: managementAgent|memUsed_average
Management Agent|Memory Swap Used (KB) Sum of the memory swapped by all powered-on virtual
machines on the host.
Key: managementAgent|swapUsed_average
Management Agent|Memory Swap In (KBps) Amount of memory that is swapped in for the Service
Console.
Key: managementAgent|swapIn_average
Management Agent|Memory Swap Out (KBps) Amount of memory that is swapped out for the Service
Console.
Key: managementAgent|swapOut_average
Management Agent|CPU Usage CPU usage.

Key: managementAgent|cpuUsage_average
Storage Path Metrics for Host Systems

Storage path metrics provide information about data storage use.
StoragePath|Total Latency (ms) Total latency in milliseconds.

Key: storagePath|totalLatency
StoragePath|Total Usage (KBps) Total latency in kilobytes per second.

Key: storagePath|usage
StoragePath|Read Throughput (KBps) Rate of reading data from the virtual disk.
Key: storagePath|read_average
StoragePath|Write Throughput (KBps) Rate of writing data.

Key: storagePath|write_average
StoragePath|Total IOPS Average number of commands issued per second during

Key: storagePath|commandsAveraged_average
StoragePath|Read IOPS Average number of read commands issued per second

Key: storagePath|numberReadAveraged_average
StoragePath|Write IOPS Average number of write commands issued per second

Key: storagePath|totalWriteLatency_average
StoragePath|Write IOPS Average number of write commands issued per second

Key: storagePath|numberWriteAveraged_average
StoragePath|Read Latency (ms) Average amount of time for a read operation by the
storage adapter.
Key: storagePath|totalReadLatency_average
VMware, Inc. 986

StoragePath|Highest Latency Highest Latency.

Key: storagePath|maxTotalLatency_latest
StoragePath|Storage Path Name Storage path name.

Key: storagePath|storagePathName
Storage Adapter Metrics for Host Systems

Storage adapter metrics provide information about data storage use.
Storage Adapter|Total Usage (KBps) Total latency.

Key: storageAdapter|usage
Storage Adapter|Port WWN Port World Wide Name.

Key: storageAdapter|portWWN
Storage Adapter|Total IOPS Average number of commands issued per second by the
storage adapter during the collection interval.
Key: storageAdapter|commandsAveraged_average
Storage Adapter|Read IOPS Average number of read commands issued per second
by the storage adapter during the collection interval.
Key: storageAdapter|numberReadAveraged_average
Storage Adapter|Write IOPS Average number of write commands issued per second
by the storage adapter during the collection interval.
Key: storageAdapter|numberWriteAveraged_average
Storage Adapter|Read Throughput (KBps) Rate of reading data by the storage adapter.
Key: storageAdapter|read_average
Storage Adapter|Read Latency (ms) This metric shows the average amount of time for a read
operation by the storage adapter.
Use this metric to monitor the storage adapter read
operation performance. A high value means that the ESXi
is performing a slow storage read operation.
Total latency is the sum of kernel latency and device
latency.
Key: storageAdapter|totalReadLatency_average
Storage Adapter|Write Latency (ms) This metric shows the average amount of time for a write
operation by the storage adapter.
Use this metric to monitor the storage adapter write
performance operation. A high value means that the ESXi
is performing a slow storage write operation.
Total latency is the sum of kernel latency and device
latency.
Key: storageAdapter|totalWriteLatency_average
Storage Adapter|Write Throughput (KBps) Rate of writing data by the storage adapter.
Key: storageAdapter|write_average
VMware, Inc. 987

Storage Adapter|Demand Demand.

Key: storageAdapter|demand
Storage Adapter|Highest Latency Highest Latency.

Key: torageAdapter|maxTotalLatency_latest
Storage Adapter|Outstanding Requests Outstanding Requests.

Key: storageAdapter|outstandingIOs_average
Storage Adapter|Queue Depth Queue Depth.

Key: storageAdapter|queueDepth_average
Storage Adapter|Queue Latency (ms) The average time spent in the ESX Server VM Kernel
queue per command.
Key: storageAdapter|queueLatency_average
Storage Adapter|Queued Queued.

Key: storageAdapter|queued_average
Storage Metrics for Host Systems

Storage|Total IOPS Average number of commands issued per second during

Key: storage|commandsAveraged_average
Storage|Read Latency (ms) Average amount of time for a read operation in

milliseconds.
Key: storage|totalReadLatency_average
Storage|Read Throughput (KBps) Read throughput rate in kilobytes.

Key: storage|read_average
Storage|Read IOPS Average number of read commands issued per second

Key: storage|numberReadAveraged_average
Storage|Total Latency (ms) Total latency in milliseconds.

Key: storage|totalLatency_average
Storage|Total Usage (KBps) Total throughput rate in kilobytes per second.

Storage|Write Latency (ms) Average amount of time for a write operation in

milliseconds.
Key: storage|totalWriteLatency_average
Storage|Write Throughput (KBps) Write throughput rate in kilobytes per second.

Key: storage|write_average
Storage|Write IOPS Average number of write commands issued per second

Key: storage|numberWriteAveraged_average
VMware, Inc. 988

Sensor Metrics for Host Systems

Sensor metrics provide information about host system cooling.
Sensor|Fan|Speed (%) Percent fan speed.

Key: Sensor|fan|currentValue
Sensor|Fan|Health State Fan health state.

Key: Sensor|fan|healthState
Sensor|Temperature|Temp C Fan temperature in centigrade.

Key: Sensor|temperature|currentValue
Sensor|Temperature|Health State Fan health state.

Key: Sensor|temperature|healthState
Power Metrics for Host Systems

Power metrics provide information about host system power use.
Power|Energy (Joule) Total energy used since last stats reset.

Power|Power (Watt) Host power use in watts.

Power|Power Cap (Watt) Host power capacity in watts.

Key: power|powerCap_average
Disk Space Metrics for Host Systems

Diskspace|Number of Virtual Disks Number of virtual disks.

Key: diskspace|numvmdisk
Diskspace|Shared Used (GB) Used shared disk space in gigabytes.

Key: diskspace|shared
Diskspace|Snapshot Disk space used by snapshots in gigabytes.

Diskspace|Virtual Disk Used (GB) Disk space used by virtual disks in gigabytes.
Key: diskspace|diskused
Diskspace|Virtual machine used (GB) Disk space used by virtual machines in gigabytes.
Key: diskspace|used
Diskspace|tTotal disk space used Total disk space used on all datastores visible to this
object.
VMware, Inc. 989

Diskspace|Total disk spacey Total disk space on all datastores visible to this object.
Diskspace|Total provisioned disk space Total provisioned disk space on all datastores visible to
this object.
Key: diskspace|total_provisioned .
Diskspace|Utilization (GB) Storage space utilized on connected vSphere

datastores.
Diskspace|Workload (%) Total storage space available on connected vSphere

datastores.
Summary Metrics for Host Systems

Summary metrics provide information about overall host system performance.
Summary|Number of Running VMs This metric shows the number of VMs running on the
host during the last metric collection time.
Large spikes of running VMs might be a reason for CPU
or memory spikes as more resources are used in the
host.
Number of Running VMs gives you a good indicator of
how many requests the ESXi host must juggle. This
excludes powered off VMs as they do not impact ESXi
performance. A change in this number in your
environment can contribute to performance problems.
A high number of running VMs in a host also means a
higher concentration risk, as all the VMs will become
unavailable (or be relocated by HA) if the ESXi crashes.
Look for any correlation between spikes in the number
of running VMs and spikes in other metrics such as CPU
Contention/Memory Contention.
Summary|Maximum Number of VMs Maximum number of virtual machines

VMware, Inc. 990

Summary|Number of vMotions This metric shows the number of vMotions that

occurred in the host in the last X minutes.
The number of vMotions is a good indicator of stability.
In a healthy environment, this number should be stable
and relatively low.
Look for correlation between vMotions and spikes in
other metrics such as CPU/Memory contention.
The vMotion should not create any spikes, however, the
VMs moved into the host might create spikes in
memory usage, contention and CPU demand and
contention.
Key: summary|number_vmotion
Summary|Total Number of Datastores Total Number of Datastores.

Summary|Number of VCPUs on Powered On VMs Total number of VCPUs of Virtual Machines that are
powered on.
Summary|Number of VMs Total number of virtual machines.

HBR Metrics for Host Systems

Host-based replication (HBR) metrics provide information about vSphere replication.
HBR|Replication Data Received Rate Replication Data Received Rate.

Key: hbr|hbrNetRx_average
HBR|Replication Data Transmitted Rate Replication Data Transmitted Rate.

Key: hbr|hbrNetTx_average
HBR|Replicated VM Count Number of replicated virtual machines.

Key: hbr|hbrNumVms_average
Cost Metrics for Host Systems

Monthly Hardware Maintenance Total Cost Monthly total cost for hardware maintenance.
Key: cost|maintenanceTotalCost
Monthly Host OS License Total Cost Monthly total cost for the host operating system license.
Key: cost|hostOslTotalCost
Monthly Network Total Cost Monthly total cost for network including cost of NIC cards
associated with host.
Key: cost|networkTotalCost
VMware, Inc. 991

Monthly Server Hardware Total Cost Monthly total cost for server hardware, based on amortized
monthly value.
Key: cost|hardwareTotalCost
Monthly Facilities Total Cost Monthly total cost of facilities including real estate, power,
and cooling.
Key: cost|facilitiesTotalCost
Monthly Host OS Labor Total Cost Monthly total cost for the host operating system labor.
Key: cost|hostLaborTotalCost
Monthly Server Fully Loaded Cost Monthly cost for a fully loaded server incorporating all cost
driver values attributed to the server.
Key: cost|totalLoadedCost
MTD Server Total Cost Month to date cost for a fully loaded server incorporating
all cost driver values attributed to the server.
Key: totalMTDCost
Disabled Metrics
Metric Name Key
CPU|Idle (msec) cpu|idle_summation
CPU|Used (msec) cpu|used_summation
Datastore I/O|Average Observed Virtual Machine Disk I/O datastore|vmPopulationAvgWorkload

Workload

Operations
Datastore I/O|Maximum Observed VM Disk I/O Workload datastore|vmPopulationMaxWorkload
Network I/O|bytesRx (kbps) net|bytesRx_average
Network I/O|bytesTx (kbps) net|bytesTx_average
Network I/O|Demand (%) net|demand
Network I/O|Error Packets Received net|errorsRx_summation
Network I/O|Max Observed Received Throughput (kbps) net|maxObserved_Rx_KBps
Network I/O|Max Observed Throughput (kbps) net|maxObserved_KBps
VMware, Inc. 992

Metric Name Key
Network I/O|Max Observed Transmitted Throughput (kbps) net|maxObserved_Tx_KBps
Network I/O|Packets Received per second net|packetsRxPerSec
Network I/O|Packets Dropped net|dropped
vFlash Module|Latest Number of Active Vm Disks vflashModule|numActiveVMDKs_latest
Net|Received Packets Dropped Number of received packets dropped in the

Net|Transmitted Packets Dropped Number of transmitted packets dropped in the

Net|Packets Dropped (%) This metric shows the percentage of received and
transmitted packets dropped during the collection
interval.
This metric is used to monitor reliability and
performance of the ESXi network. When a high value is
displayed, the network is not reliable and performance
suffers.
Key: net|droppedPct
Diskspace|Not Shared (GB) Unshared disk space in gigabytes.

Key: diskspace|notshared
Cluster Compute Resource Metrics

vRealize Operations Manager collects configuration, disk space, CPU use, disk, memory, network,
power, and summary metrics for cluster compute resources.
Cluster Compute Resource metrics include capacity and badge metrics. See definitions in:
n Badge Metrics
Configuration Metrics for Cluster Compute Resources

Configuration metrics provide information about configuration settings.
Configuration|Failover Level DAS configuration failover level.

Key: configuration|dasconfig|failoverLevel
Configuration|Active Admission Control Policy DAS configuration active admission control policy.
Key: configuration|dasconfig|activeAdministrationControlPolicy
VMware, Inc. 993

Configuration|CPU Failover Resources Percent Percent CPU failover resources for DAS configuration admission
control policy.
Key: configuration|dasconfig|adminissionControlPolicy|
cpuFailoverResourcesPercent
Configuration|Memory Failover Resources Percent Percent memory failover resources for DAS configuration
admission control policy.
Key: configuration|dasconfig|adminissionControlPolicy|
memoryFailoverResourcesPercent
Disk Space Metrics for Cluster Compute Resources

Diskspace|Virtual machine used (GB) Space used by virtual machine files in gigabytes.
Key: diskspace|used
Diskspace|Total disk space used Total disk space used on all datastores visible to this object.
Diskspace|Total disk space Total disk space on all datastores visible to this object.
Diskspace|Total provisioned disk space Total provisioned disk space on all datastores visible to this
object.
Diskspace|Virtual Disk Used (GB) Space used by virtual disks in gigabytes.

Diskspace|Snapshot Space (GB) Space used by snapshots in gigabytes.

Diskspace|Shared Used (GB) Shared used space in gigabytes.

Diskspace|Utilization (GB) Storage space used on the connected vSphere Datastores.

Diskspace|Total Capacity (GB) Total storage space available on the connected vSphere
datastores.
CPU Usage Metrics for Cluster Compute Resources

VMware, Inc. 994

CPU|Capacity Usage This metric shows the percentage of the capacity used.
CPU|CPU Contention (%) This metric is an indicator of the overall contention for CPU
resources that occurs across the workloads in the cluster. When
contention occurs, it means that some of the virtual machines are
not immediately getting the CPU resources they are requesting.
Use this metric to identify when a lack of CPU resources might be
causing performance issues in the cluster.
This metric is the sum of the CPU contention across all hosts in
the cluster averaged over two times the number of physical CPUs
in the cluster to account for hyper-threading. CPU contention
takes into account:
n CPU Ready
n CPU Co-stop
n Power management
n Hyper threading
This metric is more accurate than CPU Ready since it takes into
account CPU Co-stop and Hyper threading.
When using this metric, the number should be lower than the
performance you expect. If you expect performance at 10%, then
the number should be lower than 10%.
Since this value is averaged across all hosts in the cluster, you
might find that some hosts have a higher CPU contention while
others are lower. To ensure that vSphere spreads out the running
workloads across hosts, consider enabling a fully automated DRS
in the cluster.
CPU|Demand (%) This metric is an indicator of the overall demand for CPU
resources by the workloads in the cluster.
It shows the percentage of CPU resources that all the virtual
machines might use if there were no CPU contention or CPU limits
set. It represents the average active CPU load in the past five
minutes.
Key: cpu|demandPct
CPU|Demand (MHz) CPU utilization level based on descendant virtual machines

utilization. This Includes reservations, limits, and overhead to run
the virtual machines.
Key: cpu|demandmhz
CPU|Number of CPU Sockets Number of CPU sockets.

CPU|Overall CPU Contention Overall CPU contention in milliseconds.

CPU|Host Provisioned Capacity Provisioned CPU capacity in megahertz.

CPU|Provisioned vCPUs Number of provisioned CPU cores.

VMware, Inc. 995

CPU|Usage (MHz) Average CPU use in megahertz.

CPU|Demand CPU Demand.

CPU|Overhead Amount of CPU overhead.

CPU|Demand without overhead Value of demand excluding any overhead.

CPU|Provisioned Capacity Provisioned Capacity (MHz).

CPU|Number of hosts stressed Number of hosts stressed.

Key: cpu|num_hosts_stressed
CPU|Stress Balance Factor Stress Balance Factor.

Key: cpu|stress_balance_factor
CPU|Lowest Provider Capacity Remaining Lowest Provider Capacity Remaining.

Key: cpu|min_host_capacity_remaining
CPU|Workload Balance Factor Workload Balance Factor.

Key: cpu|workload_balance_factor
CPU|Highest Provider Workload Highest Provider Workload.

Key: cpu|max_host_workload
CPU|Host workload Max-Min Disparity Difference of Max and Min host workload in the container.
Key: cpu|host_workload_disparity
CPU|Host stress Max-Min Disparity Difference of Max and Min host stress in the container.
Key: cpu|host_stress_disparity
CPU|Total Capacity (MHz) Total CPU resources configured on the descendant ESXi hosts.
CPU|Usable Capacity (MHz) The usable CPU resources that are available for the virtual
machines after considering reservations for vSphere High
Availability (HA) and other vSphere services.
Disk Metrics for Cluster Compute Resources

VMware, Inc. 996

Disk|Total IOPS Average number of commands issued per second during the
Disk|Total Latency (ms) Average amount of time taken for a command from the
perspective of the guest operating system. This metric is the sum
of the Kernel Command Latency and Physical Device Command
Latency metrics.
Disk|Read Latency (ms) Average amount of time for a read operation from the virtual
disk. The total latency is the sum of Kernel latency and device
latency.
Disk|Write Latency (ms) The average amount of time taken for a read from the
perspective of a Guest OS. This is the sum of Kernel Read
Latency and Physical Device Read Latency.
Key: disk|totalWriteLatency_averag
Disk|Read Throughput (KBps) Number of times data was read from the disk in the defined
interval.
Disk|Read IOPS Average number of read commands issued per second during
Key: disk|numberReadAveraged_averag
Disk|Total Throughput (KBps) Average of the sum of the data read and written for all the disk
instances of the host or virtual machine.
Disk|Write Throughput (KBps) Number of times data was written to disk during the collection
interval.
Disk|Write IOPS Average number of write commands issued per second during
Disk|Read Requests Amount of data read from the disk during the collection interval.
Disk|Write Requests Amount of data written to the disk during the collection interval.
Disk|Commands Issued Number of disk commands issued during the collection interval.
Disk|Total Queued Outstanding operations Sum of queued operation and outstanding operations.
Disk|Max Observed OIO Max observed outstanding IO for a disk.

VMware, Inc. 997

Memory Metrics for Cluster Compute Resources

Mem|Active Write (KB) Active writes in kilobytes.

Mem|Compressed (KB) Average compression in kilobytes.

Mem|Compression Rate (KBps) Average compression rate in kilobytes.

Mem|Consumed (KB) Amount of host memory consumed by the virtual machine for
guest memory.
Mem|Contention (%) This metric is an indicator of the overall contention for memory
resources that occurs across the workloads in the cluster. When
contention occurs, it means that some of the VMs are not
immediately getting the memory resources that they are
requesting.
Use this metric to identify when lack of memory resources might
be causing performance issues in the cluster.
Mem|Contention (KB) Contention in kilobytes.

Mem|Decompression Rate (KBps Decompression rate in kilobytes.

Mem|Granted (KB) Amount of memory available for use.

Mem|Guest Active (KB) Amount of memory that is actively used.

Mem|Heap (KB) Amount of memory allocated for heap.

Key: mem|heap_average
Mem|Heap Free (KB) Free space in the heap.

Key: mem|heapfree_average
Mem|Balloon This metric shows the amount of memory currently used by the
virtual machine memory control. It is only defined at the VM
level.
Mem|VM Overhead (KB) Memory overhead reported by host.

Mem|Provisioned Memory (KB) Provisioned memory in kilobytes.

Mem|Reserved Capacity (KB) Reserved capacity in kilobytes.

VMware, Inc. 998

Mem|Shared (KB) Amount of shared memory.

Mem|Shared Common (KB) Amount of shared common memory.

Key: mem|sharedcommon_average
Mem|Swap In (KB) Amount of memory that is swapped in for the service console.
Mem|Swap In Rate (KBps) Rate at which memory is swapped from disk into active memory
during the interval.
Mem|Swap Out (KB) Amount of memory that is swapped out for the service console.
Mem|Swap Out Rate (KBps) Rate at which memory is being swapped from active memory
into disk during the current interval.
Mem|Swap Used (KB) Amount of memory used for swap space.

Mem|Total Capacity (KB) Total capacity in kilobytes.

Key: mem|totalCapacity_average
Mem|Reserved (KB) Amount of unreserved memory.

Key: mem|unreserved_average
Mem|Usable Memory (KB) Usable memory in kilobytes.

Mem|Usage/Usable Percent memory used.

Mem|Host Usage (KB) Memory use in kilobytes.

Key: mem|host_usage
Mem|Machine Demand Memory Machine Demand in KB.

Mem|ESX System Usage Memory usage by the VMkernel and ESX user-level services.
Mem|Usage (%) This metric shows the portion of the total memory in all hosts in
the cluster that is being used.
This metric is the sum of memory consumed across all hosts in
the cluster divided by the sum of physical memory across all
hosts in the cluster.
∑ memory consumed on all hosts
- X 100%
∑ physical memory on all hosts
Mem|Usage (KB) Memory currently in use as a percentage of total available

memory.
VMware, Inc. 999

Mem|VM kernel Usage (KB) Amount of memory that the VM kernel uses.
Key: mem|sysUsage_average
Mem|Zero (KB) Amount of memory that is all 0.

Mem|Number of Hosts Stressed Number of hosts stressed.

Key: mem|num_hosts_stressed
Mem|Stress Balance Factor Stress balance factor.

Key: mem|stress_balance_factor
Mem|Lowest Provider Capacity Remaining Lowest provider capacity remaining.

Key: mem|min_host_capacity_remaining
Mem|Workload Balance Factor Workload balance factor.

Key: mem|workload_balance_factor
Mem|Highest Provider Workload Highest provider workload.

Key: mem|max_host_workload
Mem|Host workload Max-Min Disparity Difference of Max and Min host workload in the container.
Key: mem|host_workload_disparity
Mem|Host stress Max-Min Disparity Difference of Max and Min host stress in the container.
Key: mem|host_stress_disparity
Mem|Utilization (KB) Memory utilization level based on the descendant virtual

machines utilization. Includes reservations, limits, and overhead
to run the Virtual Machines.
Key: mem|total_need
Mem|Total Capacity (KB) Total physical memory configured on descendant ESXi hosts.
Mem|Usable Capacity (KB) The usable memory resources available for the virtual machines
after considering reservations for vSphere HA and other vSphere
services.
Network Metrics for Cluster Compute Resources

Net|Data Receive Rate (KBps) Average amount of data received per second.
Net|Data Transmit Rate (KBps) Average amount of data transmitted per second.
Net|Packets Dropped Number of packets dropped in the performance interval.

Key: net|dropped
Net|Packets Dropped (%) Percentage of packets dropped.

Key: net|droppedPct
VMware, Inc. 1000

Net|Packets Received Number of packets received in the performance interval.

Net|Packets Transmitted Number of packets transmitted in the performance interval.

Net|Received Packets Dropped Number of received packets dropped in the performance

interval.
Net|Transmitted Packets Dropped Number of transmitted packets dropped in the performance

interval.
Net|Total Throughput (KBps) The sum of the data transmitted and received for all the NIC
Datastore Metrics for Cluster Compute Resources

Datastore metrics provide information about Datastore use.

Datastore|Read IOPS Average number of read commands issued per second during
Datastore|Write IOPS Average number of write commands issued per second during
Datastore|Read Throughput (KBps) Amount of data read in the performance interval.

Datastore|Write Throughput (KBps) Amount of data written to disk in the performance interval.
Cluster Services Metrics for Cluster Compute Resources

Cluster Services metrics provide information about cluster services.
Cluster Services|Total Imbalance Key: clusterServices|number_drs_vmotion
Cluster Services|Total Imbalance Key: clusterServices|total_imbalance
Cluster Services|Total Imbalance Key: clusterServices|total_imbalance
ClusterServices|Effective CPU Resources (MHz) VMware DRS effective CPU resources available.
Key: clusterServices|effectivecpu_average
VMware, Inc. 1001

ClusterServices|Effective Memory Resources (KB) VMware DRS effective memory resources available.
Key: clusterServices|effectivemem_average
Cluster Services|DRS Initiated vMotion Count clusterServices|number_drs_vmotion
Power Metrics for Cluster Compute Resources

Power metrics provide information about power use.
Power|Energy (Joule) Energy use in joules.

Power|Power (Watt) Average power use in watts.

Power|Power Cap (Watt) Average power capacity in watts.

Key: power|powerCap_average
Summary Metrics for Cluster Compute Resources

Summary|Number of Running Hosts Number of running hosts.

Summary|Number of Running VMs This metric shows the total number of VMs running on all hosts
in the cluster.
Summary|Number of vMotions This metric shows the number of vMotions that occurred during
the last collection cycle.
When using this metric, look for a low number which indicates
that the cluster might serve its VMs. A vMotion can impact VM
performance during the stun time.
Key: summary|number_vmotion
Summary|Number of Hosts Total number of hosts.

Summary|Number of VMs Total number of virtual machines.

Summary|Total Number of Datastores Total number of datastores.

Summary|Number of VCPUs on Powered On VMs Number of virtual CPUs on powered-on virtual machines.
Summary|Average Running VM Count per Running Average number of running virtual machines per running host.
Host Key: summary|avg_vm_density
VMware, Inc. 1002

Reclaimable Metrics for Cluster Compute Resources

Reclaimable metrics provide information about reclaimable resources.
Idle VMs|CPU (vCPUs) Number of reclaimable vCPUs of Idle VMs within the
cluster.
Key: reclaimable|idle_vms|cpu
Idle VMs|Disk Space (GB) Reclaimable disk space of Idle VMs within the cluster.
Key: reclaimable|idle_vms|disksapce
Idle VMs|Memory (KB) Reclaimable memory of Idle VMs within the cluster.
Key: reclaimable|idle_vms|mem
Idle VMs|Potential Savings Potential saving after reclamation of resources of Idle VMs
within the cluster.
Key: reclaimable|idle_vms|cost
Powered Off VMs|Disk Space (GB) Reclaimable disk space of Powered Off VMs within the
cluster.
Key: reclaimable|poweredOff_vms| diskspace
Powered Off VMs|Potential Savings Potential saving after reclamation of resources of Powered
Off VMs within the cluster.
Key: reclaimable|poweredOff_vms|cost
VM Snapshots|Disk Space (GB) Reclaimable disk space of VM Snapshots within the cluster.
Key: reclaimable| vm_snapshots | diskspace
VM Snapshots |Potential Savings Potential saving after reclamation of VM Snapshots within

the cluster.
Key: reclaimable| vm_snapshots |cost
Cost Metrics for Cluster Compute Resources

Cluster CPU Base Rate Base rate for Cluster CPU calculated by dividing the
monthly total cluster CPU cost by cluster CPU utilization %
and CPU cluster capacity (gHZ).
Key:cost|cpuBaseRate
Cluster CPU Utilization (%) Expected CPU utilization that is set by the user in cluster
cost page.
Key:cost|cpuExpectedUtilizationPct
Cluster Memory Base Rate Cluster memory base rate calculated by dividing the
monthly total cluster memory cost by cluster memory
utilization % and memory cluster capacity (GB).
Key: cost|memoryBaseRate
Cluster Memory Utilization (%) Expected memory utilization that is set by the user in
cluster cost page.
Key: cost|memoryExpectedUtilizationPct
VMware, Inc. 1003

Monthly Cluster Allocated Cost Monthly cluster allocated cost calculated by subtracting the
monthly cluster unallocated cost from the monthly cluster
total cost.
Key: cost|allocatedCost
Monthly Cluster Total Cost Fully loaded compute cost of all hosts underneath the
cluster.
Key: cost|totalCost
Monthly Cluster Unallocated Cost Monthly cluster unallocated cost calculated by subtracting
the monthly cluster allocated cost from the monthly cluster
total cost.
Key: cost|unAllocatedCost
Monthly Total Cluster CPU Cost Cost attributed to the cluster CPU from monthly cluster
total cost.
Key: cost|totalCpuCost
Monthly Total Cluster Memory Cost Cost attributed to the cluster memory from monthly cluster
total cost.
Key: cost|totalMemoryCost
MTD Cluster CPU Utilization (GHz) Month to date CPU utilization of the cluster.
Key: cost|cpuActualUtilizationGHz
MTD Cluster Memory Utilization (GB) Month to date memory utilization of the cluster.
Key: cost|memoryActualUtilizationGB
Cost|Allocation|Monthly Cluster Allocated Cost (Currency) The monthly allocated cost of all VMs in a cluster.
cost|clusterAllocatedCost
Cost|Allocation|Monthly Cluster Unallocated Cost The monthly unallocated is calculated by subtracting the
(Currency) monthly allocated cost from the cluster's cost.
cost|clusterUnAllocatedCost
Profiles Metrics for Cluster Compute Resources

Profiles metrics provide information about the profile specific capacity.
Profiles|Capacity Remaining Profile (Average) The capacity remaining in terms of fitting the average
consumer.
Key: Profiles|capacityRemainingProfile_<profile uuid>
Profiles|Capacity Remaining Profile (<custom profile Published for custom profiles enabled from policy on
name>) Cluster Compute Resource.
Capacity Allocation Metrics for Cluster Compute Resources

Capacity allocation metrics provide information about the allotment of capacity, see Capacity
Analytics Generated Metrics.
VMware, Inc. 1004

Disabled Metrics
Metric Name Key
CPU|Capacity Available to VMs (mhz) cpu|totalCapacity_average
CPU|IO Wait (msec) cpu|iowait
CPU|Reserved Capacity (mhz) cpu|reservedCapacity_average
CPU|Total Wait (msec) cpu|wait

Operations
Storage|Total Usage (kbps) storage|usage_average
Summary|Average Provisioned Capacity per Running summary|avg_vm_cpu

VM (mhz)
Summary|Average Provisioned Memory per Running summary|avg_vm_mem

VM (kb)
Summary|Average Provisioned Memory per Running summary|avg_vm_mem

VM (kb)
Summary|Maximum Number of VMs summary|max_number_vms
Network I/O|Max Observed Received Throughput net|maxObserved_Rx_KBps

(KBps)
Network I/O|Max Observed Throughput (KBps) net|maxObserved_KBps
Network I/O|Max Observed Transmitted Throughput net|maxObserved_Tx_KBps

(KBps)
Diskspace|Not Shared (GB) Space used by VMs that is not shared.

Resource Pool Metrics

vRealize Operations Manager collects configuration, CPU usage, memory, and summary metrics
for resource pool objects.
Resource Pool metrics include capacity and badge metrics. See definitions in:
VMware, Inc. 1005

n Badge Metrics
Configuration Metrics for Resource Pools

Configuration metrics provide information about memory and CPU allocation configuration.
Memory Allocation Reservation Memory Allocation Reservation.

Key: config|mem_alloc_reservation
CPU Usage Metrics for Resource Pools

Capacity Demand Entitlement (%) CPU Capacity Demand Entitlement Percentage.

Key: cpu|capacity_demandEntitlementPct
Capacity entitlement (MHz) CPU Capacity Entitlement.

Key: cpu|capacity_entitlement
CPU Contention (%) CPU capacity contention.

Demand (MHz) CPU demand in megahertz.

Key: cpu|demandmhz

Usage Average CPU use in megahertz.

Effective limit CPU effective limit.

Key: cpu|effective_limit
Reservation Used CPU reservation used.

Key: cpu|reservation_used
Estimated entitlement CPU estimated entitlement.

Key: cpu|estimated_entitlement
Dynamic entitlement CPU dynamic entitlement.

Key: cpu|dynamic_entitlement

Memory Metrics for Resource Pools

VMware, Inc. 1006

Balloon (KB) Amount of memory currently used by the virtual machine

memory control.
Compression Rate (KBps) Compression rate in kilobytes per second.

Consumed (KB) Amount of host memory consumed by the virtual machine

for guest memory.
Contention (%) Machine contention percentage.

Guest usage Guest memory entitlement.

Key: mem|guest_usage
Guest demand Guest memory entitlement.

Key: mem|guest_demand
Contention (KB) Machine contention in kilobytes.

Decompression Rate (KBps) Decompression rate in kilobytes per second.

Granted (KB) Average of memory available for use.

Guest Active (KB) Amount of memory that is actively used.

VM Overhead (KB) Memory overhead reported by host.

Shared (KB) Amount of shared memory.

Reservation Used Memory Reservation Used.

Key: mem|reservation_used
Dynamic Entitlement Memory Dynamic Entitlement.

Key: mem|dynamic_entitlement
Effective Limit Memory Effective Limit.

Key: mem|effective_limit
swapinRate_average Rate at which memory is swapped from disk into active

memory during the interval.
swapoutRate_average Rate at which memory is being swapped from active

memory to disk during the current interval.
Swapped (KB) Amount of unreserved memory.

Key: mem|swapped_average
VMware, Inc. 1007

Usage (%) Memory currently in use as a percentage of total available

memory.
Zero (KB) Amount of memory that is all zero.

Zipped (KB) Latest zipped memory in kilobytes.

Key: mem|zipped_latest
Swap In (KB) Amount of memory swapped in kilobytes.

Swap Out (KB) Amount of memory swapped out in kilobytes.

Swap Used (KB) Amount of memory used for swap space in kilobytes.
Guest Configured Memory (KB) Guest configured memory in kilobytes.

Summary Metrics for Resource Pools

Number of Running VMs Number of running virtual machines.


IO Wait (ms) IO wait time in milliseconds.

Key: summary|iowait
Data Center Metrics

vRealize Operations Manager collects CPU usage, disk, memory, network, storage, disk space,
and summary metrics for data center objects.
Data center metrics include capacity and badge metrics. See definitions in:
n Badge Metrics
CPU Usage Metrics for Data Centers

VMware, Inc. 1008

Capacity Usage (%) Percent capacity used.

CPU Contention (%) CPU capacity contention.

Demand (%) CPU demand percentage.

Key: cpu|demandPct
Demand Demand in megahertz.

Key: cpu|demandmhz
Demand (MHz) CPU utilization level based on descendant virtual machines

utilization. This Includes reservations, limits, and overhead to
run the virtual machines.
Key: cpu|demandmhz
Overhead (KB) Amount of CPU overhead.


Total Wait CPU time spent on idle state.

Key: cpu|wait
Number of CPU Sockets Number of CPU sockets.


Host Provisioned Capacity (MHz) Host provisioned capacity in megahertz.

Provisioned vCPU(s) Provisioned vCPU(s).

Reserved Capacity (MHz) The sum of the reservation properties of the (immediate)
children of the host's root resource pool.
Usage Average CPU usage in megahertz.

IO Wait IO wait time in milliseconds.

Key: cpu|iowait
Provisioned Capacity Provisioned Capacity.

Stress Balance Factor Stress Balance Factor.

Lowest Provider Capacity Remaining Lowest Provider Capacity Remaining.

VMware, Inc. 1009

Workload Balance Factor Workload Balance Factor.

Highest Provider Workload Highest Provider Workload.

Host workload Max-Min Disparity Difference of Max and Min host workload in the container.
Host stress Max-Min Disparity Difference of Max and Min host stress in the container.
Usable Capacity (MHz) The usable CPU resources that are available for the virtual
Disk Metrics for Data Centers

Total IOPS Average number of commands issued per second during the
Total Latency (ms) Average amount of time taken for a command from the
perspective of the guest operating system. This metric is the
sum of the Kernel Latency and Physical Device Latency
metrics.
Total Throughput (KBps) Average of the sum of the data read and written for all the
disk instances of the host or virtual machine.
Total queued outstanding operations Sum of queued operations and outstanding operations.
Max observed OIO Max observed IO for a disk.

Memory Metrics for Data Centers

VMware, Inc. 1010

Contention (%) Machine Contention Percentage.

Machine Demand (KB) Memory machine demand in kilobytes.

ESX System Usage Memory usage by the VM kernel and ESX user-level
services.
Provisioned Memory (KB) Provisioned host memory in kilobytes.

Reserved Capacity (KB) Reserved memory capacity in kilobytes.

Usable Memory (KB) Usable host memory in kilobytes.

Host Usage Host memory use in kilobytes.

Key: mem|host_usage
Usage/Usable (%) Percent host memory used.

VM Overhead Memory overhead reported by host.

Stress Balance Factor Stress Balance Factor.

Lowest Provider Capacity Remaining Lowest Provider Capacity Remaining.

Workload Balance Factor Workload Balance Factor.

Highest Provider Workload Highest Provider Workload.

Host workload Max-Min Disparity Difference of Max and Min host workload in the container.
Host stress Max-Min Disparity Difference of Max and Min host stress in the container.
Utilization (KB) Memory utilization level based on the descendant virtual

machines utilization. Includes reservations, limits, and
overhead to run the Virtual Machines.
Key: mem|total_need
VMware, Inc. 1011

Total Capacity (KB) Total physical memory configured on descendant ESXi

hosts.
Usable Capacity (KB) The usable memory resources available for the virtual
machines after considering reservations for vSphere HA and
Network Metrics for Data Centers

Packets Dropped Percentage of packets dropped.

Key: net|droppedPct
Max Observed Throughput Max observed rate of network throughput.

Key: net|maxObservedKBps
Data Transmit Rate Average amount of data transmitted per second.

Data Receive Rate Average amount of data received per second.

Total Throughput (KBps) The sum of the data transmitted and received for all the
Storage Metrics for Data Centers

Total Usage Total throughput rate.

Datastore Metrics for Data Centers

Datastore metrics provide information about Datastore use.

Read IOPS Average number of read commands issued per second

VMware, Inc. 1012

Write IOPS Average number of write commands issued per second


Disk Space Metrics for Data Centers

Disk space metrics provide information about disk use.
Virtual machine used Used virtual machine disk space in gigabytes.

Key: diskspace|used
Total disk space used Total disk space used on all datastores visible to this
object.
Total disk space Total disk space on all datastores visible to this object.
Total provisioned disk space Total provisioned disk space on all datastores visible to
this object.
Shared Used (GB) Shared disk space in gigabytes.

Snapshot Space (GB) Snapshot disk space in gigabytes.

Virtual Disk Used (GB) Used virtual disk space in gigabytes.

Number of Virtual Disks Number of Virtual Disks.

Utilization (GB) Storage space used on the connected vSphere

Datastores.
Total Capacity (GB) Total storage space available on the connected vSphere
datastores.
Summary Metrics for Data Centers

VMware, Inc. 1013

Number of Running Hosts Number of hosts that are ON.

Number of Running VMs Number of running virtual machines.


Number of Clusters Total number of clusters.

Number of Hosts Total number of hosts.


Total Number of Datastores Total number of datastores.

Number of VCPUs on Powered On VMs Total number of VCPUs of virtual machines that are
powered on.
Workload Indicator Workload indicator.

Average Running VM Count per Running Host Average number of running virtual machines per running
host.
Key: summary|avg_vm_density
Reclaimable Metrics for Data Centers

CPU (vCPUs) Number of reclaimable vCPUs within the data center.

Key: reclaimable|cpu
Disk Space Reclaimable disk space within the data center.

Key: reclaimable|diskspace
Potential Savings Potential saving after reclamation of resources of all

reclaimable VMs (Idle VMs, Powered Off VMs, VM
snapshots) within the data center.
Key: reclaimable|cost
Memory (KB) Reclaimable memory within the data center.

Key: reclaimable|mem
Virtual Machines Number of VMs having reclaimable resources (Memory,

disk space, vCPU) within the data center.
Key: reclaimable|vm_count
VMware, Inc. 1014

within the data center.
Off VMs within the data center.
VM Snapshots|Potential Savings Potential saving after reclamation of VM snapshots within

the data center.
Key: reclaimable|vm_snapshots |cost
Reclaimable|Orphaned Disks|Potential Savings (Currency) Displays the potential savings after reclaimation of disk
space by removing orphaned VMDks from all datastores
under datacenter.
reclaimable|cost
Reclaimable|Number of Orphaned Disks Number of reclaimable orphaned disks is the sum of all
orphaned disks on it's datastore.
reclaimable|orphaned_disk_count
Cost Metrics for Data Centers

Monthly Cluster Aggregated Allocated Cost Sum of the monthly allocated cost for both cluster and
unclustered hosts.
Key: cost|clusterAllocatedCost
Monthly Cluster Aggregated Cost The sum of monthly aggregated allocated and unallocated
cost for both cluster and unclustered hosts.
Key: cost|clusterCost
Monthly Cluster Aggregated Unallocated Cost Sum of the monthly unallocated cost for both cluster and
unclustered hosts.
Key: cost|clusterUnAllocatedCost
Monthly Datacenter Aggregated Total Cost Monthly aggregated total cost for the data center.
Key: cost|aggrTotalCost
Monthly Datastore Total Cost Monthly data store total cost.

Key: cost|totalCost
MTD VM Aggregated Direct Cost Month to date aggregated VM direct cost across all the
VMs under the data center.
Key: cost|vmDirectCost
Disabled Metrics
VMware, Inc. 1015

Metric Name Key

Operations (IOPS)
Datastore I/O|Max Observed Read Rate (KBps) datastore|maxObserved_Read
Datastore I/O|Max Observed Reads per second (IOPS) datastore|maxObserved_NumberRead
Datastore I/O|Max Observed Write Rate (KBps) datastore|maxObserved_Write
Datastore I/O|Max Observed Writes per second (IOPS)0 datastore|maxObserved_NumberWrite
Max Observed Transmitted Throughput Max observed transmitted rate of network throughput.
Max Observed Received Throughput Max observed received rate of network throughput.
Not Shared (GB) Unshared disk space in gigabytes.

Custom Data Center Metrics

vRealize Operations Manager collects CPU usage, memory, summary, network, and datastore
metrics for custom data center objects.
Custom data center metrics include capacity and badge metrics. See definitions in:
n Badge Metrics
CPU Usage Metrics for Custom Data Centers

Host Provisioned Capacity Host provisioned capacity (MHz).

Provisioned vCPU(s) Provisioned vCPU(s).


Number of hosts stressed Number of hosts stressed.

Key: cpu|num_hosts_stressed
Stress Balance Factor Stress balance factor.

Lowest Provider Capacity Remaining Lowest provider capacity remaining.

VMware, Inc. 1016

Workload Balance Factor Workload balance factor.

Highest Provider Workload Highest provider workload.

Host workload Max-Min Disparity Host workload max-min disparity.

Host stress Max-Min Disparity Difference of max and min host stress in the container.
Demand (MHz) CPU utilization level based on descendant virtual machines

utilization. This Includes reservations, limits, and overhead to
run the virtual machines.
Key: cpu|demandmhz
Usable Capacity (MHz) The usable CPU resources that are available for the virtual
Memory Metrics for Custom Data Centers

Memory metrics provide information about memory use.
Usable Memory Usable memory.

Machine Demand Memory machine demand in KB.

Number of hosts stressed Number of hosts stressed.

Key: mem|num_hosts_stressed
Stress Balance Factor Stress balance factor.

Lowest Provider Capacity Remaining Lowest provider capacity remaining.

Workload Balance Factor Workload balance factor.

Highest Provider Workload Highest provider workload.

Host workload Max-Min Disparity Host workload max-min disparity.

Host stress max-min disparity Host stress max-min disparity.

VMware, Inc. 1017

Utilization (KB) Memory utilization level based on the descendant virtual

machines utilization. Includes reservations, limits, and
overhead to run the Virtual Machines.
Key: mem|total_need
Total Capacity (KB) Total physical memory configured on descendant ESXi hosts.
Usable Capacity (KB) The usable memory resources available for the virtual
machines after considering reservations for vSphere HA and
Summary Metrics for Custom Data Centers

Number of Running VMs Number of virtual machines that are ON.


Status Status of the data center.

Key: summary|status
Network Metrics for Custom Data Centers

Usage Rate The sum of the data transmitted and received for all the NIC
Data Transmit Rate Average amount of data transmitted per second.

Data REceive Rate Average amount of data received per second.

Datastore Metrics for Custom Data Centers

VMware, Inc. 1018


Read IOPS Average number of read commands issued per second during
Write IOPS Average number of write commands issued per second during

Reclaimable Metrics for Custom Data Centers

CPU (vCPUs) Number of reclaimable vCPUs within the custom data

center.
Key: reclaimable|cpu
Disk Space Reclaimable disk space within the custom data center.
Key: reclaimable|diskspace
Potential Savings Potential saving after reclamation of resources of all

reclaimable VMs (Idle VMs, Powered Off VMs, VM
snapshots) within the custom data center.
Key: reclaimable|cost
Memory (KB) Reclaimable memory within the custom data center.

Key: reclaimable|mem
Number of Orphaned Disks Number of reclaimable orphaned disks within the custom
data center.
Reclaimable|Orphaned Disks|Potential Savings Potential savings in cost after reclamation of orphaned

disks across the custom data center.
Key: reclaimable|orphaned_disk|cost
Note The orphaned disk reclamation feature might not

work as expected when vRealize Operations Manager
monitors multiple vCenters which use shared data stores.
Virtual Machines Number of VMs having reclaimable resources (Memory,

disk space, vCPU) within the custom data center.
Key: reclaimable|vm_count
VMware, Inc. 1019

within the custom data center.
Off VMs within the custom data center.
VM Snapshots|Potential Savings Potential saving after reclamation of VM snapshots within

the custom data center.
Key: reclaimable|vm_snapshots |cost
Reclaimable|Orphaned Disks|Potential Savings (Currency) Displays the potential savings after reclaimation of disk
space by removing orphaned VMDks from all datastores
under custom datacenters.
reclaimable|cost
Reclaimable|Number of Orphaned Disks Number of reclaimable orphaned disks is the sum of the
numbers of orphaned disks on it's datastore.
Disk Space Metrics for Custom Data Centers

Disk space metrics provide information about disk use.
Utilization (GB) Storage space used on the connected vSphere

Datastores.
Total Capacity (GB) Total storage space available on the connected vSphere
datastores.
Disabled Metrics
Metric Name Key
Max Observed Throughput Max observed rate of network throughput.

Key: net|maxObserved_KBps
Max Observed Transmitted Throughput Max observed transmitted rate of network throughput.
Max Observed Received Throughput Max observed received rate of network throughput.
VMware, Inc. 1020

Metric Name Key
Max Observed Reads per second Max observed average number of read commands issued
per second during the collection interval.
Key: datastore|maxObserved_NumberRead
Max Observed Read Rate Max observed rate of reading data from the datastore.
Key: datastore|maxObserved_Read
Max Observed Writes per second Max observed average number of write commands issued
per second during the collection interval.
Key: datastore|maxObserved_NumberWrite
Max Observed Write Rate Max observed rate of writing data from the datastore.
Key: datastore|maxObserved_Write
Max Observed Number of Outstanding IO Operations Max observer number of outstanding IO operations.
Key: datastore|maxObserved_OIO
Storage Pod Metrics

vRealize Operations Manager collects datastore and disk space metrics for storage pod objects.
Storage Pod metrics include capacity and badge metrics. See definitions in:
n Badge Metrics
Table 7-2. Datastore Metrics for Storage Pods

Read IOPS Average number of read commands issued per second during the
Writes per second Average number of write commands issued per second during

Total Throughput (KBps) Usage Average.

Read Latency Average amount of time for a read operation from the datastore.
Total latency = kernel latency + device latency.
Write Latency Average amount of time for a write operation to the datastore.
Total latency = kernel latency + device latency.
VMware, Inc. 1021

Table 7-2. Datastore Metrics for Storage Pods (continued)

Total Latency (ms) The average amount of time taken for a command from the
perspective of a Guest OS. This is the sum of Kernel Command
Latency and Physical Device Command Latency.
Total IOPS Average number of commands issued per second during the
Table 7-3. Disk Space Metrics for Storage Pods

Freespace Unused space available on datastore.

Key: diskspace|freespace
Total used Total space used.

Key: diskspace|disktotal
Capacity Total capacity of datastore.

Key: diskspace|capacity
Virtual Machine used Space used by virtual machine files.

Key: diskspace|used
Snapshot Space Space used by snapshots.

VMware Distributed Virtual Switch Metrics

vRealize Operations Manager collects network and summary metrics for VMware distributed
virtual switch objects.
VMware Distributed Virtual Switch metrics include badge metrics. See definitions in Badge
Metrics.
Table 7-4. Network Metrics for VMware Distributed Virtual Switches

Total Ingress Traffic Total ingress traffic (KBps).

Key: network|port_statistics|rx_bytes
Total Egress Traffic Total egress traffic (KBps).

Key: network|port_statistics|tx_bytes
Egress Unicast Packets per second Egress unicast packets per second.
Key: network|port_statistics|ucast_tx_pkts
Egress Multicast Packets per second Egress multicast packets per second.
Key: network|port_statistics|mcast_tx_pkts
Egress Broadcast Packets per second Egress broadcast packets per second.
Key: network|port_statistics|bcast_tx_pkts
VMware, Inc. 1022

Table 7-4. Network Metrics for VMware Distributed Virtual Switches (continued)
Ingress Unicast Packets per second Ingress unicast packets per second.
Key: network|port_statistics|ucast_rx_pkts
Ingress Multicast Packets per second Ingress multicast packets per second.
Key: network|port_statistics|mcast_rx_pkts
Ingress Broadcast Packets per second Ingress broadcast packets per second.
Key: network|port_statistics|bcast_rx_pkts
Egress Dropped Packets per second Egress dropped packets per second.
Key: network|port_statistics|dropped_tx_pkts
Ingress Dropped Packets per second Ingress dropped packets per second.
Key: network|port_statistics|dropped_rx_pkts
Total Ingress Packets per second Total ingress packets per second.
Key: network|port_statistics|rx_pkts
Total Egress Packets per second Total egress packets per second.
Key: network|port_statistics|tx_pkts
Utilization Use (KBps).

Key: network|port_statistics|utilization
Total Dropped Packets per second Total dropped packets per second.
Key: network|port_statistics|dropped_pkts
Percentage of Dropped Packets Percentage of dropped packets.

Key: network|port_statistics|dropped_pkts_pct
Max Observed Ingress Traffic (KBps) Max observed ingress traffic (KBps).
Key: network|port_statistics|maxObserved_rx_bytes
Max Observed Egress Traffic (KBps) Max observed egress traffic (KBps).
Key: network|port_statistics|maxObserved_tx_bytes
Max Observed Utilization (KBps) Max observed utilization (KBps).

Key: network|port_statistics|maxObserved_utilization
Table 7-5. Summary Metrics for VMware Distributed Virtual Switches

Maximum Number of Ports Maximum number of ports.

Key: summary|max_num_ports
Used Number of Ports Used number of ports.

Key: summary|used_num_ports
Number of Blocked Ports Number of blocked ports.

Key: summary|num_blocked_ports
VMware, Inc. 1023

Table 7-6. Host Metrics for VMware Distributed Virtual Switches

MTU Mismatch Maximum Transmission Unit (MTU) mismatch.

Key: host|mtu_mismatch
Teaming Mismatch Teaming mismatch.

Key: host|teaming_mismatch
Unsupported MTU Unsupported MTU.

Key: host|mtu_unsupported
Unsupported VLANs Unsupported VLANs.

Key: host|vlans_unsupported
Config Out Of Sync Config Out Of Sync.

Key: host|config_outofsync
Number of Attached pNICs Number of attached physical NICs.

Key: host|attached_pnics
Distributed Virtual Port Group Metrics

The vCenter Adapter instance collects network and summary metrics for distributed virtual port
groups.
Distributed Virtual Port Group metrics include badge metrics. See definitions in Badge Metrics.
Table 7-7. Network Metrics for Distributed Virtual Port Groups

Ingress Traffic Ingress traffic (KBps).

Key: network|port_statistics|rx_bytes
Egress Traffic Egress traffic (KBps).

Key: network|port_statistics|tx_bytes
Egress Unicast Packets per second Egress unicast packets per second.
Key: network|port_statistics|ucast_tx_pkts
Egress Multicast Packets per second Egress multicast packets per second.
Key: network|port_statistics|mcast_tx_pkts
Egress Broadcast Packets per second Egress broadcast packets per second.
Key: network|port_statistics|bcast_tx_pkts
Ingress Unicast Packets per second Ingress unicast packets per second.
Key: network|port_statistics|ucast_rx_pkts
Ingress Multicast Packets per second Ingress multicast packets per second.
Key: network|port_statistics|mcast_rx_pkts
Ingress Broadcast Packets per second Ingress broadcast packets per second.
Key: network|port_statistics|bcast_rx_pkts
Egress Dropped Packets per second Egress dropped packets per second.
Key: network|port_statistics|dropped_tx_pkts
VMware, Inc. 1024

Table 7-7. Network Metrics for Distributed Virtual Port Groups (continued)
Ingress Dropped Packets per second Ingress dropped packets per second.
Key: network|port_statistics|dropped_rx_pkts
Total Ingress Packets per second Total Ingress packets per second.
Key: network|port_statistics|rx_pkts
Total Egress Packets per second Total Egress packets per second.
Key: network|port_statistics|tx_pkts
Utilization Utilization (KBps).

Key: network|port_statistics|utilization
Total Dropped Packets per second Total dropped packets per second.
Key: network|port_statistics|dropped_pkts
Percentage of Dropped Packets Percentage of dropped packets.

Key: network|port_statistics|dropped_pkts_pct
Max Observed Ingress Traffic (KBps) Max observed ingress traffic (KBps).
Key: network|port_statistics|maxObserved_rx_bytes
Max Observed Egress Traffic (KBps) Max observed egress traffic (KBps).
Key: network|port_statistics|maxObserved_tx_bytes
Max Observed Utilization (KBps) Max observed utilization (KBps).

network|port_statistics|maxObserved_utilization
Table 7-8. Summary Metrics for Distributed Virtual Port Groups

Maximum Number of Ports Maximum number of ports.

Key: summary|max_num_ports
Used Number of Ports Used number of ports.

Key: summary|used_num_ports
Number of Blocked Ports The number of blocked ports.

Key: summary|num_blocked_ports
Datastore Cluster Metrics

vRealize Operations Manager collects profile metrics for the datastore cluster resources.
Profiles Metrics for Datastore Cluster Resources

Profiles metrics provide information about the profile specific capacity.
VMware, Inc. 1025

Profiles|Capacity Remaining Profile (Average) The capacity remaining in terms of fitting the average
consumer.
Profiles|Capacity Remaining Profile (<custom profile Published for custom profiles enabled from policy on
name>) Datastore Cluster Resource.
Capacity Allocation Metrics for Datastore Cluster Resources

Capacity allocation metrics provide information about the allotment of capacity, see Capacity
Analytics Generated Metrics.
Datastore Metrics
vRealize Operations Manager collects capacity, device, and summary metrics for datastore
objects.
Capacity metrics can be calculated for datastore objects. See Capacity Analytics Generated
Metrics.
Capacity Metrics for Datastores

Capacity metrics provide information about datastore capacity.
Capacity|Available Space (GB) This metric shows the amount of free space that a
datastore has available.
Use this metric to know how much storage space is
unused on the datastore. Try to avoid having too little
free disk space in order to accommodate unexpected
storage growth on the datastore. The exact size of the
datastore is based on company policy.
Key: capacity|available_space
Capacity|Provisioned (GB) This metric shows the amount of storage that was
allocated to the virtual machines.
Use this metric to know how much storage space is being
used on the datastore.
Check the metric trend to identify spikes or abnormal
growth.
Key: capacity|provisioned
VMware, Inc. 1026

Capacity|Total Capacity (GB) This metric shows the overall size of the datastore.
Use this metric to know the total capacity of the
datastore.
Typically the size of the datastore should not be too
small. VMFS datastore size has grown over the years as
virtualization matures and larger virtual machines are now
onboard. Ensure that the size can handle enough virtual
machines to avoid datastore sprawl. A best practice is to
use 5 TB for VMFS and more for vSAN.
Key: capacity|total_capacity
Capacity|Used Space (GB) This metric shows the amount of storage that is being
Key: capacity|used_space
Capacity|Workload (%) Capacity workload.

Key: capacity|workload
Capacity|Uncommitted Space (GB) Uncommitted space in gigabytes.

Key: capacity|uncommitted
Capacity|Total Provisioned Consumer Space Total Provisioned Consumer Space.

Key: capacity|consumer_provisioned
Capacity|Used Space (%) This metric shows the amount of storage that is being
Use this metric to know the percentage of storage space
being used on the datastore.
When using this metric, verify that you have at least 20%
of free storage. Less than this, and you might experience
problems when a snapshot is not deleted. If you have
more than 50% free storage space, you are not utilizing
your storage in the best possible way.
Key: capacity|usedSpacePct
Device Metrics for Datastores

Device metrics provide information about device performance.
Devices|Bus Resets This metric shows the number of bus resets in the
Key: devices|busResets_summation
Devices|Commands Aborted This metric shows the number of disk commands

canceled in the performance interval.
Key: devices|commandsAborted_summation
Devices|Commands Issued This metric shows the number of disk commands issued in
the performance interval.
Key: devices|commands_summation
VMware, Inc. 1027

Devices|Total Latency (ms) This metric shows the average time taken for a command
from the perspective of a guest operating system. This
metric is the sum of Kernel Latency and Physical Device
Latency metrics.
Key: devices|totalLatency_average
Devices|Read Latency (ms) This metric shows the average time taken for a read from
the perspective of a guest operating system. This metric
is the sum of the Kernel Disk Read Latency and Physical
Device Read Latency metrics.
Key: devices|totalReadLatency_averag
Devices|Write Latency (ms) This metric shows the average amount of time for a write
operation to the datastore. Total latency is the sum of
kernel latency and device latency.
Key: devices|totalWriteLatency_average
Devices|Kernel Latency (ms) Average time spent in ESX Server V. Kernel per
command.
Key: devices|kernelLatency_average
Devices|Kernel Disk Read Latency (ms) Average time spent in ESX host VM Kernel per read.
Key: devices|kernelReadLatency_average
Devices|Kernel Write Latency (ms) Average time spent in ESX Server VM Kernel per write.
Key: devices|kernelWriteLatency_average
Devices|Number of Running Hosts Number of running hosts that are powered on.
Key: devices|number_running_hosts
Devices|Number of Running VMs Number of running virtual machines that are powered on.
Key: devices|number_running_vms
Devices|Physical Device Latency (ms) Average time taken to complete a command from the
physical device.
Key: devices|deviceLatency_average
Devices|Physical Device Read Latency (ms) Average time taken to complete a read from the physical
device.
Key: devices|deviceReadLatency_average
Devices|Queue Latency (ms) Average time spent in the ESX Server VM Kernel queue
per command.
Key: devices|queueLatency_average
Devices|Queue Read Latency (ms) Average time spent in the ESX Server VM Kernel queue
per read.
Key: devices|queueReadLatency_average
Devices|Queue Write Latency (ms) Average time spent in the ESX Server VM Kernel queue
per write.
Key: devices|queueWriteLatency_average
Devices|Read Throughput (KBps) Amount of data read in the performance interval.

Key: devices|read_average
VMware, Inc. 1028

Devices|Read Requests Number of times data was read from the disk in the
defined interval.
Key: devices|numberRead_summation
Devices|Read IOPS Average number of read commands issued per second to

the datastore during the collection interval.
Key: devices|numberReadAveraged_average
Devices|Total Throughput (KBps) Average use in kilobytes per second.

Key: devices|usage_average
Devices|Write Throughput (KBps) Amount of data written to disk in the performance

interval.
Key: devices|write_average
Devices|Write Requests Number of times data was written to the disk in the
defined interval.
Key: devices|numberWrite_summation
Devices|Total IOPS Average number of write commands issued per second to

the datastore during the collection interval.
Key: devices|numberWriteAveraged_average
Devices|Total IOPS Average number of commands issued per second during

Key: devices|commandsAveraged_average
Devices|Physical Device Write Latency (ms) Average time taken to complete a write from the physical
disk.
Key: devices|deviceWriteLatency_average
Datastore Metrics for Datastores

VMware, Inc. 1029

Datastore|Total Latency (ms) This metric shows the adjusted read and write latency at
the datastore level. Adjusted means that the latency is
taking into account the number of IOs. If your IO is read-
dominated, the combined value is influenced by the
reads.
This is the average of all the VMs running in the
datastore. Because it is an average, some VMs logically
experience higher latency that the value shown by this
metric. To see the worst latency experienced by any VM,
use the Maximum VM Disk Latency metric.
Use this metric to see the performance of the datastore.
It is one of two key performance indicators for a
datastore, the other being the Max Read Latency. The
combination of Maximum and Average gives better
insight into how well the datastore is coping with the
demand.
The number should be lower than the performance you
expect.
Datastore|Total Throughput (KBps) Average use in kilobytes per second.

Datastore|Read Latency (ms Average amount of time for a read operation from the
latency.
latency.
Datastore|Demand Demand.

Datastore|Read IOPS This metric displays the average number of read

commands issued per second during the collection
interval.
Use this metric when the total IOPS is higher than
expected. See if the metric is read or write dominated.
This helps determine the cause of the high IOPS. Certain
workloads such as backups, anti-virus scans, and
Windows updates carry a Read/Write pattern. For
example, an anti-virus scan is heavy on read since it is
mostly reading the file system.
VMware, Inc. 1030

Datastore|Write IOPS This metric displays the average number of write

commands issued per second during the collection
interval.
Use this metric when the total IOPS is higher than
expected. Drill down to see if the metric is read or write
dominated. This helps determine the cause of the high
IOPS. Certain workloads such as backups, anti-virus
scans, and Windows updates carry a Read/Write pattern.
For example, an anti-virus scan is heavy on read since it
is mostly reading the file system.
Datastore|Read Throughput (KBps) This metric displays the amount of data read in the
Datastore|Write Throughput (KBps) This metric displays the amount of data written to disk in
the performance interval.
About Datastore Metrics for Virtual SAN

The metric named datastore|oio|workload is not supported on Virtual SAN datastores. This
metric depends on datastore|demand_oio, which is supported for Virtual SAN datastores.
The metric named datastore|demand_oio also depends on several other metrics for Virtual SAN
datastores, one of which is not supported.
n The metrics named devices|numberReadAveraged_average and devices|

numberWriteAveraged_average are supported.
n The metric named devices|totalLatency_average is not supported.
As a result, vRealize Operations Manager does not collect the metric named datastore|oio|
workload for Virtual SAN datastores.
Disk Space Metrics for Datastores

Diskspace|Number of Virtual Disk Number of virtual disks.

Diskspace|Provisioned Space (GB) Provisioned space in gigabytes.

Key: diskspace|provisioned
Diskspace|Shared Used (GB) Shared used space in gigabytes.

VMware, Inc. 1031

Diskspace|Snapshot Space (GB) This metric shows the amount of space taken by
snapshots on a given database.
Use this metric to know how much storage space is being
used by virtual machine snapshots on the datastore.
Check that the snapshot is using 0 GB or minimal space.
Anything over 1 GB should trigger a warning. The actual
value depends on how IO intensive the virtual machines in
the datastore are. Run a DT on them to detect anomaly.
Clear the snapshot within 24 hours, preferably when you
have finished backing up, or patching.
Diskspace|Virtual Disk Used (GB) Virtual disk used space in gigabytes.

Diskspace|Virtual machine used (GB) Virtual machine used space in gigabytes.

Key: diskspace|used
Diskspace|Total disk space used Total disk space used on all datastores visible to this
object.
Diskspace|Total disk space Total disk space on all datastores visible to this object.
Diskspace|Total used (GB) Total used space in gigabytes.

Key: diskspace|disktotal
Diskspace|Swap File Space (GB) Swap file space in gigabytes.

Key: diskspace|swap
Diskspace|Other VM Space (GB) Other virtual machine space in gigabytes.

Key: diskspace|otherused
Diskspace|Freespace (GB) Unused space available on datastore.

Key: diskspace|freespace
Diskspace|Capacity (GB) Total capacity of datastore in gigabytes.

Key: diskspace|capacity
Diskspace|Overhead Amount of disk space that is overhead.

Key: diskspace|overhead
Summary Metrics for Datastores

VMware, Inc. 1032

Summary|Number of Hosts This metric shows the number of hosts that the datastore
is connected to.
Use this metric to know how many clusters the datastore
is attached to.
The number should not be too high, as a datastore should
not be mounted by every host. The datastore and cluster
should be paired to keep operations simple.
Summary|Number of VMs This metric shows the number of virtual machines which
save their VMDK files on the datastore. If a VM has four
VMDKs stored in four datastores, the VM is counted on
each datastore.
Use this metric to know how many VMs have at least one
VMDK on a specific datastore.
The number of VMs should be within your Concentration
Risk policy.
You should also expect the datastore to be well used. If
only a few VMs are using the datastore, this is not
considered a good use.
Summary|Maximum Number of VMs Maximum number of virtual machines.

Summary|Workload Indicator Workload indicator.

Summary|Number of Clusters This metric shows the number of clusters that the
datastore is connected to.
Template Metrics for Datastores
Template|Virtual Machine used Space used by virtual machine files.

Key: template|used
Template|Access Time Last access time.

Key: template|accessTime
Cost Metrics for Datastores

Cost metrics provides information about the cost.
VMware, Inc. 1033

Monthly Storage Rate Monthly storage rate for datastore displays the cost of 1 GB
storage.
Key: cost|storageRate
Monthly Datastore Total Cost Monthly total cost for datastore, computed by multiplying
datastore capacity with monthly storage rate.
Key: cost|totalCost
Cost|Allocation|Monthly Storage Rate (Currency) Monthly storage rate for datastore displays the cost of 1 GB
storage when the overcommit ratio is set in policy.
cost|storageRate
Reclaimable Metrics
Reclaimable|Orphaned Disks|Disk Space (GB) Summary of storage used by all orphaned VMDKs on the
datastore.
Key: reclaimable|orphaned_disk|diskspace
Reclaimable|Orphaned Disks|Potential Savings (Currency) Potential saving after reclaimation of storage by removing
orphaned VMDks from the datastore.
Key: reclaimable|orphaned_disk|cost
Disabled Metrics
Metric Name Key
Capacity|Data Store Capacity Contention (%) capacity|contention
Datastore I/O|Demand Indicator datastore|demand_indicator

Operations
Datastore I/O|Max Observed Read Latency (msec) datastore|maxObserved_Read
Datastore I/O|Max Observed Read Latency (msec) datastore|maxObserved_ReadLatency
Datastore I/O|Max Observed datastore|maxObserved_NumberRead
Datastore I/O|Max Observed Write Latency (msec) datastore|maxObserved_Write
Datastore I/O|Max Observed Write Latency (msec) datastore|maxObserved_WriteLatency
VMware, Inc. 1034

Metric Name Key
Datastore|Demand Indicator Demand Indicator.

Key: datastore|demand_indicator
Diskspace|Not Shared (GB) Unshared space in gigabytes.

Cluster Compute Metrics for Allocation Model

power, and summary metrics for cluster compute resources.
Cost Metrics for Cluster Compute Resources

Cluster CPU Base Rate Base rate for Cluster CPU calculated by dividing the
monthly total cluster CPU cost by cluster CPU over-commit
ratio.
Key:Cost|Allocation|ClusterCPUBaseRate
Cluster Memory Base Rate Cluster memory base rate calculated by dividing the
monthly total cluster memory cost b cost by cluster
memory over-commit ratio.
Key: Cost|Allocation|ClusterMemoryBaseRate
Monthly Cluster Allocated Cost Sum of of monthly cluster CPU, Memory, and Storage costs
Key: Cost|Allocation|MonthlyClusterAllocatedCost
Monthly Cluster Unallocated Cost Monthly cluster unallocated cost calculated by subtracting
the monthly cluster allocated cost from the monthly cluster
total cost.
Key: Cost|Allocation| MonthlyClusterUnallocatedCost
Monthly Storage Rate Datastore base rate is calculated by dividing Storage base
rate based on utilization by over commit ratio.
Key:Cost|Allocation|Monthly Storage Rate
Virtual Machine Metrics for Allocation Model

power, and summary metrics for virtual machine resources.
Cost Metrics for Virtual Machines

VMware, Inc. 1035

MTD VM CPU Cost Month to date virtual machine CPU cost.

Key: Cost|Allocation|MTD VM CPU Cost
MTD VM Memory Cost Month to date virtual machine memory cost.

Key: Cost|Allocation|MTD VM Memory Cost
MTD VM Storage Cost Month to date storage cost of the virtual machine.
Key: Cost|Allocation|MTD VM Storage Cost
MTD VM Total Cost Addition of CPU ,Memory ,Storage, and Direct cost.
Key: Cost|Allocation|MTD VM Total Cost
Operating System Metrics Collected by vRealize Application Remote

Collector
vRealize Application Remote Collector collects metrics for Linux and Windows operating systems.
Linux Platforms
vRealize Application Remote Collector collects the following metrics for Linux Operating Systems:
Table 7-9. Metrics for Linux

Usage Idle CPU FALSE
Usage IO-Wait CPU FALSE
Usage System CPU FALSE
IO Time Disk FALSE
Read Time Disk FALSE
Reads Disk FALSE
Write Time Disk FALSE
Writes Disk FALSE
Cached Memory FALSE
Free Memory FALSE
Inactive Memory FALSE
Total Memory TRUE
Used Memory TRUE
Used Percent Memory TRUE
Blocked Processes TRUE
Dead Processes FALSE
Running Processes FALSE
Sleeping Processes FALSE
Stopped Processes FALSE
VMware, Inc. 1036

Table 7-9. Metrics for Linux (continued)

Free Swap FALSE
In Swap FALSE
Out Swap FALSE
Total Swap TRUE
Used Swap TRUE
Used Percent Swap TRUE
Windows Platforms
vRealize Application Remote Collector collects the following metrics for Windows Operating
Systems:
Table 7-10. Metrics for Windows

Idle Time CPU FALSE
Interrupt Time CPU FALSE
Interrupts persec CPU TRUE
Privileged Time CPU FALSE
Processor Time CPU FALSE
User Time CPU FALSE
Avg. Disk Bytes Read Disk FALSE
Avg. Disk sec Read Disk FALSE
Avg. Disk sec Write Disk FALSE
Avg. Disk Write Queue Length Disk FALSE
Disk Read Time Disk FALSE
Disk Write Time Disk FALSE
Free Megabytes Disk FALSE
Free Space Disk FALSE
Idle Time Disk FALSE
Split IO persec Disk FALSE
Available Bytes Memory TRUE
Cache Bytes Memory FALSE
Cache Faults persec Memory FALSE
Committed Bytes Memory TRUE
Demand Zero Faults persec Memory FALSE
Page Faults persec Memory TRUE
VMware, Inc. 1037

Table 7-10. Metrics for Windows (continued)

Pages persec Memory FALSE
Pool Nonpaged Bytes Memory TRUE
Pool Paged Bytes Memory FALSE
Transition Faults persec Memory FALSE
Elasped Time Process FALSE
Handle Count Process FALSE
IO Read Bytes persec Process FALSE
IO Read Operations persec Process FALSE
IO Write Bytes persec Process FALSE
IO Write Operations persec Process FALSE
Privileged Time Process FALSE
Processor Time Process FALSE
Thread Count Process FALSE
User Time Process FALSE
Context Switches persec System FALSE
Processes System FALSE
Processor Queue Length System FALSE
System Calls persec System FALSE
System Up Time System FALSE
Threads System FALSE
Application Service Metrics Collected by vRealize Application

Remote Collector
vRealize Application Remote Collector collects metrics for 17 application services.
Active Directory Metrics

vRealize Application Remote Collector discovers metrics for Active Directory application service.
Table 7-11. Active Directory Metrics

Database Cache % Hit (%) Active Directory Database True
Database Cache Page Faults/sec Active Directory Database True
Database Cache Size Active Directory Database False
Data Lookups Active Directory DFS Replication False
VMware, Inc. 1038

Table 7-11. Active Directory Metrics (continued)

Database Commits Active Directory DFS Replication True
Avg Response Time Active Directory DFSN True
Requests Failed Active Directory DFSN False
Requests Processed Active Directory DFSN False
Dynamic Update Received Active Directory DNS False
Dynamic Update Rejected Active Directory DNS False
Recursive Queries Active Directory DNS False
Recursive Queries Failure Active Directory DNS False
Secure Update Failure Active Directory DNS False
Total Query Received Active Directory DNS True
Total Response Sent Active Directory DNS True
Digest Authentications Active Directory Security System- True

Wide Statistics
Kerberos Authentications Active Directory Security System- True

Wide Statistics
NTLM Authentications Active Directory Security System- True

Wide Statistics

Base Searches persec

Database adds persec

Database deletes persec

LDAP Active Threads

LDAP Client Sessions

LDAP Writes/sec
No metrics are collected for the category Active Directory.
Apache Tomcat
vRealize Application Remote Collector discovers metrics for Apache Tomcat application service.
VMware, Inc. 1039

Table 7-12. Apache Tomcat




Committed Memory

Initial Memory

Maximum Memory

Used Memory




Usage|Used Memory
JVM Memory|Number of Object Tomcat Server True









Usage|Used Memory
Process CPU Usage (%) Tomcat Server True
System CPU Usage (%) Tomcat Server True
Uptime Tomcat Server True
VMware, Inc. 1040


Cache|Hit Count Tomcat Server Web Module True
Cache|Lookup Count Tomcat Server Web Module False
JSP Count Tomcat Server Web Module False
JSP Reload Count Tomcat Server Web Module False
JSP Unload Count Tomcat Server Web Module False
Current Thread Count Tomcat Server Global Request False

Processor
Current Threads Busy Tomcat Server Global Request True

Processor
Total Request Bytes Received Tomcat Server Global Request False

Processor
Total Request Bytes Sent Tomcat Server Global Request False

Processor
Total Request Count Tomcat Server Global Request True

Processor
Total Request Error Count Tomcat Server Global Request True

Processor
Total Request Processing Time Tomcat Server Global Request True

Processor
MS SQL Metrics
vRealize Application Remote Collector discovers metrics for MS SQL application service.
Table 7-13. MS SQL Metrics

CPU:<InstanceName>|CPU Usage (%) Microsoft SQL Server False
Performance|Broker Activation|Stored Microsoft SQL Server False

Procedures Invoked per second
Performance|Buffer Manager|Buffer Microsoft SQL Server False

cache hit ratio (%)
Performance|Buffer Manager|Lazy Microsoft SQL Server False

writes per second
Performance|Buffer Manager|Page life Microsoft SQL Server False

expectancy

lookups per second

reads per second

writes per second
VMware, Inc. 1041


Performance|Databases|Active Microsoft SQL Server False

Transactions
Performance|Databases|Data File(s) Microsoft SQL Server False

Size

Size

Used Size
Performance|Databases|Log Flush Microsoft SQL Server False

Wait Time
Performance|Databases|Log Flushes Microsoft SQL Server False

per second
Performance|Databases|Transactions Microsoft SQL Server False

per second
Performance|Databases|Write Microsoft SQL Server False

Transactions per second
Performance|Databases|XTP Memory Microsoft SQL Server False

Used
Performance|General Statistics|Logins Microsoft SQL Server False

per second

Logouts per second

Processes Blocked
Performance|General Statistics|User Microsoft SQL Server False

Connections
Performance|Locks|Average Wait Time Microsoft SQL Server False
Performance|Locks|Lock Requests per Microsoft SQL Server False

second
Performance|Locks|Lock Wait Time Microsoft SQL Server False
Performance|Locks|Lock Waits per Microsoft SQL Server False

second
Performance|Locks|Number of Microsoft SQL Server False

Deadlocks per second
Performance|Memory Manager|SQL Microsoft SQL Server False

Cache Memory
Performance|Memory Manager|Target Microsoft SQL Server False

Server Memory
Performance|Memory Manager|Total Microsoft SQL Server False

Server Memory
VMware, Inc. 1042



default|Active memory grant amount

default|Disk Read Bytes per second

default|Disk Read IO

default|Disk Read IO Throttled per
second

default|Disk Write Bytes per second

default|Disk Write IO Throttled per
second

default|Used memory
Performance|SQL Statistics|Batch Microsoft SQL Server False

Requests per second
Performance|SQL Statistics|SQL Microsoft SQL Server False

Performance|SQL Statistics|SQL Re- Microsoft SQL Server False


internal|Active memory grant amount

internal|Disk Read Bytes per second

internal|Disk Read IO

internal|Disk Read IO Throttled per
second

internal|Disk Write Bytes per second

internal|Disk Write IO Throttled per
second

internal|Used memory

default|Blocked Tasks

default|CPU usage (%)
VMware, Inc. 1043



internal|Blocked Tasks

internal|CPU usage (%)
Wait Stats:<InstanceName>|Wait Time Microsoft SQL Server False
There are no metrics collected for Microsoft SQL Server Database.
PostgresSQL
vRealize Application Remote Collector discovers metrics for PostgresSQL application service.
Table 7-14. PostgresSQL

Buffers|Buffers Allocated PostgresSQL False
Buffers|Buffers Written by Backend PostgresSQL True
Buffers|Buffers Written by Background PostgresSQL False

Writer
Buffers|Buffers Written During PostgresSQL True

Checkpoints
Buffers|fsync Call Executed by PostgresSQL True

Backend
Disk Blocks|Blocks Cache Hits PostgresSQL Database False
Disk Blocks|Blocks Read PostgresSQL Database False
Disk Blocks|Blocks Read Time PostgresSQL Database True
Disk Blocks|Blocks Write Time PostgresSQL Database True
Statistics|Backends Connected PostgresSQL Database False
Statistics|Data Written by Queries PostgresSQL Database False
Statistics|Deadlocks Detected PostgresSQL Database True
Statistics|Queries Cancelled PostgresSQL Database True
Statistics|Temp Files Created by PostgresSQL Database False

Queries
Transactions|Transactions Committed PostgresSQL Database True
Transactions|Transactions Rolled Back PostgresSQL Database True
Tuples|Tuples Deleted PostgresSQL Database True
Tuples|Tuples Fetched PostgresSQL Database False
Tuples|Tuples Inserted PostgresSQL Database True
Tuples|Tuples Returned PostgresSQL Database False
Tuples|Tuples Updated PostgresSQL Database True
VMware, Inc. 1044

IIS Metrics
vRealize Application Remote Collector discovers metrics for IIS application service.
Table 7-15. IIS Metrics

CurrentQueueSize IIS HTTP Service Request Queues True
RejectedRequests IIS HTTP Service Request Queues False
Web Services:<InstanceName>|Bytes IIS Web Services False

Received
Web Services:<InstanceName>| IIS Web Services False

Connection Attempts/sec
Web Services:<InstanceName>|Current IIS Web Services False

Connections
Web Services:<InstanceName>|Get IIS Web Services False

Requests/sec
Web Services:<InstanceName>|Not IIS Web Services False

Found Errors/sec
Web Services:<InstanceName>|Post IIS Web Services False

Requests/sec
Web Services:<InstanceName>|Service IIS Web Services False

Uptime

Hits

Hits Percent (%)

Misses
Web Services:<InstanceName>|File IIS Web Services Cache False

Cache Hits Percent
Web Services:<InstanceName>| IIS Web Services Cache False

Flushed URIs
MS Exchange Server Metrics

vRealize Application Remote Collector discovers metrics for MS Exchange Server application
service.
Table 7-16. MS Exchange Server Metrics

Active Manager Server|Active Manager MS Exchange False

Role
Active Manager Server|Database State MS Exchange False

Info Writes per second
VMware, Inc. 1045


Active Manager Server| MS Exchange False

GetServerForDatabase Server-Side
Calls
Active Manager Server|Server-Side MS Exchange True

Calls per second
Active Manager Server|Total Number MS Exchange True

of Databases
ActiveSync|Average Request Time MS Exchange True
ActiveSync|Current Requests MS Exchange False
ActiveSync|Mailbox Search Total MS Exchange False
ActiveSync|Ping Commands Pending MS Exchange False
ActiveSync|Requests per second MS Exchange True
ActiveSync|Sync Commands per MS Exchange True

second
ASP.NET|Application Restarts MS Exchange False
ASP.NET|Request Wait Time MS Exchange True
ASP.NET|Worker Process Restarts MS Exchange False
Autodiscover Service|Requests per MS Exchange True

second
Availability Service|Average Time to MS Exchange True

Process a Free Busy Request
Outlook Web Access|Average Search MS Exchange True

Time
Outlook Web Access|Requests per MS Exchange False

second
Outlook Web Access|Current Unique MS Exchange False

Users
Performance|Database Cache Hit (%) MS Exchange Database False
Performance|Database Page Fault MS Exchange Database True

Stalls per second
Performance|I/O Database Reads MS Exchange Database True

Average Latency
Performance|I/O Database Writes MS Exchange Database True

Average Latency
Performance|I/O Log Reads Average MS Exchange Database False

Latency
Performance|I/O Log Writes Average MS Exchange Database False

Latency
Performance|Log Record Stalls per MS Exchange Database False

second
VMware, Inc. 1046


Performance|Log Threads Waiting MS Exchange Database False
Performance|I/O Database Reads MS Exchange Database Instance False

Average Latency
Performance|I/O Database Writes MS Exchange Database Instance False

Average Latency
Performance|Log Record Stalls per MS Exchange Database Instance False

second
Performance|Log Threads Waiting MS Exchange Database Instance False
Performance|LDAP Read Time MS Exchange Domain Controller False
Performance|LDAP Search Time MS Exchange Domain Controller False
Performance|LDAP Searches Timed MS Exchange Domain Controller False

Out per minute
Performance|Long Running LDAP MS Exchange Domain Controller False

Operations per minute
Performance|Connection Attempts per MS Exchange Web Server True

second
Performance|Current Connections MS Exchange Web Server False
Performance|Other Request Methods MS Exchange Web Server False

per second
Process|Handle Count MS Exchange Windows Service False
Process|Memory Allocated MS Exchange Windows Service False
Process|Processor Time (%) MS Exchange Windows Service True
Process|Thread Count MS Exchange Windows Service False
Process|Virtual Memory Used MS Exchange Windows Service False
Process|Working Set MS Exchange Windows Service False
JBoss EAP Metrics

vRealize Application Remote Collector discovers metrics for JBoss EAP application service.
Table 7-17. JBoss EAP Metrics

UTILIZATION|Heap Memory Usage Jboss Server True
UTILIZATION|Collection Count Jboss JVM Garbage Collector False
UTILIZATION|Collection Time Jboss JVM Garbage Collector False
UTILIZATION|Heap Memory Usage Jboss JVM Memory True
UTILIZATION|Non Heap Memory Jboss JVM Memory False

Usage
VMware, Inc. 1047

Table 7-17. JBoss EAP Metrics (continued)

UTILIZATION|Object Pending Jboss JVM Memory True

Finalization Count
UTILIZATION|Collection Usage Jboss JVM Memory Pool True
UTILIZATION|Peak Usage Jboss JVM Memory Pool False
UTILIZATION|Usage Jboss JVM Memory Pool True
RabbitMQ Metrics
vRealize Application Remote Collector discovers metrics for RabbitMQ application service.
Table 7-18. RabbitMQ Metrics

CPU|Limit RabbitMQ False
CPU|Used RabbitMQ True
Disk|Free RabbitMQ False
Disk|Free limit RabbitMQ False
FileDescriptor|Total RabbitMQ False
FileDescriptor|Used RabbitMQ False
Memory|Limit RabbitMQ False
Memory|Used RabbitMQ True
Messages|Acked RabbitMQ False
Messages|Delivered RabbitMQ False
Messages|Delivered get RabbitMQ False
Messages|Published RabbitMQ False
Messages|Ready RabbitMQ False
Messages|Unacked RabbitMQ False
Socket|Limit RabbitMQ False
Socket|Used RabbitMQ True
UTILIZATION|Channels RabbitMQ True
UTILIZATION|Connections RabbitMQ True
UTILIZATION|Consumers RabbitMQ True
UTILIZATION|Exchanges RabbitMQ True
UTILIZATION|Messages RabbitMQ True
UTILIZATION|Queues RabbitMQ True
Messages|Publish in RabbitMQ Exchange False
Messages|Publish out RabbitMQ Exchange False
VMware, Inc. 1048

There are no metrics collected for RabbitMQ Virtual Host.
MySQL Metrics
vRealize Application Remote Collector discovers metrics for MySQL application service.
Table 7-19. MySQL Metrics

Aborted connection count MySQL True
Connection count MySQL True
Event wait average time MySQL False
Event wait count MySQL False
InnoDB|All deadlock count MySQL False
InnoDB|Buffer pool size MySQL True
InnoDB|Open file count MySQL False
InnoDB|Row lock average time MySQL False
InnoDB|Row lock current waits MySQL False
InnoDB|Row lock maximum time MySQL False
InnoDB|Row lock time MySQL False
InnoDB|Row lock waits MySQL True
InnoDB|Table lock count MySQL False
IO waits average time MySQL Database False
IO waits count MySQL Database True
Read high priority average time MySQL Database False
Read high priority count MySQL Database False
Write concurrent insert average time MySQL Database False
Write concurrent insert count MySQL Database False
NGINX Metrics
vRealize Application Remote Collector discovers metrics for NGINX application service.
Table 7-20. NGINX Metrics

HTTP Status Info|Accepts Nginx True
HTTP Status Info|Active connections Nginx False
HTTP Status Info|Handled Nginx True
HTTP Status Info|Reading Nginx False
HTTP Status Info|Requests Nginx False
VMware, Inc. 1049

Table 7-20. NGINX Metrics (continued)

HTTP Status Info|Waiting Nginx True
HTTP Status Info|Writing Nginx False
Sharepoint Metrics
vRealize Application Remote Collector discovers metrics for Sharepoint application service.
Table 7-21. Sharepoint Metrics

Sharepoint Foundation|Active Threads SharePoint Server True
Sharepoint Foundation|Current Page SharePoint Server False

Requests
Sharepoint Foundation|Executing SQL SharePoint Server False

Queries
Sharepoint Foundation|Executing SharePoint Server True

Time/Page Request
Sharepoint Foundation|Incoming Page SharePoint Server False

Requests Rate
Sharepoint Foundation|Object Cache SharePoint Server False

Hit Count
Sharepoint Foundation|Reject Page SharePoint Server False

Requests Rate
Sharepoint Foundation|Responded SharePoint Server True

Page Requests Rate
Sharepoint Foundation|SQL Query SharePoint Server True

Executing Time
Network|Received Data Rate SharePoint Web Server True
Network|Sent Data Rate SharePoint Web Server True
Process|Processor Time (%) SharePoint Windows Service False
Process|Threads SharePoint Windows Service False
Oracle Weblogic Metrics

vRealize Application Remote Collector discovers metrics for Oracle Weblogic application service.
Table 7-22. Oracle Weblogic Metrics

UTILIZATION|Process Cpu Load Oracle WebLogic Server True
UTILIZATION|System Cpu Load Oracle WebLogic Server False
UTILIZATION|System Load Average Oracle WebLogic Server False
UTILIZATION|Collection Time Weblogic Garbage Collector True
VMware, Inc. 1050

Table 7-22. Oracle Weblogic Metrics (continued)

UTILIZATION|Connections HighCount Weblogic JMS Runtime True
UTILIZATION|JMS Servers TotalCount Weblogic JMS Runtime False
UTILIZATION|Active Total Count Used Weblogic JTA Runtime False
UTILIZATION|Active Transactions Weblogic JTA Runtime False

TotalCount
UTILIZATION|Transaction Abandoned Weblogic JTA Runtime True

TotalCount
UTILIZATION|Transaction RolledBack Weblogic JTA Runtime True

App TotalCount
UTILIZATION|Heap Memory Usage Weblogic JVM Memory True
UTILIZATION|Non Heap Memory Weblogic JVM Memory False

Usage
UTILIZATION|Peak Usage Weblogic JVM Memory Pool True
UTILIZATION|Usage Weblogic JVM Memory Pool False
UTILIZATION|UpTime Weblogic JVM Runtime False
Pivotal TC Server Metrics

vRealize Application Remote Collector discovers metrics for Pivotal TC Server application service.
Table 7-23. Pivotal TC Server Metrics



Process CPU Usage (%) Pivotal TC Server True
System CPU Usage (%) Pivotal TC Server True
Uptime Pivotal TC Server True

Committed Memory

Initial Memory

Maximum Memory

Used Memory

VMware, Inc. 1051

Table 7-23. Pivotal TC Server Metrics (continued)




Usage|Used Memory
JVM Memory|Number of Object Pivotal TC Server True









Usage|Used Memory
Current Thread Count Pivotal TC Server Thread Pool False
Current Threads Busy Pivotal TC Server Thread Pool True
Total Request Bytes Received Pivotal TC Server Thread Pool False
Total Request Bytes Sent Pivotal TC Server Thread Pool False
Total Request Count Pivotal TC Server Thread Pool True
Total Request Error Count Pivotal TC Server Thread Pool True
Total Request Processing Time Pivotal TC Server Thread Pool True
JSP Count Pivotal TC Server Web Module False
JSP Reload Count Pivotal TC Server Web Module False
JSP Unload Count Pivotal TC Server Web Module False
ActiveMQ Metrics
vRealize Application Remote Collector discovers metrics for ActiveMQ application service.
VMware, Inc. 1052

Table 7-24. ActiveMQ Metrics

UTILIZATION|Process CpuLoad Active MQ True
UTILIZATION|Memory Limit ActiveMQ Broker True
UTILIZATION|Memory Percent Usage ActiveMQ Broker True

(%)
UTILIZATION|Total Consumer Count ActiveMQ Broker True
UTILIZATION|Total Dequeue Count ActiveMQ Broker True
UTILIZATION|Total Enqueue Count ActiveMQ Broker True
UTILIZATION|Total Message Count ActiveMQ Broker True
UTILIZATION|Heap Memory Usage ActiveMQ JVM Memory Usage True
UTILIZATION|Non Heap Memory ActiveMQ JVM Memory Usage False

Usage
UTILIZATION|Object Pending ActiveMQ JVM Memory Usage True

FinalizationCount
UTILIZATION|Process CpuLoad ActiveMQ OS False
UTILIZATION|System Cpu Load ActiveMQ OS False
UTILIZATION|Consumer Count ActiveMQ Topic True
UTILIZATION|Dequeue Count ActiveMQ Topic True
UTILIZATION|Enqueue Count ActiveMQ Topic True
UTILIZATION|Queue Size ActiveMQ Topic True
Apache HTTPD Metrics

vRealize Application Remote Collector discovers metrics for Apache HTTPD application service.
Table 7-25. Apache HTTPD Metrics

UTILIZATION|Busy Workers Apache HTTPD True
UTILIZATION|Bytes Per Req Apache HTTPD False
UTILIZATION|Bytes Per Sec Apache HTTPD False
UTILIZATION|CPU Load Apache HTTPD True
UTILIZATION|Idle Workers Apache HTTPD True
UTILIZATION|Request Per Sec Apache HTTPD True
UTILIZATION|SCBoard DNS Lookup Apache HTTPD False
UTILIZATION|SCBoard Idle Cleanup Apache HTTPD False
UTILIZATION|SCBoard Keep Alive Apache HTTPD False
UTILIZATION|SCBoard Sending Apache HTTPD False
UTILIZATION|SCBoard Waiting Apache HTTPD False
VMware, Inc. 1053

Table 7-25. Apache HTTPD Metrics (continued)

UTILIZATION|Total Accesses Apache HTTPD False
UTILIZATION|Total Bytes Apache HTTPD True
UTILIZATION|Uptime Apache HTTPD True
MongoDB Metrics
vRealize Application Remote Collector discovers metrics for MongoDB application service.
Table 7-26. MongoDB Metrics

Acked|Active Reads MongoDB True
Acked|Active Writes MongoDB True
Acked|Current Connections MongoDB True
Acked|Cursor Timed Out MongoDB True
Acked|Deletes Per Sec MongoDB False
Acked|Document Inserted MongoDB False
Acked|Document Deleted MongoDB False
Acked|Flushes Per Sec MongoDB False
Acked|Inserts Per Sec MongoDB False
Acked|Net Input Bytes MongoDB False
Acked|Open Connections MongoDB True
Acked|Net Output Bytes MongoDB False
Acked|Queries Per Sec MongoDB False
Acked|Queued Reads MongoDB True
Acked|Queued Writes MongoDB True
Acked|Total Deletes Per Sec MongoDB False
Acked|Total Passes Per Sec MongoDB False
Acked|Total Refreshing MongoDB False
Acked|Updates Per Sec MongoDB False
Acked|Volume Size MB MongoDB False
Acked|Collection Stats MongoDB DataBases False
Acked|Data Index Stats MongoDB DataBases True
Acked|Data Indexes MongoDB DataBases False
Acked|Data Size Stats MongoDB DataBases True
VMware, Inc. 1054

Table 7-26. MongoDB Metrics (continued)

Acked|Average Object Size stats MongoDB DataBases False
Acked|Num Extents Stats MongoDB DataBases False
Riak Metrics
vRealize Application Remote Collector discovers metrics for Riak application service.
Table 7-27. Riak Metrics

UTILIZATION|CPU Average Riak KV False
UTILIZATION|Memory Processes Riak KV False
UTILIZATION|Memory Total Riak KV False
UTILIZATION|Node GETs Riak KV True
UTILIZATION|Node GETs Total Riak KV False
UTILIZATION|Node PUTs Riak KV True
UTILIZATION|Node PUTs Total Riak KV False
UTILIZATION|PBC Active Riak KV True
UTILIZATION|PBC Connects Riak KV True
UTILIZATION|Read Repairs Riak KV True
UTILIZATION|vNODE Index Reads Riak KV True
UTILIZATION|vNODE Index Writes Riak KV True
Calculated Metrics
vRealize Operations Manager calculates metrics for capacity, badges, and the health of the
system. Calculated metrics apply to a subset of objects found in the describe.xml file that
describes each adapter.
From data that the vCenter adapter collects, vRealize Operations Manager calculates metrics for
objects of type:
n vSphere World
n Virtual Machine
n Host System
n Datastore
From data that the vRealize Operations Manager adapter collects, vRealize Operations Manager
calculates metrics for objects of type:
n Node
VMware, Inc. 1055

n Cluster
Capacity Analytics Generated Metrics

The capacity engine computes and publishes metrics that can be found in the Capacity Analytics
Generated group. These metrics help you to plan your resource use based on consumer demand.
Capacity Analytics Generated Metrics Group

Capacity analytics uses the capacity engine to analyze historical utilization and generate
projected utilization. The engine takes the Demand and Usable Capacity (Total Capacity - HA)
metrics as input and calculates the output metrics that belong to the capacity analytics
generated metrics group.
The capacity analytics generated metrics group contains containers and each container contains
three output metrics, which are Capacity Remaining, Recommended Size, and Recommended
Total Capacity. It also contains the Capacity Remaining Percentage and Time Remaining metrics,
which show the most constrained values of the containers.
For the capacity metrics group, full metric names include the name of the resource container. For
example, if recommended size metrics are computed for CPU or memory, the actual metric
names appear as cpu|demand|recommendedSize or mem|demand|recommendedSize.
Table 7-28. Capacity Metrics Group

Time Remaining (Day(s)) The number of days remaining till the projected utilization crosses the threshold
for the usable capacity.
Key: timeRemaining
Capacity Remaining Capacity remaining is the maximum point between the usable capacity now and
the projected utilization for 3 days into the future. If the projected utilization is
above 100% of the usable capacity, Capacity Remaining is 0.
Key: capacityRemaining
Capacity Remaining Percentage (%) The percentage of Capacity Remaining of the most constrained resource with
respect to the usable capacity.
Key: capacityRemainingPercentage
Recommended Size The maximum projected utilization for the projection period from the current time
to 30 days after the warning threshold value for time remaining. The warning
threshold is the period during which the time remaining is green. Recommended
Size excludes HA settings.
Key: recommendedSize
Recommended Total Capacity The maximum projected utilization for the projection period from the current time
to 30 days after the warning threshold value for time remaining. Recommended
Total Capacity excludes HA settings.
Key: recommendedTotalCapacity
Capacity Analytics Generated Allocation Metrics

Capacity allocation metrics provide information about the allotment of capacity for Cluster
Compute and Datastore Cluster Resources.
VMware, Inc. 1056

Capacity Analytics Generated|CPU|Allocation|Capacity For vSphere objects published on Cluster Compute

Remaining (vCPUs) Resource only. Capacity Remaining based on overcommit
ratio (if configured in effective policy).
Key: OnlineCapacityAnalytics|cpu|alloc|capacityRemaining
Capacity Analytics Generated|CPU|Allocation| For vSphere objects published on Cluster Compute

Recommended Total Capacity (Cores) Resource only. The recommended level of total capacity, to
maintain a green state for time remaining for the given
object.
Key: OnlineCapacityAnalytics|cpu|alloc|
recommendedTotalSize
Capacity Analytics Generated|CPU|Allocation|Time For vSphere objects published on Cluster Compute

Remaining (Day(s)) Resource only. The number of days remaining is calculated
for both group and container. It calculates the time
remaining before the resources run out.
Key: OnlineCapacityAnalytics|cpu|alloc|timeRemaining
CPU|Allocation|Usable Capacity (vCPUs) For vSphere objects published on Cluster Compute

Resource only. The usable capacity (total capacity - HA)
based on configured overcommit ratio.
Key: cpu|alloc|usableCapacity
Capacity Analytics Generated|CPU|Allocation| For vSphere objects published on Cluster Compute

Recommended Size (Cores) Resource only. The recommended level of usable capacity
(total capacity - HA), to maintain a green state for time
remaining for the given object.
Key: OnlineCapacityAnalytics|cpu|alloc|recommendedSize
vRealize Operations Manager Generated Properties|CPU| For vSphere objects published on Cluster Compute
Allocation|Overcommit Ratio Setting Resource only. This property shows the allocation
overcommit ratio for CPU provided in effective policy.
Key: System Properties|cpu|alloc|overcommitRatioSetting
Capacity Analytics Generated|Memory|Allocation|Capacity For vSphere objects published on Cluster Compute

Remaining (KB) Resource only. Capacity Remaining based on overcommit
ratio (if configured in effective policy).
Key: OnlineCapacityAnalytics|mem|alloc|capacityRemaining
Capacity Analytics Generated|Memory|Allocation| For vSphere objects published on Cluster Compute

Recommended Total Capacity (KB) Resource only. The recommended level of total capacity, to
maintain a green state for time remaining for the given
object.
Key: OnlineCapacityAnalytics|mem|alloc|
Capacity Analytics Generated|Memory|Allocation|Time For vSphere objects published on Cluster Compute

Remaining (Day(s)) Resource only. The number of days remaining is calculated
for both group and container. It calculates the time
remaining before the resources run out.
Key: OnlineCapacityAnalytics|mem|alloc|timeRemaining
Memory|Allocation|Usable Capacity (KB) For vSphere objects published on Cluster Compute

Resource only. The usable capacity (total capacity - HA)
based on configured overcommit ratio.
Key: mem|alloc|usableCapacity
VMware, Inc. 1057

Capacity Analytics Generated|Memory|Allocation| For vSphere objects published on Cluster Compute

Recommended Size (KB) Resource only. The recommended level of usable capacity
(total capacity - HA), to maintain a green state for time
remaining for the given object.
Key: OnlineCapacityAnalytics|mem|alloc|recommendedSize
vRealize Operations Manager Generated Properties| For vSphere objects published on Cluster Compute
Memory|Allocation|Overcommit Ratio Setting Resource only. This property shows the allocation
overcommit ratio for Memory provided in effective policy.
Key: System Properties|mem|alloc|overcommitRatioSetting
Capacity Analytics Generated|Disk Space|Allocation| For vSphere objects published on Cluster Compute
Capacity Remaining (GB) Resource and Datastore Cluster Resource. Capacity
Remaining based on overcommit ratio (if configured in
effective policy).
Key: OnlineCapacityAnalytics|diskspace|alloc|
capacityRemaining
Capacity Analytics Generated|Disk Space|Allocation| For vSphere objects published on Cluster Compute
Recommended Size (GB) Resource and Datastore Cluster Resource. The
recommended level of total capacity to maintain a green
state for time remaining for the given object.
recommendedSize
Capacity Analytics Generated|Disk Space|Allocation|Time For vSphere objects published on Cluster Compute
Remaining (Day(s)) Resource and Datastore Cluster Resource. The number of
days remaining is calculated for both group and container.
It calculates the time remaining before the resources run
out.
timeRemaining
Disk Space|Allocation|Usable Capacity (GB) For vSphere objects published on Cluster Compute
Resource and Datastore Cluster Resource. Usable capacity
based on overcommit ratio (if configured in effective
policy).
Key: diskspace|alloc|usableCapacity
vRealize Operations Manager Generated Properties|Disk For vSphere objects published on Cluster Compute
Space|Allocation|Overcommit Ratio Setting Resource and Datastore Cluster Resource. This property
shows the allocation overcommit ratio for Disk Space
provided in effective policy.
key: System Properties|diskspace|alloc|
overcommitRatioSetting
Capacity Analytics Generated Profiles Metrics

Profiles metrics provide information about the profile specific capacity for Cluster Compute,
Datastore Cluster, Data Center, Custom Data Center, and vCenter Server resources.
VMware, Inc. 1058

Capacity Analytics Generated|Capacity Remaining (Profile) Published on Cluster Compute Resource. Calculated as a
minimum of all Profiles|capacityRemainingProfile_<profile
uuid> metrics.
Key: OnlineCapacityAnalytics|capacityRemainingProfile
Capacity Analytics Generated|Capacity Remaining (Profile) Published on Datastore Cluster Resource. Calculated as a
minimum of all Profiles|capacityRemainingProfile_<profile
uuid> metrics.
Capacity Analytics Generated|Capacity Remaining (Profile) Published on Data Center, Custom Data Center and
vCenter Server Resources. Computed as a sum of
OnlineCapacityAnalytics|capacityRemainingProfile metric of
descendant Cluster Compute Resources.
Capacity Demand Model Metrics

Demand model metrics provide information about the usable capacity and projected utilization of
resources across VMs, Host Systems, Cluster Compute, Datastore Cluster, Data Center, Custom
Data Center, and vCenter Server resources.
Capacity Analytics Generated|CPU|Capacity Remaining Published on Virtual Machine. The max point between the
(MHz) usable capacity and the projected utilization between now
and three days.
Key: OnlineCapacityAnalytics|cpu|capacityRemaining
Capacity Analytics Generated|CPU|Recommended Size Published on Virtual Machine. The recommended level of
(MHz) usable capacity (total capacity - HA) to maintain a green
state for the remaining time.
Key: OnlineCapacityAnalytics|cpu|recommendedSize
Capacity Analytics Generated|CPU|Time Remaining (Day(s)) Published on Virtual Machine. The number of days
remaining till the projected utilization crosses the threshold
Key: OnlineCapacityAnalytics|cpu|timeRemaining
Capacity Analytics Generated|Disk Space|Capacity Published on Virtual Machine. The max point between the
Remaining (GB) usable capacity and the projected utilization between now
and three days into the future.
Key: OnlineCapacityAnalytics|diskspace|capacityRemaining
Capacity Analytics Generated|Disk Space|Recommended Published on Virtual Machine. The recommended level of
Size (GB) usable capacity (total capacity - HA) to maintain a green
Key: OnlineCapacityAnalytics|diskspace|recommendedSize
Capacity Analytics Generated|Disk Space|Time Remaining Published on Virtual Machine. The number of days
(Day(s)) remaining till the projected utilization crosses the threshold
Key: OnlineCapacityAnalytics|diskspace|timeRemaining
VMware, Inc. 1059

Capacity Analytics Generated|Memory|Capacity Remaining Published on Virtual Machine. The max point between the
(KB) usable capacity and the projected utilization between now
Key: OnlineCapacityAnalytics|mem|capacityRemaining
Capacity Analytics Generated|Memory|Recommended Size Published on Virtual Machine. The recommended level of
(KB) usable capacity (total capacity - HA) to maintain a green
Key: OnlineCapacityAnalytics|mem|recommendedSize
Capacity Analytics Generated|Memory|Time Remaining Published on Virtual Machine. The number of days
(Day(s)) remaining till the projected utilization crosses the threshold
Key: OnlineCapacityAnalytics|mem|timeRemaining
Capacity Analytics Generated|CPU|Demand|Capacity Published on Host System. The max point between the
Remaining (MHz) usable capacity and the projected utilization between now
Key: OnlineCapacityAnalytics|cpu|demand|
capacityRemaining
Capacity Analytics Generated|CPU|Demand|Recommended Published on Host System. The recommended level of

Size (MHz) usable capacity (total capacity - HA) to maintain a green
recommendedSize
Capacity Analytics Generated|CPU|Demand|Time Published on Host System. The number of days remaining
Remaining (Day(s)) till the projected utilization crosses the threshold for the
usable capacity.
Key: OnlineCapacityAnalytics|cpu|demand|timeRemaining
Capacity Analytics Generated|Disk Space|Demand|Capacity Published on Host System. The max point between the
Remaining (GB) usable capacity and the projected utilization between now
Key: OnlineCapacityAnalytics|diskspace|demand|
capacityRemaining
Capacity Analytics Generated|Disk Space|Demand| Published on Host System. The recommended level of
Recommended Size (GB) usable capacity (total capacity - HA) to maintain a green
recommendedSize
Capacity Analytics Generated|Disk Space|Demand|Time Published on Host System. The number of days remaining
usable capacity.
timeRemaining
Capacity Analytics Generated|Memory|Demand|Capacity Published on Host System. The max point between the
Remaining (KB) usable capacity and the projected utilization between now
Key: OnlineCapacityAnalytics|mem|demand|
capacityRemaining
VMware, Inc. 1060

Capacity Analytics Generated|Memory|Demand| Published on Host System. The recommended level of

Recommended Size (KB) usable capacity (total capacity - HA) to maintain a green
recommendedSize
Capacity Analytics Generated|Memory|Demand|Time Published on Host System. The number of days remaining
usable capacity.
Key: OnlineCapacityAnalytics|mem|demand|timeRemaining
Capacity Analytics Generated|Disk Space|Usage|Capacity Published on Datastore. The max point between the usable
Remaining (GB) capacity and the projected utilization between now and
three days into the future.
Key: OnlineCapacityAnalytics|diskspace|total|
capacityRemaining
Capacity Analytics Generated|Disk Space|Usage| Published on Datastore. The recommended level of usable
Recommended Size (GB) capacity (total capacity - HA) to maintain a green state for
the remaining time.
recommendedSize
Capacity Analytics Generated|Disk Space|Usage|Time Published on Datastore. The number of days remaining till
Remaining (Day(s)) the projected utilization crosses the threshold for the
usable capacity.
timeRemaining
Capacity Analytics Generated|CPU|Demand|Capacity Published on Cluster Compute Resource. The max point
Remaining (MHz) between the usable capacity and the projected utilization
between now and three days into the future.
capacityRemaining
Capacity Analytics Generated|CPU|Demand|Recommended Published on Cluster Compute Resource. The

Size (MHz) recommended level of usable capacity (total capacity - HA)
to maintain a green state for the remaining time.
recommendedSize
Capacity Analytics Generated|CPU|Demand|Recommended Published on Cluster Compute Resource. The

Total Capacity (MHz) recommended level of total capacity to maintain a green
state for the time remaining.
Capacity Analytics Generated|CPU|Demand|Time Published on Cluster Compute Resource. The number of

Remaining (Day(s)) days remaining till the projected utilization crosses the
threshold for the usable capacity.
VMware, Inc. 1061

Capacity Analytics Generated|Disk Space|Demand|Capacity Published on Cluster Compute Resource. The max point
Remaining (GB) between the usable capacity and the projected utilization
capacityRemaining
Capacity Analytics Generated|Disk Space|Demand| Published on Cluster Compute Resource. The

Recommended Size (GB) recommended level of usable capacity (total capacity - HA)
to maintain a green state for the time remaining.
recommendedSize
Capacity Analytics Generated|Disk Space|Demand|Time Published on Cluster Compute Resource. The number of
timeRemaining
Capacity Analytics Generated|Memory|Demand|Capacity Published on Cluster Compute Resource. The max point
Remaining (KB) between the usable capacity and the projected utilization
capacityRemaining
Capacity Analytics Generated|Memory|Demand| Published on Cluster Compute Resource. The

Recommended Size (KB) recommended level of usable capacity (total capacity - HA)
recommendedSize
Capacity Analytics Generated|Memory|Demand| Published on Cluster Compute Resource. The

Recommended Total Capacity (KB) recommended level of total capacity to maintain a green
Capacity Analytics Generated|Memory|Demand|Time Published on Cluster Compute Resource. The number of

Capacity Analytics Generated|Disk Space|Usage|Capacity Published on Datastore Cluster. The max point between
Remaining (GB) the usable capacity and the projected utilization between
now and three days into the future.
capacityRemaining
Capacity Analytics Generated|Disk Space|Usage| Published on Datastore Cluster. The recommended level of
Recommended Size (GB) usable capacity (total capacity - HA) to maintain a green
recommendedSize
VMware, Inc. 1062

Capacity Analytics Generated|Disk Space|Usage|Time Published on Datastore Cluster. The number of days
Remaining (Day(s)) remaining till the projected utilization crosses the threshold
timeRemaining
Capacity Analytics Generated|CPU|Demand|Capacity Published on Datacenter, Custom Datacenter, vCenter. The

Remaining (MHz) max point between the usable capacity and the projected
utilization between now and three days into the future.
capacityRemaining
Capacity Analytics Generated|CPU|Demand|Recommended Published on Datacenter, Custom Datacenter, vCenter. The

Size (MHz) recommended level of usable capacity (total capacity - HA)
recommendedSize
Capacity Analytics Generated|CPU|Demand|Recommended Published on Datacenter, Custom Datacenter, vCenter. The

Total Capacity (MHz) recommended level of total capacity to maintain a green
Capacity Analytics Generated|CPU|Demand|Time Published on Datacenter, Custom Datacenter, vCenter. The

Remaining (Day(s)) number of days remaining till the projected utilization
crosses the threshold for the usable capacity.
Capacity Analytics Generated|Disk Space|Demand|Capacity Published on Datacenter, Custom Datacenter, vCenter. The
Remaining (GB) max point between the usable capacity and the projected
capacityRemaining
Capacity Analytics Generated|Disk Space|Demand| Published on Datacenter, Custom Datacenter, vCenter. The
Recommended Size (GB) recommended level of usable capacity (total capacity - HA)
recommendedSize
Capacity Analytics Generated|Disk Space|Demand|Time Published on Datacenter, Custom Datacenter, vCenter. The
timeRemaining
Capacity Analytics Generated|Memory|Demand|Capacity Published on Datacenter, Custom Datacenter, vCenter. The

Remaining (KB) max point between the usable capacity and the projected
capacityRemaining
VMware, Inc. 1063

Capacity Analytics Generated|Memory|Demand| Published on Datacenter, Custom Datacenter, vCenter. The

Recommended Size (KB) recommended level of usable capacity (total capacity - HA)
recommendedSize
Capacity Analytics Generated|Memory|Demand| Published on Datacenter, Custom Datacenter, vCenter. The

Recommended Total Capacity (KB) recommended level of total capacity to maintain a green
Capacity Analytics Generated|Memory|Demand|Time Published on Datacenter, Custom Datacenter, vCenter. The

Badge Metrics
Badge metrics provide information for badges in the user interface. They report the health, risk,
and efficiency of objects in your environment.
vRealize Operations Manager 6.x analyzes badge metric data at five-minute averages, instead of
hourly. As a result, you might find that efficiency and risk badge calculations are more sensitive
than in previous versions. Badge metrics continue to be published nightly.
Table 7-29. Badge Metrics

Badge|Compliance Overall score for compliance, on a scale of 100.
Badge|Efficiency Overall score for efficiency. The final score is between 1-100. Where
Green - 100, Yellow - 75, Orange - 50, Red - 25, Unknown: -1. The
score is derived from the criticality of alerts in the Efficiency
category.
Badge|Health Overall score for health. The final score is between 1-100. Where
Green - 100, Yellow - 75, Orange - 50, Red - 25, Unknown: -1. The
score is derived from the criticality of alerts in the Health category.
Badge|Risk Overall score for risk. The final score is between 1-100. Where Green
- 0, Yellow - 25, Orange - 50, Red - 75, Unknown: -1. The score is
derived from the criticality of alerts in the Risk category.
System Metrics
System metrics provide information used to monitor the health of the system. They help you to
identify problems in your environment.
VMware, Inc. 1064

Table 7-30. System Metrics

vRealize Operations Generated|Self - Health Score This metric displays the system health score of self
resource. The value ranges from 0 to 100 depending on
noise and the number of alarms.
Key: System Attributes|health
vRealize Operations Generated|Self - Metric Count This metric displays the number of metrics that the adapter
generates for the given object. This value does not include
the number of metrics generated by vRealize Operations
Manager, such as, Badge metrics, vRealize Operations
Generated metrics and metrics generated by Capacity
Engine
Key: System Attributes|all_metrics
vRealize Operations Generated|Total Anomalies This metric displays the number of active anomalies
(symptoms, events, DT violations) on the object and its
children.
In previous versions of vRealize Operations Manager, this
metric used to be named vRealize Operations Generated|
Self - Total Anomalies.
Key: System Attributes|total_alarms
vRealize Operations Generated|Full Set - Metric Count This metric displays the number of metrics that the adapter
of the children of the given object generates.
Key: System Attributes|child_all_metrics
vRealize Operations Generated|Availability This metric value is computed based on the adapter
instance statuses monitoring the resource. Resource
availability is displayed as 0-down, 1-Up, -1-Unknown.
Key: System Attributes|availability
vRealize Operations Generated|Alert Count Critical This metric displays the number of critical alerts on the
object and its children.
Key: System Attributes|alert_count_critical
vRealize Operations Generated|Alert Count Immediate This metric displays the number of immediate alerts on the
Key: System Attributes|alert_count_immediate
vRealize Operations Generated|Alert Count Warning This metric displays the number of active warning alerts on
the object and its children.
Key: System Attributes|alert_count_warning
vRealize Operations Generated|Alert Count Info This metric displays the number of active info alerts on the
Key: System Attributes|alert_count_info
vRealize Operations Generated|Total Alert Count This metric displays the sum of all alert count metrics.
In previous versions of vRealize Operations Manager, this
metric was named vRealize Operations Generated|Full Set -
Alert Count.
Key: System Attributes|total_alert_count
vRealize Operations Generated|Self-Alert Count This metric displays the number of all alerts on the object.
Key: System Attributes|self_alert_count
VMware, Inc. 1065

Self-Monitoring Metrics for vRealize Operations Manager

vRealize Operations Manager uses the vRealize Operations Manager adapter to collect metrics
that monitor its own performance. These self-monitoring metrics drive capacity models for
vRealize Operations Manager objects and are useful for diagnosing problems with vRealize
Operations Manager.
Analytics Metrics
vRealize Operations Manager collects metrics for the vRealize Operations Manager analytics
service, including threshold checking metrics.
Table 7-31. Analytics Metrics

ActiveAlarms Active DT Symptoms Active DT Symptoms.
ActiveAlerts Active Alerts Active alerts.
PrimaryResourcesCount Number of primary objects Number of primary objects
LocalResourcesCount Number of local objects Number of local objects
PrimaryMetricsCount Number of primary metrics Number of primary metrics
LocalMetricsCount Number of local metrics Number of local metrics
ReceivedResourceCount Number of received objects Number of received objects
ReceivedMetricCount Number of received metrics Number of received metrics
LocalFDSize Number of forward data entries Number of locally stored primary

and redundant entries in forward
data region.
LocalPrimaryFDSize Number of primary forward data Number of locally stored primary

entries entries in forward data region.
LocalFDAltSize Number of alternative forward data Number of locally stored primary

entries and redundant entries in
alternative forward data region.
LocalPrimaryFDAltSize Number of alternative primary forward Number of locally stored primary

data entries entries in alternative forward data
region.
CurrentHeapSize Current heap size Current heap size.
MaxHeapSize Max heap size Max heap size
CommittedMemory Committed memory Committed memory
CPUUsage CPU usage CPU usage
Threads Threads Threads
UpStatus Threads Threads
VMware, Inc. 1066

Overall Threshold Checking Metrics for the Analytics Service

Overall threshold checking captures various metrics for work items used to process incoming
observation data. All metrics keys for the overall threshold checking metrics begin with
OverallThresholdChecking, as in OverallThresholdChecking|Count or
OverallThresholdChecking|CheckThresholdAndHealth|OutcomeObservationsSize|TotalCount.
Table 7-32. Overall Threshold Checking Metrics for the Analytics Service
Count Count Count
Duration|TotalDuration Total Total length of duration (ms)
Duration|AvgDuration Average Average duration (ms)
Duration|MinDuration Minimum Minimum duration (ms)
Duration|MaxDuration Maximum Maximum duration (ms)
IncomingObservationsSize|TotalCount Total Total
IncomingObservationsSize|AvgCount Average Average
IncomingObservationsSize|MinCount Minimal Minimal
IncomingObservationsSize|MaxCount Maximal Maximal
CheckThresholdAndHealth|Count Count Count
CheckThresholdAndHealth|Duration| Total Total length of duration (ms)

TotalDuration
CheckThresholdAndHealth|Duration| Average Average duration (ms)

AvgDuration
CheckThresholdAndHealth|Duration| Minimum Minimum duration (ms)

MinDuration
CheckThresholdAndHealth|Duration| Maximum Maximum duration (ms)

MaxDuration
CheckThresholdAndHealth| Total Total

OutcomeObservationsSize|TotalCount
CheckThresholdAndHealth| Average Average

OutcomeObservationsSize|AvgCount
CheckThresholdAndHealth| Minimal Minimal

OutcomeObservationsSize|MinCount
CheckThresholdAndHealth| Maximal Maximal

OutcomeObservationsSize|MaxCount
SuperMetricComputation|Count Count Count
SuperMetricComputation|Duration| Total Total length of duration (ms)

TotalDuration
SuperMetricComputation|Duration| Average Average duration (ms)

AvgDuration
SuperMetricComputation|Duration| Minimum Minimum duration (ms)

MinDuration
VMware, Inc. 1067

Table 7-32. Overall Threshold Checking Metrics for the Analytics Service (continued)
SuperMetricComputation|Duration| Maximum Maximum duration (ms)

MaxDuration
SuperMetricComputation| Total Total

SuperMetricsCount|TotalCount
SuperMetricComputation|SuperMetricsCount Average Average

|AvgCount
SuperMetricComputation|SuperMetricsCount Minimal Minimal

|MinCount
SuperMetricComputation|SuperMetricsCount Maximal Maximal

|MaxCount
StoreObservationToFSDB|Count Count Count
StoreObservationToFSDB|Duration| Total Total length of duration (ms)

TotalDuration
StoreObservationToFSDB|Duration| Average Average duration (ms)

AvgDuration
StoreObservationToFSDB|Duration| Minimum Minimum duration (ms)

MinDuration
StoreObservationToFSDB|Duration| Maximum Maximum duration (ms)

MaxDuration
StoreObservationToFSDB| Total Total

StoredObservationsSize|TotalCount
StoreObservationToFSDB| Average Average

StoredObservationsSize|AvgCount
StoreObservationToFSDB| Minimal Minimal

StoredObservationsSize|MinCount
StoreObservationToFSDB| Maximal Maximal

StoredObservationsSize|MaxCount
UpdateResourceCache|Count Count Count
UpdateResourceCache|Duration| Total Total

TotalDuration
UpdateResourceCache|Duration| Average Average

AvgDuration
UpdateResourceCache|Duration|MinDuration Minimum Minimum
UpdateResourceCache|Duration| Maximum Maximum

MaxDuration
UpdateResourceCache| Total The number of estimated

ModifcationEstimateCount|TotalCount modifications done during each
resource cache object update.
UpdateResourceCache| Average Average

ModifcationEstimateCount|AvgCount
VMware, Inc. 1068

Table 7-32. Overall Threshold Checking Metrics for the Analytics Service (continued)
UpdateResourceCache| Minimal Minimal

ModifcationEstimateCount|MinCount
UpdateResourceCache| Maximal Maximal

ModifcationEstimateCount|MaxCount
ManageAlerts|Count Count The total number of times the

threshold checking work items
perform alert updates.
ManageAlerts|Duration|TotalDuration Total The duration for the alert updates

operations.
ManageAlerts|Duration|AvgDuration Average Average
ManageAlerts|Duration|MinDuration Minimum Minimum
ManageAlerts|Duration|MaxDuration Maximum Maximum
UpdateSymptoms|Count Count The total number of times the

threshold checking work items
check and build symptoms.
UpdateSymptoms|Duration|TotalDuration Total The duration for the check and

build symptoms operation.
UpdateSymptoms|Duration|AvgDuration Average Average
UpdateSymptoms|Duration|MinDuration Minimum Minimum
UpdateSymptoms|Duration|MaxDuration Maximum Maximum
Dynamic Threshold Calculation Metrics for the Analytics Service

All metrics keys for the dynamic threshold calculation metrics begin with DtCalculation, as in
DtCalculation|DtDataWrite|WriteOperationCount or DtCalculation|DtAnalyze|
AnalyzeOperationCount.
Table 7-33. Dynamic Threshold Calculation Metrics for the Analytics Service
DtDataWrite|WriteOperationCount Write operation count Write operation count
DtDataWrite|Duration|TotalDuration Total Total length of duration (ms)
DtDataWrite|Duration|AvgDuration Average Average duration (ms)
DtDataWrite|Duration|MinDuration Minimum Minimum duration (ms)
DtDataWrite|Duration|MaxDuration Maximum Maximum duration (ms)
DtDataWrite|SavedDtObjectCount| Total Total

TotalCount
DtDataWrite|SavedDtObjectCount|AvgCount Average Average
DtDataWrite|SavedDtObjectCount|MinCount Minimal Minimal
DtDataWrite|SavedDtObjectCount|MaxCount Maximal Maximal
DtAnalyze|AnalyzeOperationCount Analyze Operation Count Analyze Operation Count
VMware, Inc. 1069

Table 7-33. Dynamic Threshold Calculation Metrics for the Analytics Service (continued)
DtAnalyze|Duration|TotalDuration Total Total length of duration (ms)
DtAnalyze|Duration|AvgDuration Average Average duration (ms)
DtAnalyze|Duration|MinDuration Minimum Minimum duration (ms)
DtAnalyze|Duration|MaxDuration Maximum Maximum duration (ms)
DtAnalyze|AnalyzedMetricsCount| Total Total

TotalCount
DtAnalyze|AnalyzedMetricsCount|AvgCount Average Average
DtAnalyze|AnalyzedMetricsCount|MinCount Minimal Minimal
DtAnalyze|AnalyzedMetricsCount|MaxCount Maximal Maximal
DtDataRead|ReadOperationsCount Read Operation Count Read Operation Count
DtDataRead|Duration|TotalDuration Total Total length of duration (ms)
DtDataRead|Duration|AvgDuration Average Average duration (ms)
DtDataRead|Duration|MinDuration Minimum Minimum duration (ms)
DtDataRead|Duration|MaxDuration Maximum Maximum duration (ms)
DtDataRead|ReadDataPointsCount| Total Total

TotalCount
DtDataRead|ReadDataPointsCount| Average Average

AvgCount
DtDataRead|ReadDataPointsCount|MinCount Minimal Minimal
DtDataRead|ReadDataPointsCount| Maximal Maximal

MaxCount
Table 7-34. Function Call Metrics for the Analytics Service

FunctionCalls|Count Number of function calls Number of function calls
FunctionCalls|AvgDuration Average execution time Average execution time
FunctionCalls|MaxDuration Max execution time Max execution time
Collector Metrics
vRealize Operations Manager collects metrics for the vRealize Operations Manager Collector
service objects.
Table 7-35. Collector Metrics

ThreadpoolThreadsCount Number of pool threads Number of pool threads.
RejectedFDCount Number of rejected forward data Number of rejected forward data
VMware, Inc. 1070

Table 7-35. Collector Metrics (continued)

RejectedFDAltCount Number of rejected alternative Number of rejected alternative

forward data forward data
SentFDCount Number of sent objects Number of sent objects
SentFDAltCount Number of alternative sent objects Number of alternative sent objects
CurrentHeapSize Current heap size (MB) Current heap size.
MaxHeapsize Max heap size (MB) Maximum heap size.
CommittedMemory Committed memory (MB) Amount of committed memory.
CPUUsage CPU usage CPU usage.
Threads Threads Number of threads.
UpStatus Up Status Up Status
Controller Metrics
vRealize Operations Manager collects metrics for the vRealize Operations Manager Controller
objects.
Table 7-36. Controller Metrics

RequestedMetricCount Number of requested metrics Number of requested metrics
ApiCallsCount Number of API calls Number of API calls
NewDiscoveredResourcesCount Number of discovered objects Number of discovered objects
FSDB Metrics
vRealize Operations Manager collects metrics for the vRealize Operations Manager file system
database (FSDB) objects.
Table 7-37. FSDB Metrics

StoragePoolElementsCount Number of storage work items Number of storage work items
FsdbState Fsdb state Fsdb state
StoredResourcesCount Number of stored objects Number of stored objects
StoredMetricsCount Number of stored metrics Number of stored metrics
Table 7-38. Storage Thread Pool Metrics for FSDB

StoreOperationsCount Store operations count Store operations count
StorageThreadPool|Duration| Total Total number of duration (ms)

TotalDuration
VMware, Inc. 1071

Table 7-38. Storage Thread Pool Metrics for FSDB (continued)

StorageThreadPool|Duration|AvgDuration Average Average duration (ms)
StorageThreadPool|Duration|MinDuration Minimum Minimum duration (ms)
StorageThreadPool|Duration|MaxDuration Maximum Maximum duration (ms)
StorageThreadPool|SavedMetricsCount| Total Total

TotalCount
StorageThreadPool|SavedMetricsCount| Average Average

AvgCount
StorageThreadPool|SavedMetricsCount| Minimal Minimal

MinCount
StorageThreadPool|SavedMetricsCount| Maximal Maximal

MaxCount
Product UI Metrics
vRealize Operations Manager collects metrics for the vRealize Operations Manager product user
interface objects.
Table 7-39. Product UI Metrics

ActiveSessionsCount Active sessions Active sessions
CurrentHeapSize Current heap size Current heap size.
MaxHeapsize Max heap size Maximum heap size.
CommittedMemory Committed memory Amount of committed memory.
CPUUsage CPU usage Percent CPU use.
SessionCount Number of active sessions Number of active sessions
SelfMonitoringQueueSize Self Monitoring queue size Self Monitoring queue size
Table 7-40. API Call Metrics for the Product UI

APICalls|HTTPRequesterRequestCount HTTPRequester request count HTTPRequester request count
APICalls|AvgHTTPRequesterRequestTime HTTPRequester average request HTTPRequester average request time

time (ms)
APICalls|FailedAuthenticationCount Failed Authentication Count Failed Authentication Count
APICalls|AvgAlertRequestTime Average alert request time Average alert request time (ms)
APICalls|AlertRequestCount Alert request count Alert request count
APICalls|AvgMetricPickerRequestTime Average metric-picker request time Average metric-picker request time

(ms)
APICalls|MetricPickerRequestCount Metric picker request count Metric picker request count
VMware, Inc. 1072

Table 7-40. API Call Metrics for the Product UI (continued)

APICalls|HeatmapRequestCount Heatmap request count Heatmap request count
APICalls|AvgHeatmapRequestTime Average HeatMap request time Average HeatMap request time (ms)
APICalls|MashupChartRequestCount Mashup Chart request count Mashup Chart request count
APICalls|AvgMashupChartRequestTime Average Mashup Chart request Average Mashup Chart request time
time (ms)
APICalls|TopNRequestCount Top N request count Top N request count
APICalls|AvgTopNRequestTime Average Top N request time Average Top N request time (ms)
APICalls|MetricChartRequestCount Metric Chart request count Metric Chart request count
APICalls|AvgMetricChartRequestTime Average MetricChart request time Average MetricChart request time

(ms)
Admin UI Metrics
vRealize Operations Manager collects metrics for the vRealize Operations Manager administration
user interface objects.
Table 7-41. Admin UI Metrics

CurrentHeapSize Current heap size Current heap size (MB).
MaxHeapsize Max heap size Maximum heap size (MB).
CommittedMemory Committed memory Amount of committed memory (MB) .
CPUUsage CPU usage CPU usage (%).
SessionCount Number of active sessions Number of active sessions
SelfMonitoringQueueSize Self Monitoring queue size Self Monitoring queue size
Table 7-42. API Call Metrics for the Admin UI

APICalls|HTTPRequesterRequestCount HTTPRequester request count HTTPRequester request count
APICalls|AvgHTTPRequesterRequestTime HTTPRequester average request HTTPRequester average request time

time (ms)
Suite API Metrics

vRealize Operations Manager collects metrics for the VMware vRealize Operations Management
Suite API objects.
VMware, Inc. 1073

Table 7-43. Suite API Metrics

UsersCount Number of users Number of users
ActiveSessionsCount Active sessions Active sessions
GemfireClientReconnects Gemfire Client Reconnects Gemfire Client Reconnects
GemfireClientCurrentCalls Gemfire Client Total Outstanding Gemfire Client Total Outstanding
CurrentHeapSize Current heap size Current heap size (MB) .
MaxHeapsize Max heap size Maximum heap size (MB) .
CommittedMemory Committed memory Amount of committed memory (MB).
CPUUsage CPU usage CPU usage (%) .
CPUProcessTime CPU process time CPU process time (ms)
CPUProcessTimeCapacity CPU process time capacity CPU process time capacity (ms)
Table 7-44. Gemfire Client Call Metrics for the Suite API
GemfireClientCalls|TotalRequests Total Requests Total Requests
GemfireClientCalls|AvgResponseTime Average Response Time Average Response Time (ms)
GemfireClientCalls|MinResponseTime Minimum Response Time Minimum Response Time (ms)
GemfireClientCalls|MaxResponseTime Maximum Response Time Maximum Response Time
GemfireClientCalls|RequestsPerSecond Requests per Second Requests per Second
GemfireClientCalls|CurrentRequests Current Requests Current Requests
GemfireClientCalls|RequestsCount Requests Count Requests Count
GemfireClientCalls|ResponsesCount Responses Count Responses Count
Table 7-45. API Call Metrics for the Suite API

APICalls|TotalRequests Total Requests Total Requests
APICalls|AvgResponseTime Average Response Time (ms) Average Response Time (ms)
APICalls|MinResponseTime Minimum Response Time (ms) Minimum Response Time (ms)
APICalls|MaxResponseTime Maximum Response Time Maximum Response Time
APICalls|ServerErrorResponseCount Server Error Response Count Server Error Response Count
APICalls|FailedAuthenticationCount Failed Authentication Count Failed Authentication Count
APICalls|FailedAuthorizationCount Failed Authorization Count Failed Authorization Count
APICalls|RequestsPerSecond Requests per Second Requests per Second
APICalls|CurrentRequests Current Requests Current Requests
APICalls|ResponsesPerSecond Responses per Second Responses per Second
VMware, Inc. 1074

Table 7-45. API Call Metrics for the Suite API (continued)
APICalls|RequestsCount Requests Count Requests Count
APICalls|ResponsesCount Responses Count Responses Count
Cluster and Slice Administration Metrics

vRealize Operations Manager collects metrics for vRealize Operations Manager Cluster and Slice
Administration (CaSA) objects.
Table 7-46. Cluster and Slice Administration Metrics

CurrentHeapSize Current heap size Current heap size (MB).
MaxHeapsize Max heap size Maximum heap size (MB).
CommittedMemory Committed memory Amount of committed memory (MB).
CPUUsage CPU usage CPU usage (%)
Table 7-47. API Call Metrics for Cluster and Slice Administration
API Calls|TotalRequests Total Requests Total Requests
API Calls|AvgResponseTime Average Response Time Average Response Time (ms)
API Calls|MinResponseTime Minimum Response Time Minimum Response Time (ms)
API Calls|MaxResponseTime Maximum Response Time Maximum Response Time (ms)
API Calls|ServerErrorResponseCount Server Error Response Count Server Error Response Count
API Calls|FailedAuthenticationCount Failed Authentication Count Failed Authentication Count
API Calls|FailedAuthorizationCount Minimum Response Time Minimum Response Time (ms)
Watchdog Metrics
vRealize Operations Manager collects watchdog metrics to ensure that the vRealize Operations
Manager services are running and responsive.
Watchdog Metrics
The watchdog metric provides the total service count.
Table 7-48. Watchdog Metrics

ServiceCount Service Count Service Count
VMware, Inc. 1075

Service Metrics
Service metrics provide information about watchdog activity.
Table 7-49. Metrics for the vRealize Operations Manager Watchdog Service
Service|Enabled Enabled Enabled
Service|Restarts Restarts Number of times the process has

been unresponsive and been
restarted by Watchdog.
Service|Starts Starts Number of times the process has

been revived by Watchdog.
Service|Stops Stops Number of times the process has

been stopped by Watchdog.
Node Metrics
vRealize Operations Manager collects metrics for the vRealize Operations Manager node objects.
Metrics can be calculated for node objects. See Calculated Metrics.
Table 7-50. Node Metrics

Component Count Component count The number of vRealize Operations

Manager objects reporting for this
node
PrimaryResourcesCount Number of primary objects Number of primary objects
LocalResourcesCount Number of local objects Number of local objects
LocalMetricsCount Number of local metrics Number of local metrics
PercentDBStorageAvailable Percent disk available /storage/db Percent disk available /storage/db
PercentLogStorageAvailable Percent disk available /storage/log Percent disk available /storage/log
Table 7-51. Memory Metrics for the Node

mem|actualFree Actual Free Actual Free
mem|actualUsed Actual Used Actual Used
mem|free Free Free )
mem|used Used Used
mem|total Total Total
mem|demand_gb Estimated memory demand Estimated memory demand
VMware, Inc. 1076

Table 7-52. Swap Metrics for the Node

swap|total Total Total
swap|free Free Free
swap|used Used Used
swap|pageIn Page in Page in
swap|pageOut Page out Page out
Table 7-53. Resource Limit Metrics for the Node

resourceLimit|numProcesses Number of processes Number of processes
resourceLimit|openFiles Number of open files Number of open files
resourceLimit|openFilesMax Number of open files maximum limit Number of open files maximum
limit
resourceLimit|numProcessesMax Number of processes maximum limit Number of processes maximum

limit
Table 7-54. Network Metrics for the Node

net|allInboundTotal All inbound connections All inbound total
net|allOutboundTotal All outbound connections All outbound total
net|tcpBound TCP bound TCP bound
net|tcpClose TCP state CLOSE Number of connections in TCP

CLOSE
net|tcpCloseWait TCP state CLOSE WAIT Number of connections in TCP

state CLOSE WAIT
net|tcpClosing TCP state CLOSING Number of connections in TCP

state CLOSING
net|tcpEstablished TCP state ESTABLISHED Number of connections in TCP

state ESTABLISHED
net|tcpIdle TCP state IDLE Number of connections in TCP

state IDLE
net|tcpInboundTotal TCP inbound connections TCP inbound connections
net|tcpOutboundTotal TCP outbound connections TCP outbound connections
net|tcpLastAck TCP state LAST ACK Number of connections in TCP

state LAST ACK
net|tcpListen TCP state LISTEN Number of connections in TCP

state LISTEN
net|tcpSynRecv TCP state SYN RCVD Number of connections in TCP

state SYN RCVD
VMware, Inc. 1077

Table 7-54. Network Metrics for the Node (continued)

net|tcpSynSent TCP state SYN_SENT Number of connections in TCP

state SYN_SENT
net|tcpTimeWait TCP state TIME WAIT Number of connections in TCP

state TIME WAIT
Table 7-55. Network Interface Metrics for the Node

net|iface|speed Speed Speed (bits/sec)
net|iface|rxPackets Receive packets Number of received packets
net|iface|rxBytes Receive bytes Number of received bytes
net|iface|rxDropped Receive packet drops Number of received packets

dropped
net|iface|rxFrame Receive packets frame Number of receive packets frame
net|iface|rxOverruns Receive packets overruns Number of receive packets

overrun
net|iface|txPackets Transmit packets Number of transmit packets
net|iface|txBytes Transmit bytes Number of transmit bytes
net|iface|txDropped Transmit packet drops Number of transmit packets

dropped
net|iface|txCarrier Transmit carrier Transmit carrier
net|iface|txCollisions Transmit packet collisions Number of transmit collisions
net|iface|txErrors Transmit packet errors Number of transmit errors
net|iface|txOverruns Transmit packet overruns Number of transmit overruns
Table 7-56. Disk Filesystem Metrics for the Node

disk|fileSystem|total Total Total
disk|fileSystem|available Available Available
disk|fileSystem|used Used Used
disk|fileSystem|files Total file nodes Total file nodes
disk|fileSystem|filesFree Total free file nodes Total free file nodes
disk|fileSystem|queue Disk queue Disk queue
disk|fileSystem|readBytes Read bytes Number of bytes read
disk|fileSystem|writeBytes Write bytes Number of bytes written
disk|fileSystem|reads Reads Number of reads
disk|fileSystem|writes Writes Number of writes
VMware, Inc. 1078

Table 7-57. Disk Installation Metrics for the Node

disk|installation|used Used Used
disk|installation|total Total Total
disk|installation|available Available Available
Table 7-58. Disk Database Metrics for the Node

disk|db|used Used Used
disk|db|total Total Total
disk|db|available Available Available
Table 7-59. Disk Log Metrics for the Node

disk|log|used Used Used
disk|log|total Total Total
disk|log|available Available Available
Table 7-60. CPU Metrics for the Node

cpu|combined Combined load Combined load (User + Sys + Nice

+ Wait)
cpu|idle Idle Idle time fraction of total available

cpu (cpu load)
cpu|irq Irq Interrupt time fraction of total

available cpu (cpu load)
cpu|nice Nice Nice time fraction of total

cpu|softIrq Soft Irq Soft interrupt time fraction of

total available cpu (cpu load)
cpu|stolen Stolen Stolen time fraction of total

cpu|sys Sys Sys time fraction of total available

cpu (cpu load)
cpu|user User (cpu load) User time fraction of total

cpu|wait Wait (cpu load) Wait time fraction of total

cpu|total Total available for a cpu Total available for a cpu
cpu|allCpuCombined Total combined load for all cpus Total combined load for all cpus
(cpu load)
VMware, Inc. 1079

Table 7-60. CPU Metrics for the Node (continued)

cpu|allCpuTotal_ghz Available Available
cpu|allCpuCombined_ghz Used Used
cpu|allCpuCombined_percent CPU usage CPU usage (%)
Table 7-61. Device Metrics for the Node

device|iops Reads/Writes per second Average number of read/write

commands issued per second
device|await Average transaction time Average transaction time

(milliseconds).
device|iops_readMaxObserved Maximum observed reads per Maximum observed reads per

second second.
device|iops_writeMaxObserved Maximum observed writes per Maximum observed writes per

second second.
Table 7-62. Service Metrics for the Node

service|proc|fdUsage Total number of open file descriptors Total number of open file
descriptors.
Table 7-63. NTP Metrics for the Node

ntp|serverCount Configured server count Configured server count
ntp|unreachableCount Unreachable server count Unreachable server count
ntp|unreachable Unreachable Is the NTP server unreachable.

Value of 0 is reachable, 1 means
the server was not reached or did
not respond.
Table 7-64. Heap Metrics for the Node

heap|CurrentHeapSize Current heap size Current heap size
heap|MaxHeapSize Max heap size Max heap size
heap|CommittedMemory Committed Memory Committed Memory
Cluster Metrics
vRealize Operations Manager collects metrics for the vRealize Operations Manager cluster
objects including dynamic threshold calculation metrics and capacity computation metrics.
VMware, Inc. 1080

Metrics can be calculated for cluster objects. See Calculated Metrics.
Cluster Metrics
Cluster metrics provide host, resource, and metric counts on the cluster.
Table 7-65. Cluster Metrics

HostCount Number of Nodes in Cluster Number of Nodes in Cluster
PrimaryResourcesCount Number of primary resources Number of primary resources
LocalResourcesCount Number of local resources Number of local resources
ReceivedResourceCount Number of received resources Number of received resources
ReceivedMetricCount Number of received metrics Number of received metrics
DT Metrics
DT metrics are dynamic threshold metrics for the cluster. Non-zero values appear only if metric
collection occurs while the dynamic threshold calculations are running.
Table 7-66. DT Metrics for the Cluster

dt|isRunning Running Running
dt|dtRunTime Running duration Running duration (ms)
dt|StartTime Running start time Running start time
dt|percentage Percent Percent (%)
dt|executorCount Executor Node Count Executor Node Count
dt|resourceCount Resource Count Resource Count
dt|fsdbReadTime FSDB Read Time FSDB Read Time (ms)
dt|dtObjectSaveTime DT Object Save Time DT Object Save Time (ms)
dt|dtHistorySaveTime DT History Save Time DT History Save Time (ms)
dt|executor|resourceCount Resource Count Resource Count
Capacity Computation (CC) Metrics

CC metrics are capacity computation metrics for the cluster. Non-zero values appear only if
metric collection occurs while the capacity computation calculations are running.
Table 7-67. CC Metrics for the Cluster

cc|isRunning Running Running
cc|runTime Total Run Time Total Run Time
cc|startTime Start time Start time
VMware, Inc. 1081

Table 7-67. CC Metrics for the Cluster (continued)

cc|finishTime Finish Time Finish Time
cc|totalResourcesToProcess Total Objects Count Total Objects Count
cc|progress Progress Progress
cc|phase1TimeTaken Phase 1 Computation Time Phase 1 Computation Time
cc|phase2TimeTaken Phase 2 Computation Time Phase 2 Computation Time
Gemfire Cluster Metrics

Gemfire metrics provide information about the Gemfire cluster.
Table 7-68. Gemfire cluster Metrics for the Cluster

GemfireCluster|System|AvgReads Average reads per second The average number of reads per
second for all members
GemfireCluster|System|AvgWrites Average writes per second The average number of writes per
second for all members
GemfireCluster|System|DiskReadsRate Disk reads rate The average number of disk reads per
second across all distributed
members
GemfireCluster|System|DiskWritesRate Disk writes rate The average number of disk writes

per second across all distributed
members
GemfireCluster|System| Total garbage collection count The total garbage collection count for
GarbageCollectionCount all members
GemfireCluster|System| New garbage collection count The new garbage collection count for
GarbageCollectionCountDelta all members
GemfireCluster|System|JVMPauses JVM pause count The number of detected JVM pauses
GemfireCluster|System|JVMPausesDelta New JVM pause count The number of new detected JVM
pauses
GemfireCluster|System| Disk flush average latency Disk flush average latency (msec)
DiskFlushAvgLatency
GemfireCluster|System| Number of running functions The number of map-reduce jobs

NumRunningFunctions currently running on all members in
the distributed system
GemfireCluster|System|NumClients Number of clients The number of connected clients
GemfireCluster|System|TotalHitCount Total hit count Total number of cache hits for all
regions
GemfireCluster|System|TotalHitCountDelta New hit count Number of new cache hits for all
regions
GemfireCluster|System|TotalMissCount Total miss count The total number of cache misses for
all regions
VMware, Inc. 1082

Table 7-68. Gemfire cluster Metrics for the Cluster (continued)

GemfireCluster|System| New miss count Number of new cache misses for all
TotalMissCountDelta regions
GemfireCluster|System|Member| Swap space free Swap space free (MB)

FreeSwapSpace
GemfireCluster|System|Member| Swap space total Swap space total (MB)

TotalSwapSpace
GemfireCluster|System|Member| Committed virtual memory size Committed virtual memory size (MB)
CommittedVirtualMemorySize
GemfireCluster|System|Member| System load average System load average

SystemLoadAverage
GemfireCluster|System|Member| Free physical memory Free physical memory (MB)

FreePhysicalMemory
GemfireCluster|System|Member| Total physical memory Total physical memory (MB)

TotalPhysicalMemory
GemfireCluster|System|Member| Average cache listener calls latency Average cache listener calls latency
CacheListenerCallsAvgLatency (msec)
GemfireCluster|System|Member| Average cache writer calls latency Average cache writer calls latency
CacheWriterCallsAvgLatency (msec)
GemfireCluster|System|Member| Average deserialization latency Average deserialization latency

DeserializationAvgLatency (msec)
GemfireCluster|System|Member| Function executions per second Function executions per second

FunctionExecutionRate
GemfireCluster|System|Member| Number of JVM pauses Number of JVM pauses

JVMPauses
GemfireCluster|System|Member| Number of running functions Number of running functions

NumRunningFunctions
GemfireCluster|System|Member|PutsRate Puts per second Puts per second
GemfireCluster|System|Member|GetsRate Gets per second Gets per second
GemfireCluster|System|Member| Average gets latency Average gets latency (msec)

GetsAvgLatency
GemfireCluster|System|Member| Average puts latency Average puts latency (msec)

PutsAvgLatency
GemfireCluster|System|Member| Average serialization latency Average serialization latency (msec)

SerializationAvgLatency
GemfireCluster|System|Member|Disk| Flush average latency Flush average latency (msec)

DiskFlushAvgLatency
GemfireCluster|System|Member|Disk| Average reads per second Average reads per second

DiskReadsRate
GemfireCluster|System|Member|Disk| Average writes per second Average writes per second

DiskWritesRate
VMware, Inc. 1083


GemfireCluster|System|Member|Network| Average received bytes per Average received bytes per second
BytesReceivedRate second
GemfireCluster|System|Member|Network| Average sent bytes per second Average sent bytes per second
BytesSentRate
GemfireCluster|System|Member|JVM| Garbage Collection time Total amount of time spent on

GCTimeMillis garbage collection
GemfireCluster|System|Member|JVM| New Garbage Collection time New amount of time spent on

GCTimeMillisDelta garbage collection
GemfireCluster|System|Member|JVM| Total threads Total threads

TotalThreads
GemfireCluster|System|Member|JVM| Committed Memory Committed Memory (MB)

CommitedMemory
GemfireCluster|System|Member|JVM| Max Memory Max Memory (MB)

MaxMemory
GemfireCluster|System|Member|JVM| Used Memory Used Memory (MB)

UsedMemory
GemfireCluster|Region| Entry Count Entry Count

SystemRegionEntryCount
GemfireCluster|Region|DestroyRate Destroys per second Destroys per second
GemfireCluster|Region|CreatesRate Creates per second Creates per second
GemfireCluster|Region|GetsRate Gets per second Gets per second
GemfireCluster|Region|BucketCount Bucket count Bucket count
GemfireCluster|Region|AvgBucketSize Average number of entries per Average number of entries per

bucket bucket
GemfireCluster|Region|Member| Actual redundancy Actual redundancy

ActualRedundancy
GemfireCluster|Region|Member| Bucket count Bucket count

BucketCount
GemfireCluster|Region|Member| Average number of entries per Average number of entries per

AvgBucketSize bucket bucket
GemfireCluster|Region|Member| Creates per second Creates per second

CreatesRate
GemfireCluster|Region|Member|GetsRate Gets per second Gets per second
GemfireCluster|Region|Member| Destroys per second Destroys per second

DestroyRate
GemfireCluster|Region|Member|MissCount Number of misses count Number of cache misses
GemfireCluster|Region|Member| Number of new cache misses Number of new cache misses

MissCountDelta
VMware, Inc. 1084


GemfireCluster|Region|Member|HitCount Number of hits count Number of cache hits
GemfireCluster|Region|Member| Number of new cache hits Number of new cache hits

HitCountDelta
Threshold Checking Metrics

Threshold checking metrics check the processed and computed metrics for the cluster.
Table 7-69. Threshold Checking Metrics for the Cluster

ThresholdChecking|ProcessedMetricCount Number of processed metrics Number of processed metrics
ThresholdChecking|ProcessedMetricRate Received metric processing rate (per Received metric processing rate
second) (per second)
ThresholdChecking|ComputedMetricCount Number of computed metrics Number of computed metrics
ThresholdChecking|ComputedMetricRate Computed metric processing rate Computed metric processing rate

(per second) (per second)
Memory Metrics
Memory metrics provide memory CPU use information for the cluster.
Table 7-70. Memory Metrics for the Cluster

Memory|AvgFreePhysicalMemory Average free physical memory Average free physical memory

(GB)
Memory|TotalFreePhysicalMemory Free physical memory Free physical memory (GB)
Memory|TotalMemory Total Available Memory Total Available Memory (GB)
Memory|TotalUsedMemory Actual Used Memory Actual Used Memory (GB)
Memory|TotalDemandMemory Memory Demand Memory Demand (GB)
Elastic Memory Metrics

Elastic memory metrics provide reclaimable memory CPU use information for the cluster.
Table 7-71. Memory Metrics for the Cluster

ElasticMemory|TotalMemory Total Available Memory Total Available Memory (GB)
ElasticMemory|TotalUsedMemory Actual Used Memory Actual Used Memory (GB)
ElasticMemory|TotalDemandMemory Memory Demand Memory Demand (GB)
CPU Metrics
CPU metrics provide CPU information for the cluster.
VMware, Inc. 1085

Table 7-72. CPU Metrics for the Cluster

cpu|TotalCombinedUsage CPU Load CPU Load
cpu|TotalAvailable CPU Available CPU Available
cpu|TotalAvailable_ghz Available Available (GHz)
cpu|TotalUsage_ghz Used Used (GHz)
cpu|TotalUsage CPU usage CPU usage (%)
Disk Metrics
Disk metrics provide available disk information for the cluster.
Table 7-73. Disk Metrics for the Cluster

Disk|DatabaseStorage|AvgAvailable Average node disk available Average node disk available
Disk|DatabaseStorage|MinAvailable Minimum node disk available Minimum node disk available
Disk|DatabaseStorage|MaxAvailable Maximum node disk available Maximum node disk available
Disk|DatabaseStorage|TotalAvailable Available Available
Disk|DatabaseStorage|Total Total Total
Disk|DatabaseStorage|TotalUsed Used Used
Disk|LogStorage|AvgAvailable Average node disk available Average node disk available
Disk|LogStorage|MinAvailable Minimum node disk available Minimum node disk available
Disk|LogStorage|MaxAvailable Maximum node disk available Maximum node disk available
Disk|LogStorage|TotalAvailable Available Available
Disk|LogStorage|Total Total Total
Disk|LogStorage|TotalUsed Used Used
Persistence Metrics
vRealize Operations Manager collects metrics for various persistence resources or service
groups.
Activity Metrics
Activity metrics relate to the activity framework.
Table 7-74. Activity Metrics for Persistence

Activity|RunningCount Number Running Number Running
Activity|ExecutedCount Number Executed Number Executed
VMware, Inc. 1086

Table 7-74. Activity Metrics for Persistence (continued)

Activity|SucceededCount Number Succeeded Number Succeeded
Activity|FailedCount Number Failed Number Failed
Controller XDB Metrics

Controller metrics relate to the primary database.
Table 7-75. Controller XDB Metrics for Persistence

ControllerXDB|Size Size Size (Bytes)
ControllerXDB|TempDBSize Temporary DB Size Temporary DB Size (Bytes)
ControllerXDB|TotalObjectCount Total Object Count Total Object Count
ControllerXDB|AvgQueryDuration Average Query Duration Average Query Duration (ms)
ControllerXDB|MinQueryDuration Minimum Query Duration Minimum Query Duration (ms)
ControllerXDB|MaxQueryDuration Maximum Query Duration Maximum Query Duration (ms)
ControllerXDB|TotalTransactionCount Total Transaction Count Total Transaction Count
ControllerXDB|LockOperationErrorCount Lock Operation Error Count Lock Operation Error Count
ControllerXDB|DBCorruptionErrorCount DB Corruption Error Count DB Corruption Error Count
ControllerXDB| DB Maximum Sessions Exceeded DB Maximum Sessions Exceeded

DBMaxSessionExceededCount Count Count
ControllerXDB|NumberWaitingForSession Number of operations waiting for a Number of operations waiting for

session a session from the session pool
ControllerXDB|AvgWaitForSessionDuration Average acquisition time from Average acquisition time from

session pool session pool
ControllerXDB|MinWaitForSessionDuration Minimum acquisition time from Minimum acquisition time from

ControllerXDB|MaxWaitForSessionDuration Maximum acquisition time from Maximum acquisition time from

ControllerXDB|TotalGetSessionCount Total requests for a session from the Total requests for a session from
session pool the session pool
ControllerXDB|MaxActiveSessionCount Maximum Concurrent Session Count Maximum concurrent session

count during the past collection
interval.
Alarm SQL Metrics

Alarm metrics relate to the persistence of alerts and symptoms.
VMware, Inc. 1087

Table 7-76. Alarm XDB Metrics for Persistence

AlarmSQL|Size Size (Bytes) Size (Bytes)
AlarmSQL|AvgQueryDuration Average Query Duration (ms) Average Query Duration (ms)
AlarmSQL|MinQueryDuration Minimum Query Duration (ms) Minimum Query Duration (ms)
AlarmSQL|MaxQueryDuration Maximum Query Duration (ms) Maximum Query Duration (ms)
AlarmSQL|TotalTransactionCount Total Transaction Count Total Transaction Count
AlarmSQL|TotalAlarms Alarm Total Object Count Alarm Total Object Count
AlarmSQL|TotalAlerts Alert Total Object Count Alert Total Object Count
AlarmSQL|AlertTableSize Alert Table Size Alert Table Size
AlarmSQL|AlarmTableSize Alarm Table Size Alarm Table Size
Key Value Store Database (KVDB)

KVDB metrics relate to the persistence of storing key-value data.
KVDB|AvgQueryDuration Average Query Duration Average Query Duration
KVDB|MinQueryDuration Minimum Query Duration Minimum Query Duration
KVDB|MaxQueryDuration Maximum Query Duration Maximum Query Duration
KVDB|TotalTransactionCount Total Transaction Count Total Transaction Count
Historical Inventory Service XDB Metrics

Historical inventory service metrics relate to the persistence of configuration properties and their
changes.
Table 7-77. Historical XDB Metrics for Persistence

HisXDB|FunctionCalls|Count HisXDB| Number of Function calls Number of Function calls

FunctionCalls
HisXDB|FunctionCalls|AvgDuration Average execution time Average execution time
HisXDB|FunctionCalls|MaxDuration Max execution time Max execution time
HisXDB|Size Size Size (Bytes)
HisXDB|TempDBSize Temporary DB Size Temporary DB Size (Bytes)
HisXDB|TotalObjectCount Total Object Count Total Object Count
HisXDB|AvgQueryDuration Average Query Duration Average Query Duration (ms)
HisXDB|MinQueryDuration Minimum Query Duration Minimum Query Duration (ms)
HisXDB|MaxQueryDuration Maximum Query Duration Maximum Query Duration (ms)
HisXDB|TotalTransactionCount Total Transaction Count Total Transaction Count
VMware, Inc. 1088

Table 7-77. Historical XDB Metrics for Persistence (continued)

HisXDB|LockOperationErrorCount Lock Operation Error Count Lock Operation Error Count
HisXDB|DBCorruptionErrorCount DB Corruption Error Count DB Corruption Error Count
HisXDB|DBMaxSessionExceededCount DB Maximum Sessions Exceeded DB Maximum Sessions Exceeded

Count Count
HisXDB|NumberWaitingForSession Number of operations waiting for a Number of operations waiting for

session a session from the session pool
HisXDB|AvgWaitForSessionDuration Average acquisition time from Average acquisition time from

HisXDB|MinWaitForSessionDuration Minimum acquisition time from Minimum acquisition time from

HisXDB|MaxWaitForSessionDuration Maximum acquisition time from Maximum acquisition time from

HisXDB|TotalGetSessionCount Total requests for a session from the Total requests for a session from
session pool the session pool
HisXDB|HisActivitySubmissionCount HIS activity submission count Number of Historical Inventory

Service activities submitted
HisXDB|HisActivityCompletionCount HIS activity completion count Number of Historical Inventory

Service activities completed
HisXDB|HisActivityCompletionDelayAvg HIS activity average completion The average amount of time from
delay activity submission to completion
HisXDB|HisActivityCompletionDelayMax HIS activity maximum completion The maximum amount of time

delay from activity submission to
completion
HisXDB|HisActivityAbortedCount HIS activity abort count Number of Historical Inventory

Service activities stopped.
Remote Collector Metrics

vRealize Operations Manager collects metrics for the vRealize Operations Manager remote
collector node objects.
Table 7-78. Remote Collector Metrics

ComponentCount Component Count The number of vRealize Operations

Manager Objects reporting for this
node.
Table 7-79. Memory Metrics for the Remote Collector

mem|actualFree Actual Free Actual Free
mem|actualUsed Actual Used Actual Used
VMware, Inc. 1089

Table 7-79. Memory Metrics for the Remote Collector (continued)

mem|free Free Free )
mem|used Used Used
mem|total Total Total
mem|demand_gb Estimated memory demand Estimated memory demand
Table 7-80. Swap Metrics for the Remote Collector

swap|total Total Total
swap|free Free Free
swap|used Used Used
swap|pageIn Page in Page in
swap|pageOut Page out Page out
Table 7-81. Resource limit Metrics for the Remote Collector

resourceLimit|numProcesses Number of processes Number of processes
resourceLimit|openFiles Number of open files Number of open files
resourceLimit|openFilesMax Number of open files maximum limit Number of open files maximum
limit
resourceLimit|numProcessesMax Number of processes maximum limit Number of processes maximum

limit
Table 7-82. Network Metrics for the Remote Collector

net|allInboundTotal All inbound connections All inbound total
net|allOutboundTotal All outbound connections All outbound total
net|tcpBound TCP bound TCP bound
net|tcpClose TCP state CLOSE Number of connections in TCP

CLOSE
net|tcpCloseWait TCP state CLOSE WAIT Number of connections in TCP

state CLOSE WAIT
net|tcpClosing TCP state CLOSING Number of connections in TCP

state CLOSING
net|tcpEstablished TCP state ESTABLISHED Number of connections in TCP

state ESTABLISHED
net|tcpIdle TCP state IDLE Number of connections in TCP

state IDLE
net|tcpInboundTotal TCP inbound connections TCP inbound connections
VMware, Inc. 1090

Table 7-82. Network Metrics for the Remote Collector (continued)

net|tcpOutboundTotal TCP outbound connections TCP outbound connections
net|tcpLastAck TCP state LAST ACK Number of connections in TCP

state LAST ACK
net|tcpListen TCP state LISTEN Number of connections in TCP

state LISTEN
net|tcpSynRecv TCP state SYN RCVD Number of connections in TCP

state SYN RCVD
net|tcpSynSent TCP state SYN_SENT Number of connections in TCP

state SYN_SENT
net|tcpTimeWait TCP state TIME WAIT Number of connections in TCP

state TIME WAIT
Table 7-83. Network Interface Metrics for the Remote Collector

net|iface|speed Speed Speed (bits/sec)
net|iface|rxPackets Receive packets Number of received packets
net|iface|rxBytes Receive bytes Number of received bytes
net|iface|rxDropped Receive packet drops Number of received packets

dropped
net|iface|rxFrame Receive packets frame Number of receive packets frame
net|iface|rxOverruns Receive packets overruns Number of receive packets

overrun
net|iface|txPackets Transmit packets Number of transmit packets
net|iface|txBytes Transmit bytes Number of transmit bytes
net|iface|txDropped Transmit packet drops Number of transmit packets

dropped
net|iface|txCarrier Transmit carrier Transmit carrier
net|iface|txCollisions Transmit packet collisions Number of transmit collisions
net|iface|txErrors Transmit packet errors Number of transmit errors
net|iface|txOverruns Transmit packet overruns Number of transmit overruns
Table 7-84. Disk Filesystem Metrics for the Remote Collector

disk|fileSystem|total Total Total
disk|fileSystem|available Available Available
disk|fileSystem|used Used Used
disk|fileSystem|files Total file nodes Total number of file nodes
disk|fileSystem|filesFree Total free file nodes Total free file nodes
VMware, Inc. 1091

Table 7-84. Disk Filesystem Metrics for the Remote Collector (continued)
disk|fileSystem|queue Disk queue Disk queue
disk|fileSystem|readBytes Read bytes Number of bytes read
disk|fileSystem|writeBytes Write bytes Number of bytes written
disk|fileSystem|reads Reads Number of reads
disk|fileSystem|writes Writes Number of writes
Table 7-85. Disk Installation Metrics for the Remote Collector

disk|installation|used Used Used
disk|installation|total Total Total
disk|installation|available Available Available
Table 7-86. Disk Database Metrics for the Remote Collector

disk|db|used Used Used
disk|db|total Total Total
disk|db|available Available Available
Table 7-87. Disk Log Metrics for the Remote Collector

disk|log|used Used Used
disk|log|total Total Total
disk|log|available Available Available
Table 7-88. CPU Metrics for the Remote Collector

cpu|combined Combined load Combined load (User + Sys + Nice

+ Wait)
cpu|idle Idle Idle time fraction of total available

cpu (cpu load)
cpu|irq Irq Interrupt time fraction of total

cpu|nice Nice Nice time fraction of total

cpu|softIrq Soft Irq Soft interrupt time fraction of

total available cpu (cpu load)
cpu|stolen Stolen Stolen time fraction of total

VMware, Inc. 1092

Table 7-88. CPU Metrics for the Remote Collector (continued)

cpu|sys Sys Sys time fraction of total available

cpu (cpu load)
cpu|user User User time fraction of total

cpu|wait Wait Wait time fraction of total

cpu|total Total available for a cpu Total available for a cpu
cpu|allCpuCombined Total combined load for all cpus Total combined load for all cpus
(cpu load)
cpu|allCpuTotal_ghz Available Available
cpu|allCpuCombined_ghz Used Used
cpu|allCpuCombined_percent CPU usage CPU usage (%)
Table 7-89. Device Metrics for the Remote Collector

device|iops Reads/writes per second Average number of read/write

commands issued per second
during the collection interval
device|await Average transaction time Average transaction time

(milliseconds)
Table 7-90. Service Metrics for the Remote Collector

service|proc|fdUsage Total number of open file descriptors Total number of open file
descriptors (Linux). Total number
of open handles (Windows)
Table 7-91. NTP Metrics for the Remote Collector

ntp|serverCount Configured server count Configured server count
ntp|unreachableCount Unreachable server count Unreachable server count
ntp|unreachable Unreachable Is the NTP server unreachable.

Value of 0 is reachable, 1 means
the server was not reached or
didn't respond.
vRealize Automation Metrics

vRealize Automation collects metrics for objects such as, deployment, blueprint, reservation,
business group, tenant, user, vRealize Automation World, and vRealize Automation Management
Pack Instance.
VMware, Inc. 1093

Managed Resources Object as a Filter in vRealize Automation

The vRealize Automation solution uses filters to display the VMware vCenter adapter objects that
are managed by or have some association with vRealize Automation. Some of the dashboards
have widgets that are configured to display only VMware vCenter adapter objects that vRealize
Automation manages or is associated with. vRealize Automation uses an object called Managed
Resources as a filter to display only those objects. All of these resources are placed under the
Managed Resources object of type vRealize Automation Entity Status. The absence of this filter
causes all VMware vCenter adapter objects to be displayed in the widgets. If you delete the
Managed Resources object, the adapter re-creates the object, but the dashboards display
incorrect information in the widgets that use this filter. If you delete the Managed Resources
object, you must manually configure the widgets in the dashboard and select the Managed
Resources object as a filter in each section that displays the VMware vCenter adapter objects.
Blueprint Metrics
vRealize Automation collects metrics for objects such as the blueprint object.
Table 7-92. Blueprint Metrics

Group Name Metrics
Deployment Count Total Deployments
Deployment Count Total Off
Deployment Count Total on
Deployment Count VM Count
Business Group Metrics

vRealize Automation collects metrics for objects such as the business group object.
Table 7-93. Business Group Metrics

Property Name Metrics
Memory Allocation (MB)
Memory Free(MB)
Memory Reserved(MB)
Memory Used(MB)
Memory Allocated (%)
Memory Used (%)
Storage Allocation (GB)
Storage Free(GB)
Storage Reserved(GB)
Storage Used(GB)
Storage Allocated (%)
Storage Used (%)
VMware, Inc. 1094

Table 7-93. Business Group Metrics (continued)

Quota Reserved
Quota Used
Quota Free
Quota Used (%)
Summary VM count
Summary Deployment Count
Summary Failed Requests count
Summary Total Reservation Count
Summary Failed Request Count
You can also view capacity analytics generated metrics for the business group object.
Deployment Metrics
vRealize Automation collects the metrics for the deployment object.
Table 7-94. Deployment Metrics

Summary VM Count
Deployment Deployment Time
Deployment Approval Time
Deployment Cost to Date
Reservation Metrics
vRealize Automation collects metrics for objects such as the reservation object.
Table 7-95. Reservation Metrics

Property Metrics
Average Deployment Time Memory|Allocation (MB)

The total allocated memory on the cluster compute
resource.
Memory|Free(MB)
The free memory on the cluster compute resource.
Memory|Reserved (MB)
The total reserved memory on the reservation.
Memory|Total
The total physical memory of the cluster compute
resource.
Memory|Used (MB)
VMware, Inc. 1095

Table 7-95. Reservation Metrics (continued)

Property Metrics
Memory|Memory Allocated on all VMs

The total memory allocated on this reservation.
Memory|Allocated (%)
The percentage of total memory allocated on the cluster
compute resource.
Memory|Used (%)
The percentage of memory used on the cluster compute
resource.
Storage|Allocation (GB)
Storage|Total
The total physical storage of the cluster compute resource.
Storage|Free(GB)
Storage|Reserved(GB)
Storage|Used(GB)
Storage|Allocation (%)
Storage|Used (%)
The storage percentage used on the cluster compute
resource.
Quota|Reserved
Quota|Used
Quota|Free
Quota|Used (%)
The quota percentage used on the reservation.
Summary|VM count
Summary|Powered Off
Summary|Total Datastores
Summary| Datastores
You can also view capacity analytics generated metrics for the reservation object.
Tenant Metrics
vRealize Automation collects metrics for objects such as the tenant object.
Table 7-96. Tenant Metrics

Memory Allocation (MB)
Memory Free(MB)
Memory Reserved(MB)
Memory Used(MB)
VMware, Inc. 1096

Table 7-96. Tenant Metrics (continued)

Memory Allocated (%)
Memory Used (%)
Storage Allocation (GB)
Storage Free(GB)
Storage Reserved(GB)
Storage Used(GB)
Storage Allocated (%)
Storage Used (%)
Quota Reserved
Quota Used
Quota Free
Quota Used (%)
Summary VM count
Summary Deployment Count
Summary Failed Requests count
Summary Powered off VM count
Summary Total Business Group
Summary Total Blueprint
Summary Total Deployment
Summary Total Reservation
You can also view capacity analytics generated metrics for the tenant object.
vRealize Automation World Metrics

vRealize Automation collects metrics for objects such as the vRealize Automation World object.
Table 7-97. vRealize Automation World Metrics

Group Name Metrics
Summary Total vRA Instance
Summary Total Tenants
Summary Total Business Group Count
Summary Total Blueprint Count
Summary Total Deployment Count
VMware, Inc. 1097

Table 7-97. vRealize Automation World Metrics (continued)

Group Name Metrics
Summary Total Cluster Count
Summary VM Count
vRealize Automation Management Pack Instance Metrics

vRealize Automation collects metrics for objects such as the vRealize Automation Management
Pack Instance object.
Table 7-98. vRealize Automation Management Pack Instance Metrics

Group Name Metrics
Summary VM Count
Summary Total Business Group Count
Summary Total Blueprint Count
Summary Total Deployment Count
Summary Total Tenant Count
User Metrics
vRealize Automation collects metrics for objects such as the user object.
Table 7-99. User Metrics

Summary Finalized Request Count
Summary Running Request Count
Metrics for vSAN

vRealize Operations Manager collects metrics for vSAN objects.
In the menu, click Environment > All Objects > vSAN Adapter. Select one of the vSAN adapter
objects listed and click the All Metrics tab.
Disk I/O and Disk Space Metrics for vSAN Disk Groups
The vRealize Operations Manager collects the metrics you use to monitor the performance of
your vSAN disk groups.
Disk I/O metrics for the vSAN disk groups include:
n Disk I/O|Reads Per Second (IOPS)
n Disk I/O|Writes Per Second (IOPS
VMware, Inc. 1098

n Disk I/O|Max Observed Reads Per Second (IOPS)
n Disk I/O|Max Observed Writes Per Second (IOPS)
n Disk I/O|Throughput Read (bps)
n Disk I/O|Throughput Write (bps)
n Disk I/O|Average Read Latency (ms)
n Disk I/O|Average Write Latency (ms)
n Disk I/O|Total Bus Resets
n Disk I/O|Total Commands Aborted per second
The following Disk I/O metrics are disabled by default:
n Disk I/O|Read Count
n Disk I/O|Write Count
n Disk I/O|Average Device Latency
n Disk I/O|Average Device Read Latency
n Disk I/O|Average Device Write Latency
n Disk I/O|Total Number of Errors
Disk space metrics for vSAN disk groups include:
n Disk Space|Capacity (bytes)
n Disk Space|Used (bytes)
n Disk Space|Usage (%)
Read Cache Metrics for vSAN Disk Groups

The vRealize Operations Manager collects metrics and performs capacity trend analysis on a
hybrid vSAN read cache. Read Cache metrics are not collected for a vSAN all-flash configuration.
Read cache metrics for the vSAN disk group include:
n Read Cache|Hit Rate (%)
n Read Cache|Miss Rate Ratio
n Read Cache|Reads Per Second (IOPS)
n Read Cache|Read Latency (ms)
n Read Cache|Writes Per Second (IOPS)
n Read Cache|Write Latency (ms)
The following read cache metrics are disabled by default:
n Read Cache|Read I/O Count
n Read Cache|Write I/O Count
VMware, Inc. 1099

Write Buffer Metrics for vSAN Disk Groups

The vRealize Operations Manager collects the metrics you use to monitor the write buffer
capacity of your vSAN disk groups.
A reasonably balanced system consumes a significant amount of write buffer. Before placing
additional workload on the vSAN, check the write buffer metrics for the vSAN disk group.
n Write Buffer|Capacity (bytes)
n Write Buffer|Free (%)
n Write Buffer|Usage (%)
n Write Buffer|Used (byte)
n Write Buffer|Reads Per Second (IOPS)
n Write Buffer|Read Latency (ms)
n Write Buffer|Writes Per Second (IOPS)
n Write Buffer|Write Latency (ms)
The following write buffer metrics are disabled by default:
n Write Buffer|Read I/O Count
n Write Buffer|Write I/O Count
Congestion Metrics for vSAN Disk Groups

The vRealize Operations Manager collects congestion metrics for the vSAN disk group.
n Congestion| Memory Congestion - Favorite
n Congestion| SSD Congestion - Favorite
n Congestion| IOPS Congestion - Favorite
n Congestion| Slab Congestion
n Congestion| Log Congestion
n Congestion| Comp Congestion
Cache De-stage Metrics for vSAN Disk Groups

The vRealize Operations Manager collects cache de-stage metrics for the vSAN disk groups.
Cache de-stage metrics include:
n Bytes De-stage from SSD
n Zero-bytes De-stage
Resync Traffic Metrics for vSAN Disk Groups

The vRealize Operations Manager collects resync traffic metrics for the vSAN disk groups.
VMware, Inc. 1100

Resync traffic metrics include:
n Read IOPS for Resync Traffic
n Write IOPS for Resync Traffic
n Read Throughput for Resync Traffic
n Write Throughput for Resync Traffic
n Read Latency for Resync Traffic
n Write Latency for Resync Traffic
Metrics for vSAN Cluster

your vSAN cluster.
Metrics for vSAN cluster include:
Component Metrics
Component Limit n vSAN|Component Limit|Component Limit Used (%)

n vSAN|Component Limit|Total Component Limit
n vSAN|Component Limit|Used Component Limit
Disk Space n vSAN|Disk Space|Disk Space Used (%)

n vSAN|Disk Space|Total Disk Space (GB)
n vSAN|Disk Space|Used Disk Space (GB)
Read Cache n vSAN|Read Cache|Read Cache Reserved (%)

n vSAN|Read Cache|Reserved Read Cache Size (GB)
n vSAN|Read Cache|Total Read Cache Size (GB)
Performance n vSAN|Read Cache|Reads Per Second (IOPS)

n vSAN|Read Cache|Read Throughput (KBps)
n vSAN|Read Cache|Average Read Latency (ms)
n vSAN|Read Cache|Writes Per Second (IOPS)
n vSAN|Read Cache|Write Throughput (KBps)
n vSAN|Read Cache|Average Write Latency (ms)
n vSAN|Read Cache|Congestion
n vSAN|Read Cache|Outstanding I/O
n vSAN|Read Cache|Total IOPS
n vSAN|Read Cache|Total Latency (ms)
n vSAN|Read Cache|Total Throughput (KBps)
Deduplication And Compression n vSAN|Deduplication And Compression Overview|Used Before

Overview n vSAN|Deduplication And Compression Overview|Used After
n vSAN|Deduplication And Compression Overview|Savings
n vSAN|Deduplication And Compression Overview|Ratio
VMware, Inc. 1101

Component Metrics
Summary n Summary|Number of Cache Disks

n Summary|Total Number of Capacity Disks
n Summary|CPU Workload
n Summary|Memory Workload
n Summary|Total Number of Disk Groups
n Summary|Total Active Alerts Count
n Summary|Total Number of VMs
n Summary|Total Number of Hosts
n Summary|vSAN Cluster Capacity Remaining (%)
n Summary|VSAN Cluster Storage Time Remaining
n Summary|vSAN Capacity Disk Used
KPI n KPI|Sum Host VMKernel Packets Dropped

n KPI|Count Disk Group Congestion Above 50
n KPI|Max Disk Group Congestion
n KPI|Sum Disk Group Errors
n KPI|Min Disk Group Capacity Free
n KPI|Min Disk Group Read Cache Hit Rate
n KPI|Min Disk Group Write Buffer Free
n KPI|Max Disk Group Read Cache/Write Buffer Latency
n KPI|Max Capacity Disk Latency
IO Size n vSAN Cluster | All Metrics | vSAN | Performance | I/O Size (KB)
n vSAN Cluster | All Metrics | vSAN | Performance | Read I/O Size (KB)
n vSAN Cluster | All Metrics | vSAN | Performance | Write I/O Size (KB)
Resynchronization Status n vSAN Cluster | All Metrics | vSAN | Resync | Bytes left to resync (bytes)
( Metrics applicable for vSAN 6.7 n vSAN Cluster | All Metrics | vSAN | Resync | Resyncing Objects
and later)
Metrics for vSAN Enabled Host

your vSAN enabled host.
Metrics for a vSAN enabled host include:
Component Metrics
Component Limit n vSAN|Component Limit|Component Limit Used (%)

n vSAN|Component Limit|Total Component Limit
n vSAN|Component Limit|Used Component Limit
Disk Space n vSAN|Disk Space|Disk Space Used (%)

n vSAN|Disk Space|Total Disk Space (GB)
n vSAN|Disk Space|Used Disk Space (GB)
Read Cache n vSAN|Read Cache|Read Cache Reserved (%)

n vSAN|Read Cache|Reserved Read Cache Size (GB)
n vSAN|Read Cache|Total Read Cache Size (GB)
Performance Metrics
VMware, Inc. 1102

Component Metrics
n Network n vSAN|Performance|Network|Inbound Packets Loss Rate

n vSAN|Performance|Network|Outbound Packets Loss Rate
n vSAN|Performance|Network|<vnic>|Inbound Packets Loss rate (%)
n vSAN|Performance|Network|<vnic>|Outbound Packets Loss Rate (%)
n vSAN|Performance|Network|<vnic>|Inbound Packets Per second
n vSAN|Performance|Network|<vnic>|Outbound Packets Per second
n vSAN|Performance|Network|<vnic>|Throughput Inbound (KBps)
n vSAN|Performance|Network|<vnic>|Throughput Outbound (KBps)
n CPU Utilization n vSAN | Performance | CPU | Core Utilization (%) (For Hyper-Threading Technology)
n vSAN | Performance | CPU | PCPU Utilization (%)
n vSAN | Performance | CPU | PCPU Usage (%)
Metrics for vSAN Datastore

your vSAN datastore.
Datastore I/O metrics for vSAN datastore include:
n Datastore I/O|Reads Per Second (IOPS)
n Datastore I/O|Read Rate (KBps)
n Datastore I/O|Read Latency (ms)
n Datastore I/O|Writes Per Second (IOPS)
n Datastore I/O|Write Rate (KBps)
n Datastore I/O|Write Latency (ms)
n Datastore I/O|Outstanding I/O requests
n Datastore I/O|Congestion
Metrics for vSAN Cache Disk

your vSAN cache disk.
Metrics for vSAN cache disk include:
VMware, Inc. 1103

Component Metrics
Performance n Performance|Bus Resets

n Performance|Commands Aborted Per Second
The following performance metrics are disabled by default:
n Performance|Device Latency (ms)
n Performance|Device Read Latency (ms)
n Performance|Device Write Latency (ms)
n Performance|Read Requests Per Second
n Performance|Average Reads Per Second
n Performance|Write Requests Per Second
n Performance|Average Writes Per Second
n Performance|Read Rate
n Performance|Write Rate
n Performance|Usage
n Performance|HDD Errors
SCSI SMART Statistics n SCSI SMART Statistics|Health Status

n SCSI SMART Statistics|Media Wearout Indicator
Note SMART data
collection is disabled by n SCSI SMART Statistics|Write Error Count
default. To enable SMART n SCSI SMART Statistics|Read Error Count
data collection, ensure n SCSI SMART Statistics|Power on Hours
that the Enable SMART n SCSI SMART Statistics|Reallocated Sector Count
data collection instance
n SCSI SMART Statistics|Raw Read Error Rate
identifier is set to true. For
n SCSI SMART Statistics|Drive Temperature
proper data collection,
ensure that ESXi hosts in n SCSI SMART Statistics|Maximum Observed Drive Temperature
your vCenter Server n SCSI SMART Statistics|Drive Rated Max Temperature
inventory have CIM n SCSI SMART Statistics|Write Sectors TOT Count
service enabled and CIM n SCSI SMART Statistics|Read Sectors TOT Count
providers for each SMART
n SCSI SMART Statistics|Initial Bad Block Count
metric installed.
n SCSI SMART Statistics|Worst Media Wearout Indicator
n SCSI SMART Statistics|Worst Write Error Count
n SCSI SMART Statistics|Worst Read Error Count
n SCSI SMART Statistics|Worst Power-on Hours
n SCSI SMART Statistics|Power Cycle Count
n SCSI SMART Statistics|Worst Power Cycle Count
n SCSI SMART Statistics|Worst Reallocated Sector Count
n SCSI SMART Statistics|Worst Raw Read Error Rate
n SCSI SMART Statistics|Worst Driver Rated Max Temperature
n SCSI SMART Statistics|Worst Write Sectors TOT Count
n SCSI SMART Statistics|Worst Read Sectors TOT Count
n SCSI SMART Statistics|Worst Initial Bad Block Count
Capacity n vSAN|Health|Capacity|Total Disk Capacity (GB)

n vSAN|Health|Capacity|Used Disk Capacity (GB)
VMware, Inc. 1104

Component Metrics
Congestion Health n vSAN|Health|Congestion Health|Congestion Value
Performance n vSAN|Performance|Physical Layer Reads Per Second

n vSAN|Performance|Physical Layer Writes Per Second
n vSAN|Performance|Physical Layer Read Throughput (KBps)
n vSAN|Performance|Physical Layer Write Throughput (KBps)
n vSAN|Performance|Physical Layer Read Latency (ms)
n vSAN|Performance|Physical Layer Write Latency (ms)
n vSAN|Performance|Physical Layer Read Count
n vSAN|Performance|Physical Layer Write Count
n vSAN|Performance|Device Average Latency (ms)
n vSAN|Performance|Guest Average Latency (ms)
Metrics for vSAN Capacity Disk

your vSAN capacity disk.
Metrics for vSAN capacity disk include:
VMware, Inc. 1105

Component Metrics
Performance n Performance|Bus Resets

n Performance|Commands Aborted Per Second
The following performance metrics are disabled by default:
n
n Performance|Device Latency (ms)

n Performance|Device Read Latency (ms)
n Performance|Device Write Latency (ms)
n Performance|Read Requests Per Second
n Performance|Average Reads Per Second
n Performance|Write Requests Per Second
n Performance|Average Writes Per Second
n Performance|Read Rate
n Performance|Write Rate
n Performance|Usage
n Performance|HDD Errors
SCSI SMART Statistics n SCSI SMART Statistics|Health Status

n SCSI SMART Statistics|Media Wearout Indicator
Note SMART data collection is
disabled by default. To enable n SCSI SMART Statistics|Write Error Count
SMART data collection, ensure that n SCSI SMART Statistics|Read Error Count
the Enable SMART data n SCSI SMART Statistics|Power on Hours
collection instance identifier is set n SCSI SMART Statistics|Reallocated Sector Count
to true. For proper data collection,
n SCSI SMART Statistics|Raw Read Error Rate
ensure that ESXi hosts in your
n SCSI SMART Statistics|Drive Temperature
vCenter Server inventory have CIM
service enabled and CIM providers n SCSI SMART Statistics|Maximum Observed Drive Temperature
for each SMART metric installed. n SCSI SMART Statistics|Drive Rated Max Temperature
n SCSI SMART Statistics|Write Sectors TOT Count
n SCSI SMART Statistics|Read Sectors TOT Count
n SCSI SMART Statistics|Initial Bad Block Count
n SCSI SMART Statistics|Worst Media Wearout Indicator
n SCSI SMART Statistics|Worst Write Error Count
n SCSI SMART Statistics|Worst Read Error Count
n SCSI SMART Statistics|Worst Power-on Hours
n SCSI SMART Statistics|Power Cycle Count
n SCSI SMART Statistics|Worst Power Cycle Count
n SCSI SMART Statistics|Worst Reallocated Sector Count
n SCSI SMART Statistics|Worst Raw Read Error Rate
n SCSI SMART Statistics|Worst Driver Rated Max Temperature
n SCSI SMART Statistics|Worst Write Sectors TOT Count
n SCSI SMART Statistics|Worst Read Sectors TOT Count
n SCSI SMART Statistics|Worst Initial Bad Block Count
Capacity n vSAN|Health|Total Disk Capacity (GB)

n vSAN|Health|Used Disk Capacity (GB)
VMware, Inc. 1106

Component Metrics
Congestion Health vSAN|Health|Congestion Value
Performance n vSAN|Performance|Physical Layer Reads Per Second

n vSAN|Performance|Physical Layer Writes Per Second
n vSAN|Performance|Physical Layer Read Throughput (KBps)
n vSAN|Performance|Physical Layer Write Throughput (KBps)
n vSAN|Performance|Physical Layer Read Latency (ms)
n vSAN|Performance|Physical Layer Write Latency (ms)
n vSAN|Performance|Physical Layer Read Count
n vSAN|Performance|Physical Layer Write Count
n vSAN|Performance|Device Average Latency (ms)
n vSAN|Performance|Guest Average Latency (ms)
n vSAN|Performance|vSAN Layer Reads Per Second
n vSAN|Performance|vSAN Layer Writes Per Second
n vSAN|Performance|vSAN Layer Read Latency (ms)
n vSAN|Performance|vSAN Layer Write Latency (ms)
n vSAN|Performance|vSAN Layer Read Count
n vSAN|Performance|vSAN Layer Write Count
Properties for vSAN capacity disk include:
n Name
n Size
n Vendor
n Type
n Queue Depth
Metrics for vSAN Fault Domain Resource Kind

your vSAN stretched cluster with fault domain.
Metrics for vSAN fault domain resource kind includes:
n CPU
n Demand
n Demand (MHz)
n Demand without overhead (MHz)
n Overhead (MHz)
n Reserved Capacity (MHz)
n Total Capacity (MHz)
n VM CPU Usage (MHz)
VMware, Inc. 1107

n Workload (%)
n Disk Space
n Demand
n Workload (%)
n Memory
n Contention (KB)
n Demand
n Host Usage (KB)
n Machine Demand (KB)
n Reserved Capacity (KB)
n Total Capacity (KB)
n Utilization (KB)
n Workload (%)
n vSAN
n Disk Space
n Total Disk Space (GB)
n Used Disk Space (GB)
Metrics for vSAN World

your vSAN world.
Metrics for vSAN world include:
n Summary|Total Number of VMs
n Summary|Total Number of Hosts
n Summary|Total IOPS
n Summary|Total Latency
n Summary|Total Number of Clusters
n Summary|Total Number of DiskGroups
n Summary|Total Number of Cache Disks
n Summary|Total Number of Capacity Disks
n Summary|Total Number of Datastores
n Summary|Total vSAN Disk Capacity (TB)
n Summary|Total vSAN Disk Capacity Used (TB)
VMware, Inc. 1108

n Summary|Remaining Capacity (TB)
n Summary|Remaining Capacity (%)
n Summary|Total Savings by Deduplication and Compression (GB)
Capacity Model for vSAN Objects

The capacity model introduced in vRealize Operations Manager 6.7 now extends the support for
vSAN objects like, vSAN cluster, Fault domains, and Cache/Capacity disks. The Capacity tab
provides Time Remaining data for the selected vSAN cluster, Fault domain, Cache/Capacity Disk
objects. The information is presented in a graphical format.
Where You Find the Capacity Tab

In the menu, click Environment, then select a group, custom data center, application, or
inventory object. The Object details page appears. Click the Capacity tab.
The vRealize Operations Manager defines the capacity model for the following vSAN resource
containers:
n vSAN Cluster
n Disk Space
n vSAN Fault Domain
n CPU
n Memory
n Disk Space
n vSAN Cache/Capacity Disk
n Disk Space
Understanding the Capacity Tab

For the selected vSAN resource, the capacity tab lists the capacity used and Time Remaining
until the associated CPU, memory, and disk space resources, respectively, run out.
n If you select the vSAN cluster, the capacity tab lists the capacity used and time remaining
until the associated disk space runs out.
n If you select the vSAN Fault Domain, the capacity tab lists the capacity used and time
remaining until the associated CPU, memory, and disk space resources run out.
n If you select the vSAN Cache/Capacity Disk Space, the capacity tab lists capacity used and
time remaining until the associated disk space runs out.
The available graph depicts - for your choice of CPU, memory, or disk space - the amount of
resource used, plotted against time. A line on the graph shows 100 percent usable capacity and a
trend line projects how swiftly resource use is approaching 100 percent. The time line shows
when the selected resource is to reach capacity.
VMware, Inc. 1109

Metrics for the Operating Systems and Remote Service Monitoring

Plug-ins in End Point Operations Management
vRealize Operations Manager collects metrics for the object types in the Operating Systems and
Remote Service Monitoring plug-ins.
Due to rounding in metric time calculation, there can be situations in which the Resource
Availability metric is rounded up. Rounding up the metric appears as gaps in the metrics reported
by the End Point Operations Management agent. However, the metrics are fully reported.
Operating Systems Plug-in Metrics

The Operating Systems plug-in collects metrics for object types such Linux, AIX, Solaris, and
Windows. The Operating Systems plug-in also collects metrics for Windows services, Script
services, and Multiprocess services.
End Point Operations Management agents discover file systems and automatically monitor them
for read/write rates, total capacity, used capacity, and so on.
AIX Metrics
The Operating Systems Plug-in discovers the metrics for the AIX object type. AIX 6.1 and 7.1 are
supported.
Table 7-100. AIX Metrics

Name Category KPI
Resource Availability AVAILABILITY True
System Uptime AVAILABILITY True
File System Reads/Writes THROUGHPUT False
File System Reads/Writes per Minute THROUGHPUT False
Tcp Passive Opens THROUGHPUT False
Tcp Out Segs per Minute THROUGHPUT False
Tcp Attempt Fails THROUGHPUT False
Tcp Estab Resets per Minute THROUGHPUT False
Tcp Retrans Segs THROUGHPUT False
Tcp Out Segs THROUGHPUT False
Tcp Estab Resets THROUGHPUT False
Tcp Active Opens THROUGHPUT False
Tcp Curr Estab THROUGHPUT False
Tcp In Errs THROUGHPUT False
Tcp In Errs per Minute THROUGHPUT False
Tcp Active Opens per Minute THROUGHPUT False
Tcp Out Rsts per Minute THROUGHPUT False
VMware, Inc. 1110

Table 7-100. AIX Metrics (continued)

Name Category KPI
Tcp Out Rsts THROUGHPUT False
Tcp Attempt Fails per Minute THROUGHPUT False
Tcp Passive Opens per Minute THROUGHPUT False
Tcp In Segs per Minute THROUGHPUT False
Tcp In Segs THROUGHPUT False
Tcp Retrans Segs per Minute THROUGHPUT False
Cpu Wait Time UTILIZATION False
Cpu Idle UTILIZATION False
Cpu Idle Time UTILIZATION False
Cpu Idle Time per Minute UTILIZATION False
Cpu Wait Time per Minute UTILIZATION False
Cpu Usage UTILIZATION True
Cpu Wait UTILIZATION False
Cpu Nice UTILIZATION False
Free Memory UTILIZATION False
Load Average 15 Minutes UTILIZATION False
Load Average 1 Minute UTILIZATION False
Nfs Server V3 Write per Minute UTILIZATION False
Nfs Server V3 Readlink per Minute UTILIZATION False
Nfs Server V3 Readdirplus per Minute UTILIZATION False
Nfs Server V3 Commit per Minute UTILIZATION False
Nfs Server V3 Access UTILIZATION False
Nfs Server V3 Access per Minute UTILIZATION False
Nfs Server V3 Rename per Minute UTILIZATION False
Nfs Server V3 Fsstat per Minute UTILIZATION False
Nfs Server V3 Create per Minute UTILIZATION False
Nfs Server V3 Mkdir per Minute UTILIZATION False
Nfs Server V3 Mknod UTILIZATION False
Nfs Server V3 Read per Minute UTILIZATION False
Nfs Server V3 Fsstat UTILIZATION False
Nfs Server V3 Link UTILIZATION False
Nfs Server V3 Write UTILIZATION False
Nfs Server V3 Lookup per Minute UTILIZATION False
VMware, Inc. 1111


Name Category KPI
Nfs Server V3 Link per Minute UTILIZATION False
Nfs Server V3 Rmdir per Minute UTILIZATION False
Nfs Server V3 Mkdir UTILIZATION False
Nfs Server V3 Remove per Minute UTILIZATION False
Nfs Server V3 Symlink UTILIZATION False
Nfs Server V3 Symlink per Minute UTILIZATION False
Nfs Server V3 Remove UTILIZATION False
Nfs Server V3 Null UTILIZATION False
Nfs Server V3 Readdirplus UTILIZATION False
Nfs Server V3 Readdir UTILIZATION False
Nfs Server V3 Getattr per Minute UTILIZATION False
Nfs Server V3 Read UTILIZATION False
Nfs Server V3 Lookup UTILIZATION False
Nfs Server V3 Pathconf UTILIZATION False
Nfs Server V3 Readlink UTILIZATION False
Nfs Server V3 Pathconf per Minute UTILIZATION False
Nfs Server V3 Mknod per Minute UTILIZATION False
Nfs Server V3 Setattr per Minute UTILIZATION False
Nfs Server V3 Setattr UTILIZATION False
Nfs Server V3 Create UTILIZATION False
Nfs Server V3 Fsinfo per Minute UTILIZATION False
Nfs Server V3 Fsinfo UTILIZATION False
Nfs Server V3 Getattr UTILIZATION False
Nfs Server V3 Rmdir UTILIZATION False
Nfs Server V3 Readdir per Minute UTILIZATION False
Nfs Server V3 Rename UTILIZATION False
Nfs Server V3 Commit UTILIZATION False
Nfs Server V3 Null per Minute UTILIZATION False
Number of CPUs UTILIZATION False
Page Major faults UTILIZATION False
Percent Used Memory UTILIZATION True
Page Major faults per Second UTILIZATION False
Page Faults per Second UTILIZATION False
Page Faults UTILIZATION False
VMware, Inc. 1112


Name Category KPI
Percent Used Swap UTILIZATION True
Percent Free Swap UTILIZATION False
Percent Free Memory UTILIZATION False
Running Processes UTILIZATION False
Sleeping Processes UTILIZATION False
Stopped Processes UTILIZATION False
System Cpu Time per Minute UTILIZATION False
System Cpu UTILIZATION False
System Cpu Time UTILIZATION False
Swap Used UTILIZATION False
Swap Pages In UTILIZATION False
Swap Pages In per Minute UTILIZATION False
Swap Total UTILIZATION False
Swap Free UTILIZATION False
Swap Pages Out UTILIZATION False
Swap Pages Out per Minute UTILIZATION False
Total disk capacity UTILIZATION False
Total Processes UTILIZATION False
Total Memory UTILIZATION False
Total disk usage UTILIZATION False
User Cpu Time UTILIZATION False
User Cpu UTILIZATION False
User Cpu Time per Minute UTILIZATION False
Used Memory UTILIZATION False
Zombie Processes UTILIZATION False
Linux Metrics
The Operating Systems Plug-in discovers the metrics for the Linux object type.
Table 7-101. Linux Metrics

Name Category KPI
System Uptime AVAILABILITY False
VMware, Inc. 1113

Table 7-101. Linux Metrics (continued)

Name Category KPI
File System Reads/Writes per THROUGHPUT False

Minute
Tcp State Established THROUGHPUT False
Tcp State LISTEN THROUGHPUT False
Tcp State CLOSING THROUGHPUT False
Tcp State SYN_SENT THROUGHPUT False
Tcp State TIME_WAIT THROUGHPUT False
Tcp State SYN_RECV THROUGHPUT False
Tcp Outbound Connections THROUGHPUT False
Tcp Inbound Connections THROUGHPUT False
Tcp State FIN_WAIT1 THROUGHPUT False
Tcp State CLOSE_WAIT THROUGHPUT False
Tcp State CLOSE THROUGHPUT False
Tcp State LAST_ACK THROUGHPUT False
VMware, Inc. 1114


Name Category KPI
Cpu Stolen UTILIZATION False
Cpu Irq Time per Minute UTILIZATION False
Cpu SoftIrq Time UTILIZATION False
Cpu Stolen Time per Minute UTILIZATION False
Cpu Stolen Time UTILIZATION False
Cpu Irq UTILIZATION False
Cpu SoftIrq Time per Minute UTILIZATION False
Cpu Irq Time UTILIZATION False
Cpu SoftIrq UTILIZATION False
Free Memory (+ buffers/cache) UTILIZATION False
Nfs Server V3 Readlink per UTILIZATION False

Minute
Nfs Server V3 Readdirplus per UTILIZATION False

Minute
Nfs Server V3 Rename per UTILIZATION False

Minute
VMware, Inc. 1115


Name Category KPI
Nfs Server V3 Remove per UTILIZATION False

Minute
Nfs Server V3 Pathconf per UTILIZATION False

Minute
Nfs Server V3 Readdir per UTILIZATION False

Minute
VMware, Inc. 1116


Name Category KPI
Used Memory (- buffers/cache) UTILIZATION False
VMware, Inc. 1117

Solaris Metrics
The Operating Systems Plug-in discovers the metrics for the Solaris object type. Solaris x86 and
SPARC are supported.
Table 7-102. Solaris Metrics

Name Category KPI
TCP Attempt Fails THROUGHPUT False
TCP State Established THROUGHPUT False
TCP Estab Resets per Minute THROUGHPUT False
TCP Retrans Segs THROUGHPUT False
TCP State LISTEN THROUGHPUT False
TCP State CLOSING THROUGHPUT False
TCP State SYN_SENT THROUGHPUT False
TCP State TIME_WAIT THROUGHPUT False
TCP State SYN_RECV THROUGHPUT False
TCP In Errs per Minute THROUGHPUT False
TCP Out Segs per Minute THROUGHPUT False
TCP Passive Opens per Minute THROUGHPUT False
TCP Out Segs THROUGHPUT False
TCP Estab Resets THROUGHPUT False
TCP Active Opens per Minute THROUGHPUT False
TCP Outbound Connections THROUGHPUT False
TCP Curr Estab THROUGHPUT False
TCP In Errs THROUGHPUT False
TCP Inbound Connections THROUGHPUT False
TCP Active Opens THROUGHPUT False
TCP Out Rsts per Minute THROUGHPUT False
TCP In Segs THROUGHPUT False
TCP Retrans Segs per Minute THROUGHPUT False
TCP Passive Opens THROUGHPUT False
TCP Out Rsts THROUGHPUT False
TCP State FIN_WAIT1 THROUGHPUT False
TCP State FIN_WAIT2 THROUGHPUT False
VMware, Inc. 1118

Table 7-102. Solaris Metrics (continued)

Name Category KPI
TCP State CLOSE_WAIT THROUGHPUT False
TCP In Segs per Minute THROUGHPUT False
TCP State CLOSE THROUGHPUT False
TCP State LAST_ACK THROUGHPUT False
TCP Attempt Fails per Minute THROUGHPUT False
Nfs Server V3 Readlink per Minute UTILIZATION False
Nfs Server V3 Readdirplus per Minute UTILIZATION False
Nfs Server V3 Rename per Minute UTILIZATION False
Nfs Server V3 Remove per Minute UTILIZATION False
VMware, Inc. 1119


Name Category KPI
Nfs Server V3 Pathconf per Minute UTILIZATION False
Nfs Server V3 Symlink UTILIZATION False
Nfs Server V3 Readdir per Minute UTILIZATION False
VMware, Inc. 1120


Name Category KPI
Microsoft Windows Metrics

The Operating Systems Plug-in discovers the metrics for the Microsoft Windows object type.
Microsoft Windows Server 2012 R2 and 2008 R2 are supported.
Table 7-103. Microsoft Windows Metrics

Name Category KPI
Avg. Disk sec/Transfer THROUGHPUT False
VMware, Inc. 1121

Table 7-103. Microsoft Windows Metrics (continued)

Name Category KPI
Tcp State Established THROUGHPUT False
Tcp State LISTEN THROUGHPUT False
Tcp State CLOSING THROUGHPUT False
Tcp State SYN_SENT THROUGHPUT False
Tcp State TIME_WAIT THROUGHPUT False
Tcp State SYN_RECV THROUGHPUT False
Tcp Outbound Connections THROUGHPUT False
Tcp Inbound Connections THROUGHPUT False
Tcp State CLOSE_WAIT THROUGHPUT False
Tcp State CLOSE THROUGHPUT False
Tcp State LAST_ACK THROUGHPUT False
VMware, Inc. 1122


Name Category KPI
Memory Page Faults/sec UTILIZATION False
Memory System Driver Resident Bytes UTILIZATION False
Memory Available Bytes UTILIZATION False
Memory System Driver Total Bytes UTILIZATION False
Memory % Committed Bytes In Use UTILIZATION False
Memory Standby Cache Core Bytes UTILIZATION False
Memory Transition Pages RePurposed/sec UTILIZATION False
Memory Write Copies/sec UTILIZATION False
Memory Available KBytes UTILIZATION False
Memory Page Reads/sec UTILIZATION False
Memory Committed Bytes UTILIZATION False
Memory Pool Nonpaged Bytes UTILIZATION False
Memory System Code Resident Bytes UTILIZATION False
Memory Page Writes/sec UTILIZATION False
Memory Available MBytes UTILIZATION False
Memory Standby Cache Normal Priority Bytes UTILIZATION False
Memory Pages/sec UTILIZATION False
Memory Modified Page List Bytes UTILIZATION False
Memory Cache Faults/sec UTILIZATION False
Memory Pool Nonpaged Allocs UTILIZATION False
Memory System Code Total Bytes UTILIZATION False
Memory Pool Paged Allocs UTILIZATION False
Memory Pages Input/sec UTILIZATION False
Memory Pool Paged Bytes UTILIZATION False
Memory Pool Paged Resident Bytes UTILIZATION False
Memory Cache Bytes UTILIZATION False
Memory Standby Cache Reserve Bytes UTILIZATION False
MemoryFreeSystemPageTableEntries UTILIZATION False
Memory Free %26 Zero Page List Bytes UTILIZATION False
Memory System Cache Resident Bytes UTILIZATION False
Memory Cache Bytes Peak UTILIZATION False
VMware, Inc. 1123


Name Category KPI
Memory Commit Limit UTILIZATION False
Memory Transition Faults/sec UTILIZATION False
Memory Pages Output/sec UTILIZATION False
Total Memory UTILIZATION True
Windows Service Metrics

The Operating Systems Plug-in discovers the metrics for Windows Service.
VMware, Inc. 1124

Table 7-104. Windows Services Metrics

Name Category KPI
Start Time AVAILABILITY False
Start Type AVAILABILITY False
Cpu User Time UTILIZATION False
Cpu Total Time per Minute UTILIZATION False
Cpu System Time per Minute UTILIZATION False
Cpu Total Time UTILIZATION False
Cpu User Time per Minute UTILIZATION False
Cpu System Time UTILIZATION False
Memory Size UTILIZATION True
Open Handles UTILIZATION False
Resident Memory Size UTILIZATION False
Threads UTILIZATION False
If you stop an End Point Operations Management agent by using Windows Services, and remove
the data directory from inside the agent installation directory, when you start the agent again,
using Windows Services, no metrics are collected. If you are deleting the data directory, do not
use Windows Services to stop and start an End Point Operations Management agent. Stop the
agent using epops-agent.bat stop. Delete the data directory, then start the agent using epops-
agent.bat start.
Script Metrics
The Operating Systems Plug-in discovers the metrics for the Script service. The metrics will be
available only if the shell script is configured.
VMware, Inc. 1125

Table 7-105. Script Metrics

Name Category KPI Description
Resource Availability AVAILABILITY True Displays if the script is

available or not. If the value
is "0" the script is
unavailable. If the value is
"100" the script it available.
Key: Availability|Resource
Availability
Execution Time THROUGHPUT True Time spent to run the script.

Key: Throughput|Execution
Time (ms)
Result Value UTILIZATION True Exit value of the script. If the

script contains "echo 1", the
the value is 1. If the script
contains "echo 0", the value
will be 0.
Key: Utilization|Result value
Multiprocess Service Metrics

The Operating Systems Plug-in discovers the metrics for the Multiprocess service.
Table 7-106. Multiprocess Metrics

Name Category KPI
Cpu User Time UTILIZATION False
Cpu Total Time per Minute UTILIZATION False
Cpu System Time per Minute UTILIZATION False
Cpu Total Time UTILIZATION False
Cpu User Time per Minute UTILIZATION False
Cpu System Time UTILIZATION False
Memory Size UTILIZATION True
Number of Processes UTILIZATION False
Resident Memory Size UTILIZATION False
NFS Metrics
The End Point Operations Management agents collect metrics for the NFS-mounted file systems.
The following metrics are collected.
VMware, Inc. 1126

Name Category
Resource Availability Availability
Use Percent (%) Utilization
Total Bytes Free (KB) Utilization
Remote Service Monitoring Plug-in Metrics

The Remote Service Monitoring plug-in collects metrics for object types such HTTP Check, TCP
Check, and ICMP Check.
HTTP Check Metrics

The Remote Service Monitoring Plug-in discovers the metrics for the HTTP Check object type.
Table 7-107. HTTP Check Metrics

Name Category KPI
Last Modified AVAILABILITY False
State CLOSE THROUGHPUT False
State CLOSE_WAIT THROUGHPUT False
State ESTABLISHED THROUGHPUT False
Inbound Connections THROUGHPUT False
State TIME_WAIT THROUGHPUT False
All Inbound Connections THROUGHPUT False
State SYN_SENT THROUGHPUT False
State FIN_WAIT2 THROUGHPUT False
Outbound Connections THROUGHPUT False
State LAST_ACK THROUGHPUT False
Response Time THROUGHPUT True
State CLOSING THROUGHPUT False
All Outbound Connections THROUGHPUT False
State SYN_RECV THROUGHPUT False
Response Code UTILIZATION True
ICMP Check Metrics

The Remote Service Monitoring Plug-in discovers the metrics for the ICMP Check object type.
VMware, Inc. 1127

Table 7-108. ICMP Check Metrics

Name Category KPI
TCP Check Metrics

The Remote Service Monitoring Plug-in discovers the metrics for the TCP Check object type.
Table 7-109. TCP Check Metrics

Name Category KPI
State CLOSE THROUGHPUT False
State CLOSE_WAIT THROUGHPUT False
State ESTABLISHED THROUGHPUT False
Inbound Connections THROUGHPUT False
State TIME_WAIT THROUGHPUT False
All Inbound Connections THROUGHPUT False
State SYN_SENT THROUGHPUT False
Outbound Connections THROUGHPUT False
State LAST_ACK THROUGHPUT False
State CLOSING THROUGHPUT False
All Outbound Connections THROUGHPUT False
State SYN_RECV THROUGHPUT False
Alert Definitions in vRealize Operations Manager

Alert definitions are a combination of symptoms and recommendations that identify problem
areas in vRealize Operations Manager and generate alerts on which you act for those areas.
Alert definitions are provided for various objects in your environment. You can also create your
own alert definitions. See Create an Alert Definition for Department Objects.
n Cluster Compute Resource Alert Definitions

The vCenter adapter provides alert definitions that generate alerts on the Cluster Compute
Resource objects in your environment.
VMware, Inc. 1128

n Host System Alert Definitions

The vCenter adapter provides alert definitions that generate alerts on the Host System
n vRealize Automation Alert Definitions

areas in your environment and generate alerts on which you can act.
n vSAN Alert Definitions

vRealize Operations Manager generates an alert if a problem occurs with the components in
the storage area network that the vSAN adapter is monitoring.
n Alerts in the vSphere Web Client

The vSphere Web Client displays the results of health tests for the following vSAN
monitored groups:
n vSphere Distributed Port Group

The vCenter adapter provides alert definitions that generate alerts on the vSphere
Distributed Port objects in your environment.
n Virtual Machine Alert Definitions

The vCenter adapter provides alert definitions that generate alerts on the virtual machine
n vSphere Distributed Switch Alert Definitions

The vCenter adapter provides alert definitions that generate alerts on the vSphere
Distributed Switch objects in your environment.
n vCenter Server Alert Definitions

The vCenter adapter provides alert definitions that generate alerts on the vCenter Server
n Datastore Alert Definitions

The vCenter adapter provides alert definitions that generate alerts on the datastore objects
n Data Center Alert Definitions

The vCenter adapter provides alert definitions that generate alerts on the Data Center
n Custom Data Center Alert Definitions

The vCenter adapter provides alert definitions that generate alerts on the Custom Data
Center objects in your environment.
Cluster Compute Resource Alert Definitions

The vCenter adapter provides alert definitions that generate alerts on the Cluster Compute
Resource objects in your environment.
VMware, Inc. 1129

Health/Symptom-Based
These alert definitions have the following impact and criticality information.
Impact
Health
Criticality
Symptom-based
Alert Definition Symptoms Recommendations
Fully-automated DRS-enabled cluster Symptoms include all of the following: 1 Check the migration threshold in
has CPU contention caused by less n DRS enabled the DRS settings for the cluster. To
than half of the virtual machines. enable DRS to balance the cluster
n DRS fully automated
workloads change it to a more
n Cluster CPU contention at
aggressive level.
warning/immediate/critical level
2 Use the workload balance feature
n > 0 descendant virtual machines
in vRealize Operations to migrate
have [ Virtual machine CPU
one or more virtual machines to a
demand at warning/ immediate/
different cluster.
critical level ]
3 Use vMotion to migrate some
n <= 50% of descendant virtual
virtual machines to a different
machines have [Virtual machine
cluster if possible.
CPU demand at warning/
4 Add more hosts to the cluster to
immediate/critical level ]
increase memory capacity.
n DRS Migration Threshold is not
5 Right-size large virtual machines as
zero
it helps in reducing overall resource
contention. Use the Reclaimable
Capacity feature within vRealize
Operations for right sizing of VMs.
has CPU contention caused by more n DRS enabled the DRS settings for the cluster. To
aggressive level.
2 User the workload balance feature
n Cluster CPU demand at warning/
immediate/critical level
n > 50% of descendant virtual different cluster.
machines have [ Virtual machine
CPU demand at warning/
zero
increase CPU capacity.
VMware, Inc. 1130

has CPU contention caused by n DRS enabled the DRS settings for the cluster. To
overpopulation of virtual machines. enable DRS to balance the cluster
aggressive level.
n Cluster CPU workload at warning/
n = 0 descendant virtual machines different cluster.
have [ Virtual machine CPU
critical level ]
zero
Fully-automated DRS-enabled cluster Symptoms include all of the following: 1 Check the applications running on
has unexpected high CPU workload. n DRS enabled the virtual machines in the cluster
to determine whether high CPU
workload is an expected behavior.
n Cluster CPU workload above DT
n Cluster CPU workload at warning/
3 Use vSphere vMotion to migrate
some virtual machines to a
different cluster if possible.
has memory contention caused by less n DRS enabled the DRS settings for the cluster. To
n Cluster memory contention at
aggressive level.
n > 0 descendant virtual machines
have [ Virtual machine memory
workload at warning /immediate/
different cluster.
critical level ]
n <= 50% of descendant virtual
machines have [Virtual machine
memory workload at warning/
4 To increase memory capacity add
more hosts to the cluster.
zero
VMware, Inc. 1131

has memory contention caused by n DRS enabled the DRS settings for the cluster.
more than half of the virtual machines. Change it to a more aggressive
level to enable DRS to balance the
cluster workloads.
n Cluster memory workload at
n > 50% of descendant virtual different cluster.
memory demand at warning/
zero
has memory contention caused by n DRS enabled the DRS settings for the cluster. To
overpopulation of virtual machines. enable DRS to balance the cluster
aggressive level.
n = 0 descendant virtual machines different cluster.
have [ Virtual machine memory
demand at warning /immediate/
critical level ]
zero
VMware, Inc. 1132

More than 5% of virtual machines in the n Virtual machine memory limit is 1 Add more hosts to the cluster to
cluster have memory contention due set AND increase memory capacity.
to memory compression, ballooning or n > 5% of descendant virtual 2 Use vMotion to migrate some
swapping. machines have [ virtual machine virtual machines off the host or
memory contention is at warning/ cluster.
immediate/critical level] AND
n > 5% of descendant virtual
memory is compressed OR
n Virtual machine is using swap OR
n Virtual machine memory
ballooning is at warning/
immediate/critical level]
Fully-automated DRS-enabled cluster Symptoms include all of the following: 1 Check the applications running on
has unexpected high memory n DRS enabled the virtual machines in the cluster
workload and contention. to determine whether high memory
workload is an expected behavior.
n Cluster memory contention above
DT
n Cluster memory content is at
3 Use vSphere vMotion to migrate
some virtual machines to a
different cluster if possible.
vSphere HA failover resources are vSphere HA failover resources are To resolve this problem, use similar
insufficient. insufficient (fault symptom) CPU and memory reservations for all
virtual machines in the cluster. If this
solution is not possible, consider using
a different vSphere HA admission
control policy, such as reserving a
percentage of cluster resource for
failover. Alternatively, you can use
advanced options to specify a cap for
the slot size. For more information, see
the vSphere Availability Guide. Hosts
that have vSphere HA agent errors are
not good candidates for providing
failover capacity in the cluster and
their resources are not considered for
vSphere HA admission control
purposes. If many hosts have a
vSphere HA agent error, vCenter
Server generates this event leading to
the fault. To resolve vSphere HA agent
errors, check the event logs for the
hosts to determine the cause of the
errors. After you resolve any
configuration problems, reconfigure
vSphere HA on the affected hosts or
on the cluster.
VMware, Inc. 1133

vSphere HA master missing. vCenter Server is unable to find a

master vSphere HA agent (fault
symptom)
Proactive HA provider has reported Proactive HA provider reported host Contact your hardware vendor
health degradation on the underlying health degradation. support.
hosts.
Host System Alert Definitions

The vCenter adapter provides alert definitions that generate alerts on the Host System objects in
your environment.
Impact
Health
Criticality
VMware, Inc. 1134

Symptom-based
Standalone host has CPU contention Symptoms include the following: Use
caused by less than half of the virtual n Host inside a cluster 1 Add the host to a fully-automated-
machines. DRS cluster to allow vSphere to
n Host CPU contention is at
warning/immediate/critical level move virtual machine as needed
when resources are available on
n > 0 child virtual machines have
other hosts in the cluster.
[Virtual machine CPU demand at
warning /immediate/critical level] 2 Use vMotion to migrate some
virtual machines with high CPU
n <= 50% of child virtual machines
workload to other hosts that have
have [Virtual machine CPU
available CPU capacity.
critical level] 3 Right-size large virtual machines as
Operations for recommended
rightsizing of VMs.
Standalone host has CPU contention Symptoms include the following: 1 Add the host to a fully-automated-
caused by more than half of the virtual n Host inside a cluster DRS cluster to allow vSphere to
machines. move virtual machine as needed
n Host CPU demand at warning/
n > 50% of child virtual machines
critical level]
rightsizing of VMs.
Standalone host has CPU contention Symptoms include the following: 1 Add the host to a fully-automated-
due to overpopulation of virtual n Host inside a cluster DRS cluster to allow vSphere to
machines. move virtual machine as needed
n = 0 child virtual machines have
warning/ immediate/critical level]
rightsizing of VMs.
VMware, Inc. 1135

Host in a cluster that does not have Symptoms include the following: 1 Enable fully-automated DRS in the
fully-automated DRS enabled has n Host inside a cluster cluster to allow vSphere to move
contention caused by less than half of virtual machine as needed when
n [ DRS Enabled OR ! DRS fully
the virtual machines. resources are available on other
automated ]
warning /immediate/critical level]
critical level]
rightsizing of VMs.
fully-automated DRS enabled has CPU n Host inside a cluster cluster to allow vSphere to move
contention caused by more than half virtual machine as needed when
of the virtual machines. resources are available on other
automated]
n Host CPU contention at warning/
critical level]
rightsizing of VMs.
fully-automated DRS enabled has CPU n Host inside a cluster cluster to allow vSphere to move
contention caused by overpopulation virtual machine as needed when
of virtual machines. resources are available on other
automated]
n Host CPU contention at warning/
warning /immediate/critical level
rightsizing of VMs.
VMware, Inc. 1136

Standalone host has memory Symptoms include the following: 1 Add the host to a fully-automated-
contention caused by less than half of n Host inside a cluster DRS cluster to allow vSphere to
the virtual machines. move virtual machine as needed
n Host memory workload at
n Host memory contention at
have [Virtual machine memory
3 Upgrade the host to use a host
critical level]
that has larger memory capacity.
rightsizing of VMs.
contention caused by more than half n Host inside a cluster DRS cluster to allow vSphere to
of the virtual machines. move virtual machine as needed
critical level]
rightsizing of VMs.
VMware, Inc. 1137

contention due to overpopulation of n Host inside a cluster DRS cluster to allow vSphere to
virtual machines. move virtual machine as needed
[Virtual machine memory
workload at warning/ immediate/
critical level]
rightsizing of VMs.
fully-automated DRS enabled has n [DRS Enabled OR ! DRS fully cluster to allow vSphere to move
memory contention caused by less automated] virtual machine as needed when
than half of the virtual machines. resources are available on other
critical level]
critical level]
rightsizing of VMs.
memory contention caused by more virtual machine as needed when
n [DRS Enabled OR ! DRS fully
than half of the virtual machines. resources are available on other
automated]
critical level]
rightsizing of VMs.
VMware, Inc. 1138

memory contention caused by virtual machine as needed when
n [DRS Enabled OR ! DRS fully
overpopulation of virtual machines. resources are available on other
automated]
critical level]
rightsizing of VMs.
Host is experiencing high number of Symptoms include the following: 1 Reduce the amount of network
received or transmitted packets n Host network received packets traffic being generated by virtual
dropped. dropped machines by moving some of them
to a host with lower network
n Host network transmitted packets
traffic.
dropped
2 Verify the health of the physical
network adapter, configuration,
driver and firmware versions.
3 Contact VMware support.
Host is experiencing high number of Symptoms include the following: 1 If the host has one CPU, upgrade
received packets dropped. n Host network received packets the host or use a host that has
dropped larger CPU capacity.
n Host network received packets 2 Add an additional NIC to the host.

dropped above DT 3 Reduce the amount of network
n Host network data receive traffic being generated by virtual
workload at Warning level machines by moving some of them
n Host network data receive
traffic.
workload above DT
n Host CPU demand at Critical level
Host is experiencing high number of Symptoms include the following: 1 Add an additional NIC to the host.
transmitted packets dropped. n Host network transmitted packets 2 Reduce the amount of network
dropped traffic being generated by virtual
n Host network transmitted packets machines by moving some of them
dropped above DT to a host with lower network
traffic.
n Host network data transmit
workload at Warning level
n Host network data transmit
workload above DT
n Host is dropping high percentage
of packets
VMware, Inc. 1139

ESXi host has detected a link status Physical NIC link state flapping (fault ESXi disables the device to avoid the
'flapping' on a physical NIC. symptom). link flapping state. You might need to
replace the physical NIC. The alert will
be canceled when the NIC is repaired
and functioning. If you replace the
physical NIC, you might need to
manually cancel the alert.
ESXi host has detected a link status Physical NIC link state down (fault ESXi disables the device to avoid the
down on a physical NIC. symptom). link flapping state. You might need to
replace the physical NIC. The alert will
be canceled when the NIC is repaired
and functioning. If you replace the
physical NIC, you might need to
Battery sensors are reporting Symptoms include the following: Change or replace the hardware if
problems. n Battery sensor health is red OR necessary. Contact the hardware
vendor for assistance. After the
n Battery sensor health is yellow
problem is resolved, the alert will be
canceled when the sensor that
reported the problem indicates that
the problem no longer exists.
Baseboard Management Controller Symptoms include the following: Change or replace the hardware if
sensors are reporting problems. n Baseboard Management necessary. Contact the hardware
Controller sensor health is red OR vendor for assistance. After the
n Baseboard Management
Controller sensor health is yellow
Fan sensors are reporting problems. n Fan sensor health is red OR Change or replace the hardware if
n Fan sensor health is yellow necessary. Contact the hardware
Hardware sensors are reporting n Hardware sensor health is red OR Change or replace the hardware if
problems. n Hardware sensor health is yellow necessary. Contact the hardware
Memory sensors are reporting n Memory sensor health is red OR Change or replace the hardware if
problems. n Memory sensor health is yellow necessary. Contact the hardware
VMware, Inc. 1140

Path redundancy to storage device n A path to storage device went See KB topic, Path redundancy to the
degraded down storage device is degraded (1009555)
n Host has no redundancy to
storage device
Power sensors are reporting problems. n Power sensor health is red OR Change or replace the hardware if
n Power sensor health is yellow necessary. Contact the hardware
Processor sensors are reporting n Processor sensor health is red Change or replace the hardware if
problems. n Processor sensor health is yellow necessary. Contact the hardware
SEL sensors are reporting problems. n SEL sensor health is red OR Change or replace the hardware if
n SEL sensor health is yellow necessary. Contact the hardware
Storage sensors are reporting n Storage sensor health is red OR Change or replace the hardware if
problems. n Storage sensor health is yellow necessary. Contact the hardware
System Board sensors are reporting n System board sensor health is red Change or replace the hardware if
problems. OR necessary. Contact the hardware
n System board sensor health is vendor for assistance. After the
yellow problem is resolved, the alert will be
VMware, Inc. 1141

Temperature sensors are reporting n Temperature sensor health is red Change or replace the hardware if
problems. OR necessary. Contact the hardware
n Temperature sensor health is vendor for assistance. After the
yellow problem is resolved, the alert will be
Voltage sensors are reporting n Voltage sensor health is red OR Change or replace the hardware if
problems. n Voltage sensor health is yellow necessary. Contact the hardware
Health/Critical
Impact
Health
Criticality
Critical
Host has lost connection to vCenter. Host disconnected from vCenter Click "Open Host in vSphere Web
Client" in the Actions menu at the top
of Alert details page to connect to the
vCenter managing this host and
manually reconnect the host to
vCenter Server. After the connection
to the host is restored by vCenter
Server, the alert will be canceled.
vSphere High Availability (HA) has vSphere HA detected a network Resolve the networking problem that
detected a network-isolated host. isolated host (fault symptom). prevents the host from pinging its
isolation addresses and communicating
with other hosts. Make sure that the
management networks that vSphere
HA uses include redundancy. With
redundancy, vSphere HA can
communicate over more than one
path, which reduces the chance of a
host becoming isolated.
VMware, Inc. 1142

vSphere High Availability (HA) has vSphere HA detected a host failure Find the computer that has the
detected a possible host failure. (fault symptom). duplicate IP address and reconfigure it
to have a different IP address. This
fault is cleared and the alert canceled
when the underlying problem is
resolved, and the vSphere HA primary
agent is able to connect to the HA
agent on the host.
Note You can use the Duplicate IP

warning in the /var/log/vmkernel log
file on an ESX host or the /var/log/
messages log file on an ESXi host to
identify the computer that has the
duplicate IP address.
Host is experiencing network Symptoms include all the following: 1 Review the load balancing policy in
contention caused by too much traffic. n Host is experiencing dropped the Port Group and the vSwitch.
network packets 2 Add an additional NIC to the host.
n Host network workload at 3 Reduce the amount of network
warning/immediate/critical level traffic being generated by virtual
machines by moving some of them
traffic.
The host has lost connectivity to a Lost network connectivity to dvPorts Replace the physical adapter or reset
dvPort. (fault symptom). the physical switch. The alert will be
canceled when connectivity is restored
to the dvPort.
VMware, Inc. 1143

The host has lost connectivity to the Lost network connectivity (fault To determine the actual failure or to
physical network. symptom). eliminate possible problems, check the
status of the vmnic in the vSphere
Client or from the ESX service console:
n To check the status in the vSphere
Client, select the ESX host, click
Configuration, and then click
Networking. The vmnics currently
assigned to virtual switches appear
in the diagrams. If a vmnic displays
a red X, that link is currently down.
n From the service console, run the
command:esxcfg-nics. The output
that appears is similar to the
following: Name PCI Driver Link
Speed Duplex Description
----------------------------------------------
-------------------- vmnic0 04:04.00
tg3 Up 1000Mbps Full Broadcom
BCM5780 Gigabit Ethernet vmnic1
04:04.01 tg3 Up 1000Mbps Full
Broadcom BCM5780 Gigabit
Ethernet. The Link column shows
the status of the link between the
network adapter and the physical
switch. The status can be either Up
or Down. If some network adapters
are up and others are down, you
might need to verify that the
adapters are connected to the
intended physical switch ports. To
verify the connections, bring down
each ESX host port on the physical
switch, run esxcfg-nics -l", and
observe the affected vmnics.
Verify that the vmnic identified in the
alert is still connected to the switch
and configured properly:
n Make sure that the network cable
is still connected to the switch and
to the host.
n Make sure that the switch is
connected to the system, is still
functioning properly, and has not
been inadvertently misconfigured.
For more information, see the
switch documentation.
n Check for activity between the
physical switch and the vmnic. You
can check activity by performing a
network trace or observing activity
LEDs.
VMware, Inc. 1144

n Check for network port settings on

the physical switch.
To reconfigure the service console IP
address if the affected vmnic is
associated with a service console, see
http://kb.vmware.com/kb/1000258 If
the problem is caused by your
hardware, contact your hardware
vendor for replacement hardware.
The host lost connectivity to a Lost connection to NFS server (fault 1 Verify the NFS server is running.
Network File System (NFS) server. symptom). 2 Check the network connection to
make sure the ESX host can
connect to the NFS server.
3 Determine whether the other hosts
that use the same NFS mount are
experiencing the same problem,
and check the NFS server status
and share points.
4 Make sure that you can reach the
NFS server by logging into the
service console and using vmkping
to ping the NFS server: "vmkping
<nfs server>".
5 For advanced troubleshooting
information, seehttp://
kb.vmware.com/kb/1003967
A fatal error occurred on a PCIe bus A fatal PCIe error occurred. Check and replace the PCIe device
during system reboot. identified in the alert as the cause of
the problem. Contact the vendor for
assistance.
A fatal memory error was detected at A fatal memory error occurred. Replace the faulty memory or contact
system boot time. the vendor.
Health/Immediate
Impact
Health
Criticality
VMware, Inc. 1145

Immediate
Alert Definition Symptom Recommendations
The host has lost redundant Lost network redundancy to DVPorts Replace the physical adapter or reset
connectivity to a dvPort. (fault symptom). the physical switch. The alert will be
canceled when connectivity is restored
to the DVPort.
The host has lost redundant uplinks to Lost network redundancy (fault To determine the actual failure or to
the network. symptom). eliminate possible problems, first
connect to ESX through SSH or the
console:
1 Identify the available uplinks by
running esxcfg-nics -l.
2 Remove the reported vmnic from
the port groups by running
esxcfg-vswitch -U <affected
vmnic#> affected vSwitch.
3 Link available uplinks to the
affected port groups by running
esxcfg-vswitch -L
<available vmnic#>
affected vSwitch.
Next, check the status of the vmnic in
vSphere Client or the ESX service
console:
1 In vSphere Client, select the ESX
host, click Configuration, and then
click Networking.
The vmnics currently assigned to

virtual switches appear in the
diagrams. If a vmnic displays a red
X, that link is currently unavailable.
2 From the service console, run
esxcfg-nics -l. The output that
appears is similar to the following
example: Name PCI Driver Link
Speed Duplex Description.
--------------------------------------------------
---------------- vmnic0 04:04.00 tg3 Up
1000Mbps Full Broadcom BCM5780
Gigabit Ethernet vmnic1 04:04.01 tg3
Up 1000Mbps Full Broadcom
BCM5780 Gigabit Ethernet. The Link
column shows the status of the link
between the network adapter and the
physical switch. The status can be
either Up or Down. If some network
adapters are up and others are down,
you might need to verify that the
adapters are connected to the
intended physical switch ports. To
verify the connections, shut down each
VMware, Inc. 1146

ESX host port on the physical switch,

run the "esxcfg-nics -l" command, and
observe the affected vmnics. Verify
that the vmnic identified in the alert is
still connected to the switch and
configured properly:
1 Make sure that the network cable
is still connected to the switch and
to the host.
2 Make sure that the switch is
connected to the system, is still
functioning properly, and was not
inadvertently misconfigured. (See
the switch documentation.)
3 Perform a network trace or
observe activity LEDs to check for
activity between the physical
switch and the vmnic.
4 Check for network port settings on
the physical switch.
If the problem is caused by

hardware, contact your hardware
vendor for a hardware
replacement.
A PCIe error occurred during system A recoverable PCIe error occurred. The PCIe error is recoverable, but the
boot, but the error is recoverable. system behavior is dependent on how
the error is handled by the OEM
vendor's firmware. Contact the vendor
for assistance.
A recoverable memory error has A recoverable memory error Since recoverable memory errors are
occurred on the host. occurred. vendor-specific, contact the vendor for
assistance.
Risk/Symptom-Based
Impact
Risk
Criticality
VMware, Inc. 1147

Symptom-based
ESXi Host is violating vSphere 5.5 n Active directory authentication Fix the vSphere 5.5 Hardening Guide
Hardening Guide. disabled OR Rules Violations according to the
n Non-compliant NTP service recommendations in the vSphere5
startup policy OR Hardening Guide
n SSH service is running OR

n NTP service stopped OR
n Non-compliant timeout value for
automatically disabling local and
remote shell access OR
n vSphere Authentication Proxy not
used for password protection
when adding ESXi hosts to active
directory OR
n Persistent logging disabled OR
n Bidirectional CHAP for iSCSI traffic
disabled OR
n Non-compliant firewall setting to
restrict access to NTP client OR
n NTP server for time
synchronization not configured
OR
n Non-compliant ESXi Shell service
startup policy OR
n Non-compliant firewall setting to
restrict access to SNMP server OR
n ESXi Shell service is running OR
n Non-compliant DCUI service
startup policy OR
n Dvfilter bind IP address
configured OR
n Non-compliant SSH service
startup policy OR
n DCUI service is running OR
n Non-compliant idle time before an
interactive shell is automatically
logged out OR
n Non-compliant DCUI access user
list OR
n Remote syslog is not enabled
vRealize Automation Alert Definitions

areas in your environment and generate alerts on which you can act.
VMware, Inc. 1148

Symptom and alert definitions are defined for vRealize Automation objects. The alerts are
population-based alerts based on the risk or health of a certain percentage of child objects.
There are no alerts generated for network profiles.
The health and risk thresholds are as follows:
Health
n When 25%-50% of the child objects have health issues, the parent object will trigger an alert
with a Warning health level.
with an Immediate health level.
with a Critical health level.
Risk
n When 25%-50% of the child objects have risk issues, the parent object will trigger an alert
with a Warning risk level.
with an Immediate risk level.
with a Critical risk level.
vSAN Alert Definitions

vRealize Operations Manager generates an alert if a problem occurs with the components in the
storage area network that the vSAN adapter is monitoring.
Alerts for the vSAN Cluster Object

Alerts on the vSAN Cluster object have health, risk, and efficiency impact.
Table 7-110. vSAN Cluster Object Health Alert Definitions

Alert Alert Type Alert Subtype Description
Basic (unicast) connectivity check Storage Configuration Triggered when basic (unicast) connectivity
(normal ping) has failed on vSAN check (normal ping) has failed on the vSAN
host. host due to network misconfiguration.
Check the free space on physical Storage Availability Triggered when a check of free space on
disks in the vSAN cluster. physical disks in the vSAN cluster results in an
error or warning.
CLOMD process on the host has Storage Availability Triggered when CLOMD process on the host
issues and impacting the has issues and impacting the functionality of
functionality of vSAN cluster. vSAN cluster.
VMware, Inc. 1149

Table 7-110. vSAN Cluster Object Health Alert Definitions (continued)

Disk load variance between some Storage Performance Triggered when disk load variance between
vSAN disks exceeded the threshold some vSAN disks exceeded the threshold
value. value.
vSAN cannot perform the load balance
properly.
Host ESXi version and the vSAN Storage Configuration Host ESXi version and the vSAN disk format
disk format version is incompatible version is incompatible with the other hosts
with the other hosts and disks in a and disks in a vSAN cluster.
vSAN cluster.
Host has invalid unicast agent and Storage Configuration Triggered when the host has invalid unicast
impacting the health of vSAN agent and impacting the health of vSAN
Stretched Cluster. Stretched Cluster.
An invalid unicast agent on the host can cause
a communication malfunction with the witness
host.
Host in a vSAN cluster does not Network Configuration Triggered when the host in a vSAN cluster
have a VMkernel NIC configured for does not have a VMkernel NIC configured for
vSAN traffic. vSAN traffic.
Note
Even if an ESXi host is part of the vSAN

cluster, but is not contributing storage, it must
still have a VMkernel NIC configured for vSAN
traffic.
Host in a vSAN cluster has Network Configuration Triggered when the host in a vSAN cluster has
connectivity issues and vCenter connectivity issues and vCenter Server does
Server does not know its state. not know its state.
Host in a vSAN cluster has IP Network Configuration Triggered when the host in a vSAN cluster has
multicast connectivity issue. IP multicast connectivity issue. It means that
multicast is most likely the root cause of a
vSAN network partition.
Host is either running an outdated Storage Configuration Triggered when the host is either running an
version of the vSAN Health Service outdated version of the vSAN Health Service
VIB or It is not installed on the host. VIB or It is not installed on the host.
Network latency check of vSAN Network Configuration Triggered if network latency check of vSAN
hosts failed. It requires < 1 ms RTT. hosts is greater than or equal to 1 ms RTT.
One or more hosts in the vSAN Network Configuration Triggered when one or more hosts in the
cluster have misconfigured vSAN cluster have misconfigured multicast
multicast addresses. addresses.
One or more physical disks on Storage Availability Triggered when one or more physical disks on
vSAN host is experiencing software vSAN host is experiencing software state
state health issues. health issues.
One or more vSAN enabled hosts Network Configuration Triggered when one or more vSAN enabled
are not in the same IP subnet hosts are not in the same IP subnet.
VMware, Inc. 1150


Overall health of the physical disks Storage Availability Triggered when overall health of the physical
in a vSAN Cluster is impacted. disks in a vSAN Cluster is impacted. See the
health status of each physical disk individually
on all the hosts.
Overall health of VMs residing on Storage Availability Triggered when overall health of the VMs on a
vSAN datastore is reporting issues. vSAN datastore is impacted.
Overall health of vSAN objects is Storage Availability Triggered when overall health of vSAN objects
reporting issues. is reporting issues.
Ping test with large packet size Network Configuration Triggered when ping test with large packet
between all VMKernel adapters size between all VMKernel adapter with
with vMotion traffic enabled has vMotion traffic enabled is impacted.
issues.
Ping test with small packet size Network Configuration Triggered when ping test with small packet
between all VMkernel adapters with size between all VMKernel adapter with
vMotion traffic enabled has issues. vMotion traffic enabled is impacted.
Site latency between two fault Storage Performance Site latency between two fault domains and
domains and the witness host has the witness host has exceeded the
exceeded the recommended recommended threshold values in a vSAN
threshold values in a vSAN Stretched cluster.
Stretched cluster.
Statistics collection of vSAN Storage Availability Triggered when statistics collection of vSAN
performance service is not working performance service is not working correctly.
correctly. This means that statistics collection or writing
statistics data to storage have failed for three
consecutive intervals.
MTU check (ping with large packet Storage Configuration Triggered when MTU check (ping with large
size) has failed on vSAN host. packet size) has failed on vSAN environment
due to some MTU misconfiguration in the
vSAN network.
The preferred fault domain is not Storage Configuration Triggered when the preferred fault domain is
set for the witness host in a vSAN not set for the witness host in a vSAN
Stretched cluster. Stretched cluster and affecting the operations
of vSAN Stretched cluster.
Unicast agent is not configured on Storage Configuration Triggered when unicast agent is not
the host and affecting operations of configured on the host and affecting
vSAN Stretched cluster. operations of vSAN Stretched cluster.
vCenter Server has lost connection Storage Availability Triggered when the host that is part of a vSAN
to a host that is part of a vSAN cluster is in disconnected state or not
cluster. responding and vCenter Server does not know
its state.
vSAN Cluster contains host whose Storage Configuration Triggered when vSAN Cluster contains host
ESXi version does not support whose ESXi version does not support vSAN
vSAN Stretched Cluster. Stretched Cluster.
VMware, Inc. 1151


vSAN cluster has issues in electing Storage Configuration Triggered when vSAN cluster has issues in
stats master of vSAN Performance electing stats primary of vSAN Performance
service. This affects the service.
functionality of vSAN Performance
service.
vSAN cluster has multiple network Network Configuration Triggered when vSAN cluster has multiple
partitions. network partitions due to a network issue.
vSAN Cluster has multiple Stats DB Storage Configuration Triggered when vSAN cluster has issues in
objects which are creating conflicts electing stats primary of vSAN Performance
and affecting vSAN Performance service.
Service This affects the functionality of vSAN
Performance service.
vSAN disk group has incorrect Storage Configuration Triggered when vSAN disk group has incorrect
deduplication and compression deduplication and compression configuration.
configuration
vSAN has encountered an issue Storage Availability Triggered when vSAN has encountered an
while reading the metadata of a issue while reading the metadata of a physical
physical disk disk and cannot use this disk.
vSAN health service is not installed Storage Configuration Triggered when vSAN health service is not
on the host installed on the host.
vSAN host and its disks have Storage Configuration Triggered when vSAN host and its disks have
inconsistent deduplication and inconsistent deduplication and compression
compression configuration with the configuration with the cluster.
cluster
vSAN is unable to retrieve the Storage Availability Triggered when vSAN is unable to retrieve the
physical disk information from host physical disk information from host. vSAN
Health Service may not be working properly
on this host.
vSAN Performance Service is not Storage Configuration Triggered when vSAN Performance Service is
enabled. not enabled.
vSAN Performance Service is Storage Configuration Triggered when vSAN Performance Service is
unable to communicate and unable to communicate and retrieve statistics
retrieve statistics from host from host.
vSAN Stretched cluster contains a Storage Configuration Triggered when vSAN Stretched cluster
witness host without a valid disk contains a witness host without a valid disk
group. group.
If the witness host does not have any disk
claimed by vSAN then its fault domain is not
available.
vSAN Stretched cluster does not Storage Configuration Triggered when vSAN Stretched cluster does
contain a valid witness host. not contain a valid witness host.
This affects the operations of vSAN Stretched
cluster.
vSAN Stretched cluster does not Storage Configuration Triggered when vSAN Stretched cluster does
contain two valid fault domains. not contain two valid fault domains.
VMware, Inc. 1152


vSAN Stretched cluster has Storage Configuration Triggered when vSAN Stretched cluster
inconsistent configuration for contains multiple unicast agents.
Unicast agent. This means multiple unicast agents were set on
non-witness hosts.
vSAN witness host has an invalid Storage Configuration Triggered when vSAN witness host has an
preferred fault domain. invalid preferred fault domain.
Witness host is a part of vSAN Storage Configuration Triggered when witness host is a part of the
Stretched cluster. vCenter cluster, which forms vSAN Stretched
cluster.
Witness host resides in one of the Storage Configuration Triggered when witness host resides in one of
data fault domains. the data fault domains.
This affects the operations of vSAN Stretched
cluster.
Table 7-111. vSAN Cluster Object Risk Alert Definitions

After one additional host failure, Storage Capacity Triggered when after one additional host
vSAN Cluster will not have enough failure, vSAN Cluster will not have enough
resources to rebuild all objects resources to rebuild all objects.
Capacity disk used for vSAN is Storage Performance Triggered when a capacity disk used for vSAN
smaller than 255 GB (default max is smaller than 255 GB (default max
component size). component size), so virtual machines that run
on the vSAN Datastore might experience disk
space issues.
Capacity disk used for vSAN is Storage Availability Triggered when a capacity disk used for vSAN
smaller than 255 GB (default max is smaller than 255 GB (default max
component size). component size), so virtual machines that run
on the vSAN Datastore might experience disk
space issues.
Controller with pass-through and Storage Configuration Triggered when a controller with pass-through
RAID disks has issues. and RAID disks has issues.
Disk format version of one or more Storage Configuration Triggered when the disk format version of one
vSAN disks is out of date or more vSAN disks is out of date and is not
compatible with other vSAN disks. This can
lead to problems in creating or powering on
VMs, performance degradation, and EMM
failures.
ESXi host issues retrieving Storage Configuration Triggered when the ESXi host issues retrieving
hardware info. hardware info.
Firmware provider hasn't all its Storage Configuration Triggered when a firmware provider has not
dependencies met or is not met all its dependencies or is not functioning
functioning as expected. as expected.
VMware, Inc. 1153

Table 7-111. vSAN Cluster Object Risk Alert Definitions (continued)

Host with inconsistent extended Storage Configuration Triggered when a host with inconsistent
configurations is detected. extended configurations is detected.
vSAN cluster extended configurations are set
as object repair timer is 60 minutes, site read
locality is Enabled, customized swap object is
Enabled, large scale cluster support is
Disabled; For host with inconsistent extended
configurations, vSAN cluster remediation is
recommended, for host doesn't support any
extended configuration, ESXi software
upgrade is needed; And to make cluster
scalability configuration take effect, host
reboot could be required.
Inconsistent configuration (like Storage Configuration Triggered when there is inconsistent

dedup/compression, encryption) configuration (like dedup/compression,
setup on hosts or disks with the encryption) setup on hosts or disks with the
cluster. cluster.
Network adapter driver is not Storage Configuration Triggered when the network adapter driver is
VMware certified. not VMware certified.
Network adapter firmware is not Storage Configuration Triggered when the network adapter firmware
VMware certified. is not VMware certified.
Network adapter is not VMware Storage Configuration Triggered when the network adapter is not
certified. VMware certified.
Network configuration of the vSAN Storage Availability Triggered when the network configuration of
iSCSI target service is not valid. the vSAN iSCSI target service is not valid.
This health check validates the presence of the
default vmknic for the vSAN iSCSI target
service, and verifies that all the existing targets
have valid vmknic configurations.
Non-vSAN disks are used for VMFS Storage Availability Triggered when non-vSAN disks are used for
or Raw Device Mappings(RDMs). VMFS or Raw Device Mappings (RDMs).
Number of vSAN components on a Storage Capacity Triggered when the number of vSAN
disk is reaching or has reached its components on a disk is reaching or has
limit. reached its limit. This will cause failure in the
deployment of new Virtual Machines and also
impact rebuild operations.
Number of vSAN components on a Storage Capacity Triggered when the number of vSAN
host is reaching or has reached its components on a host is reaching or has
limit. reached its limit.
This will cause failure in the deployment of
new Virtual Machines and also impact rebuild
operations.
VMware, Inc. 1154


One or more ESXi hosts in the Storage Availability Triggered when one or more hosts in the
cluster do not support CPU AES-NI cluster do not support CPU AES-NI or have it
or have it disabled. disabled. As a result, the system might use the
software encryption that is significantly slower
than AES-NI.
RAID controller configuration has Storage Configuration Triggered when the RAID controller
issues. configuration has issues.
Storage I/O controller driver is not Storage Configuration Triggered when the stability and integrity of
VMware certified vSAN may be at risk as the storage I/O
controller driver is not VMware certified.
Storage I/O controller drivers is not Storage Configuration Triggered when the stability and integrity of
supported with the current version vSAN may be at risk as the storage I/O
of ESXi running on the host controller driver is not supported with the
current version of ESXi running on the host.
Storage I/O Controller firmware not Storage Configuration Triggered when the storage I/O Controller
is VMware certified. firmware not is VMware certified.
Storage I/O controller is not Storage Configuration Triggered when the vSAN environment may
compatible with the VMware be at risk as the Storage I/O controller on the
Compatibility Guide ESXi hosts that are participating in a vSAN
cluster are not compatible with the VMware
Compatibility Guide.
The current status of the Customer Storage Availability Triggered when the current status of the
Experience Improvement Program Customer Experience Improvement Program
(CEIP) not is enabled. (CEIP) not is enabled.
The Internet connectivity is not Storage Availability Triggered when internet connectivity is not
available for vCenter Server. available for vCenter Server.
The resync operations are throttled Storage Configuration Triggered when resync operations are
on any hosts. throttled. Please clear the limit, unless you
need it for particular cases like a potential
cluster meltdown.
Time of hosts and VC are not Storage Configuration Triggered when the time of hosts and VC are
synchronized within 1 minute. not synchronized within 1 minute.
Any difference larger than 60 seconds will lead
this check to fail. If the check fails, it is
recommended that you check the NTP server
configuration.
vCenter Server or any of the ESXi Storage Availability Triggered when the vCenter Server or any of
hosts experience problems when the hosts experience problems when
connecting to Key Management connecting to KMS.
Servers (KMS).
VMware, Inc. 1155


vCenter server state was not Storage Configuration Triggered when the vCenter server state was
pushed to ESXi due to vCenter not pushed to ESXi due to vCenter server
server being out of sync. being out of sync.
During normal operation, the vCenter server
state is regarded as source of truth, and ESXi
hosts are automatically updated with the latest
host membership list. When vCenter server is
replaced or recovered from backup, the host
membership list in vCenter server may be out
of sync. This health check detects such cases,
and alerts if vCenter server state was not
pushed to ESXi due to vCenter server being
out of sync. In such cases, first fully restore the
membership list in vCenter server, and then
perform 'Update ESXi configuration' action if
required.
vSAN and VMFS datastores are on Storage Configuration Triggered when the vSAN and VMFS
a same Dell H730 controller with datastores are on a same Dell H730 controller
the lsi_mr3driver. with the lsi_mr3driver.
vSAN build recommendation based Storage Availability Triggered when the vSAN build is not
on the available releases and VCG compatible with available releases and VCG
compatibility guide. compatibility guide.
This is the ESXi build that vSAN recommends
as the most appropriate, given the hardware,
its compatibility per the VMware Compatibility
Guide and the available releases from VMware.
vSAN build recommendation engine Storage Availability Triggered when the vSAN build
has all its dependencies met and is recommendation engine has issues.
functioning as expected. The vSAN Build Recommendation Engine relies
on the VMware compatibility guide and
VMware release metadata for its
recommendation. To provide build
recommendations, it also requires VMware
Update Manager service availability, internet
connectivity, and valid credentials for
my.vmware.com. This health check ensures
that all dependencies are met and that the
recommendation engine is functioning
correctly.
vSAN Cluster disk space capacity is Storage Capacity Triggered when the disk usage in a vSAN
less than 5% cluster reaches 95% of capacity.
Cleared by removing virtual machines that are
no longer in use or adding more disks to the
cluster.
VMware, Inc. 1156


vSAN Cluster disk space usage is Storage Capacity Triggered when the disk usage in a vSAN
approaching capacity cluster reaches 80% of capacity.
Cleared by removing virtual machines that are
no longer in use or adding more disks to the
cluster.
vSAN cluster is reaching or has Storage Capacity Triggered when the vSAN cluster is reaching
reached its limit for components, or has reached its limit for components, free
free disk space and read cache disk space and read cache reservations.
reservations.
vSAN Cluster virtual disk count Storage Capacity Triggered when the number of virtual disks per
capacity is less than 5%. host in the vSAN cluster reaches 95% of
capacity.
Cleared by adding most hosts to the cluster.
vSAN Cluster virtual disk count is Storage Capacity Triggered when the number of virtual disks per
approaching capacity. host in the vSAN cluster reaches 75% of
capacity.
Cleared by adding most hosts to the cluster.
vSAN configuration for LSI 3108- Storage Configuration Triggered when the vSAN configuration for LSI
based controller has issues. 3108-based controller has issues.
vSAN disk group type (All-Flash or Storage Configuration Triggered when the vSAN disk group type (All-
Hybrid) for the used SCSI controller Flash or Hybrid) for the used SCSI controller is
is not VMware certified. not VMware certified.
vSAN enabled hosts have Storage Configuration Triggered when some advanced configuration
inconsistent values for advanced settings have different values on different
configuration options. hosts in the vSAN cluster.
vSAN firmware version Storage Configuration Triggered when the vSAN firmware version
recommendation based on the recommendation based on the VCG check has
VCG. issues.
vSAN has encountered an integrity Storage Availability Triggered when the vSAN has encountered an
issue with the metadata of an integrity issue with the metadata of an
individual component on a physical individual component on a physical disk.
disk.
vSAN HCL DB auto updater is not Storage Configuration Triggered when the vSAN HCL DB auto
working properly. updater is not working properly. This means
that vSAN cannot download and update its
HCL DB automatically.
vSAN HCL DB is not up-to-date. Storage Configuration Triggered when the vSAN HCL DB is not up-to-
date.
vSAN Health Service is not able to Storage Availability Triggered when the vSAN Health Service is not
find the appropriate controller utility able to find the appropriate controller utility for
for the storage controller on the the storage controller on the ESXi host.
ESXi host.
VMware, Inc. 1157


vSAN is running low on the vital Storage Performance Triggered when the vSAN is running low on
memory pool (heaps) needed for the vital memory pool (heaps) needed for the
the operation of physical disks. operation of physical disks.
This can lead to a variety of performance
issues such as virtual machine storage
performance degradation, operation failures,
or even ESXi hosts going unresponsive.
vSAN is running low on the vital Storage Performance Triggered when the vSAN is running low on
memory pool (slabs) needed for the the vital memory pool (slabs) needed for the
operation of physical disks. operation of physical disks.
vSAN is using a physical disk which Storage Performance Triggered when the vSAN is using a physical
has high congestion value. disk which has high congestion value.
vSAN iSCSI target service home Storage Availability Triggered when the vSAN iSCSI target service
object has issues. home object has issues.
This health check verifies the integrity of the
vSAN iSCSI target service home object. It also
verifies that the configuration of the home
object is valid.
vSAN iSCSI target service is not Storage Availability Triggered when the vSAN iSCSI target service
running properly or is not correctly is not running properly or is not correctly
enabled on the host. enabled on the host.
This health check verifies the service runtime
status of the vSAN iSCSI target service, and
checks whether the service is correctly
enabled on each host.
vSAN performance service statistics Storage Availability Triggered when the vSAN performance service
database object is reporting issues. statistics database object is reporting issues.
vSphere cluster members do not Storage Configuration Triggered when the vSphere cluster members
match vSAN cluster members. do not match vSAN cluster members.
VMware, Inc. 1158

Table 7-112. vSAN Cluster Object Efficiency Alert Definitions

vSAN Cluster flash read cache is Storage Capacity Triggered when the Read Cache (RC) in the
approaching capacity. vSAN cluster reaches 80% of capacity.
Cleared by adding flash storage to the read
cache.
vSAN Cluster flash read cache Storage Capacity Triggered when the Read Cache (RC) in the
capacity is less than 5%. vSAN cluster reaches 95% of capacity.
Cleared by adding flash storage to the read
cache.
vSAN Adapter Instance Object Alert Definitions

Alerts on the vSAN Adapter Instance Object have health impact.
Performance Service on vSAN Storage Configuration Triggered when the vSphere Virtual SAN
cluster might be off or experience Performance Service is off or experiences
issues. issues for one of the vSAN-enabled cluster
compute resources.
Cleared by enabling Virtual SAN
performance service in vSphere.
vSAN adapter instance failed to Storage Configuration Triggered when the vSAN adapter instance
collect data from vSAN Health failed to collect data from vSAN Health
Service. The health Service might Service. The health Service might have
have issues. issues.
vSAN Disk Group Object Alert Definitions

Alerts on the vSAN Disk Group Object have efficiency impact.
vSAN Disk Group read cache hit Storage Performance Triggered when the vSAN disk group read
rate is less than 90%. cache hit rate is less than 90%.
Cleared by adding more cache to
accommodate the workload.
vSAN Disk Group read cache hit Storage Capacity Triggered when the vSAN disk group read
rate is less than 90% and write cache hit rate is less than 90% and the vSAN
buffer free space is less than 10%. disk group write buffer free space is less
than 10%.
Cleared by adding more flash capacity to the
vSAN disk group.
vSAN Host Object Alert Definitions

Alerts on the vSAN Host Object have security impact.
VMware, Inc. 1159

vSAN host has encryption Storage Configuration Triggered when the vSAN host has
disabled, while the vSAN cluster encryption disabled, while the vSAN cluster
has encryption enabled. has encryption enabled.
Cleared by enabling encryption on vSAN
host.
vSAN host encryption is enabled, Storage Configuration Triggered when the vSAN host has
while the vSAN cluster encryption encryption enabled, while the vSAN cluster
is disabled. has encryption disabled.
cluster.
vSAN Capacity Disk Object Alert Definitions

Alerts on the vSAN Capacity Disk object have security impact.
vSAN capacity disk has encryption Storage Configuration Triggered when the vSAN capacity disk has
capacity disk.
vSAN capacity disk encryption is Storage Configuration Triggered when the vSAN capacity disk has
enabled, while the vSAN cluster encryption enabled, while the vSAN cluster
encryption is disabled. has encryption disabled.
cluster.
vSAN Cache Disk Object Alert Definitions

Alerts on the vSAN Cache Disk object have security impact.
vSAN cache disk has encryption Storage Configuration Triggered when the vSAN cache disk has
cache disk.
vSAN cache disk encryption is Storage Configuration Triggered when the vSAN cache disk has
enabled, while the vSAN cluster encryption enabled, while the vSAN cluster
encryption is disabled. has encryption disabled.
cluster.
VMware, Inc. 1160

Alerts in the vSphere Web Client

The vSphere Web Client displays the results of health tests for the following vSAN monitored
groups:
n Network
n Physical disk
n Cluster
n Limits
n Data
n Hardware compatibility
n Performance Service
n Stretched Cluster (if enabled)
Each group contains several individual checks. If a check fails, the vSAN adapter issues a warning
or error level alert. The alert indicates the host or cluster where the problem occurred and
provides a recommendation to clear the alert. For a complete list of all vSAN health test alerts,
see Knowledge Base article 2114803.
vSphere Distributed Port Group

The vCenter adapter provides alert definitions that generate alerts on the vSphere Distributed
Port objects in your environment.
Health/Critical
Impact
Health
Criticality
Critical
One or more ports are in a link down Symptoms include all of the following: Verify that there is physical
state. n Port is connected. connectivity for the NICs on the host.
Verify the admin status on the port.
n One or more ports are in a link
down state.
One or more ports are experiencing Port is experiencing dropped Check if the packet drops are due to
network contention. packets. high CPU resource utilization or uplink
bandwidth utilization. User vMotion to
migrate the virtual machine that the
port is attached to a different host.
VMware, Inc. 1161

Virtual Machine Alert Definitions

The vCenter adapter provides alert definitions that generate alerts on the virtual machine objects
Impact
Health
Criticality
Symptom-based
Virtual machine is experiencing n Virtual machine memory limit is Increase the memory limit for the
memory compression, ballooning or set AND virtual machine to match the
swapping due to memory limit. n Virtual machine memory demand recommended memory size.
exceeds configured memory limit Alternatively, remove memory limit for
AND the virtual machine.
n [Virtual machine memory is

compressed OR
n Virtual machine is using swap OR
n Virtual machine memory
ballooning is at warning/
immediate/critical level] AND
n Recommended virtual machine
memory size
Virtual machine has CPU contention Virtual machine CPU I/O wait is at Increase the datastore I/O capacity for
caused by IO wait. warning/immediate/critical level. the connected data stores to reduce
CPU I/O wait on the virtual machine.
Virtual machine has unexpected high Symptoms include all of the following: 1 Check the guest applications to
memory workload. n Virtual machine memory determine whether high memory
workload is at Warning/ workload is an expected behavior.
Immediate/Critical level 2 Add more memory for this virtual
n Anomaly is starting to/ machine.
moderately/critically high
Virtual machine has memory Symptoms include all of the following: Add more memory for this virtual
contention due to swap wait and high n Virtual machine CPU swap wait is machine.
disk read latency. at warning/immediate/critical
level (5/10/15)
n Virtual machine has
read latency at warning level
n Recommended virtual machine
memory size
VMware, Inc. 1162

Virtual machine has memory n ! Virtual machine memory limit is 1 Add memory reservations to this
contention due to memory set AND virtual machine to prevent
compression, ballooning or swapping. n Virtual machine has memory ballooning and swapping.
contention at warning/immediate/ 2 Use vSphere vMotion to migrate
critical level AN this virtual machine to a different
n [ Virtual machine memory host or cluster.
ballooning at warning/immediate/
critical level OR
n Virtual machine memory is
compressed OR
n Virtual machine is using swap]
Virtual machine has unexpected high Symptoms include all of the following: 1 Check the applications running on
disk I/O workload. n Virtual machine disk I/O workload the virtual machine to determine
at Warning/Immediate/Critical whether high disk I/O workload is
level (80/90/95) an expected behavior.
n Virtual machine disk I/O workload 2 Use vSphere Storage vMotion to

above DT migrate this virtual machine to a
different datastore with higher
IOPS.
Virtual machine has disk I/O read Symptoms include all of the following: 1 Check whether you have enabled
latency problem. n Virtual machine disk read latency Storage IO control on the
at Warning /Immediate/Critical datastores connected to the virtual
level machine.
n Virtual machine disk read latency 2 Increase IOPS for the datastores
above DT connected to the virtual machine.
n Virtual machine has low co-stop 3 UsevSphere Storage vMotion to

migrate this virtual machine to a
n Virtual machine has low CPU
different datastore with higher
swap wait
IOPS.
Virtual machine has disk I/O write Symptoms include all of the following: 1 Check whether you have enabled
latency problem. n Virtual machine disk write latency Storage IO Control on the data
at Warning/ Immediate/Critical stores connected to the datastore.
level 2 Increase IOPS for the data stores
n Virtual machine disk write latency connected to the virtual machine.
above DT 3 If the virtual machine has multiple
n Virtual machine has low CPU snapshots, delete the older
swap wait (< 3 ms) snapshots.
4 Use vSphere Storage vMotion to
migrate some virtual machines to a
different datastore.
Virtual machine has disk I/O latency Symptoms include all of the following: 1 If the virtual machine has multiple
problem caused by snapshots. n Virtual machine CPU I/O wait is at snapshots, delete the older
warning/immediate/critical level snapshots.
n Virtual machine has at least one 2 Reduce the number of snapshots

snapshot by consolidating the snapshots into
one snapshot. In vSphere Client,
n All child datastores have [ ! Disk
select the VM, right-click, select
command latency at warning
Snapshot, and then Consolidate.
level ]
VMware, Inc. 1163

Not enough resources for vSphere HA Not enough resources forvSphere HA 1 If virtual machine CPU reservation
to start the virtual machine. to start VM (Fault symptom). is set, decrease the CPU
reservation configuration.
2 If virtual machine memory
reservation is set, decrease the
memory reservation configuration.
3 Add more hosts to cluster.
4 Bring any failed hosts online or
resolve a network partition, if one
exists.
5 If DRS is in manual mode, look for
pending recommendations and
approve the recommendations so
that vSphere HA failover can
proceed.
The Fault tolerance state of the virtual VM fault tolerance state changed to Enable the secondary virtual machine
machine has changed to "Disabled" disabled (Fault symptom). indicated in the alert.
state.
vSphere HA failed to restart a network vSphere HA failed to restart a Manually power on the virtual machine.
isolated virtual machine. network isolated virtual machine
(Fault symptom).
The fault tolerance state of the virtual VM Fault Tolerance state changed to Keep HA enabled when Fault tolerance
machine has changed to "Needs needs secondary (Fault symptom). (FT) is required to protect virtual
Secondary" state. machines.
vSphere HA cannot perform a failover vSphere HA virtual machine failover 1 If the error information reports that
operation for the virtual machine unsuccessful (Fault symptom) a file is locked, the virtual machine
might be powered on a host that
the vSphere HAmaster agent can
no longer monitor by using the
management network or heartbeat
datastores.
2 The virtual machine might have
been powered on by a user on a
host outside of the cluster. If any
hosts are declared offline,
determine whether a networking or
storage problem caused the
situation.
3 If the error information reports that
the virtual machine is in an invalid
state, an in-progress operation
might be preventing access to the
virtual machine files. Determine
whether any operations are in
progress, such as a clone operation
that is taking a long time to
complete.
4 You can also try to power on the
virtual machine and investigate any
returned errors.
VMware, Inc. 1164

One or more virtual machine guest file Symptoms include all of the following: Add a new virtual hard disk or expand
systems are running out of disk space. n Guest file system usage at the existing disk of the virtual machine.
warning level Before expanding the existing disk,
remove all the snapshots. Once done,
n Guest file system usage at critical
use a guest OS specific procedure to
level
expand the file system on the new or
expanded disk.
Virtual machine has CPU contention Symptoms include all of the following: 1 Set memory reservations for the
due to memory page swapping in the n Virtual machine CPU swap wait is virtual machine to prevent its
host. at Critical level memory from being swapped.
n Virtual machine CPU swap wait is 2 Verify that VMware Tools is

at Immediate level installed and running, and that the
balloon driver is enabled in the
n Virtual machine CPU swap wait is
guest. Memory ballooning helps
at Warning level
the host reclaim unused memory
from the guest more effectively,
and might avoid swapping.
3 Use vMotion to migrate this virtual
machine to a different host or
cluster.
Efficiency/Warning
Impact
Efficiency
Criticality
Warning
Virtual machine is idle. Symptoms include all of the following: Power off this virtual machine to allow
n Virtual machine is idle for other virtual machines to use CPU
and memory that this virtual machine is
n Virtual machine high ready time
wasting.
on each vCPU
n ! Virtual machine is powered off
Risk/Symptom-Based
Impact
Risk
Criticality
VMware, Inc. 1165

Symptom-based
Virtual machine has CPU contention Symptoms include all of the following: Review the symptoms listed and
caused by co-stop. n Virtual machine CPU co-stop at remove the number of vCPUs from the
warning/immediate/critical level virtual machine as recommended by
the symptom.
n ! Virtual machine is powered off
n Number of vCPUs to remove from
virtual machine
Virtual machine is violating vSphere 5.5 n Unrestricted VM-to-VM Fix the vSphere 5.5 hardening guide
hardening guide. communication through VMCI OR rule violations according to the
n VMsafe CPU/Memory APIs-port recommendations in the vSphere
number configured OR Hardening Guide (XLSX).
n Dvfilter network API enabled OR

n Non-compliant max VMX file size
OR
n Non-compliant max VM log file
size OR
n Allow unauthorized modification
of device settings OR
n Allow unauthorized connect and
disconnect of devices OR
n Tools auto install not disabled OR
n Non-compliant max number of
remote console connections OR
n Allow VM to obtain detailed
information about the physical
host OR
n Non-compliant max VM log file
count OR
n Feature not exposed in vSphere:
MemsFss is not disabled OR
n VMsafe CPU/memory API
enabled OR
n Parallel port connected OR
n Console drag and drop operation
not disabled OR
n Console copy operation not
disabled OR
n Serial port connected OR
n Feature not exposed in vSPhere:
AutoLogon is not disabled OR
n Use independent non persistent
disk OR
UnityPush is not disabled OR
n Shrink virtual disk not disabled -
diskShrink OR
GetCreds is not disabled OR
VMware, Inc. 1166

n CD-ROM connected OR
HGFSServerSet is not disabled OR
n Console paste operation not
disabled OR
BIOSBBS is not disabled OR
n Shrink virtual disk not disabled -
diskWiper OR
n USB controller connected OR
Monitor Control is not disabled
OR
n Floppy drive connected OR
LaunchMenu is not disabled OR
n Versionget is not disabled OR
Toporequest is not disabled OR
Unity-interlock not disabled OR
n VM logging is not disabled OR
Unity is not disabled OR
Trashfolderstate is not disabled
OR
n VGA only mode is not enabled OR
Trayicon is not disabled OR
Unity-Taskbar is not disabled OR
Versionset is not disabled OR
n VM console access via VNC
protocol is not disabled OR
Protocolhandler is not disabled
OR
n VIX message is not disabled OR
Shellaction is not disabled OR
n 3D features is not disabled OR
Unity-Windowcontents is not
disabled OR
VMware, Inc. 1167


Unity-Unityactive is not disabled
Virtual machine has CPU contention Symptoms include all of the following: None.
due to multi-vCPU scheduling issues n Virtual machine CPU co-stop is at
(co-stop) caused by snapshots Warning level OR
n Virtual machine CPU co-stop is at
Immediate level OR
n Virtual machine CPU co-stop is at
Critical level
And
n Virtual machine is powered off OR
n Virtual machine has at least one
snapshot
vSphere Distributed Switch Alert Definitions

The vCenter adapter provides alert definitions that generate alerts on the vSphere Distributed
Switch objects in your environment.
Health/Critical
Impact
Health
Criticality
Critical
Network traffic is blocked for one or Network traffic is blocked for one or Check the security policy on the port
more ports. more ports. groups as well as any ACL rule
configuration.
Health/Warning
Impact
Health
Criticality
VMware, Inc. 1168

Warning
Distributed Switch configuration is out Distributed Switch configuration is Change the distributed switch
of sync. out of sync with the vCenter Server. configuration to match the host.
Identify the distributed switch
properties that are out of sync. If these
properties were changed locally on the
host in order to maintain connectivity,
update the distributed switch
configuration in the vCenter Server.
Otherwise, re-apply the the vCenter
Server configuration to this host.
One or more VLANs are unsupported One or more VLANs are unsupported Ensure the VLAN configuration on the
by the physical switch. by the physical switch. physical switch and the distributed
port groups are consistent.
Teaming configuration does not match Teaming configuration does not Ensure the teaming configuration on
the physical switch. match the physical switch. the physical switch and the distributed
switch are consistent.
The MTU on the Distributed Switch is The MTU on the Distributed Switch is Ensure the MTU configuration on the
not allowed by one or more VLANs on not allowed by one or more VLANs physical switch and the distributed
the host. on the host. switch are consistent.
There is an MTU mismatch between There is an MTU mismatch between Adjust the MTU configuration on the
the host and a physical switch. the host and a physical switch. host to match the physical switch.
Change the MTU configuration on the
physical switch.
Risk/Warning
Impact
Risk
Criticality
Warning
The distributed switch configuration is Host without redundant physical Verify that at least two NICs on each
incorrect. connectivity to the distributed switch. host is connected to the distributed
switch.
vCenter Server Alert Definitions

The vCenter adapter provides alert definitions that generate alerts on the vCenter Server objects
VMware, Inc. 1169

Impact
Health
Criticality
Symptom-based
A problem occurred with a vCenter The vCenter Server health changed The actions to take to resolve the
Server component. (fault symptom). problems depend on the specific
problem that caused the fault. Review
the issue details, and check the
documentation.
Duplicate object name found in Duplicate object name found in the Ensure the virtual machines names are
thevCenter Server. vCenter Server. unique before enabling the Name-
Based Identification feature.
The vCenter Server Storage data The vCenter Server storage data Ensure vCenter Management
collection failed. collection failed. Webservice is started and Storage
Management Service is functioning.
VASA Provider(s) disconnected One or more VASA Providers If the VASA provider is inaccessible
disconnected from vCenter. from the vCenter and you are getting
an invalid certificate error then please
check the following kbase
article:2079087. Please contact the
hardware vendor for further support.
Certificate for VASA Provider(s) will One or more VASA Providers' Please contact the hardware vendor
expire soon certificates will expire soon. for getting support on the CA
certificates and CRLs for VASA
provider.
Refreshing CA certificates and CRLs for Refreshing CA certificates and CRLs Please refresh the storage provider
VASA Provider(s) failed for one or more VASA Providers certificate as per the following
failed. document: Refresh Storage Provider
Certificates. Please contact the
hardware vendor for further support.
Note The Refresh Storage Provider

Certificates is in the vSphere Storage
6.5 guide.
Datastore Alert Definitions

The vCenter adapter provides alert definitions that generate alerts on the datastore objects in
your environment.
VMware, Inc. 1170

Impact
Health
Criticality
Symptom-based
Datastore has unexpected high Disk Symptoms include all of the following: 1 Check the applications running on
I/O workload. n Datastore disk I/O workload at the virtual machines placed on the
warning/immediate/critical level datastore to determine whether
high disk I/O workload is expected
n Datastore disk I/O workload
behavior.
above DT
2 Increase IOPS for the datastore.
Health/Critical
Impact
Health
Criticality
VMware, Inc. 1171

Critical
A storage device for a datastore has Storage device has been turned off Ask the administrator about the device
been detected to be off. administratively (fault symptom). state. The fault will be resolved and the
alert canceled if the device is turned
on. If SCSI devices are detached or
permanently removed, you must
Datastore has lost connectivity to a Host(s) lost connectivity to storage The storage device path, for example,
storage device. device(s) (fault symptom). vmhba35:C1:T0:L7, contains several
potential failure points: Path Element |
Failure Point
---------------------------------------
vmhba35 | HBA (Host Bus Adapter) C1
| Channel T0 | Target (storage
processor port) L7 | LUN (Logical Unit
Number or Disk Unit).
To determine the cause of the failure
or to eliminate possible problems:
Identify the available storage paths to
the reported storage device by
running esxcfg-mpath - l. For more
information, see http://
kb.vmware.com/kb/1003973. Check
that a rescan does not restore visibility
to the targets. For information on
rescanning the storage device by using
the command-line interface and the
vSphere Client, see http://
kb.vmware.com/kb/1003988.
Determine whether the connectivity
issue is with the iSCSI storage or the
fiber storage.
Troubleshoot the connectivity to the
iSCSI storage by using the software
initiator:
1 Check whether a ping to the
storage array fails from ESX. For
more information, see http://
kb.vmware.com/kb/1003486
2 Check whether a vmkping to each
network portal of the storage array
fails. For more information,
seehttp://kb.vmware.com/kb/
10037828.
3 Check that the initiator is
registered on the array. For more
information, contact your storage
vendor.
VMware, Inc. 1172

4 Check that the following physical

hardware is functioning correctly:
Ethernet switch, Ethernet cables
between the switch and the ESX
host, and Ethernet cables between
the switch and the storage array.
To troubleshoot the connectivity to the
fiber-attached storage, check the fiber
switch. The fiber switch zoning
configuration permits the ESX host to
see the storage array. If you require
assistance, contact your switch
vendor. The fiber switch propagates
RSCN messages to the ESX hosts. For
more information about configuring
the fiber switch, see http://
Finally, check the following physical
hardware: the storage processors on
the array, the fiber switch and the
Gigabit Interface Converter (GBIC)
units in the switch, the fiber cables
between the fiber switch and the
array, and the array itself.
You must rescan after making changes
to make sure that the targets are
detected. If storage connectivity is
restored for all of the affected host
and storage device combinations, the
fault is cleared and the alert canceled.
If storage connectivity for the devices
indicated is caused by a permanent
loss or change, you must cancel the
fault alert as a workaround. The alert
will then be canceled automatically.
Health/Immediate
Impact
Health
Criticality
VMware, Inc. 1173

Immediate
Datastore has one or more hosts that Host(s) lost redundancy to storage The storage device path, for example,
have lost redundant paths to a storage device(s) (fault symptom). vmhba35:C1:T0:L7, contains several
device. potential failure points:
Path Element | Failure Point
---------------------------------------
vmhba35 | HBA (Host Bus Adapter) C1
| Channel T0 | Target (storage
processor port) L7 | LUN (Logical Unit
Number or Disk Unit).
Use the following guidance to
determine the cause of the failure or to
eliminate possible problems. Identify
the available storage paths to the
reported storage device by running
esxcfg-mpath - l. For more
information, see http://
Check that a rescan does not restore
visibility to the targets. For information
on rescanning the storage device by
using the command-line interface and
the vSphere Client, see http://
Determine whether the connectivity
issue is with the iSCSI storage or the
fiber storage. Troubleshoot the
connectivity to the iSCSI storage by
using the software initiator:
1 Check whether a ping to the
storage array fails from ESX. For
more information, seehttp://
2 Check whether a vmkping to each
network portal of the storage array
fails. For more information,
seehttp://kb.vmware.com/kb/
10037828.
3 Check that the initiator is
registered on the array. For more
information, contact your storage
vendor.
4 Check that the following physical
hardware is functioning correctly:
Ethernet switch, Ethernet cables
between the switch and the ESX
host, and Ethernet cables between
the switch and the storage array.
VMware, Inc. 1174

To troubleshoot the connectivity to the

fiber-attached storage, check the fiber
switch. The fiber switch zoning
configuration permits the ESX host to
see the storage array. If you require
assistance, contact your switch
vendor. The fiber switch propagates
RSCN messages to the ESX hosts. For
more information about configuring
the fiber switch, seehttp://
Finally, check the following physical
hardware: the storage processors on
the array, the fiber switch and the
Gigabit Interface Converter (GBIC)
units in the switch, the fiber cables
between the fiber switch and the
array, and the array itself. You must
rescan after making changes to make
sure that the targets are detected. If
storage connectivity is restored for all
of the affected host and storage
device combinations, the fault is
cleared and the alert canceled. If
storage connectivity for the devices
indicated is caused by a permanent
loss or change, you must cancel the
fault alert as a workaround. The alert
will be canceled automatically after
that.
Risk/Symptom-Based
Impact
Risk
Criticality
VMware, Inc. 1175

Symptom-based
Datastore is running out of disk space. Symptoms include all of the following: 1 Add more capacity to the
n Datastore space usage reaching datastore.
warning/immediate/critical level 2 Use vSphere vMotion to migrate
n ! Datastore space growth above some virtual machines to a
DT different datastore.
n Datastore space time remaining is 3 Delete unused snapshots of virtual

low machines from datastore.
4 Delete any unused templates on
the datastore.
Data Center Alert Definitions

The vCenter adapter provides alert definitions that generate alerts on the Data Center objects in
your environment.
Risk/Symptom-Based
These alert definitions have the following impact and criticality information:
Impact
Risk
Criticality
VMware, Inc. 1176

Symptom-based
Data center has unbalanced CPU Symptoms include all of the following: Rebalance the container to spread the
"demand" workload. n DRS enabled workload more evenly.

n DC is unbalanced on CPU
"demand" workload
n DC has significant CPU "demand"
workload difference
n At least one cluster in DC has high
CPU "demand" workload
Data center has unbalanced memory Symptoms include all of the following: Rebalance the container to spread the
"demand" workload. n DRS enabled workload more evenly.
n DRS fully enabled

n DC is unbalanced on memory
"demand" workload difference
memory "demand" workload
Data center has unbalanced memory Symptoms include all of the following: Rebalance the container to spread the
"consumed" workload. n DRS enabled workload more evenly.

n DC is unbalanced on memory
"consumed" workload
n DC has significant memory
"consumed" workload difference
memory "consumed" workload
Custom Data Center Alert Definitions

The vCenter adapter provides alert definitions that generate alerts on the Custom Data Center
Risk/Symptom-Based
Impact
Risk
Criticality
VMware, Inc. 1177

Symptom-based
Custom data center has unbalanced Symptoms include all of the following: Rebalance the container to spread the
CPU "demand" workload. n DRS enabled workload more evenly.
n CDC is unbalanced on CPU
"demand" workload
n CDC has significant CPU
n At least one cluster in CDC has
high CPU "demand" workload
Custom data center has unbalanced Symptoms include all of the following: Rebalance the container to spread the
memory "demand" workload. n DRS enabled workload more evenly.

n CDC is unbalanced on memory
"demand" workload
n CDC has significant memory
high memory"demand" workload
Custom Datacenter has unbalanced Symptoms include all of the following: Rebalance the container to spread the
memory "consumed" workload. n DRS enabled workload more evenly.

n CDC is unbalanced on memory
"consumed" workload
n CDC has significant memory
"consumed" workload difference
high memory"consumed"
workload
Property Definitions in vRealize Operations Manager

Properties are attributes of objects in the vRealize Operations Manager environment. You use
properties in symptom definitions. You can also use properties in dashboards, views, and reports.
vRealize Operations Manager uses adapters to collect properties for target objects in your
environment. Property definitions for all objects connected through the vCenter adapter are
provided. The properties collected depend on the objects in your environment.
You can add symptoms based on properties to an alert definition so that you are notified if a
change occurs to properties on your monitored objects. For example, disk space is a hardware
property of a virtual machine. You can use disk space to define a symptom that warns you when
the value falls below a certain numeric value. See Defining Symptoms for Alerts.
VMware, Inc. 1178

vRealize Operations Manager generates Object Type Classification and Subclassification

properties for every object. You can use object type classification properties to identify whether
an object is an adapter instance, custom group, application, tier, or a general object with
property values ADAPTER_INSTANCE, GROUP, BUSINESS_SERVICE, TIER, or GENERAL,
respectively.
Properties for vCenter Server Components

The VMware vSphere solution is installed with vRealize Operations Managerand includes the
vCenter adapter. vRealize Operations Manager uses the vCenter adapter to collect properties for
objects in the vCenter Server system.
vCenter Server components are listed in the describe.xml file for the vCenter adapter. The
following example shows the runtime property memoryCap or Memory Capacity for the virtual
machine in the describe.xml.
<ResourceGroup instanced="false" key="runtime" nameKey="5300" validation="">

<ResourceAttribute key="memoryCap" nameKey="1780" dashboardOrder="200" dataType="float"
defaultMonitored="true" isDiscrete="false" isRate="false" maxVal=""
minVal="" isProperty="true" unit="kb"/>
</ResourceGroup>
The ResourceAttribute element includes the name of the property that appears in the UI and is
documented as a Property Key. isProperty = "true" indicates that ResourceAttribute is a
property.
vCenter Server Properties

vRealize Operations Manager collects summary and event properties for vCenter Server system
objects.
Table 7-113. Summary Properties Collected for vCenter ServerSystem Objects

Property Key Property Name Description
summary|version Version Version
summary|vcuuid VirtualCenter ID Virtual Center ID
summary|vcfullname Product Name Product Name
Table 7-114. Event Properties Collected for vCenter ServerSystem Objects

event|time Last VC Event Time Last Virtual Center Event Time
event|key Last VC Event ID Last Virtual Center Event ID
Table 7-115. Custom Field Manager Property Collected for vCenter ServerSystem Objects
CustomFieldManager|CustomFieldDef Custom Field Def Custom Field Def for vCenter Tagging
information at the Adapter level.
VMware, Inc. 1179

Virtual Machine Properties

vRealize Operations Manager collects configuration, runtime, CPU, memory, network I/O, and
properties about summary use for virtual machine objects. Properties are collected with the first
cycle of data collection. Once collected, the next property collection occurs only when there is
data change. In case of no data change, no property is collected.
Table 7-116. vRealize Automation Properties Collected for Virtual Machine Objects
vRealize Automation|Blueprint Name Blueprint Name Virtual machines deployed byvRealize Automation to be
excluded from workload placements.
Table 7-117. Properties Collected for Virtual Machine Objects to Support VIN Adapter
Localization
RunsOnApplicationComponents Application components Application components running on the Virtual

running on the Virtual Machine
Machine
DependsOnApplicationComponents Application components the Application components running on other

Virtual Machine depends on machines that this Virtual Machine depends
on.
Table 7-118. Properties Collected for Guest File Systems

guestfilesystem|capacity_property Guest File System stats| This property is disabled by default.

Guest File System Capacity
Property
guestfilesystem|capacity_property_total Guest File System stats|Total This property is disabled by default.

Guest File System Capacity
Property(gb)
Table 7-119. Properties Collected for Disk Space Objects

diskspace|snapshot|creator Disk Space|Snapshot|Creator This property is disabled by default.
diskspace|snapshot|description Disk Space|Snapshot| This property is disabled by default.

Description
Table 7-120. Configuration Properties Collected for Virtual Machine Objects

config|name Name Name
config|guestFullName Guest Fullname Guest OS full name configured by the

user.
config|hardware|numCpu Number of virtual CPUs Number of virtual CPUs
config|hardware|memoryKB Memory Memory
VMware, Inc. 1180

Table 7-120. Configuration Properties Collected for Virtual Machine Objects (continued)
config|hardware|thinEnabled Thin Provisioned Disk Indicates whether thin provisioning is

enabled
config|hardware|diskSpace Disk Space Disk Space
config|cpuAllocation|reservation Reservation CPU reservation
config|cpuAllocation|limit Limit CPU limit
config|cpuAllocation|shares|shares Shares CPU shares
config|memoryAllocation|reservation Reservation CPU reservation
config|memoryAllocation|limit Limit Limit
config|memoryAllocation|shares|shares Shares Memory shares
config|extraConfig|mem_hotadd Memory Hot Add Memory Hot Add Configuration
config|extraConfig|vcpu_hotadd VCPU Hot Add VCPU Hot Add Configuration
config|extraConfig|vcpu_hotremove VCPU Hot Remove VCPU Hot Remove Configuration
config|security|disable_autoinstall Disable tools auto install Disable tools auto install

(isolation.tools.autoInstall.disable) (isolation.tools.autoInstall.disable)
config|security|disable_console_copy Disable console copy operations Disable console copy operations

(isolation.tools.copy.disable) (isolation.tools.copy.disable)
config|security|disable_console_dnd Disable console drag and drop Disable console drag and drop
operations operations
(isolation.tools.dnd.disable) (isolation.tools.dnd.disable)
config|security| Enable console GUI operations Enable console GUI operations

enable_console_gui_options (isolation.tools.setGUIOptions.enab (isolation.tools.setGUIOptions.enable)
le)
config|security|disable_console_paste Disable console paste operations Disable console paste operations

(isolation.tools.paste.disable) (isolation.tools.paste.disable)
config|security| Disable virtual disk shrink Disable virtual disk shrink

disable_disk_shrinking_shrink (isolation.tools.diskShrink.disable) (isolation.tools.diskShrink.disable)
config|security| Disable virtual disk wiper Disable virtual disk wiper

disable_disk_shrinking_wiper (isolation.tools.diskWiper.disable) (isolation.tools.diskWiper.disable)
config|security|disable_hgfs Disable HGFS file transfers Disable HGFS file transfers

(isolation.tools.hgfsServerSet.disab (isolation.tools.hgfsServerSet.disable)
le)
config|security| Avoid using independent Avoid using independent

disable_independent_nonpersistent nonpersistent disks (scsiX:Y.mode) nonpersistent disks (scsiX:Y.mode)
config|security|enable_intervm_vmci Enable VM-to-VM communication Enable VM-to-VM communication

through VMCI (vmci0.unrestricted) through VMCI (vmci0.unrestricted)
config|security|enable_logging Enable VM logging (logging) Enable VM logging (logging)
config|security|disable_monitor_control Disable VM Monitor Control Disable VM Monitor Control

(isolation.monitor.control.disable) (isolation.monitor.control.disable)
VMware, Inc. 1181

config|security| Enable 3D features on Server and Enable 3D features on Server and

enable_non_essential_3D_features desktop virtual machines desktop virtual machines
(mks.enable3d) (mks.enable3d)
config|security| Disable unexposed features - Disable unexposed features -

disable_unexposed_features_autologon autologon autologon
(isolation.tools.ghi.autologon.disabl (isolation.tools.ghi.autologon.disable)
e)
config|security| Disable unexposed features - Disable unexposed features - biosbbs

disable_unexposed_features_biosbbs biosbbs (isolation.bios.bbs.disable) (isolation.bios.bbs.disable)

disable_unexposed_features_getcreds getcreds getcreds
(isolation.tools.getCreds.disable) (isolation.tools.getCreds.disable)

disable_unexposed_features_launchmenu launchmenu launchmenu
(isolation.tools.ghi.launchmenu.cha (isolation.tools.ghi.launchmenu.chang
nge) e)

disable_unexposed_features_memsfss memsfss memsfss
(isolation.tools.memSchedFakeSa (isolation.tools.memSchedFakeSampl
mpleStats.disable) eStats.disable)

disable_unexposed_features_protocolhan protocolhandler protocolhandler
dler (isolation.tools.ghi.protocolhandler. (isolation.tools.ghi.protocolhandler.inf
info.disable) o.disable)

disable_unexposed_features_shellaction shellaction shellaction
(isolation.ghi.host.shellAction.disab (isolation.ghi.host.shellAction.disable)
le)

disable_unexposed_features_toporequest toporequest toporequest
(isolation.tools.dispTopoRequest.di (isolation.tools.dispTopoRequest.disa
sable) ble)

disable_unexposed_features_trashfolderst trashfolderstate trashfolderstate
ate (isolation.tools.trashFolderState.dis (isolation.tools.trashFolderState.disabl
able) e)
config|security| Disable unexposed features - Disable unexposed features - trayicon

disable_unexposed_features_trayicon trayicon (isolation.tools.ghi.trayicon.disable)
(isolation.tools.ghi.trayicon.disable)
config|security| Disable unexposed features - unity Disable unexposed features - unity

disable_unexposed_features_unity (isolation.tools.unity.disable) (isolation.tools.unity.disable)
config|security| Disable unexposed features - Disable unexposed features - unity-

disable_unexposed_features_unity_interlo unity-interlock interlock
ck (isolation.tools.unityInterlockOpera (isolation.tools.unityInterlockOperatio
tion.disable) n.disable)
VMware, Inc. 1182


disable_unexposed_features_unity_taskba unity-taskbar taskbar
r (isolation.tools.unity.taskbar.disabl (isolation.tools.unity.taskbar.disable)
e)

disable_unexposed_features_unity_unitya unity-unityactive unityactive
ctive (isolation.tools.unityActive.disable) (isolation.tools.unityActive.disable)

disable_unexposed_features_unity_windo unity-windowcontents windowcontents
wcontents (isolation.tools.unity.windowConte (isolation.tools.unity.windowContents.
nts.disable) disable)

disable_unexposed_features_unitypush unitypush unitypush
(isolation.tools.unity.push.update.d (isolation.tools.unity.push.update.disa
isable) ble)

disable_unexposed_features_versionget versionget versionget
(isolation.tools.vmxDnDVersionGet (isolation.tools.vmxDnDVersionGet.dis
.disable) able)

disable_unexposed_features_versionset versionset versionset
(solation.tools.guestDnDVersionSe (solation.tools.guestDnDVersionSet.di
t.disable) sable)
config|security|disable_vix_messages Disable VIX messages from the Disable VIX messages from the VM
VM (isolation.tools.vixMessage.disable)
(isolation.tools.vixMessage.disable)
config|security|enable_vga_only_mode Disable all but VGA mode on Disable all but VGA mode on virtual
virtual machines (svga.vgaOnly) machines (svga.vgaOnly)
config|security|limit_console_connection Limit number of console Limit number of console connections

connections (RemoteDisplay.maxConnection)
(RemoteDisplay.maxConnection)
config|security|limit_log_number Limit number of log files Limit number of log files (log.keepOld)
(log.keepOld)
config|security|limit_log_size Limit log file size (log.rotateSize) Limit log file size (log.rotateSize)
config|security|limit_setinfo_size Limit VMX file size Limit VMX file size

(tools.setInfo.sizeLimit) (tools.setInfo.sizeLimit)
config|security|enable_console_VNC Enable access to VM console via Enable access to VM console via VNC
VNC protocol protocol (RemoteDisplay.vnc.enabled)
(RemoteDisplay.vnc.enabled)
config|security| Disable unauthorized removal, Disable unauthorized removal,

disable_device_interaction_connect connection of devices connection of devices
(isolation.device.connectable.disab (isolation.device.connectable.disable)
le)
VMware, Inc. 1183

config|security| Disable unauthorized modification Disable unauthorized modification of

disable_device_interaction_edit of devices devices (isolation.device.edit.disable)
(isolation.device.edit.disable)
config|security|enable_host_info Enable send host information to Enable send host information to

guests guests (tools.guestlib.enableHostInfo)
(tools.guestlib.enableHostInfo)
config|security|network_filter_enable Enable dvfilter network APIs Enable dvfilter network APIs

(ethernetX.filterY.name) (ethernetX.filterY.name)
config|security| VMsafe CPU/memory APIs - IP VMsafe CPU/memory APIs - IP

vmsafe_cpumem_agentaddress address (vmsafe.agentAddress) address (vmsafe.agentAddress)
config|security| VMsafe CPU/memory APIs - port VMsafe CPU/memory APIs - port

vmsafe_cpumem_agentport number (vmsafe.agentPort) number (vmsafe.agentPort)
config|security|vmsafe_cpumem_enable Enable VMsafe CPU/memory APIs Enable VMsafe CPU/memory APIs

(vmsafe.enable) (vmsafe.enable)
config|security|disconnect_devices_floppy Disconnect floppy drive Disconnect floppy drive
config|security|disconnect_devices_cd Disconnect CD-ROM Disconnect CD-ROM
config|security|disconnect_devices_usb Disconnect USB controller Disconnect USB controller
config|security| Disconnect parallel port Disconnect parallel port

disconnect_devices_parallel
config|security|disconnect_devices_serial Disconnect serial port Disconnect serial port
config|faultTolerant config|faultTolerant
Note Security properties not collected by default. They are collected only if the vSphere
Hardening Guide policy is applied to the objects, or if the vSphere Hardening Guide alerts are
manually enabled in the currently applied policy.
Table 7-121. Runtime Properties Collected for Virtual Machine Objects

runtime|memoryCap Memory Capacity Memory Capacity
Table 7-122. CPU Usage Properties Collected for Virtual Machine Objects
cpu|limit CPU limit CPU limit
cpu|reservation CPU reservation CPU reservation
cpu|speed CPU CPU Speed
cpu|cpuModel CPU Model CPU Model
VMware, Inc. 1184

Table 7-123. Memory Properties Collected for Virtual Machine Objects

mem|host_limit VM Limit Mem Machine Limit
mem|host_reservation Memory|VM Reservation(kb) This property is disabled by default.
Table 7-124. Network Properties Collected for Virtual Machine Objects

net|mac_address Mac Address Mac Address
net|ip_address IP Address IP Address
net|vnic_label Network:<ID>|Label This property is disabled by default.
net|nvp_vm_uuid Network I/O|NVP VM UUID This property is disabled by default.
net|vnic_type Network I/O|Virtual NIC Type This property is disabled by default.
net|ipv6_address Network|IPv6 Address This property is disabled by default.
net|ipv6_prefix_length Network|IPv6 Prefix Length This property is disabled by default.
net|default_gateway Network|Network I/O|Default Gateway This property is disabled by default.
net|subnet_mask Network|Subnet Mask This property is disabled by default.
Table 7-125. Summary Properties Collected for Virtual Machine Objects

summary|customTag|customTagValue Value Custom Tag Value
summary|tag vSphere Tag vSphere Tag Name
summary|parentCluster Parent Cluster Parent Cluster
summary|parentHost Parent Host Parent Host
summary|parentDatacenter Parent data center Parent data center
summary|parentVcenter Parent vCenter Parent vCenter
summary|guest|fullName Guest OS Full Name Guest OS Full Name as identified by VMware

tools.
summary|guest|ipAddress Guest OS IP Address Guest OS IP Address
summary|guest|toolsRunningStatus Tools Running Status Guest Tools Running Status
summary|guest|toolsVersionStatus2 Tools Version Status Guest Tools Version Status 2
summary|guest| vRealize Operations Agent An ID to identify a VM in Agent Adapter's

vrealize_operations_agent_id ID world.
summary|guest| vRealize Operations Euc An ID to identify a VM in Agent Adapter's

vrealize_operations_euc_agent_id Agent ID world.
summary|config|numEthernetCards Number of NICs Number of NICs
summary|config|isTemplate VM Template Indicates whether it is a VM Template.
summary|runtime|powerState Power State Power State
summary|runtime|connectionState Connection State Connection State
VMware, Inc. 1185

Table 7-125. Summary Properties Collected for Virtual Machine Objects (continued)
summary|config|appliance summary|config|appliance
summary|config|productName Summary|Configuration|
Product Name
Table 7-126. Virtual Disk Properties Collected for Virtual Machine Objects
virtualDisk|configuredGB Virtual Disk|Configured(GB)
virtualDisk|datastore Virtual Disk|Datastore
virtualDisk|fileName Virtual Disk|File Name This property is disabled by default.
virtualDisk|label Virtual Disk|Label
Table 7-127. Datastore Properties Collected for Virtual Machine Properties

datastore|maxObservedNumberRead Datastore I/O|Highest

Observed Number of Read
Requests
datastore|maxObservedNumberWrite Datastore I/O|Highest

Observed Number of Write
Requests
datastore|maxObservedOIO Datastore I/O|Highest

Observed Outstanding
Requests
datastore|maxObservedRead Datastore I/O|Highest

Observed Read Rate(kbps)
datastore|maxObservedWrite Datastore I/O|Highest

Observed Write Rate(kbps)
Datastore properties collected for virtual machine objects have been disabled in this version of
vRealize Operations Manager. This means that they do not collect data by default.
Host System Properties

vRealize Operations Manager collects configuration, hardware, runtime, CPU, network I/O, and
properties about summary use for host system objects.
Table 7-128. Configuration Properties Collected for Host System Objects

config|diskSpace Disk Space Disk Space
config|network|nnic Number of NICs Number of NICs
config|network|linkspeed Average Physical NIC Speed Average Physical NIC Speed
VMware, Inc. 1186

Table 7-128. Configuration Properties Collected for Host System Objects (continued)
config|network|dnsserver DNS Server List of DNS Servers
config|product|productLineId Product Line ID Product Line ID
config|product|apiVersion API Version API Version
config|storageDevice|plugStoreTopology| Total number of Path Total number of storage paths

numberofPath
config|storageDevice|multipathInfo| Total number of Active Path Total number of active storage paths
numberofActivePath
config|storageDevice|multipathInfo| Multipath Policy Multipath Policy

multipathPolicy
config|hyperThread|available Available Indicates whether hyperthreading is

supported by the server
config|hyperThread|active Active Indicates whether hyperthreading is

active
config|ntp|server NTP Servers NTP Servers
config|security|ntpServer NTP server NTP server
config|security|enable_ad_auth Enable active directory Enable active directory authentication

authentication
config|security|enable_chap_auth Enable mutual chap authentication Enable mutual chap authentication
config|security|enable_auth_proxy Enable authentication proxy Enable authentication proxy

(UserVars.ActiveDirectoryVerifyC (UserVars.ActiveDirectoryVerifyCAM
AMCertificate) Certificate)
config|security|syslog_host Remote log host Remote log host

(Syslog.global.logHost) (Syslog.global.logHost)
config|security|dcui_access Users who can override lock down Users who can override lock down
mode and access the DCUI mode and access the DCUI
(DCUI.Access) (DCUI.Access)
config|security|shell_interactive_timeout Shell interactive timeout Shell interactive timeout

(UserVars.ESXiShellInteractiveTime (UserVars.ESXiShellInteractiveTimeOu
Out) t)
config|security|shell_timeout Shell timeout Shell timeout

(UserVars.ESXiShellTimeOut) (UserVars.ESXiShellTimeOut)
config|security|dvfilter_bind_address Dvfilter bind ip address Dvfilter bind ip address

(Net.DVFilterBindIpAddress) (Net.DVFilterBindIpAddress)
config|security|syslog_dir Log directory Log directory (Syslog.global.logDir)

(Syslog.global.logDir)
config|security|firewallRule|allowedHosts Allowed hosts Allowed hosts in the firewall

configuration
config|security|service|isRunning Running Indicates whether a service is running

or not. Services are: Direct Console
UI, ESXi shell, SSH, or NTP Daemon.
config|security|service|ruleSet Ruleset Ruleset for each service.
VMware, Inc. 1187

Table 7-128. Configuration Properties Collected for Host System Objects (continued)
config|security|service|policy Policy Policy for each service.
config|security|tlsdisabledprotocols TLS Disabled Protocols TLS Disabled Protocols
Note Security properties not collected by default. They are collected only if the vSphere
Hardening Guide policy is applied to the objects, or if the vSphere Hardening Guide alerts are
manually enabled in the currently applied policy.
Table 7-129. Hardware Properties Collected for Host System Objects

hardware|memorySize Memory Size Memory Size
hardware|cpuInfo|numCpuCores Number of CPU Cores Number of CPU Cores
hardware|cpuInfo|hz CPU Speed per Core CPU Speed per Core
hardware|cpuInfo|numCpuPackages Number of CPU Packages Number of CPU Packages
hardware|cpuInfo| Active CPU Power Management Policy Active CPU Power Management Policy
powerManagementPolicy
hardware|cpuInfo| Power Management Technology Power Management Technology

powerManagementTechnology
hardware|cpuInfo|biosVersion BIOS Version BIOS Version
hardware|vendor Hardware|Vendor Indicates the hardware manufacturer
Table 7-130. Runtime Properties Collected for Host System Objects

runtime|connectionState Connection State Connection State
runtime|powerState Power State Power State
runtime|maintenanceState Maintenance State Maintenance State
runtime|memoryCap Memory Capacity Memory Capacity
Table 7-131. Configuration Manager Properties Collected for Host System Objects
configManager|memoryManager| Service Console Reserved Service console reserved memory

consoleReservationInfo|
serviceConsoleReserved
Table 7-132. CPU Usage Properties Collected for Host System Objects
cpu|speed CPU CPU Speed
cpu|cpuModel CPU Model CPU Model
VMware, Inc. 1188

Table 7-133. Network Properties Collected for Host System Objects

net|maxObservedKBps Highest Observed Throughput Highest Observed Throughput (KBps)
net|mgmt_address Management Address Management Address
net|ip_address IP Address IP Address
net|discoveryProtocol|cdp| Management IP Address Management IP Address

managementIpAddress
net|discoveryProtocol|cdp| System Name System Name

systemName
net|discoveryProtocol|cdp|portName Port Name Port Name
net|discoveryProtocol|cdp|vlan VLAN VLAN
net|discoveryProtocol|cdp|mtu MTU MTU
net|discoveryProtocol|cdp| Hardware Platform Hardware Platform

hardwarePlatform
net|discoveryProtocol|cdp| Software Version Software Version

softwareVersion
net|discoveryProtocol|lldp| Management IP Address Management IP Address

managementIpAddress
net|discoveryProtocol|lldp| System Name System Name

systemName
net|discoveryProtocol|lldp|portName Port Name Port Name
net|discoveryProtocol|lldp|vlan VLAN VLAN
Table 7-134. System Properties Collected for Host System Objects

sys|build Build number VMWare build number
sys|productString Product String VMWare product string
Table 7-135. Summary Properties Collected for Host System Objects

summary|version Version Version
summary|hostuuid Host UUID Host UUID
summary|evcMode Current EVC Mode Current EVC Mode
summary|parentCluster Parent Cluster Parent Cluster
summary|parentDatacenter Parent Datacenter Parent Datacenter
summary|parentVcenter Parent Vcenter Parent Vcenter
VMware, Inc. 1189

Table 7-136. Datastore Properties Collected for Host System Objects

datastore|maxObservedNumberRead Datastore I/O|Highest

Observed Number of Read
Requests
datastore|maxObservedNumberWrite Datastore I/O|Highest

Observed Number of Write
Requests
datastore|maxObservedOIO Datastore I/O|Highest

Observed Outstanding
Requests
datastore|maxObservedRead Datastore I/O|Highest

Observed Read Rate(kbps)
datastore|maxObservedWrite Datastore I/O|Highest

Observed Write Rate(kbps)
net|discoveryProtocol|cdp|timeToLive Network I/O|Discovery

Protocol|Cisco Discovery
Protocol|Time to Live
net|discoveryProtocol|lldp|timeToLive Network I/O|Discovery

Protocol|Link Layer
Discovery Protocol|Time to
Live
Datastore properties collected for host system objects have been disabled in this version of
vRealize Operations Manager. This means that they do not collect data by default.
Cluster Compute Resource Properties

vRealize Operations Manager collects configuration and summary properties for cluster compute
resource objects.
Table 7-137. Configuration Properties Collected for Cluster Compute Resource Objects
Table 7-138. Summary Properties Collected for Cluster Compute Resource Objects
summary|parentDatacenter Parent data center Parent data center
summary|parentVcenter Parent vCenter Parent vCenter
VMware, Inc. 1190

Table 7-139. DR, DAS, and DPM Configuration Properties Collected for Cluster Compute
Resource Objects
configuration|drsconfig|enabled Enabled Indicates whether DRS is enabled
configuration|drsconfig| Default DRS Behavior Default DRS Behavior

defaultVmBehavior
configuration|drsconfig|affinityRules Affinity Rules DRS Affinity Rules
configuration|dasconfig|enabled HA Enabled HA Enabled
configuration|dasconfig| Admission Control Enabled Admission Control Enabled

admissionControlEnabled
configuration|dpmconfiginfo|enabled DPM Enabled DPM Enabled
configuration|dpmconfiginfo| Default DPM Behavior Default DPM Behavior

defaultDpmBehavior
configuration|drsConfig| Cluster Configuration|DRS

pctIdleMBInMemDemand Configuration|Idle Consumed
Memory
configuration|drsConfig|targetBalance Cluster Configuration|DRS

Configuration|Tolerable
imbalance threshold
DRS properties are collected for disaster recovery. DAS properties are collected for high
availability service, formerly distributed availability service. DPM properties are collected for
distributed power management.
Resource Pool Properties

vRealize Operations Manager collects configuration, CPU, memory, and summary properties for
resource pool objects.
Table 7-140. Configuration Properties Collected for Resource Pool Objects

config|cpuAllocation|reservation Reservation CPU reservation
config|cpuAllocation|limit Limit CPU limit
config|cpuAllocation| Expandable Reservation CPU expandable reservation

expandableReservation
config|cpuAllocation|shares|shares Shares CPU shares
config|memoryAllocation|reservation Reservation Memory reservation
config|memoryAllocation|limit Limit Memory limit
config|memoryAllocation| Expandable Reservation Memory expandable reservation

expandableReservation
config|memoryAllocation|shares|shares Shares Memory shares
VMware, Inc. 1191

Table 7-141. CPU Usage Properties Collected for Resource Pool Objects
cpu|limit CPU Limit CPU Limit
cpu|reservation CPU reservation CPU Reservation
cpu|expandable_reservation CPU expandable reservation CPU Expandable Reservation
cpu|shares CPU Shares CPU Shares
cpu|corecount_provisioned Provisioned vCPU(s) Provisioned vCPU(s)
Table 7-142. Memory Properties Collected for Resource Pool Objects

mem|limit Memory limit Memory limit
mem|reservation Memory reservation Memory reservation
mem|expandable_reservation Memory expandable reservation Memory expandable reservation
mem|shares Memory Shares Memory Shares
Table 7-143. Summary Properties Collected for Resource Pool Objects

Data Center Properties

vRealize Operations Manager collects configuration and summary properties for data center
objects.
Table 7-144. Configuration Properties Collected for Data Center Objects

Table 7-145. Summary Properties Collected for Data Center Objects

summary|parentVcenter Parent Vcenter Parent Vcenter
Storage Pod Properties

vRealize Operations Manager collects configuration and summary properties for storage pod
objects.
VMware, Inc. 1192

Table 7-146. Configuration Properties Collected for Storage Pod Objects

config|sdrsconfig| VM storage antiaffinity rules Storage Distributed Resource Scheduler

vmStorageAntiAffinityRules (SDRS) VM anti-affinity rules
config|sdrsconfig|vmdkAntiAffinityRules VMDK antiaffinity rules Storage Distributed Resource Scheduler

(SDRS) Virtual Machine Disk (VMDK) anti-
affinity rules
VMware Distributed Virtual Switch Properties

vRealize Operations Manager collects configuration and summary properties for VMware
distributed virtual switch objects.
Table 7-147. Configuration Properties Collected for VMware Distributed Virtual Switch Objects
Table 7-148. Capability Properties Collected for VMware Distributed Virtual Switch Objects
capability|nicTeamingPolicy NIC Teaming Policy NIC Teaming Policy
Distributed Virtual Port Group Properties

vRealize Operations Manager collects configuration and summary properties for distributed
virtual port group objects.
Table 7-149. Configuration Properties Collected for Distributed Virtual Port Group Objects
Table 7-150. Summary Properties Collected for Distributed Virtual Port Group Objects
summary|active_uplink_ports Active DV uplinks Active DV uplinks
Datastore Properties
vRealize Operations Manager collects configuration, summary, and properties about datastore
use for datastore objects.
Table 7-151. Configuration Properties Collected for Datastore Objects

VMware, Inc. 1193

Table 7-152. Summary Properties Collected for Datastore Objects

summary|diskCapacity Disk Capacity Disk Capacity
summary|isLocal Is Local Is local datastore
summary|accessible Datastore Accessible Datastore Accessible
summary|path Summary|Path
summary|scsiAdapterType Summary|SCSI Adapter Type This property is disabled by default.
Table 7-153. Datastore Properties Collected for Datastore Objects

datastore|hostcount Host Count Host Count
datastore|hostScsiDiskPartition Host SCSI Disk Partition Host SCSI Disk Partition
* datastore| Datastore I/O|Highest Observed Disabled

maxObservedNumberRead Number of Read Requests
* datastore| Datastore I/O|Highest Observed Disabled

maxObservedNumberWrite Number of Write Requests
* datastore|maxObservedOIO Datastore I/O|Highest Observed Disabled

Outstanding Requests
* datastore|maxObservedRead Datastore I/O|Highest Observed Read Disabled

Latency
* datastore| Datastore I/O|Highest Observed Read Disabled

maxObservedReadLatency Latency
* datastore|maxObservedWrite Datastore I/O|Highest Observed Write Disabled

Latency
* datastore| Datastore I/O|Highest Observed Write Disabled

maxObservedWriteLatency Latency
Datastore properties marked with an asterisk (*) have been disabled in this version of vRealize
Operations Manager. This means that they do not collect data by default.
Self-Monitoring Properties for vRealize Operations Manager

vRealize Operations Manager uses the vRealize Operations Manager adapter to collect properties
that monitor its own objects. These self-monitoring properties are useful for monitoring changes
within vRealize Operations Manager.
Analytics Properties
vRealize Operations Manager collects properties for the vRealize Operations Manager analytics
service.
VMware, Inc. 1194

Table 7-154. Properties Collected for Analytics Service Objects

HAEnabled HA Enabled Indicates HA is enabled with a value of 1,

disabled with a value of 0.
ControllerDBRole Role Indicates persistence service role for the

controller: 0 – Primary, 1 – Replica, 4 – Client..
ShardRedundancyLevel Shard redundancy level The target number of redundant copies for
Object data.
LocatorCount Locator Count The number of configured locators in the

system
ServersCount Servers Count The number of configured servers in the

system
Node Properties
vRealize Operations Manager collects properties for the vRealize Operations Manager node
objects.
Table 7-155. Configuration Properties Collected for Node Objects

config|numCpu Number of CPU Number of CPUs
config|numCoresPerCpu Number of cores per CPU Number of cores per CPU
config|coreFrequency Core Frequency Core Frequency
Table 7-156. Memory Properties Collected for Node Objects

mem|RAM System RAM System RAM
Table 7-157. Service Properties Collected for Node Objects

service|proc|pid Process ID Process ID
Remote Collector Properties

vRealize Operations Manager collects properties for the vRealize Operations Manager remote
collector objects.
Table 7-158. Configuration Properties Collected for Remote Collector Objects

config|numCpu Number of CPU Number of CPUs
config|numCoresPerCpu Number of cores per CPU Number of cores per CPU
config|coreFrequency Core Frequency Core Frequency
VMware, Inc. 1195

Table 7-159. Memory Properties Collected for Remote Collector Objects

mem|RAM System RAM System RAM
Table 7-160. Service Properties Collected for Remote Collector Objects

service|proc|pid Process ID Process ID
Properties for vSAN

vRealize Operations Manager displays object properties for vSAN.
Properties for vSAN Disk Groups

vRealize Operations Manager displays the following property for vSAN disk groups:
n vSAN Disk Groups: Configuration|vSAN Configuration
Properties for vSAN Cluster

The vRealize Operations Manager displays the following properties for vSAN cluster.
n Configuration|vSAN|Deduplication and Compression Enabled
n Configuration|vSAN|Preferred fault domain
n Configuration|vSAN|Stretched Cluster
n Configuration|vSAN|vSAN Configuration
n Configuration|vSAN|Encryption
Properties for vSAN Enabled Host

The vRealize Operations Manager displays the following property for vSAN enabled host.
n Configuration|vSAN Enabled
Properties for vSAN Cache Disk

vRealize Operations Manager displays the following properties for the vSAN cache disk.
Properties for vSAN include:
VMware, Inc. 1196

Component Metrics
Configuration n Configuration Properties|Name

n Configuration Properties|Size
n Configuration Properties|Vendor
n Configuration Properties|Type
n Configuration Properties|Queue Depth
SCSI SMART Statistics n SCSI SMART Statistics|Media Wearout Indicator Threshold

n SCSI SMART Statistics|Write Error Count Threshold
n SCSI SMART Statistics|Read Error Count Threshold
n SCSI SMART Statistics|Reallocated Sector Count Threshold
n SCSI SMART Statistics|Raw Read Error Rate Threshold
n SCSI SMART Statistics|Drive Temperature Threshold
n SCSI SMART Statistics|Drive Rated Max Temperature Threshold
n SCSI SMART Statistics|Write Sectors TOT Count Threshold
n SCSI SMART Statistics|Read Sectors TOT Count Threshold
n SCSI SMART Statistics|Initial Bad Block Count Threshold
Properties for vSAN Capacity Disk

vRealize Operations Manager displays the following properties for the vSAN capacity disk.
Properties for vSAN include:
Component Metrics
Configuration n Configuration Properties|Name

n Configuration Properties|Size
n Configuration Properties|Vendor
n Configuration Properties|Type
n Configuration Properties|Queue Depth
SCSI SMART Statistics n SCSI SMART Statistics|Media Wearout Indicator Threshold

n SCSI SMART Statistics|Write Error Count Threshold
n SCSI SMART Statistics|Read Error Count Threshold
n SCSI SMART Statistics|Reallocated Sector Count Threshold
n SCSI SMART Statistics|Raw Read Error Rate Threshold
n SCSI SMART Statistics|Drive Temperature Threshold
n SCSI SMART Statistics|Drive Rated Max Temperature Threshold
n SCSI SMART Statistics|Write Sectors TOT Count Threshold
n SCSI SMART Statistics|Read Sectors TOT Count Threshold
n SCSI SMART Statistics|Initial Bad Block Count Threshold
Properties for vRealize Automation

vRealize Operations Manager displays properties for vRealize Automation objects.
VMware, Inc. 1197

Some of the useful properties for virtual machine objects deployed through vRealize Automation
are as follows:
n vRealize Automation|Expense month to date: Expenses till date for the virtual machine
n vRealize Automation|Machine expiration date: Expiration date of the virtual machine.
n vRealize Automation|Machine destroy date: Destroy date of the virtual machine.
VMware, Inc. 1198

Vrealize Operations Manager 75 Help

Uploaded by

Copyright:

Available Formats

Vrealize Operations Manager 75 Help

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Vrealize Operations Manager 75 Help

Uploaded by

Copyright:

Available Formats

vRealize Operations

Manager 7.5 Help

VMware vRealize Operations Manager 7.5 Help 9

1 About VMware vRealize Operations Manager 10

Resize your Cluster by Adding Nodes 98

Defining Compliance Standards 428

View DRS Summary 775

5 Monitoring Objects in Your Managed Environment 778

6 Capacity Optimization for Your Managed Environment 907

Select VMs 930

7 Metric, Property, and Alert Definitions 942

Properties for vSAN 1196

This chapter includes the following topics:

Best Practices for Deploying vRealize Operations Manager

n Deploy analytics nodes in the same vSphere Cluster.

n Deploy analytics nodes on storage of the same type.

Management Packs and Adapters

Initial Considerations for Deploying vRealize Operations Manager

n High Availability (HA)

n Distributed Resource Scheduler (DRS)

Multiple Data Centers

It is recommended that latency between sites is less than 200ms.

A valid certificate signed by a trusted Certificate Authority, private, or public, is an important

Scaling Vertically by Adding Resources

Table 2-1. Analytics Nodes Deployment Sizes

Extra large 24 128 GB

Scaling Vertically -by Increasing Storage

You can increase storage independently of vCPU and Memory.

Scaling Horizontally (Adding nodes)

Table 2-2. Supported Remote Collector Sizes

Standard 6000 250

Large 32,000 2,000

High Availability Considerations

Clusters consist of a primary node, and primary replica node.

Adapter and Management Packs Considerations

n Management Pack for NSX for vSphere

n Management Pack for OpenStack

n Management Pack for Storage Devices

n Management Pack for Log Insight

Several hybrid adapters are available for vRealize Operations Manager.

n vRealize Operations for Horizon adapter

n vRealize Operations for Published Applications adapter

n Management Pack for vRealize Hyperic

End Point Operations Management Adapter

Remote Collectors Behind a Load Balancer for End Point Operations

AIM Collectors Group

Remote Collector Remote Collector Remote Collector

Hardware Requirements for Analytic Nodes and Remote Collectors

Table 2-3. Hardware Requirements for System Components

Medium analytic 8 vCPU 32 GB 2.0 Ghz minimum, 1875 IOPS

Large analytic node 16 vCPU 48 GB 2.0 Ghz minimum, 3750 IOPS

Table 2-3. Hardware Requirements for System Components (continued)

Standard remote 2 vCPU 4 GB 2.0 Ghz minimum, N/A

Large remote 4 vCPU 16 GB 2.0 Ghz minimum, N/A

Port Requirements for vRealize Operations Manager

Port Requirements for vRealize Operations Manager

Ports Information for vRealize Operations Manager

Small Deployment Profile for vRealize Operations Manager

Virtual Appliance Name