Splunk Search

Splunk data doesn't split correctly

zhoayang
Engager

Hi Splunk team, 

When I used Splunk to search the log data and found it didn't split correctly, It displayed as below:

zhoayang_0-1643354979552.png

The two data have been combined together, Can anyone has some suggestions do this situation? appreciate it.

Labels (1)
0 Karma

gcusello
SplunkTrust
SplunkTrust

Hi @zhoayang,

could you share some sample of your original logs (not the oned displayed in Splunk search)?

please one of the event correctly parsed and one of the event not correctly parsed.

Anyway, in Community you can find many examples of JSON parsing e.g. https://community.splunk.com/t5/Getting-Data-In/How-to-parse-JSON-log-data/m-p/121521.

Ciao.

Giuseppe

yuanliu
SplunkTrust
SplunkTrust

It looks like a problem with LINE_BREAKER in props.conf. (See Configure event line breaking.)  By default Splunk indexer assumes "([\r\n]+)", i.e., a new line, to be the separator of events.  But some logs seem to have jammed into a single line.  There is no universal regex to break non-hierarchical structures like JSON.  So, it is best to ask developers to break events neatly.  If developers can guarantee that the first field is always "namespace" as in illustrated examples, you can try ([\r\n]+|}{"namespace":).

There is a dedicated forum Getting Data In in which this type of issues are discussed.

Tags (2)
Get Updates on the Splunk Community!

Splunk Enterprise Security: Your Command Center for PCI DSS Compliance

Every security professional knows the drill. The PCI DSS audit is approaching, and suddenly everyone's asking ...

Developer Spotlight with Guilhem Marchand

From Splunk Engineer to Founder: The Journey Behind TrackMe    After spending over 12 years working full time ...

Cisco Catalyst Center Meets Splunk ITSI: From 'Payments Are Down' to Root Cause in ...

The Problem: When Networks and Services Don't Talk Payment systems fail at a retail location. Customers are ...