Splunk Search

Likely Bug With Transaction MaxEvents

Path Finder


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)


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
Take the 2021 Splunk Career Survey

Help us learn about how Splunk has
impacted your career by taking the 2021 Splunk Career Survey.

Earn $50 in Amazon cash!