Splunk Search

how to extract fields from json format event?

nehamvinchankar
Path Finder

Hi all, i want to extract fields from event which is in json format

INFO [processor: anchsdgeiskgcbc/5; event: 1-57d28402-9058-11ee-83b7-021a6f9d1f1c] : DETAILS: [
{
"ERROR_MESSAGE": "\nError: abchdvshsuaajs.\n",
"NUMBER": "123r57",
"DB_TIMESTAMP": "2023-11-30"
},
{
"ERROR_MESSAGE": "\nError: ehwegagsuabajehss.\n",
"NUMBER": "63638w82u",
"DB_TIMESTAMP": "2023-11-30"
},

and similarly we have these error data in one event

Fields to be extracted -
ERROR_MESSAGE
NUMBER
DB_TIMESTAMP




Labels (1)
0 Karma

ITWhisperer
SplunkTrust
SplunkTrust

Given that this doesn't appear to be wholly correct JSON, you could start with something like this

| rex "DETAILS: (?<details>\[.*\])"
| spath input=details 
0 Karma

nehamvinchankar
Path Finder

no this is not working

 

0 Karma

ITWhisperer
SplunkTrust
SplunkTrust

What results do you get then?

0 Karma

nehamvinchankar
Path Finder

nehamvinchankar_0-1701833361480.png

details field is blank

0 Karma

ITWhisperer
SplunkTrust
SplunkTrust

Try this

| rex "(?ms)DETAILS: (?<details>\[.*\])"
| spath input=details 
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!

Persistent Queue at TcpOut — One of Splunk's Most Practical Features

Splunk introduced persistent queueing at the tcpout layer as one of the most practical resilience features in ...

Skip the Awkward Silence: Have a .conf-ersation at .conf26

Picture this. You arrive at .conf26 already having your socializing and networking plans mapped out. No ...

Rethinking Zero Trust: From Product Purchases to Logical Control Evidence

Implementing Zero Trust (ZT) across complex environments often falters at the very beginning due to a ...