Splunk Search

Why is extracted field formatted incorrectly?

yk010123
Path Finder

I have the following log that Splunk is not recognizing well :

msg=id=123342521352 operation=write

 

How can I write a query so that ID is parsed by itself?

The goal is to be able to build a table like :

id operation
123342521352 write

 

Unfortunately, when I tried

table id operation

The id is always empty as it does not seem to be parsed correctly

Labels (2)
Tags (2)
0 Karma
1 Solution

yuanliu
SplunkTrust
SplunkTrust

If you look at events, you'll find the field msg with "id" as value.  In SPL, you can use rex to extract id as a field, e.g.,

| rex "msg=id=(?<id>\d+)"

View solution in original post

yuanliu
SplunkTrust
SplunkTrust

If you look at events, you'll find the field msg with "id" as value.  In SPL, you can use rex to extract id as a field, e.g.,

| rex "msg=id=(?<id>\d+)"
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!

Why Splunk Customers Should Attend Cisco Live 2026 Las Vegas

Why Splunk Customers Should Attend Cisco Live 2026 Las Vegas     Cisco Live 2026 is almost here, and this ...

What Is the Name of the USB Key Inserted by Bob Smith? (BOTS Hint, Not the Answer)

Hello Splunkers,   So you searched, “what is the name of the usb key inserted by bob smith?”  Not gonna lie… ...

Automating Threat Operations and Threat Hunting with Recorded Future

    Automating Threat Operations and Threat Hunting with Recorded Future June 29, 2026 | Register   Is your ...