Workload memory vs memory usage on vm

[MustafaSadek]

Helo 

I see there is meteic (memory workload) is utilized in vrealize operation at the same time the memory usage is not utilized?

Is workload refer to the memory usage on the winodws operating system?

What is difference bwtween memory usage and workload ? Which one should i monitor if customer asked for memory usage on vm winodws ?

[MustafaSadek]

Any update folks?

[maksym007]

The best option to send customer info - is from the guest os level. 

His second question will be what is creating/causing such workload. 

[MustafaSadek]

You are right but the issue is that customer complained freeze at his vm . That metric workload was utilized at that time . So i wanted to know if memory worload has relationship . 

[maksym007]

Other VMs were affected too on that host at the same time? 

If only one VM was affected and the rest were OK so check only that particular VM

[MustafaSadek]

The others vms were ok. My question is what is that workload and why usage was not utilized while workload was nor 

[maksym007]

The workload is a vROps synthetic value that is derived using multiple raw metrics that, when combined together, give you a true indicator of how busy/utilized a resource is. Workload, as an object-wide indicator, is configurable using profiles. These profiles allow you to decide 'which' raw metrics to consider as part of the "workload" status. Whereas more specific workload indicators, such as VM>CPU>Workload is going to be more reliant upon an underlying formula that is NOT user configurable and defined within the Management Pack itself. Usage% will merely be a raw vCenter metric, calculated by the vCenter Server and merely represented within vROps.

The workload is a vROps synthetic value that is derived using multiple raw metrics that, when combined together, give you a true indicator of how busy/utilized a resource is. Workload, as an object-wide indicator, is configurable using profiles. These profiles allow you to decide 'which' raw metrics to consider as part of the "workload" status. Whereas more specific workload indicators, such as VM>CPU>Workload is going to be more reliant upon an underlying formula that is NOT user configurable and defined within the Management Pack itself. Usage% will merely be a raw vCenter metric, calculated by the vCenter Server and merely represented within vROps.

[maksym007]

The workload is a vROps synthetic value that is derived using multiple raw metrics that, when combined together, give you a true indicator of how busy/utilized a resource is. Workload, as an object-wide indicator, is configurable using profiles. These profiles allow you to decide 'which' raw metrics to consider as part of the "workload" status. Whereas more specific workload indicators, such as VM>CPU>Workload is going to be more reliant upon an underlying formula that is NOT user configurable and defined within the Management Pack itself. Usage% will merely be a raw vCenter metric, calculated by the vCenter Server and merely represented within vROps.