Splunk Search

Transaction command not returning results

ssaenger
Communicator

I would like to extract from my log file user details on how many time they have had a request to the SGW where the number of times is gretaer than 1.
I would like to make a table showing the user_id and number of times they made the request.

i would also like to do a total count of users with more than 1 request.

I thought transaction would do this, however its not resolving any results and seems to be very slow when running the search.

index=sgw sourcetype=sgw_log Request_type=Open TxType=Request | transaction user_id | where eventcount>1 | table user_id eventcount

thanks,

Tags (2)
0 Karma

lguinn2
Legend

You don't need the transaction command for this. I would avoid using the transaction command, if possible, because it is not nearly as efficient as stats.

 index=sgw sourcetype=sgw_log Request_type=Open TxType=Request 
| stats count as request_count by user_id 
| appendpipe [ stats count(eval(request_count>1)) as "Users with Multiple Requests") ]

If you only want to list the users with multiple requests:

 index=sgw sourcetype=sgw_log Request_type=Open TxType=Request 
| stats count as request_count by user_id 
| where request_count > 1
|  appendpipe [ stats count as "Users with Multiple Requests") ]
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!

From Raw Data to Executive-Ready Stories, Faster

Build Data Stories for Every Audience  A dashboard is rarely just a dashboard. It might be the view an ...

Guided Onboarding with Auto-schema Is Now Generally Available

  We are excited to announce the General Availability of Guided Onboarding with Auto-Schematization ...

ATTENTION: We’re Moving! (AGAIN!)

The Splunk Community Slack is undergoing a system migration to keep our workspace secure and ...