Splunk Search

Regex after delimited field extraction

tnkoehn
Path Finder

After a delimited field extraction in transforms.conf, I have a field called Gateway_Name that contains, for example, a value of "den01gsx01". I am trying to perform a regex on that field in props.conf to extract "den01". I was told I could to it this way but I do not even get a Site field extracted.

My props.conf looks like this:
[test]
REPORT-parsefields = test_parse
EXTRACT-site = (?<Site>^\w{5}) in Gateway_Name

My transforms.conf looks like this:
[test_parse]
DELIMS = "|"
FIELDS = "Event_Header", "Gateway_Name", "Accounting_ID", "Start_Date", "Start_Time", "Disconnect_Date", "Disconnect_Time", "Call_Duration", "Disconnect_Reason", "Service_Delivered", "Call_Direction", "Calling_Number", "Called_Number", "Billing_Number", "Route_Label"

Am I doing something wrong? Is there a better way?

Tags (1)
1 Solution

gkanapathy
Splunk Employee
Splunk Employee

REPORT runs after EXTRACT as sowings says, but you can quite simply get the effect you want by setting up your EXTRACT-site rule as a REPORT instead. REPORTS are processed in lexicographic order, so you can just do props.conf:

[test]
REPORT-parsefields = test_parse
REPORT-site = site

which will run REPORT-site/site after REPORT-parsefields/test_parse. Then in transforms.conf, you would add:

[site]
SOURCE_KEY = Gateway_Name
REGEX = (?<Site>^\w{5})

View solution in original post

gkanapathy
Splunk Employee
Splunk Employee

REPORT runs after EXTRACT as sowings says, but you can quite simply get the effect you want by setting up your EXTRACT-site rule as a REPORT instead. REPORTS are processed in lexicographic order, so you can just do props.conf:

[test]
REPORT-parsefields = test_parse
REPORT-site = site

which will run REPORT-site/site after REPORT-parsefields/test_parse. Then in transforms.conf, you would add:

[site]
SOURCE_KEY = Gateway_Name
REGEX = (?<Site>^\w{5})

tnkoehn
Path Finder

Worked great! Thx!

0 Karma

tnkoehn
Path Finder

Ah. That's pretty cool. I will try this on Monday. Thanks!

0 Karma

sowings
Splunk Employee
Splunk Employee

REPORT rules fire after EXTRACT rules; the Gateway_Name field won't exist to look for Site within it (EXTRACT-site). Consider a regular expression that's anchored on the delimiter.

You can try something like ([^|])*|){<N>} where N is the number of pipe-separated fields to skip. Looks like it should be 1.

Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Index This | What travels the world but is also stuck in place?

April 2026 Edition  Hayyy Splunk Education Enthusiasts and the Eternally Curious!   We’re back with this ...

Discover New Use Cases: Unlock Greater Value from Your Existing Splunk Data

Realizing the full potential of your Splunk investment requires more than just understanding current usage; it ...

Continue Your Journey: Join Session 2 of the Data Management and Federation Bootcamp ...

As data volumes continue to grow and environments become more distributed, managing and optimizing data ...