Splunk Search

How to edit my props.conf for a custom field extraction based on the source field?

hortonew
Builder

I'm having issues creating a custom field extraction based on the source field. Here's all the information.

inputs.conf - Heavy Forwarder

[monitor:///mnt/splunkLogShare/TS2/...]
disabled = 0
index = test
sourcetype = Support:TS2

props.conf - Search Head (metadata [props] export=system)

[Support:*]
EXTRACT-custom_extracted_field = /mnt/splunkLogShare/(TS1|TS2|TS3|TS4|TS5)/(?<custom_extracted_field>[^/]+)/.* in source

Directory structure - Heavy Forwarder

/mnt/splunkLogShare/TS2/300-222222/file1.txt
/mnt/splunkLogShare/TS2/300-222222/file2.txt
/mnt/splunkLogShare/TS2/300-222222/dir1/
/mnt/splunkLogShare/TS2/300-222222/dir1/file3.txt

Searching for the following returns nothing as custom_extracted_field doesn't exist

index=test custom_extracted_field=300-222222

Searching the following creates custom_extracted_field without issue

index=test source=\*300-222222\* | rex field=source "/mnt/splunkLogShare/(TS1|TS2|TS3|TS4|TS5)/(?[^/]+)/.*"

No automatic field extraction is happening. Thoughts?

0 Karma
1 Solution

dshpritz
SplunkTrust
SplunkTrust

Worked with hortonew via IRC. Looks like it was just a bad props spec 🙂

Edit: You still cannot do wildcards like * for sourcetype specs in props 😞

View solution in original post

dshpritz
SplunkTrust
SplunkTrust

Worked with hortonew via IRC. Looks like it was just a bad props spec 🙂

Edit: You still cannot do wildcards like * for sourcetype specs in props 😞

hortonew
Builder

Seems you can't add a sourcetype spec with a wildcard. Added each sourcetype individually and it started working. e.g.:

[Support:TS1]
EXTRACT-...
[Support:TS2]
EXTRACT-...

0 Karma
Get Updates on the Splunk Community!

Stay Connected: Your Guide to May Tech Talks, Office Hours, and Webinars!

Take a look below to explore our upcoming Community Office Hours, Tech Talks, and Webinars this month. This ...

They're back! Join the SplunkTrust and MVP at .conf24

With our highly anticipated annual conference, .conf, comes the fez-wearers you can trust! The SplunkTrust, as ...

Enterprise Security Content Update (ESCU) | New Releases

Last month, the Splunk Threat Research Team had two releases of new security content via the Enterprise ...