Getting Data In

LINEMERGE / props.conf issues on XML

helius
Path Finder

Greetings,

I'm receiving XML files and noticed that the first half (around 257 lines) is a single event, but everything after that is a separate event.

screenshot
Reading the documentation, I see mention of modifying the props.conf to fix this. So, I've decided to use the following:

[source::elemental_job]
SHOULD_LINEMERGE = true
MAX_EVENTS = 2000
BREAK_ONLY_BEFORE = ^(<command)
MUST_NOT_BREAK_BEFORE = ^(</command) 

However, this does not work. It seems to have no effect actually.

Can someone tell me what I'm doing wrong?

1 Solution

helius
Path Finder

After much research, found the solution......

I realized that the forwarders don't actually handle working with the data I see on the search head. This is done on the indexers. So I added the following to the props.conf on the indexers we use and it works perfectly.

[source::/opt/elemental_se/web/log/*/job_*/*_emecmd.xml]
SHOULD_LINEMERGE = true
TRUNCATE = 0
MAX_EVENTS = 5000
BREAK_ONLY_BEFORE = ^(<command)
MUST_NOT_BREAK_BEFORE = ^(</command)

View solution in original post

helius
Path Finder

After much research, found the solution......

I realized that the forwarders don't actually handle working with the data I see on the search head. This is done on the indexers. So I added the following to the props.conf on the indexers we use and it works perfectly.

[source::/opt/elemental_se/web/log/*/job_*/*_emecmd.xml]
SHOULD_LINEMERGE = true
TRUNCATE = 0
MAX_EVENTS = 5000
BREAK_ONLY_BEFORE = ^(<command)
MUST_NOT_BREAK_BEFORE = ^(</command)
Get Updates on the Splunk Community!

Splunk + ThousandEyes: Correlate frontend, app, and network data to troubleshoot ...

 Are you tired of troubleshooting delays caused by siloed frontend, application, and network data? We've got a ...

Splunk Observability for AI

Don’t miss out on an exciting Tech Talk on Splunk Observability for AI!Discover how Splunk’s agentic AI ...

🔐 Trust at Every Hop: How mTLS in Splunk Enterprise 10.0 Makes Security Simpler

From Idea to Implementation: Why Splunk Built mTLS into Splunk Enterprise 10.0  mTLS wasn’t just a checkbox ...