Hi all
One of the vROps metrics is %ready at the VM layer, which is fine, now in alerts or reports I really want a % Ready that reflects the %Ready divided by how many CPUs the VMs has... so I can say generate an alert if it goes beyond 5% overall.. So I created a super metric as:
sum(${this, attribute=cpu|readyPct})/sum(${this, attribute=config|hardware|num_Cpu})
Which does seem to produce some results... but they don't seem to be what im after... some examples below...
This view has VM, CPU ready, Configured CPUs, and 3 Super metric variables (the same one) just Last, Average and Max... over the last hour so I can see if theres any differences... same at 5 min intervals.
Taking VM1 as an example id have expected the supermetric to be around 6.397%... but its not... any ideas of why bnot or am I misunderstanding something here?
Name | CPU|Ready (%) | Configuration|Hardware|Number of virtual CPUs | SM-VM Ready % (Last) | SM-VM Ready % (Average) | SM-VM Ready % (Max) |
VM1 | 24.588 | 4 | 12.228 | 12.301 | 12.301 |
VM2 | 24.068 | 4 | 12.137 | 12.029 | 12.029 |
VM3 | 22.588 | 4 | 12.261 | 11.219 | 11.219 |
VM4 | 22.244 | 4 | 11.056 | 11.159 | 11.159 |
VM5 | 22.227 | 4 | 10.951 | 11.335 | 11.335 |
VM6 | 21.758 | 4 | 11.214 | 10.844 | 10.844 |
VM7 | 21.402 | 4 | 10.833 | 10.7 | 10.7 |
VM8 | 20.737 | 4 | 11.774 | 10.262 | 10.262 |
VM9 | 20.695 | 4 | 9.816 | 10.394 | 10.394 |
VM10 | 20.41 | 4 | 11.04 | 10.095 | 10.095 |
VM11 | 20.3 | 4 | 11.21 | 10.099 | 10.099 |
VM12 | 20.264 | 4 | 10.75 | 10.151 | 10.151 |
VM13 | 19.986 | 4 | 9.913 | 9.987 | 9.987 |
VM14 | 18.953 | 4 | 10.006 | 9.517 | 9.517 |
VM15 | 18.731 | 4 | 7.864 | 9.498 | 9.498 |
VM16 | 17.907 | 4 | 10.175 | 8.903 | 8.903 |
VM17 | 17.722 | 4 | 9.22 | 8.786 | 8.786 |
VM18 | 14.646 | 4 | 8.054 | 7.246 | 7.246 |
VM19 | 14.142 | 2 | 14.093 | 14.149 | 14.149 |
VM20 | 14.114 | 2 | 14.479 | 14.142 | 14.142 |
VM21 | 14.081 | 2 | 14.067 | 14.082 | 14.082 |
VM22 | 14.058 | 2 | 14.427 | 14.075 | 14.075 |
VM23 | 14.031 | 2 | 13.557 | 14.043 | 14.043 |
VM24 | 14.021 | 2 | 13.873 | 14.046 | 14.046 |
VM25 | 13.994 | 2 | 14.392 | 14.013 | 14.013 |
VM26 | 13.935 | 2 | 14.312 | 13.956 | 13.956 |
VM27 | 13.925 | 2 | 13.95 | 13.946 | 13.946 |
VM28 | 13.906 | 2 | 13.624 | 13.956 | 13.956 |
VM29 | 13.881 | 2 | 13.771 | 13.921 | 13.921 |
VM30 | 13.83 | 2 | 13.85 | 13.843 | 13.843 |
VM31 | 5.487 | 4 | 2.823 | 2.738 | 2.738 |
VM32 | 4.25 | 1 | 0.359 | 8.423 | 8.423 |
VM33 | 3.83 | 4 | 1.911 | 1.91 | 1.91 |
VM34 | 3.819 | 8 | 1.124 | 0.957 | 0.957 |
VM35 | 3.617 | 8 | 1.055 | 0.906 | 0.906 |
VM36 | 3.368 | 8 | 0.741 | 0.851 | 0.851 |
VM37 | 3.359 | 12 | 0.566 | 0.561 | 0.561 |
VM38 | 3.004 | 4 | 1.341 | 1.523 | 1.523 |
VM39 | 2.924 | 8 | 0.723 | 0.731 | 0.731 |
VM40 | 2.669 | 4 | 1.511 | 1.325 | 1.325 |
VM41 | 2.629 | 8 | 0.607 | 0.661 | 0.661 |
VM42 | 2.46 | 4 | 1.52 | 1.235 | 1.235 |
VM43 | 2.326 | 4 | 1.124 | 1.171 | 1.171 |
VM44 | 2.254 | 8 | 0.567 | 0.567 | 0.567 |
VM45 | 2.128 | 8 | 0.539 | 0.533 | 0.533 |
VM46 | 2.12 | 4 | 0.738 | 1.09 | 1.09 |
VM47 | 2.06 | 8 | 0.533 | 0.516 | 0.516 |
VM48 | 2.031 | 4 | 1.049 | 1.028 | 1.028 |
VM49 | 2.017 | 4 | 0.638 | 1.044 | 1.044 |
VM50 | 1.983 | 4 | 1.066 | 0.987 | 0.987 |
VM51 | 1.929 | 4 | 0.981 | 0.967 | 0.967 |
VM52 | 1.897 | 2 | 2.021 | 1.891 | 1.891 |
VM53 | 1.882 | 4 | 0.931 | 0.94 | 0.94 |
VM54 | 1.864 | 4 | 1.022 | 0.921 | 0.921 |
VM55 | 1.828 | 4 | 0.939 | 0.909 | 0.909 |
VM56 | 1.82 | 4 | 0.924 | 0.912 | 0.912 |
VM57 | 1.761 | 4 | 0.719 | 0.9 | 0.9 |
VM58 | 1.743 | 4 | 0.755 | 0.888 | 0.888 |
VM59 | 1.585 | 4 | 1.001 | 0.771 | 0.771 |
VM60 | 1.582 | 4 | 0.522 | 0.811 | 0.811 |
VM61 | 1.579 | 4 | 0.752 | 0.797 | 0.797 |
VM62 | 1.517 | 8 | 0.368 | 0.379 | 0.379 |
Raised a SR with VMware...
${this, metric=cpu|readyPct}/${this,metric=config|hardware|num_Cpu}
this seems to work better, still testing it but looks good so far.
Raised a SR with VMware...
${this, metric=cpu|readyPct}/${this,metric=config|hardware|num_Cpu}
this seems to work better, still testing it but looks good so far.
Hi John,
I understand when reading your post that you use supermetric to calculate CPU Ready % average over the last hour. Am I correct?
I'm just starting using vRops and I'm searching to obtain a similar supermetric to calculate datastore average latency over the last hour,
Please can you help me and share your supermetric command?
Many thanks in advance,
Regards,
Yann,
This is the SM I've used for years... Works like a charm. Applies to the VM....
${this, metric=cpu|readyPct}/${this, metric=cpu|corecount_provisioned}