Getting Data In

Line breaking stops working from 12am - 1am everyday

king2jd
Path Finder

Hello,

We have a distributed environment with load balancing to 9 indexers. At 12am, our logs stop line breaking and start group multiple entries into one event and random log lines (no timestamps) for the next hour. Then it miraculously starts to work again. Never seen such a thing, thoughts?

alt text

0 Karma

woodcock
Esteemed Legend

The problem is that your timestamp is using <date><SingleSpace><SINGLE digit hour=0> for the midnight hour but it is using <DATE><SingleSpace><DOUBLE digit hour> the rest of the time. So you need to make sure that your TIME_FORMAT, MAX_TIMESTAMP_LOOKAHEAD, LINE_BREAKER, etc. can each accommodate this variability. One of these is poorly-written enough to fail on the zero-hour because that format is different than all of the others.

burwell
SplunkTrust
SplunkTrust

Could this be an error in regex on the line breaking?

Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.

Can’t make it to .conf25? Join us online!

Get Updates on the Splunk Community!

Can’t Make It to Boston? Stream .conf25 and Learn with Haya Husain

Boston may be buzzing this September with Splunk University and .conf25, but you don’t have to pack a bag to ...

Splunk Lantern’s Guide to The Most Popular .conf25 Sessions

Splunk Lantern is a Splunk customer success center that provides advice from Splunk experts on valuable data ...

Unlock What’s Next: The Splunk Cloud Platform at .conf25

In just a few days, Boston will be buzzing as the Splunk team and thousands of community members come together ...