Dashboards & Visualizations

Event Breaking Catastrophe!

markhvesta
Path Finder

Line Breaking is not functioning correctly for an XML source type.

We want to break between these two elements </result> <result expand

Here is the most recent config:
SHOULD_LINEMERGE=false
LINE_BREAKER=<result\sexpand
BREAK_ONLY_BEFORE=<result\sexpand
BREAK_ONLY_BEFORE_DATE=false
MUST_BREAK_AFTER=\/results>

Does this need to be applied to the indexers or in the props.conf on the forwarder? And if just the forwarder, just on the application/local or also in the system/local?

Tags (1)
0 Karma
1 Solution

woodcock
Esteemed Legend

Never use the BREAK_* options; always use LINE_BREAKER like this (you must have a capture group😞

props.conf (on your Indexers/HFs):

SHOULD_LINEMERGE = false
LINE_BREAKER = <\/result>([\r\n\s]*)<result\s+expand

View solution in original post

woodcock
Esteemed Legend

Never use the BREAK_* options; always use LINE_BREAKER like this (you must have a capture group😞

props.conf (on your Indexers/HFs):

SHOULD_LINEMERGE = false
LINE_BREAKER = <\/result>([\r\n\s]*)<result\s+expand
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!

Meet the .conf26 AI Agent Buildathon Winners

At the .conf26 AI Agent Buildathon, Splunk users turned their operational expertise into working AI agents ...

Trusted Autonomy in the SOC: A Maturity Journey

AI is compressing attacker timelines and pushing SOC teams beyond human capacity thresholds. The next SOC ...

Supercharging Windows Security Detection Performance: Introducing Hybrid Field ...

Windows event logs—from Security auditing and Sysmon to PowerShell script blocks—form the operational backbone ...