Getting Data In

lines not breaking in old (rolled) log files

mmattek
Path Finder

so I have a case where my line breaks are fine in the Director.log

but in Director.log.20100517 00-20-29##20.log

they don't get applied.

What's interesting is the get the right source type from the props.conf (in the deployed app)

[source::...Director.log...]
sourcetype = rs_director

and that stanza should take care of it..
the in props.conf of the local app on the indexer, i have this:

[rs_director]
BREAK_ONLY_BEFORE=^\d+-\d+-\d+\s+\d+:\d+:\d+.\d+:
pulldown_type = true
AUTO_TAG = false
KV_MODE = none
MAX_TIMESTAMP_LOOKAHEAD = 25
MAX_EVENTS = 512
AUTO_LINEMERGE = false
TIME_FORMAT = %m-%d-%y %H:%M:%S
TZ = EST-5EDT,M3.2.0,M11.1.0

but it doesn't break the old logs (the regex works fine in the base log)..

Tags (1)
0 Karma

yannK
Splunk Employee
Splunk Employee

If your events are single line
Try SHOULD_LINEMERGE = false
instead of AUTO_LINEMERGE

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!

Splunk Add-on for Microsoft Windows 11.0.3: Parse Once, Search Faster

The updated Splunk Add-on for Microsoft Windows helps customers search Windows events faster by reducing ...

What's New in Splunk Enterprise Security 8.8 and Beyond

Threats move at machine speed. Keeping up should not depend on having the biggest budget, the largest team, or ...

A Four-Part Event Series: State of Observability - Where AI Meets Performance

As AI agents take on more complex tasks, teams need greater visibility into how they behave, what they cost, ...