Written in vROps 8.12, this super metric is designed to sum the VM Costs in a VM folder
vmfoldersupermetric.json
Super Metric to display the amount of % a datastore is overprovisioned. This super metric can be used in a view or heatmap to quickly identify datastores that are overprovisioned
Super Metric - DatastoreOverprovisioning.json
This super metric defines the number of Powered Off ESXi Hosts
powered_off_esxi_hosts.json
I had to create this super metric on the OS object such that I could compare it to the Processor Queue Length \r\nmetric discovered by Telegraf
VM vCPU Multiplier v3.json
Use this super metric and alert definition to fire an alert whenever a new VM is created
New-VM-Super-Metric-and-Alert-master.zip
Super Metric to display the amount of memory a cluster is overprovisioned in %. This super metric can be used in a view or heatmap to quickly identify clusters that are overprovisioned based on memory
Super Metric - Cluster Memory Overprovisioning.json
This sample includes two Super Metrics which are based on the VMware Fling "Virtual Machine Compute Optimizer" which provides a report of VMs with recommended CPU socket and core configuraiton based on the VM resource allocation for CPU and memory and the ESXi host configuration. To use these samples, import using Administration > Configuration > Super Metrics and assign to VM object types and then enable in policy (you can also use Super Metric preview if you prefer not to enable in policy). The sample uses two super metrics, one to calculate the optimal number of cores per socket and the other to calculate the optimal number of sockets
NUMA Optimization.json
Here are four Super Metrics giving us what we need
vm_vcpu_and_memory_supermetrics.json
The Monthly Compute Cluster Total Storage Cost. Summary of all Parent Datastore Cost #SuperMetrics #MIT #vRealizeOperationsManager #vROPS #vRealizeOpsSuperMetrics
supermetric.json
While Right sizing VMs , vRealize Operations can provide Recommended vCPU Increase or Recommended vCPU Reduction , but the customer will need to use this value to manually add to or subtract from the provisioned vCPU count to get the ���Actual Recommended vCPU��� To make it easier for the customers and to get this value within vRealize Operations itself , I used below logic to create a super metric to get the ���Actual Recommended Value��� If the value of Recommended vCPUs to add is equal to 0 , then Actual Recommended vCPU = Provisioned vCPUs ��� Recommended vCPUs to remove (as an Oversized VM ) , or else Actual Recommended vCPU = Provisioned vCPUs + Recommended vCPUs to add ( as an Undersized VM ) This works for vROps 7.x , vROps 8.0 and vROps 8.1.x #vRealizeOperationsManager #vRealizeOpsSuperMetrics #MIT #SuperMetrics #vROPS
Actual Recommended vCPU.json