Splunk Search

calculate duration of connection

jalfrey
Communicator

I have these two log messages

Jul 2 10:21:50 10.197.1.254 id=firewall sn=0017C5C027C1 time="2013-07-02 17:21:50 UTC" fw=67.115.118.49 pri=6 c=262144 m=98 msg="Connection Opened" n=565679 src=192.168.168.65:1330:MGMT dst=192.168.168.169:443:MGMT proto=tcp/https sent=64

ul 2 10:21:58 10.197.1.254 id=firewall sn=0017C5C027C1 time="2013-07-02 17:21:57 UTC" fw=67.115.118.49 pri=6 c=1024 m=537 msg="Connection Closed" n=606900 src=192.168.168.65:1330:MGMT dst=192.168.168.169:443:MGMT proto=tcp/https sent=670 rcvd=473 spkt=8 rpkt=6 cdur=7366

As you can see the first one is for "Connection Opened" and the second "Connection Closed". Both the src and dst are the same so I believe this is a single stream. How do I calculate the total duration of this connection?

0 Karma

lguinn2
Legend

There are many ways to tackle this problem. One is to use the transaction command, which will automatically create a field called duration for you. This example creates the transactions and formats a nice table

yoursearchhere ("Connection Opened" OR "Connection Closed")
| transaction src dst startswith="Connection Opened" endswith="Connection Closed"
| table _time as StartTime duration src dst
| fieldformat duration=tostring(duration,"duration")
| fieldformat StartTime=strftime(StartTime,"%x %X")
0 Karma

Jon_Webster
Splunk Employee
Splunk Employee

If you are getting your timestamps indexed correctly, then the "duration" field which is created for every "transaction" event will show you your duration in seconds. In your example the duration should be "8", as the difference between the 10:21:50 and 10:21:58 in your timestamps.

0 Karma
Career Survey
First 500 qualified respondents will receive a $20 gift card! Tell us about your professional Splunk journey.
Get Updates on the Splunk Community!

Introduction to Splunk AI

How are you using AI in Splunk? Whether you see AI as a threat or opportunity, AI is here to stay. Lucky for ...

Splunk + ThousandEyes: Correlate frontend, app, and network data to troubleshoot ...

Are you tired of troubleshooting delays caused by siloed frontend, application, and network data? We've got a ...

Maximizing the Value of Splunk ES 8.x

Splunk Enterprise Security (ES) continues to be a leader in the Gartner Magic Quadrant, reflecting its pivotal ...