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!

New Year. New Skills. New Course Releases from Splunk Education

A new year often inspires reflection—and reinvention. Whether your goals include strengthening your security ...

Splunk and TLS: It doesn't have to be too hard

Overview Creating a TLS cert for Splunk usage is pretty much standard openssl.  To make life better, use an ...

Faster Insights with AI, Streamlined Cloud-Native Operations, and More New Lantern ...

Splunk Lantern is a Splunk customer success center that provides practical guidance from Splunk experts on key ...