This post is more than 5 years old
20 Posts
0
2078
February 8th, 2016 11:00
Formula Results Inconsistent using math.spatial.Sum
Greetings,
I am working on creating a custom report in Vipr SRM 3.7 that SUMs the
metric "name==Capacity" for each Mapped and Masked LUN on a VNX array
and shows that summed value along with the LUN Count in the Parent report. I am
using this formula to Sum the LUN Capacity metrics, "math.spatial.Sum" on the child node and using that value in my Parent Table.
It seems the formula is not always consistent in its sumation. Sometimes I see the correct value in the report and other times not, (i am checking it manual against an export of all Masked and Mapped LUN capacities).
Does anyone know why the formula values appear to be inconsistent?
I can provide the report definition if that would help.
Thanks.
Flo_csI
2 Intern
•
166 Posts
0
February 11th, 2016 03:00
Hello,
With 3.7 we added a couple of things to smooth collection issue :
1. To bubble up values from a node to an upper node we use MakeRange formula rather than Nop (in case of a collector stops for a long period of time we will use the latest known value)
2. We don't use the raw data but aggregates (it allows to align time-series data point and avoid not having a blank value in case we miss a polling cycle)
The discrepancies you noticed are probably caused by raw data not being aligned.
In attachment you will find a report which should suits your needs.
It is a simple report which you can improve. You will noticed that when you click on an array you will see a chart.
This is a tip we commonly use when I don't understand why the results are odd. Instead of a table we use a chart so we can see when it goes wrong.
Let me know if it works.
1 Attachment
Array Capacity mapped _ masked Template.xml
LCS2
20 Posts
0
February 11th, 2016 05:00
This report works and is consistent in reporting the capacity values.
Questions:
1.) I noticed on the util.MakeRange formula there are properties defined to the name=="Capacities" svclevel device part
dgraid arraytyp sgname dgstype poolname - what is the purpose to these?
2.) Does setting "Default Results" on a formula ensure that the value from that formula is used in the Value: Capacity
defined in the table?
3.) I thought LInks to other reports was frowned upon, "WWN Linker". Has that changed with 3.7?
Thank you!
Flo_csI
2 Intern
•
166 Posts
1
February 15th, 2016 01:00
1) Complex expansion allows you to switch from one data set to another (you start from a Virtual Machine & you end up to an Array). The properties you see are the ones of the dataset where you are. It allows to carry these properties in the upper node.
2) Actually Default Results is only used for Graph or Bar reports not table it says which formula should be used by default. It has influence here.
3) Not really, I engage you to use links (but don't modify them). WWN Linker is the standard LUN report.
LCS2
20 Posts
0
February 15th, 2016 03:00
Thank you, this is really good information.