eva.tuczai

Turbo Tip: Working with the Workload Chart

Blog Post created by eva.tuczai on Feb 14, 2015

The Workload Chart, available from navigating from the Workload tab, is a better way to look at the Health and Risks in your environment because the perspective is all about the VIRTUAL MACHINES or the DEMAND.

 

New in Operations Manger v5.1, you can now leverage this chart by narrowing down the perspective, to be able to change the axis on the chart.  Let's explore this in more detail.

Select the gear icon in the Current Workload Chart view This will take you to an "Edit Panel" view that will allow you to make the following changes:

1. Switch from Virtual Machines to Applications - Demand in VMTurbo comes from the workload of your Virtual Machines (default) or if you have the Application Control Module, the Applications which are the drivers of Demand on your infrastructure

2. Define your Axis - both the X & Y axis now have options to choose viewing where your workload is based on either the 1) Providers or 2) Commodities or Metrics

When Demand =  VMs the list will look like this:

Note that the Providers are what is giving resources to the Demand you selected.  Looking at the SUPPLY CHAIN view in VMTurbo you will see that the following relationships

 

DemandProvider
Application

Action Manager = a way to throttle Demand such as VDI Control, and other uses coming in future versions

Application = Application dependencies

Containers = for applications discovered on Containers

Virtual Machines = applications running on VMs (majority of scenarios)

Virtual Machines

Datastore = storage as a resource to VMs

Host = physical machines as a resource to Host

VPod = with the Network Control Module, a collection of VMs that have network transactions between them

Virtual Data Center = the resources allocated from a VDC or Resource Pool

 

You can also narrow down your perspective by Choosing Commodities - or values being monitored of the Provider:

 

DemandCommodities (monitored values of the Provider, sorted alphabetically)
Application

CPU

Mem

Heap, Threads (if the Provider is another Application)

VCPU

VMem

Virtual Machines

CPU Ready Queue by Number of VCPU

Ballooning

CPU

CPU Provisioned (CPU overcommitment)

CPUAllocation (from VDCs)

Flow (from the Network Control Module)

Flow Allocation (from the Network Control Module)

IO

IOPS

Latency (Storage)

Mem

Mem Provisioned (Memory overcommitment)

MemAllocation (from VDCs)

Net (Network Throughput)

Storage Amount

Storage Provisioned (Storage overcommitment in thin provisioning)

StorageAllocation (from VDCs)

Swapping

 

 

We can use these combinations to answer questions like "From an Application Perspective, where am I over or underutilized in VMem from my Virtual Machines?"  I adjust my axis and I can see this perspective on the same view from above:

 

 

Selecting the Demand in the upper right, I can see these risks and related actions:

I can switch to VM by Host and Mem to see more details

 

Going back to Applications as Demand, selecting a larger underutilized group, I can narrow my scope to see my Applications:

 

Enjoy experimenting and let us know how you use this!

 

Stay Green

Eva

Outcomes