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!

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 ...