Splunk Search

Transaction on unique field reduces events?

salokin_
Engager

Hello,
I don't understand the following behaviour and am looking for a solution. The following example is somewhat simplified, but still contains the "error"

(admission-controller.cc AND pool_name="*")
| stats dc(id)

> 28.635

The above code selects some events and counts the unique ids. In this case 28.635.

(admission-controller.cc AND pool_name="*")
| transaction id
| stats dc(id)

> 4.999

This code now uses transaction on id. In my understanding, as there are 28.635 different ids, the result of the second statement should be the same as the first one. But it isn't, it's less with 4999 instead. Could someone please explain why and offer a solution?

Best regards
Nikolas

0 Karma

salokin_
Engager

solved it, with keepevicted=true it produces the same results.

The complete code of the second statement then looks like that:

(admission-controller.cc AND pool_name="*")
     | transaction id keepevicted=true
     | stats dc(id)

28635

0 Karma
Get Updates on the Splunk Community!

Aligning Observability Costs with Business Value: Practical Strategies

 Join us for an engaging Tech Talk on Aligning Observability Costs with Business Value: Practical ...

Mastering Data Pipelines: Unlocking Value with Splunk

 In today's AI-driven world, organizations must balance the challenges of managing the explosion of data with ...

Splunk Up Your Game: Why It's Time to Embrace Python 3.9+ and OpenSSL 3.0

Did you know that for Splunk Enterprise 9.4, Python 3.9 is the default interpreter? This shift is not just a ...