Splunkers... I am looking at a VPN logs from a Cisco ASA and trying to calculate the amount of time per day per user that a user spends logged into the VPN. I can run the following and the output looks right:
asa_logid="%ASA-6-602303" OR asa_logid="%ASA-6-602304" outbound sourcetype="syslog" earliest=-10d@d latest=+1d@d | transaction startswith="has been created" endswith="has been deleted" by vpn_session
What I get in output is an event that is started and ended properly by the vpn_session id(an extracted value from the log) but user. I also get a value called duration (which seems to be the length of the event in seconds). Thus I figured I could sum the duration by user by date_month like below:
asa_logid="%ASA-6-602303" OR asa_logid="%ASA-6-602304" outbound sourcetype="syslog" source="/var/log/hosts/172.30.64.2/messages.log" earliest=-10d@d latest=+1d@d | transaction startswith="has been created" endswith="has been deleted" by vpn_session | stats sum(duration) by vpn_user date_month date_year
However this summation shows people logged into the VPN for hundreds of hours per day... clearly not possible...
What am I doing wrong here?
Your search syntax looks right, and the stats should calculate the sum of the duration field. You should note that your stats is calculating the total duration for the month, not for the day, so it's not unreasonable for it to be greater than 86,400s.
Another possibility is that vpn_user has become a multivalued field and certain sessions are counting against multiple users.
I'd pipe the output of
stats sum(duration) count to see what the total duration and number of sessions is, as a sanity check.
I don't have any issues getting the month day, the problem is that the two events that make up the transaction have two different month days. How do I get it to evaluation only ONE of them.
Ok... so I ran some MORE analysis... and it looks like date_mday is a multi-value field (for those events that last over the break in the day, ie start at 1130pm and end at 0200am). At which point we are counting this event on BOTH days..
Going to have to figure out how to only report that ONCE.