Getting Data In

events print()-ed from Python input merged

gliptak
Explorer

While using print() to emit events from Python input, sometimes the events from separate print statements get merged. An example (edited) below:

 

 

2020-11-05T20:23:21.988802+00:00, application="application1"
2020-11-05T20:23:21.993878+00:00, application="application2"

 

 

I'm unclear why these particular ones got merged (there were other records print() -ed at 2020-11-05T20:23:21, and all events had increasing/unique timestamp)

Any pointers on how to prevent this? Thanks

Labels (3)
0 Karma

richgalloway
SplunkTrust
SplunkTrust

The example looks like two separate events.  How are they "merged"?  What are the props.conf settings for that sourcetype?

---
If this reply helps you, Karma would be appreciated.

gliptak
Explorer

events.png

sourcetype wasn't configured while above event was indexed

Configuring the sourcetype with SHOULD_LINEMERGE = false might not work well as events have multi-line fields

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!

Splunk Add-on for Microsoft Windows 11.0.3: Parse Once, Search Faster

The updated Splunk Add-on for Microsoft Windows helps customers search Windows events faster by reducing ...

What's New in Splunk Enterprise Security 8.8 and Beyond

Threats move at machine speed. Keeping up should not depend on having the biggest budget, the largest team, or ...

A Four-Part Event Series: State of Observability - Where AI Meets Performance

As AI agents take on more complex tasks, teams need greater visibility into how they behave, what they cost, ...