Splunk Search

Custom dynamic field extraction

Simon
Contributor

Dear fellow splunkers,

I've got some events where the automatic field extraction of Splunk doesn't work. The log format looks like:

[log@1588 value="RASLOG"][timestamp@1588 value="2012-12-14T08:41:12.718453"][msgid@1588 value="SEC-1193"][seqnum@1588 value="26555"][severity@1588 value="INFO"]

Is there a way to create dynamic field extractions in the form of:

[<key>@1588 value=<value>]

I'm aware that it's possible to create a field extraction for each of my fields by hand but I'm searching for a dynamic solution 🙂

Thanks
Simon

Tags (1)
0 Karma
1 Solution

Ayn
Legend

Sure.

In transforms.conf, define your extraction:

[mycustomextraction]
REGEX = \[([^@]+)@1588 value="([^"]+)"
FORMAT = $1::$2

Then refer to your extraction in props.conf

[mysourcetype]
REPORT-customextraction = mycustomextraction

View solution in original post

Ayn
Legend

Sure.

In transforms.conf, define your extraction:

[mycustomextraction]
REGEX = \[([^@]+)@1588 value="([^"]+)"
FORMAT = $1::$2

Then refer to your extraction in props.conf

[mysourcetype]
REPORT-customextraction = mycustomextraction

Simon
Contributor

Oh man, that's so ridiculous simple that I feel shamed now 😉 Thanks for that quick solution!

0 Karma
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!

(re)Introducing the Splunk Community Champions + 2026 – 2027 Splunk MVPs ...

This program exists as a channel to empower and recognize Splunk advocates and help supercharge initiatives to ...

Introducing the 2026 - 2027 SplunkTrust cohort!

The goal of the SplunkTrust™ membership has historically been to acknowledge and recognize those who go above ...

Pro Tips for .conf26: How to Prep Like a Splunk Veteran

There’s no shortage of incredible content lined up for .conf26 in Denver, from deep-dive technical sessions ...