Splunk Search

Transaction Events Issue

jberlin
Path Finder

My search is partially working in the aspect that it returns event data, however all of the events are mashed into one and the duration is calculated off the first event and the last event.

Search Command:
(index=jjj host=server OR host=server2 (inbound OR outbound)) | xmlkv | table _time, host, TokenId, inbound, outbound, _raw | transaction TokenId | search TokenId="$tokenId$"

I would like to the returned data to show each event as they occur or inbound event and outbound event for 1 duration time. Then move on to the next event and so on.

jb

Tags (1)
0 Karma
1 Solution

jberlin
Path Finder

Adding maxspan and maxpause to the transaction resolved the problem.

View solution in original post

0 Karma

jberlin
Path Finder

Adding maxspan and maxpause to the transaction resolved the problem.

0 Karma

lguinn2
Legend

Don't use the transaction command, then. It might also be helpful if you explained your data a little more. What do you mean "for 1 duration time"? What exactly do you want the output to look like?

In the meantime, I suggest this:

(index=jjj host=server OR host=server2 (inbound OR outbound)) "$tokenId$" 
| xmlkv 
| search TokenId="$tokenId$"
| table  _time, host, TokenId, inbound, outbound, _raw 
0 Karma
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Splunk Enterprise Security: An Automated Phishing Response Workflow

Originally posted on Splunk.com.   Key takeaways  The volume of phishing emails can overwhelm even the most ...

Sharper ES Detections, Agentic AI Integrations, Smarter Workload Management, and More ...

Splunk Lantern is Splunk’s customer success center that provides practical guidance from Splunk experts on key ...

Data Outage Monitoring and Reporting

We’ve all been there, right? Living our best life, working on our Splunk environment, when out of nowhere a ...