@andrewcg which are the fields you want to stitch together after transaction command?
You should ideally try stats for your correlation instead of transaction . There are several examples of stats for transaction on Splunk Answers.
<yourCurrentSearch>
| fields _time, session_id, field1, field2, field3
| eval Time=_time
| bin _time span=30s
| stats count as eventcount list(*) as list_* by _time session_id
| eval maxTime=mvindex(list_Time,0),minTime=mvindex(list_Time,eventcount-1), duration=maxTime-minTime
| fields - minTime maxTime
Following is a runanywhere example based on Splunk's _internal index just to generate some data and correlate using component (similar to session_id )
index=_internal sourcetype=splunkd
| fields _time, component, log_level, date_hour, date_minute, date_second
| eval Time=_time
| bin _time span=30s
| stats count as eventcount list(*) as list_* by component _time
| eval maxTime=mvindex(list_Time,0),minTime=mvindex(list_Time,eventcount-1), duration=maxTime-minTime
| fields - minTime maxTime
Please try out and confirm!
... View more