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!

Free Professional Services for .conf26 Attendees

This year at .conf26, we are doing something a little different. We are bringing the best minds from ...

Defend at Machine Speed: Your Guide to Security Sessions at .conf26

Splunk .conf26   With threats moving at machine speed and attack surfaces expanding across hybrid ...

Where Innovation Takes Flight: The Splunk4Aviation Flight Sim Lands at .conf26

If you hear someone at .conf26 shouting "gear down, GEAR DOWN" across the show floor, you have found us.  The ...