Splunk Search

_txn_orphan field missing from transaction command after upgrade

eugenek
Path Finder

Just upgraded SH from 7.0.2 to 7.2.5.1 (indexers still in progress) and some reports which rely on _txn_orphan broke. If I understand correctly, this should be returning the _txn_orphan field.
| makeresults | eval foo="start;stop;start" | eval start_stop=split(foo,";") | mvexpand start_stop |fields - foo | transaction _time startswith="start_stop=start" endswith="start_stop=stop" keeporphans=true unifyends=true

0 Karma
1 Solution

eugenek
Path Finder

Worked with support and while the | makeresults-based query doesn't work on 7.0.2 either they confirmed that the behavior of that field changed between the versions.

More specifically,

There was some changes in SPL-159182 for memory management back in 7.1.4.
The _txn_orphan still exists, but only if the events aren't part of a transaction (even an incomplete one).

View solution in original post

eugenek
Path Finder

Worked with support and while the | makeresults-based query doesn't work on 7.0.2 either they confirmed that the behavior of that field changed between the versions.

More specifically,

There was some changes in SPL-159182 for memory management back in 7.1.4.
The _txn_orphan still exists, but only if the events aren't part of a transaction (even an incomplete one).

sloshburch
Splunk Employee
Splunk Employee

Thanks for adding the explanation from support!

0 Karma
Get Updates on the Splunk Community!

Introducing the 2024 SplunkTrust!

Hello, Splunk Community! We are beyond thrilled to announce our newest group of SplunkTrust members!  The ...

Introducing the 2024 Splunk MVPs!

We are excited to announce the 2024 cohort of the Splunk MVP program. Splunk MVPs are passionate members of ...

Splunk Custom Visualizations App End of Life

The Splunk Custom Visualizations apps End of Life for SimpleXML will reach end of support on Dec 21, 2024, ...