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!

Build Scalable Security While Moving to Cloud - Guide From Clayton Homes

 Clayton Homes faced the increased challenge of strengthening their security posture as they went through ...

Mission Control | Explore the latest release of Splunk Mission Control (2.3)

We’re happy to announce the release of Mission Control 2.3 which includes several new and exciting features ...

Cloud Platform | Migrating your Splunk Cloud deployment to Python 3.7

Python 2.7, the last release of Python 2, reached End of Life back on January 1, 2020. As part of our larger ...