Splunk Search

Is it possible to pass variables in props.conf with my current configuration?

ltrand
Contributor

I was wondering if it was possible to write a props.conf something similar to the following:

props:

[sourcetype = masterlog_*]
REPORT-extract-various-fields = masterlog_extractions_$1

and then have transforms like this:

[masterlog_extractions_SomeLog1]
Delims = "\t"
Fields = _time,id,src,dest,count,msg

[masterlog_extractions_SomeLog2]
Delims = "\t"
Fields = _time,sub_id,choice,variable,code,quantity

So the idea is that I don't have to write a props & transform for each sourcetype, that I could have one props point to the correct transform & have it just work? Ultimately this will go on the search head to define the fields and I would like to avoid index time extraction.

0 Karma

Runals
Motivator

So in your props do this

[(?::){0}masterlog_*]
REPORT-extract-various-fields = masterlog_extractions_SomeLog1, masterlog_extractions_SomeLog2
0 Karma

ltrand
Contributor

As an update, I've tried several methods to perform this and it does not look like it is possible. I've attempted calling it as a * and as a $1 and it is not feeding the events through the parser correctly. My next step will be to put splunk into a debug logging mode so that I can see where exactly it hits, but I need to stand up a test search head so I don't have actual users & logs from the other search apps.

0 Karma
Get Updates on the Splunk Community!

More Ways To Control Your Costs With Archived Metrics | Register for Tech Talk

Tuesday, May 14, 2024  |  11AM PT / 2PM ET Register to Attend Join us for this Tech Talk and learn how to ...

.conf24 | Personalize your .conf experience with Learning Paths!

Personalize your .conf24 Experience Learning paths allow you to level up your skill sets and dive deeper ...

Threat Hunting Unlocked: How to Uplevel Your Threat Hunting With the PEAK Framework ...

WATCH NOWAs AI starts tackling low level alerts, it's more critical than ever to uplevel your threat hunting ...