Getting Data In

Linebreaking not working as expected

dpatnam
Path Finder

I have a logfile whose events are not being broken up in Splunk. Here are the two separate events that are being shown together in Splunk console.

16:45:12,772 INFO> intro_response.pl:549 main:: - Batch AAAIE120809004119P03 successfully transferred to staging server.
16:45:12,774 INFO> intro_response.pl:568 main:: - account=act,program=932,admin=opsprg12,pgmssn=932-574,wfstate='BATCH_PUBLISHED',subject=Math,grade=11,error_code='',msg='Batch published to ePEN',batchnum=AAAIE120809004119P03,batch_count=5

Here's the configuration I have in props.conf for this logfile -

TIME_FORMAT = %H:%i:%s
SHOULD_LINEMERGE = false
BREAK_ONLY_BEFORE = \d+:\d+:\d+\,\d+
MAX_EVENTS = 2000

This configuration was working fine earlier but it stopped working for some reason this week. Any help on this would be greatly appreciated.

Tags (1)
0 Karma

kristian_kolb
Ultra Champion

Sorry, but what is %i in TIME_FORMAT? Don't you think that %M would be more correct? Or even:

TIME_FORMAT=%H:%M:%S,%3N

which would let you capture the milliseconds as well.

0 Karma

lguinn2
Legend

Since you have SHOULD_LINEMERGE=false, that implies that Splunk is not seeing your line break character properly. The BREAK_ONLY_BEFORE is not used when SHOULD_LINEMERGE=false. And MAX_EVENTS should be removed - MAX_EVENTS is the maximum number of lines per event - when you set SHOULD_LINEMERGE=false, that is irrelevant because an event can have only one line.

From Configure event linebreaking:

"Splunk determines event boundaries in two steps:

  1. Line breaking, which uses the LINE_BREAKER attribute's regex value to split the incoming stream of bytes into separate lines. By default, the LINE_BREAKER is any sequence of newlines and carriage returns (that is, ([\r\n]+))."

So this is the default:

LINE_BREAKER=[\r\n]+

Is it possible that your line is actually separated by different characters in the log? Or, try this explicitly

TIME_FORMAT = %H:%i:%s
SHOULD_LINEMERGE = false
LINE_BREAKER=[\r\n]+
0 Karma

kbecker
Communicator

Give this a shot...

TIME_PREFIX=^
TIME_FORMAT=%H:%M:%S
MAX_TIMESTAMP_LOOKAHEAD=8
BREAK_ONLY_BEFORE=^/d{2}/:/d{2}/:/d{2}

0 Karma

dpatnam
Path Finder

Thank you kbecker for your response. Just tried your suggestion. No luck though. I am still seeing separate events getting bundled up.

0 Karma
Get Updates on the Splunk Community!

.conf24 | Registration Open!

Hello, hello! I come bearing good news: Registration for .conf24 is now open!   conf is Splunk’s rad annual ...

ICYMI - Check out the latest releases of Splunk Edge Processor

Splunk is pleased to announce the latest enhancements to Splunk Edge Processor.  HEC Receiver authorization ...

Introducing the 2024 SplunkTrust!

Hello, Splunk Community! We are beyond thrilled to announce our newest group of SplunkTrust members!  The ...