Getting Data In

props.conf change does not take effect

RalphT
New Member

By source type or file, I changed the line breaking setting but it never takes effect.
On my local test system it works fine. On the distributed environment it does not.
The Splunk Web Server has been restarted, no effect. I either need separate lines or all lines together. I have tried both. I have modified props.conf in the App directory and added the same stanza under system/local.

Do the Splunk Forwarder Instances need to be changed? I have several forwarders sending data to the central server. I have not had those changed yet.

Why do I need this done? Default Splunk behavior is 256 lines followed by single lines. This breaks the extract command when multiple values are extracted. Counts are typically under reported.

Samples that fail on distributed environment:

[stats_file]

MAX_EVENTS = 3000

[stats_file]

DATETIME_CONFIG=CURRENT

SHOULD_LINEMERGE=FALSE

LINE_BREAKER=([\r\n]+)
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!

Kick the Tires Before You Commit: A Hands-On Tour of the Splunk Observability Cloud ...

Evaluating an enterprise observability platform usually goes like this: fill out a form, get a free trial with ...

Deep insights, no barriers: Splunk Observability Cloud Free Edition

As software delivery cycles continue to accelerate, observability shouldn’t be a luxury — it should be a ...

Monitoring AI Agents with Splunk Observability Cloud

Let’s say I’m running a travel planning AI app in production. A user asks for three concise hotel options in ...