Getting Data In

Timestamp and line not properly break

antonyhan
Path Finder

I have this inputs.conf

[ServerLogs]
SHOULD_LINEMERGE = true
TRUNCATE = 0
BREAK_ONLY_BEFORE = ^\d{6}\s+\d{2}\:\d{2}\:\d{2}\:\d{3}\s+
TIME_PREFIX = ^
MAX_TIMESTAMP_LOOKAHEAD = 20
TIME_FORMAT =%m%d%y %H:%M:%S:%3N
BREAK_ONLY_BEFORE_DATE = true

and piece of my log looks like:

        <imagePath>C:\Fiserv\TCAP\bin\..\data\images\20160714222778400413_20160714141254232.img</imagePath>
      </imageObject>
      <itemUserFields />
      <cpcsData />


071216 09:36:03:364 4524/6.4.2.10/2 INFO  CCaptureApiServerApp::InitInstance(): before requestProcessor.DoModal() 

Second piece of log was recognized correctly with property time format. however for the first piece, the line was also broken before, and a time was recognized from "20160714141254232", which I am confused that that's not the time format I defined.

Anyone can shed some light here?

0 Karma
1 Solution

twinspop
Influencer

You've got 2 break definitions. Which is odd. Also, I've had much better luck using LINE_BREAKER vs BREAK_ONLY_BEFORE for some reason.

[ServerLogs]
LINE_BREAKER = ([\r\n]+)\d{6}\s+\d{2}\:\d{2}\:\d{2}\:\d{3}\s+
SHOULD_LINEMERGE = false
TRUNCATE = 0
MAX_TIMESTAMP_LOOKAHEAD = 20
TIME_FORMAT =%m%d%y %H:%M:%S:%3N
TIME_PREFIX = ^

View solution in original post

0 Karma

twinspop
Influencer

You've got 2 break definitions. Which is odd. Also, I've had much better luck using LINE_BREAKER vs BREAK_ONLY_BEFORE for some reason.

[ServerLogs]
LINE_BREAKER = ([\r\n]+)\d{6}\s+\d{2}\:\d{2}\:\d{2}\:\d{3}\s+
SHOULD_LINEMERGE = false
TRUNCATE = 0
MAX_TIMESTAMP_LOOKAHEAD = 20
TIME_FORMAT =%m%d%y %H:%M:%S:%3N
TIME_PREFIX = ^
0 Karma

antonyhan
Path Finder

Thanks twinspop. it turns out a file permission problem on the servers and your setting works.

0 Karma

antonyhan
Path Finder

Tried and didn't work.
So weird....

0 Karma
Get Updates on the Splunk Community!

App Platform's 2025 Year in Review: A Year of Innovation, Growth, and Community

As we step into 2026, it’s the perfect moment to reflect on what an extraordinary year 2025 was for the Splunk ...

Operationalizing Entity Risk Score with Enterprise Security 8.3+

Overview Enterprise Security 8.3 introduces a powerful new feature called “Entity Risk Scoring” (ERS) for ...

Unlock Database Monitoring with Splunk Observability Cloud

  In today’s fast-paced digital landscape, even minor database slowdowns can disrupt user experiences and ...