I have a base report that pulls together information from multiple events using stats command. I have called the report Completed Events. From this report I have created some other reports to do some summary analysis on those completed events. I have setup report acceleration on the different reports and Splunk properly identifies them as the same base query so puts the report under the same summary.
My question is if other reports are created or other search queries are run that use the same search query base as the Completed Events report will those also benefit from the report acceleration summary? I would like for other end users to be able to take the Completed Events report and open it up in the search and build their own summary stats that they want.
When you accelerate a search, you tell Splunk to create a secondary
tsidx index which speeds up searching. In order to make sure that other saved searches use this
tsidx, you should also accelerate them, also. This will not cause Splunk to do any extra work because it will only do the secondary indexing once, no matter how many times you accelerate different searches on the same data.
Here is another question with more details:
I am asking more about the internals of how Splunk works. When you say "In order to make sure..." that doesn't really answer my question. I don't want to have to tell all my end users that are using a certain report as a starting place (it is a report that summarizes multiple events into one but can be further summarized) to remember to accelerate their reports. I would rather just configure the summary report with acceleration and have inherent acceleration on any other report or adhoc search query to be accelerated. Is that possible? Is that how Splunk works?
It should work for everybody but if the acceleration is only configured on one search, if that search is deleted or unaccelerated, the acceleration is gone for all searches.