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!

Agentic SOC Triage: Investigating Splunk ES Notables with MCP Server and a Local LLM

The Problem: Too Many Alerts, Too Little Context Security operations teams running Splunk Enterprise Security ...

All Work and No Play? Not at .conf26! Unwind at These Evening Events

Between hands-on technical sessions, keynote reveals, and diving into live architectures, .conf26 is packed ...

Join the Hackathon at .conf26 and build a No-Code AI agent

Join us for the AI Agent Buildathon, an in-person, three-hour hands-on Hackathon where you’ll use Splunk Agent ...