topic Props/transforms for stashed data in Knowledge Management

Props/transforms for stashed data

Simon — Tue, 06 Aug 2013 07:57:34 GMT

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

Re: Props/transforms for stashed data

martin_mueller — Tue, 06 Aug 2013 08:57:45 GMT

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

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

Re: Props/transforms for stashed data

Simon — Tue, 06 Aug 2013 14:37:36 GMT

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

Thx
Simon