Getting Data In

keep original sourcetype in summary index

grodaas
Explorer

I have multiple scheduled searches that run on large indexes and save the results to a summary index. There is no aggregation in the searches, only filtering. An example search would be something like "index=http google.com".

My problem is that when I save the search to the summary index the sourcetype is changed to "stash". I would like to keep the old sourcetype. Is there a way to tell Splunk to keep the original sourcetype?

0 Karma

jagadeeshm
Contributor

Summary Indexing by default change the sourcetype to stash. This is how splunk knows that data is already in splunk and your summary data will not be account for your additional license.
You can change the sourcetype, but remember the data will go against your license.
I guess one of the practices is to re-use the source field and set it to sourcetype for summary indexes.
For example :
index=xyz result=success | stats count .... | collect index=summary source=sourcetype

0 Karma

johandk
Path Finder

A workaround for this could be simply doing something like this

index=http google.com | eval orig_sourcetype=sourcetype

Tipmoose
Explorer

This does not work for me either. I posted a question about it yesterday. any use of the collect command throws your stuff into "stash". How convenient.

0 Karma

grodaas
Explorer

This does not seem to work for me. No matter what I do I can't get the Splunk to use the orgin sourcetype when reading from the summary index.

This is the command that is stored in Manager » Searches and reports » View Recent » "latest" :

index="pdns" | search "google" | eval orig_sourcetype=sourcetype | summaryindex spool=t uselb=t addtime=t index="testalarms" file="google_645699260.stash_new" name="google" marker=""

I have also tried updating props.conf:

[source::/opt/splunk/var/spool/splunk/*]
sourcetype = pdns2

or

[stash]
sourcetype = pdns2
priority = 101

0 Karma
.conf21 CFS Extended through 5/20!

Don't miss your chance
to share your Splunk
wisdom in-person or
virtually at .conf21!

Call for Speakers has
been extended through
Thursday, 5/20!