Splunk Search

Transactions events at the same second

aohls
Contributor

I am using the transaction command to identify if a report runs over a certain time. Below is my search:

| transaction startswith="Start" endswith="Finish" keeporphans=true
| where _txn_orphan=1

This primarily is working except there seem to be some false positives. If a report runs and finishes within the same second (which happens if a user forgets a parameter) Splunk is still counting it as orphaned, so _txn_orphan is still 1 but it should be 0 since it actually completed. Has anyone run into this and have a better way or workaround for this?

0 Karma

DavidHourani
Super Champion

Hi @aohls,

You can easily get rid of this by adding to your condition a minimum duration for the transaction. That way all those noisy transaction won't show anymore 🙂

Cheers,
David

0 Karma
Get Updates on the Splunk Community!

Extending Observability Content to Splunk Cloud

Register to join us !   In this Extending Observability Content to Splunk Cloud Tech Talk, you'll see how to ...

What's new in Splunk Cloud Platform 9.1.2312?

Hi Splunky people! We are excited to share the newest updates in Splunk Cloud Platform 9.1.2312! Analysts can ...

What’s New in Splunk Security Essentials 3.8.0?

Splunk Security Essentials (SSE) is an app that can amplify the power of your existing Splunk Cloud Platform, ...