Getting Data In

splitting multiple event and display data using table

sjothi1
New Member

I have splitted my mixed log which contains both text and json to table .
For reference I have queried it as a table as shown below:

alt text

and used the below query to extract the fields like splunkId,processId, processLogId

index=****source=****  | sort -time | fields _time _raw  
| eval data = replace(_raw,"}\n{","Processed SplunkLogger") | eval data = replace(data,"{"," ")     
| eval data = replace(data,"}"," ")  | eval data = split(data,"Processed SplunkLogger") 
| where like(data, "%levelIndicator='****'%") | mvexpand data  |  eval _raw=data | table splunkId,processId, processLogId

But it doesn't returns anything, Can anyone please help me out with it.

0 Karma

skalliger
Motivator

So, where to start.. First of all, you started with a | fields _time _raw. Those fields are always included and cannot be exluced. Later however, you want to table fields that are not available anymore (splunkdId, processId, processLogId).
Secondly, why do you have text and JSON both in the same sourcetype (it sounds like you do)? Why don't you split the events into different sourcetypes? If you're extracting JSON data, you won't need to access _raw anymore because JSON will extract fields for you.

Skalli

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!

Data Management Digest – August 2026

MichelleCorpora_1-1788182384472.png Welcome to the August 2026 edition of Data Management Digest! August was a ...

Your Feedback. Our Roadmap. Visit the PX Feedback Booth at .conf26

You use Splunk every day, come and help shape what's next.  Save Your Seat: Product-Focused Sessions at ...

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...