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

Celebrating the Winners of the ‘Splunk Build-a-thon’ Hackathon!

We are thrilled to announce the winners of the Splunk Build-a-thon, our first-ever hackathon dedicated to ...

Why You Should Register for Splunk University at .conf25

Level up before .conf25 even begins Splunk University is back in Boston, September 6–8, and it’s your chance ...

Building Splunk proficiency is a marathon, not a sprint

Building Splunk skills is a lot like training for a marathon. It’s about consistent progress, celebrating ...