Another question, do you need that number to be dynamic?
Or in simple terms, do you need your users to be able to apply filters on the dasboards that would remove some of the events and then get a new value that trepresnets the overlaps without the filtered events?
Assuming yes, then your best route in high level, would be to:
- Generate an Indicator widget. It doesn't realy matter which formula you set for it so you can keep it a static 1
- Create Python script that would be used as a Custom Code Transoformation (CCT) script:
- When you set a CCT for a widget, Sisense would essentialy execute that script on the server and execute it on the widget's original query result and then it returns the scripts output to the widget. You can pass the dasboard filter selection as addtional paramters to the script
- So the idea is that you would essentially write a CCT script that would build a simpel JAQL that would rertieve all the events ordered by their timestampe and then you would process each data point by their order only for the events that had happened within the followign 72 hours.
- I reccomend moving the date to be a numeric date in epoc seconds as it would signficantly improve your perofmance and simplify your script.
- Make sure to remember to apply the dashboard filters when you pull the initital data set that needs to be processed.
- Based on the numbers that you have provided, I believe that even for 10K records the CCT script won't take more then 30-40 seconds to load tops (if written properly).
I didn't find the official documents for the CCT but note that this is a fairly advacned topic in Sisense and you also need to ask your admin to enable that feature for your Sisense server:
Good luck and let me know how it goes (:
Ravid
Paldi Solutions - Gold Certiefied Sisense Parneter
