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!

Index This | I am a number, but when you add ‘G’ to me, I go away. What number am I?

March 2024 Edition Hayyy Splunk Education Enthusiasts and the Eternally Curious!  We’re back with another ...

What’s New in Splunk App for PCI Compliance 5.3.1?

The Splunk App for PCI Compliance allows customers to extend the power of their existing Splunk solution with ...

Extending Observability Content to Splunk Cloud

Register to join us !   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to ...