Knowledge Management

Props/transforms for stashed data

Simon
Contributor

Hi

There are multiple searches generating different stashed data with different markers, sometimes written to different indexes using "collect". We'd like to use props/transforms e.g. for automatic lookups or field extractions.
Unfortunately, the fields host, source and sourcetype aren't specific enough any more, they have the same values for all the populating searches.
Can we somehow set the sourcetype to a predefined value already at collect time? What are the other options, expect doing everything "manually" in the search?

Thanks
Simon

0 Karma
1 Solution

martin_mueller
SplunkTrust
SplunkTrust

You can do something like this: http://splunk-base.splunk.com/answers/88926/modify-_raw-collect-into-second-index-how-to-best-retain...

Be warned though, writing a sourcetype other than stash into an index should make the entire index count against your license.

View solution in original post

martin_mueller
SplunkTrust
SplunkTrust

You can do something like this: http://splunk-base.splunk.com/answers/88926/modify-_raw-collect-into-second-index-how-to-best-retain...

Be warned though, writing a sourcetype other than stash into an index should make the entire index count against your license.

Simon
Contributor

Thanks, that's what I've searched for. I'm currently not worried about license volume.

Thx
Simon

0 Karma
Get Updates on the Splunk Community!

Fall Into Learning with New Splunk Education Courses

Every month, Splunk Education releases new courses to help you branch out, strengthen your data science roots, ...

Super Optimize your Splunk Stats Searches: Unlocking the Power of tstats, TERM, and ...

By Martin Hettervik, Senior Consultant and Team Leader at Accelerate at Iver, Splunk MVPThe stats command is ...

How Splunk Observability Cloud Prevented a Major Payment Crisis in Minutes

Your bank's payment processing system is humming along during a busy afternoon, handling millions in hourly ...