Hello,
Don't include the time any where while doing the summary. When you start aggregating data the search automatically becomes faster.We all know collect command will populate all the value but it has limitation where it take the local machine's name rather than the actual host. So do something like this.
Have some sample timing to have granularity of the summary
index=iis|bucket _time span=30m| stats count dc(cs_username) by cs_username
Create a saved search and schedule it for a one time load to the target summary index. define the earliest and latest parameter according to your requirement. Avoid running it again and again to have duplicate entries.
with the above you can preserve internal event timing and you can use the time range picker because in the summary data you have the time trend.
in your Dashboard do the calculation. You should be fine now by user selecting time ranges
Thanks,
L
... View more