The table below explains in detail the steps of a Splunk Enterprise or Splunk Cloud Platform search to report on the average duration of payments processed. For more information, review the use case monitoring payment responses.
Some commands, parameters, and field names in the searches below may need to be adjusted to match your environment. In addition, to optimize the searches shown below, you should specify an index and a time range when appropriate.
Splunk recommends that customers look into using data models, report acceleration, or summary indexing when searching across hundreds of GBs of events in a single search. The searches provided here are a good starting point, but depending on your data, search time range, and other factors, more can be done to ensure that they scale appropriately.
||sourcetype=<payment processing data>||Search only your payment processing data.|
||eval _time=strptime(_time, "%Y/%m/%d %H:%M:%S")||Parse the time stamp into a UNIX time value.|
||sort _time||Sort the results from oldest to newest.|
||stats count values(_time) AS _time first(epoch) AS first last(epoch) AS last BY sessionID||Display the times of the payment request and response. Then group the payments by their unique identifier.|
||where count>1||Limit the results to those with more than 1 transaction.|
||eval duration=last-first||Create a duration field that is equal to the last minus first time.|
||timechart avg(duration) span=5m fixedrange=F||Graph the average duration of payment responses over time in 5-minute increments, expanding the chart as needed to cover all events.|