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!

Observability Unlocked: Kubernetes Monitoring with Splunk Observability Cloud

  Ready to master Kubernetes and cloud monitoring like the pros?Join Splunk’s Growth Engineering team for an ...

Wrapping Up Cybersecurity Awareness Month

October might be wrapping up, but for Splunk Education, cybersecurity awareness never goes out of season. ...

🌟 From Audit Chaos to Clarity: Welcoming Audit Trail v2

🗣 You Spoke, We Listened  Audit Trail v2 wasn’t written in isolation—it was shaped by your voices.  In ...