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!

Manage Edge Processor pipelines end to end with APIs

This guide uses the Data Management APIs to create an Edge Processor, onboard one instance, deploy a pipeline ...

Splunk Brings Proof of Control to Digital Asset Transfers

Digital assets now sit inside the core of financial services. HSBC launched its Tokenized Deposit Service in ...

Manage Ingest Processor pipelines end to end with APIs

This guide uses the Data Management APIs to create an Ingest Processor pipeline, deploy it to the ...