Splunk Search

Why is stats more efficient and better supported with MapReduce than transaction?

kj384g
New Member

I was told that stats is more efficent and better supported with MapReduce... is that true and if so why?

0 Karma

martin_mueller
SplunkTrust
SplunkTrust

The two don't do the same thing.

stats usually does less, so it'll be faster than transaction which is doing more work. For example, transaction will build multi-value fields for you while stats only builds those fields you specify.

As for using MapReduce more efficiently, grouping events together with transaction requires knowing all the events in one place - the search head. stats has less complex features - e.g. no maxspan, maxpause, non-unique identifiers - that allow a lot of work to be done on the indexers.

To sum up, if stats does what you need then it'll be faster almost every time.

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 ...