When creating Super Metrics, I've had problems with what vROPS auto-populates when using the native selection tools (in red in the screenshot). It usually populates unnecessary info that prevent s the metric from calculating. For example, your post contains....
adaptertype=VMWARE, objecttype=HostSystem, attribute=hardware|memorySize, depth=1
adaptertype=VMWARE, objecttype=HostSystem, attribute=hardware|cpuInfo|numCpuPackages, depth=1
Try these instead....
this, metric=hardware|memorySize, depth=1
this, metric=hardware|cpuInfo|numCpuPackages, depth=1
This is an example of one of my super metrics (it calculates uptime in days for a VM). When I first tried to create it using the native selection tools, it auto-populated unnecessary info that prevented the metric from calculating.
Auto-populated version (doesn't work):
Modified version (works):
In super metrics Attributes are properties and most cant be used in super metrics.
When you select a host system it showed you two windows
The right is the properties/attributes and the left is metrics. Try and use the metrics.
I just want to clear up some miss info. Auto population does work and is needed in some insistence. To explain i will break it down First you need to understand how vrops object levels work. When you select an object there are three things you want specifically in super metrics
- To manipulate one or more metrics on the object you are selecting. In your case the Host
- To get stats on an object further up or down from the object you are selecting
- to manipulate a metric on the object you are selecting using a metric from a different object further up or down from the object you are selecting
So lets take the first one as this is the easiest Want you are wanting to do is that the memory in the host and decide it by the number of sockets this is simple as the host has both those metrics.
When creating the metric select the object you what ( hosts) then click the this button from the top next to operators then select the metric. What this is doing is telling the super metric that the metric will be based on the object i am selecting ( this object). This is not bound to the Host because if the metric is present on another object it will show data because you used the "This"
That is why for you the this option is a good fit.
The second one:
Now say you want to select a cluster and want to get the average disk commands per second that metric for all the VMs in the cluster is not present at the cluster level so you cant use the this value at the start that is where the other info is used.
The supre metric needs to know the location of the metric and where is is expected to be. That is why you need the adaptertype=VMWARE, objecttype=VirtualMachine, attribute=virtualDisk|commandsAveraged_average, part.
Looking at the below supermetric it is simply getting the average (avg function) of all the Vms on a cluster. The metric we are looking is 5 levels down from the cluster that is what the depth is for
Avg(${adaptertype=VMWARE, objecttype=VirtualMachine, attribute=virtualDisk|commandsAveraged_average, depth=5})
If you used the this in this SM it would not work because it would ignore the depth value as the this is looking for the metric that does not exist on the cluster
third one
This is one of my capacity SM.
All this is doing is geting the number of cores in a cluster and the taking away the number of cores in one host multiplying it by 7 and then takingaway the vCPUs assigned to all the VMs
((${this, metric=cpu|corecount_provisioned}-(${this,metric=cpu|corecount_provisioned}/${this, metric=summary|number_running_hosts}))*7)-sum(${adaptertype=VMWARE, objecttype=VirtualMachine, attribute=config|hardware|num_Cpu, depth=2})
Notice the VMs part is not using the this because i needed to go down 2 levels from the cluster to the VM and it is using an attribute that is why i said most dont work as there are some that do
Apologises this went on for so long ( i could go on for longer but wont) and i hope it helps
what is you new metric.
Also a good tip. After you create your new metric, below the super metric screen there is a box
Make sure to specify the object the SM is for and when you go into the policy enable the SM for that object only and not the all objects one. This will cut down the processing needed during a collection cycle as vrops will try to work out the metric on all objects even if it does not work