5.0
Table Of Contents
- VMware vCenter Operations Manager Advanced Getting Started Guide
- Contents
- VMware vCenter Operations Manager Advanced Getting Started Guide
- vCenter Operations Manager Features
- Preparing to Monitor a vCenter Operations Manager Virtual Environment
- Object Type Icons in the Inventory Pane
- Badge Concepts for vCenter Operations Manager Planning
- Major Badges in vCenter Operations Manager
- Working with Metrics and Charts on the All Metrics Tab
- Planning the vCenter Operations Manager Workflow
- Monitoring Day-to-Day Activity in vCenter Operations Manager
- Identify an Overall Health Issue
- Determine the Timeframe and Nature of a Health Issue
- Determine Whether the Environment Operates as Expected
- Identify the Source of Performance Degradation
- Identify Events that Occurred when an Object Experienced Performance Degradation
- Identify the Top Resource Consumers
- Determine the Extent of a Performance Degradation
- Determine When an Object Might Run Out of Resources
- Determine the Cause of a Problem with a Specific Object
- Address a Problem with a Specific Virtual Machine
- Address a Problem with a Specific Datastore
- Identify Objects with Stressed Capacity
- Identify Stressed Objects with vCenter Operations Manager
- Identify the Underlying Memory Resource Problem for Clusters and Hosts
- Identify the Underlying Memory Resource Problem for a Virtual Machine
- Determine the Percentage of Used and Remaining Capacity to Assess Current Needs
- Preparing Proactive Workflows in vCenter Operations Manager
- Planning and Analyzing Data for Capacity Risk
- Identify Clusters with the Space for Virtual Machines
- Identify the Source of Performance Degradation Through Heat Maps
- Identify Datastores with Space for Virtual Machines
- Identify Datastores with Wasted Space
- Identify the Virtual Machines with Resource Waste Across Datastores
- Identify the Host and Datastore with the Highest Latency
- Optimizing Data for Capacity
- Determine How Efficiently You Use the Virtual Infrastructure
- Identify the Consolidation Ratio Trend for a Datacenter or Cluster
- Determine Reclaimable Resources from Underused Objects
- Assess Virtual Machine Capacity Use
- Assess Virtual Machine Optimization Data
- Identify Powered-Off Virtual Machines to Optimize Data
- Identify Idle Virtual Machines to Optimize Capacity
- Identify Oversized Virtual Machines to Optimize Data
- Determine the Trend of Waste for a Virtual Machine
- Forecasting Data for Capacity Risk
- Create Capacity Scenarios for Virtual Machines With New Profiles
- Create Capacity Scenarios for Virtual Machines With Existing Profiles
- Create a Hardware Change Scenario
- Create a What-If Scenario to Remove Virtual Machines
- Combine the Results of What-If Scenarios
- Compare the Results of What-If Scenarios
- Delete a Scenario from the What-If Scenarios List
- Planning and Analyzing Data for Capacity Risk
- Planning vCenter Operations Manager Workflow with Alerts
- Customizing vCenter Operations Manager Configuration Settings
- Index
Table 1-1. Major Metric Concepts
Metric Description
Provisioned Amount of a resource that the user configures.
The provisioned metric might apply to the amount of
physical memory for a host or the number of vCPUs for a
virtual machine.
Usable Actual amount of a resource that the object can use.
The usable amount is less than or equal to the provisioned
amount. The difference between the provisioned amount
and usable amount stems from factors such as hardware
capacity and virtualization overhead. This overhead might
include the memory that an ESX host uses to run the host, to
support reservations for virtual machines, and to add a
buffer for high availability.
The usable metric does not apply to virtual machines.
Usage Amount of a resource that an object consumes.
The usage amount is less than or equal to the usable amount.
Demand Amount of a physical resource that the object might consume
without any existing constraints.
An object becomes constrained because of under-
provisioning or contention with other consumers of the
resource. A virtual machine might require 10GB of memory
but can only get 5GB because the virtual machine must share
resources with other virtual machines on the host.
When the demand amount is less than the usage amount, the
environment might have wasted resources. When the
demand amount is greater than the usage amount, the
environment might incur latency and exhibit decreased
performance.
Contention Effect of the difference between the amount of the resource
that the object requires and the amount of the resource that
the object gets.
This metric measures the effect of conflict for a resource
between consumers. Contention measures latency or the
amount of time it takes to gain access to a resource. This
measurement accounts for dropped packets for networking.
Limit Maximum amount that an object can obtain from a resource.
The limit sets the upper bound for CPU, memory, or disk I/O
resources that you allocate and configure in vCenter Server.
The usage amount is less than or equal to the limit amount.
The demand amount can be greater than the limit amount.
The limit amount is less than or equal to the provisioned
amount.
The default limit amount is unlimited.
Rules: Usage <= Limit
Demand can be greater than Limit .
Chapter 1 vCenter Operations Manager Features
VMware, Inc. 9