I've had it set to 1 minute just to generate data constantly while I test. Ultimately, it will probably be around 4h time chunks which will also help with speed because we can dedup more events with each feed into the summary index. So yeah, our requirements are: Save data for a year (vs 3 months on the normal index) Make querying a year fast vs the full data on the normal index Have it be as up to date as possible (100% up to date if possible, hence 1 minute runs right now) Nice to have is self repairing like accelerated reports do What I'd really want is an accelerated report summary that also happens to stick around longer than the actual indexed data does. Because that would only hold specific data, be self repairing, be 100% accurate and be fast. That said, summary indexing is our only option as accelerated report data ages off with the index age off as I'm told. That stinks because I really liked the speed and self healing of accelerated reports. If we accelerate teh summary index we can help with speed, but we will never get the self healing and possibly drop data over time. What happens if we run a summary index feeding report every 4 hours but look back 48 hours? Is it smart enough to not replicate data already in the summary index or not?
... View more