Getting Data In

Logs with XML data is being read as two separate events by Splunk

venksel
Explorer

Hi There Folks!

Please refer screen shot of the original log file in a NotePad.
http://prntscr.com/w82jd1

Although its one single event, as illustrated with a red line separator, Splunk UF is reading it as two separate events with diff time stamps.  I did read about MAX_EVENTS and TRUNCATE and my props.conf in UF and Indexer is updated to the following:

 

[default]
MAX_EVENTS = 100000
TRUNCATE = 100000
BREAK_ONLY_BEFORE_DATE = false

However, the problem persists. Any insights on what might be causing this issue?  Thanks for your help in advance.

Cheers

Labels (1)
0 Karma

scelikok
SplunkTrust
SplunkTrust

Hi, @venksel,

Adding below TIME_PREFIX should help, Splunk is trying to guess event boundaries with timestamps. Since you have two timestamps in your event, you get two separate events.

You should put this props.conf to your indexer(s).

 

[xmlsourcetype]
TIME_PREFIX = [-]{12}[\r\n]+

 

 

 

If this reply helps you an upvote is appreciated.

 

If this reply helps you an upvote and "Accept as Solution" is appreciated.
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!

Design, Compete, Win: Submit Your Best Splunk Dashboards for a .conf26 Pass

Hello Splunkers,  We’re excited to kick off a Splunk Dashboard contest! We know that dashboards are a primary ...

May 2026 Splunk Expert Sessions: Security & Observability

Level Up Your Operations: May 2026 Splunk Expert Sessions Whether you are refining your security posture or ...

Network to App: Observability Unlocked [May & June Series]

In today’s digital landscape, your environment is no longer confined to the data center. It spans complex ...