Getting Data In

Why are my JSON logs getting combined together in Splunk when using Bunyan?

bbarani
Engager

I am using Bunyan (https://www.npmjs.com/package/bunyan) as a logger for my node Java Script application and the log output is in the below format.

{"name":"Product list page","hostname":"plist","pid":24,"level":30,"msg":"Time:  1537221680271","time":"2018-09-17T22:01:20.271Z","v":0}
{"name":"Product list page","hostname":"plist","pid":24,"level":30,"msg":"Cache flag is set to===> true","time":"2018-09-17T22:01:20.272Z","v":0}
{"name":"Product list page","hostname":"plist","pid":24,"level":30,"msg":"Response status---> 200","time":"2018-09-17T22:01:20.272Z","v":0}

The data gets to logstash and then to Splunk. When I pull the data in to Splunk, I see them as below (grouped together)

10:01:25.505 PM 
{   [-] 
     @timestamp:     2018-08-17T22:01:25.505Z   
     LOGLEVEL:   UNKNOWN    
     kubernetes:    {   [+] 
    }   
     log:    {"name":"Product list page","hostname":"plist","pid":24,"level":30,"msg":"Time:  1537221680271","time":"2018-09-17T22:01:20.271Z","v":0}
{"name":"Product list page","hostname":"plist","pid":24,"level":30,"msg":"Cache flag is set to===> true","time":"2018-09-17T22:01:20.272Z","v":0}
{"name":"Product list page","hostname":"plist","pid":24,"level":30,"msg":"Response status---> 200","time":"2018-09-17T22:01:20.272Z","v":0}
tags:   [   [+] 
    ]   
     type:   ms_Log 
}

I want each log entry to appear separately in Splunk as below (even better if it can be formatted). Any inputs are appreciated?

 @timestamp:     2018-09-17T22:01:20.271Z
 LOGLEVEL:   INFO   
 kubernetes:    {   [+] 
}   
 log:   {"name":"Product list page","hostname":"plist","pid":24,"level":30,"msg":"Time:  1537221680271","time":"2018-09-17T22:01:20.271Z","v":0}
 tags:  [   [+] 
]   
 type:   Microservice_Log   



 @timestamp:     2018-09-17T22:01:20.272Z
 LOGLEVEL:   INFO   
 kubernetes:    {   [+] 
}   
 log:   {"name":"Product list page","hostname":"plist","pid":24,"level":30,"msg":"Cache flag is set to===> true","time":"2018-09-17T22:01:20.272Z","v":0}
 tags:  [   [+] 
]   
 type:   Microservice_Log   
Tags (2)
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 ...