Knowledge Management

Cisco Firewall Datacube Summary Index

BP9906
Builder

Hello,
I could not find much documentation about this so thats why I'm posting here.
I wanted to find out more information about the Cisco Firewall datacube scheduled searches for summary indexing.

1) Whats its purpose?
2) How could I prove that it is causing the "stash" sourcetype to spike during the 6hr scheduled summary indexing? metrics.log shows a spike but not where its coming from. The dates/times correspond with the scheduler.log for this saved search.
3) What do I break if I shut it off?

Thank you!

Tags (2)
0 Karma

dart
Splunk Employee
Splunk Employee

It's a summary search used in the Splunk App for Cisco Security.

All summary searches will use the stash sourcetype. You could prove that it's this search by running a search for index=* sourcetype=stash | stats count by search_name which will tell you how many results are generated from each summary search. If you really need approx data size then this will give you it, but it will be slower index=* sourcetype=stash | stats count sum(eval(len(_raw))) as utf8_chars by search_name

You may break some views in the Splunk App for Cisco Security.

0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Vibe-coding, AI, and Splunkcraft: Highlights from the .conf26 Builder Bar

If you stopped by the Builder Bar at .conf26, thank you! This year, we brought ...

Thanks for the Memories: .conf26 Took Learning to New Heights

Thank you, Splunk Community, for making .conf26 in Denver one for the books. From packed Splunk University ...

Best Practices: Splunk auto adjust pipeline queue

When you enable autoAdjustQueue in Splunk, maxSize should be understood as the queue size Splunk starts with ...