Getting Data In

Line break involving CRLF

nithin204
Explorer

Hi,

I have JSON msgs in my log which has Carriage Return Line Feed character at the end of each line and the next line.

It looks as follows..

Line 1: "Message 1......." [CRLF]
Line 2: [CRLF]
Line 3 : " message 2......"[ CRLF]
Line 4: [CRLF]
Line 5: " Message 3 .... " [ CRLF]

I've configured my props.conf as
[sourcetype]
SHOULD_LINEMERGE = false
LINE_BREAKER = [\r\n]+
KV_MODE= json
N0_BINARY_CHECK=1

If I view my logs from UI, few of my events are single lines and others are combination of two lines, three lines or even more. Can some one help me fix this. What is the regex we must use to match CRLF at the end of line and in the next line ( this line is empty)

Thanks

Tags (1)
0 Karma

jsie_splunk
Splunk Employee
Splunk Employee

Hi,

The LINE_BREAKER regex requires a capture group to tell Splunk what to discard. Have you tried this as your regular expression?

[sourcetype]
SHOULD_LINEMERGE = false
LINE_BREAKER = ([\r\n]+)

Regards

0 Karma

nithin204
Explorer

Yes jsie, I did add the capture group in my regex. It didn't work

0 Karma

jsie_splunk
Splunk Employee
Splunk Employee

Can you share a sanitized sample of the raw data? Either include it here within as a code element, or via pastebin (or similar).

0 Karma

nithin204
Explorer

1) ##SPlunkFileHeader## ************************* LF
2) {"name": *****Json msg***** "} Destination= ' < value of field from header> ' LF
3) CR LF
4) { "client-name":******* ,Json msg>******"} Destination = ' Value' LF
5) CR LF
.....

There is a LF after every line and the next line has CR LF

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 ...