Splunk Search

Unexplained: Inconsistent/incomplete transaction eventcount when using maxevents with startswith

collinrice
Explorer

I am getting an inconsistent number of events in a transaction, relative to the value specified for maxevents=x:

| transaction ComputerName startswith=(EventCode=1100) maxevents=x

Here are the eventcounts for each ComputerName where x=[10, 20, 30, 40], and maxevents undefined (i.e. not included in the SPL).:

________________ x = 10_____20_____30_____40__Undefined
Computer1, txn A......3......3.....13.....23.....423
Computer1, txn B......5......5......5.....25.....705
Computer2.............5.....15.....15.....15.....855
Computer3.............6......6.....26.....26.....986
Computer4............10.....20.....30.....20.....100
Computer5, txn A......4.....14.....14.....14.....134
Computer5, txn B......6.....16.....16.....36.....836

Using maxspan and not maxevents consistently produces the expected results (verified by comparing the transaction'ed events to the list of raw events).

QUESTIONS: All computer have more than ten events that could be included in a transaction that starts with EventCode=1100, so why are there less than 10 events included in the transaction when maxevents=10? Shouldn't the transaction include (i.e. eventcount) up to then maxevent value when possible?

Why does the eventcount jump up inconsistently when maxevents is changed to different values?

Why does the eventcount for Computer4 actually decrease from 30 to 20 when maxevents is increased to 40?

0 Karma
Get Updates on the Splunk Community!

Introducing Splunk Enterprise 9.2

WATCH HERE! Watch this Tech Talk to learn about the latest features and enhancements shipped in the new Splunk ...

Adoption of RUM and APM at Splunk

    Unleash the power of Splunk Observability   Watch Now In this can't miss Tech Talk! The Splunk Growth ...

Routing logs with Splunk OTel Collector for Kubernetes

The Splunk Distribution of the OpenTelemetry (OTel) Collector is a product that provides a way to ingest ...