<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Cisco ASA Timechart in Splunk Search</title>
    <link>https://community.splunk.com/t5/Splunk-Search/Cisco-ASA-Timechart/m-p/279522#M84446</link>
    <description>&lt;P&gt;I'm looking to create a timechart of VPN sessions that shows the number of users logged on over the course of a 24 hour period. The problem is I want the count to stay up until the logoff/timeout event occurs for that user. I can easily create the list of users that are currently logged on and I'm using that as my starting point. NOTE: I've created the event type of "vpn_session_event" which looks at level 6 events in the Cisco ASA.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;eventtype=vpn_session_event  | transaction fields="user" maxspan=12h30m connected=f startswith="*connection established*"  | search eventtype!=cisco_vpn_end | dedup user
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;This will produce the list of current users, Now I need to chart this over time to get a count of how many user sessions were started over the course of the day dropping the number when the disconnect event occurs to show peak usage. Anyone have a technique for this?&lt;/P&gt;</description>
    <pubDate>Tue, 29 Sep 2020 10:21:38 GMT</pubDate>
    <dc:creator>jmaple</dc:creator>
    <dc:date>2020-09-29T10:21:38Z</dc:date>
    <item>
      <title>Cisco ASA Timechart</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Cisco-ASA-Timechart/m-p/279522#M84446</link>
      <description>&lt;P&gt;I'm looking to create a timechart of VPN sessions that shows the number of users logged on over the course of a 24 hour period. The problem is I want the count to stay up until the logoff/timeout event occurs for that user. I can easily create the list of users that are currently logged on and I'm using that as my starting point. NOTE: I've created the event type of "vpn_session_event" which looks at level 6 events in the Cisco ASA.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;eventtype=vpn_session_event  | transaction fields="user" maxspan=12h30m connected=f startswith="*connection established*"  | search eventtype!=cisco_vpn_end | dedup user
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;This will produce the list of current users, Now I need to chart this over time to get a count of how many user sessions were started over the course of the day dropping the number when the disconnect event occurs to show peak usage. Anyone have a technique for this?&lt;/P&gt;</description>
      <pubDate>Tue, 29 Sep 2020 10:21:38 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Cisco-ASA-Timechart/m-p/279522#M84446</guid>
      <dc:creator>jmaple</dc:creator>
      <dc:date>2020-09-29T10:21:38Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ASA Timechart</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Cisco-ASA-Timechart/m-p/279523#M84447</link>
      <description>&lt;P&gt;We do something similar with our firewalls, tracking the number of sessions that are active. Adding timechart count(connect_id) for us charts the number of action connections over a given period of time and shows the peak during the day.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt; eventtype=vpn_session_event  
| transaction fields="user" maxspan=12h30m connected=f startswith="*connection established*"  
| search eventtype!=cisco_vpn_end 
| dedup user
| **timechart count(user)**
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Mon, 25 Jul 2016 12:43:35 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Cisco-ASA-Timechart/m-p/279523#M84447</guid>
      <dc:creator>user12345a_2</dc:creator>
      <dc:date>2016-07-25T12:43:35Z</dc:date>
    </item>
    <item>
      <title>Re: Cisco ASA Timechart</title>
      <link>https://community.splunk.com/t5/Splunk-Search/Cisco-ASA-Timechart/m-p/279524#M84448</link>
      <description>&lt;P&gt;You need the &lt;CODE&gt;concurrency&lt;/CODE&gt; command:&lt;BR /&gt;
&lt;A href="http://docs.splunk.com/Documentation/Splunk/6.1.4/SearchReference/Concurrency"&gt;http://docs.splunk.com/Documentation/Splunk/6.1.4/SearchReference/Concurrency&lt;/A&gt;&lt;/P&gt;

&lt;P&gt;Also, ditch the &lt;CODE&gt;transaction&lt;/CODE&gt; command first:&lt;BR /&gt;
&lt;A href="http://wiki.splunk.com/Virtual_.conf#March_2016"&gt;http://wiki.splunk.com/Virtual_.conf#March_2016&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Sat, 30 Jul 2016 21:55:28 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Splunk-Search/Cisco-ASA-Timechart/m-p/279524#M84448</guid>
      <dc:creator>woodcock</dc:creator>
      <dc:date>2016-07-30T21:55:28Z</dc:date>
    </item>
  </channel>
</rss>

