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+)"
Get Updates on the Splunk Community!

.conf24 | Registration Open!

Hello, hello! I come bearing good news: Registration for .conf24 is now open!   conf is Splunk’s rad annual ...

ICYMI - Check out the latest releases of Splunk Edge Processor

Splunk is pleased to announce the latest enhancements to Splunk Edge Processor.  HEC Receiver authorization ...

Introducing the 2024 SplunkTrust!

Hello, Splunk Community! We are beyond thrilled to announce our newest group of SplunkTrust members!  The ...