I am designing a panel using Number Display Viz, the search returns 13 rows, so the visualization must show 13 gauges. When the data load is large and the calculations are updated many times, then the visualization shows a threshold limit instead of the actual value.
I reviewed the visualization code and apparently the problem is that every time the calculation is updated the correct new value is sent to the method doDrawItem but the parameter doAFullRedraw is false, and hence the last value is not rendered on screen. As far I can tell, this looks like a bug in the visualization code.
Is there any way I can workaround this issue as a user of the visualization?
Hi @jmcr
Can you provide a sample of what your output data looks like so I can try and reproduce the problem? If the value is not being set appropriately, the usual reason is that the visualisation is trying to guess which column is which and it hasn't guessed correctly. Make sure your column/field is named "value" and it will be correctly set.
If doAFullRedraw is false, then the value will still be updated.
all the best
Hi @jmcr
Can you provide a sample of what your output data looks like so I can try and reproduce the problem? If the value is not being set appropriately, the usual reason is that the visualisation is trying to guess which column is which and it hasn't guessed correctly. Make sure your column/field is named "value" and it will be correctly set.
If doAFullRedraw is false, then the value will still be updated.
all the best
The search returns two columns: title and value; 13 rows. the visualization works correctly when loading small to moderate data ranges. When loading larger data ranges most of the gauges shows the value of one of the threshold limits.
ok sounds like you are using it correctly. However what do you mean by "larger data ranges"?
If you give me sample data that shows the problem I will be able to solve this much quicker.
Thanks for your interest in this issue, I prepared the data and directions in a file, I hope you can reproduce the bug, it is happening the same in a server and in my workstation, here is the link:
https://mcgsystems-my.sharepoint.com/:u:/g/personal/jr_mcg_dk/EUxqSGTqxx1CmJYL-O2yt0UB6rAe3ldjzm_iET...
ok yes. I have managed to recreate the problem and I can see what you are talking about. Thank you for data and the very detailed instructions. I will try get this fixed in the next day or two.
OK I have fixed the bug and pushed a new version (1.6.6) to Splunkbase. https://splunkbase.splunk.com/app/4537/
Thank you so much for reporting the bug and providing such a reproducible test case.