Splunk Search

Likely Bug With Transaction MaxEvents

SplunkPersonal
Path Finder

Hello,

I'm using transaction to process events. Per the documentation (https://docs.splunk.com/Documentation/Splunk/7.2.0/SearchReference/Transaction), I set maxevents to a negative number so there is no limit. I only get 500 results however. But if I change maxevents to 5000 events, I get 2700 events with the exact same query.

Can you confirm this is not working as intended with a negative value for maxevents?

Thank you.

Tags (1)

simonzfor
Explorer

I have a similar issue where I have an expected of about 1500 events in a transaction. If I set maxevents to 1000, I get two different transactions. If I set maxevents to too big or disable it by using a negative value, they get excluded entirely from the end result. I find this behavior very strange.

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!

Kubernetes Alerts That Work Out of the Box with AutoDetect detectors in Splunk ...

A deployment rolls out slowly, one pod sits not ready for a few minutes, and whoever is on call gets an alert ...

Observability at Your Fingertips Directly From Splunk Platform—for Free

At .conf, we announced our roadmap to bring observability foundations to Splunk Platform. Bringing metrics and ...

Accelerate Splunk App Development with AI

  Learn how to automate the repetitive parts of your build cycle.   Watch On-Demand   Replay the Accelerate ...