<?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 Re: Splunk and Cisco ASA No Event Data in Monitoring Splunk</title>
    <link>https://community.splunk.com/t5/Monitoring-Splunk/Splunk-and-Cisco-ASA-No-Event-Data/m-p/40289#M6944</link>
    <description>&lt;P&gt;You should not need to set any inputs.conf changes to get your Cisco ASA sourcetyped correctly. it should be set to syslog sourcetype by default, and then there's a transforms.conf that should force the sourcetype to cisco_asa by regexing a match against the incoming syslog data. Any syslog data with "%ASA-" in it should be automatically sourcetyped as cisco_asa (not cisco:asa like you have above, I believe.)&lt;/P&gt;

&lt;P&gt;There are a few apps out there that have a typo in them for the transforms.conf that does this, however. The stanza below is the correct one that should be in your transforms.conf under your app's default directory (check the one for the TA....). Note the commented out INCORRECT regex. The uncommented one is the one you want.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[force_sourcetype_for_cisco_asa]
DEST_KEY = MetaData:Sourcetype
REGEX = %ASA-\d+-\d+
#REGEX = %ASA--\d+-\d+
FORMAT = sourcetype::cisco_asa
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Then check that your data is being sourcetyped correctly:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=* %ASA | dedup sourcetype | table sourcetype
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;and you should be good to go.&lt;/P&gt;</description>
    <pubDate>Mon, 28 Sep 2020 15:45:49 GMT</pubDate>
    <dc:creator>jbrodsky_splunk</dc:creator>
    <dc:date>2020-09-28T15:45:49Z</dc:date>
    <item>
      <title>Splunk and Cisco ASA No Event Data</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Splunk-and-Cisco-ASA-No-Event-Data/m-p/40287#M6942</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;

&lt;P&gt;I have DL'd and installed the following:&lt;/P&gt;

&lt;P&gt;Splunk App for Cisco ASA ver 1.0&lt;BR /&gt;
Splunk for Cisco ASA Technology Add-on ver 1.1&lt;BR /&gt;
Google Maps&lt;BR /&gt;
Sideview Utils&lt;/P&gt;

&lt;OL&gt;
&lt;LI&gt;My Splunk server is receiving SYSLOG from my ASA ( verified with TCP Dump )&lt;/LI&gt;
&lt;LI&gt;I can use a * to search the logfiles&lt;/LI&gt;
&lt;LI&gt;I have updated my input.conf = sourcetype=cisco:asa, index: main&lt;/LI&gt;
&lt;/OL&gt;

&lt;P&gt;I still am showing no data in the following:&lt;/P&gt;

&lt;OL&gt;
&lt;LI&gt;Fiewall Dashboard Page&lt;/LI&gt;
&lt;LI&gt;Overview Page&lt;/LI&gt;
&lt;LI&gt;Summary Page&lt;/LI&gt;
&lt;/OL&gt;

&lt;P&gt;Any help much appreciated.&lt;/P&gt;

&lt;P&gt;Thanks,&lt;BR /&gt;
Brian&lt;/P&gt;</description>
      <pubDate>Mon, 20 May 2013 23:48:52 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Splunk-and-Cisco-ASA-No-Event-Data/m-p/40287#M6942</guid>
      <dc:creator>brianma</dc:creator>
      <dc:date>2013-05-20T23:48:52Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk and Cisco ASA No Event Data</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Splunk-and-Cisco-ASA-No-Event-Data/m-p/40288#M6943</link>
      <description>&lt;P&gt;Splunk Add-on for Cisco ASA&lt;/P&gt;

&lt;P&gt;I do not see this information below to make the change &lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;My Splunk server is receiving SYSLOG from my ASA ( verified with TCP Dump )
I can use a * to search the logfiles
I have updated my input.conf = sourcetype=cisco:asa, index: main
&lt;/CODE&gt;&lt;/PRE&gt;</description>
      <pubDate>Wed, 29 Jan 2014 15:45:48 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Splunk-and-Cisco-ASA-No-Event-Data/m-p/40288#M6943</guid>
      <dc:creator>rshorter</dc:creator>
      <dc:date>2014-01-29T15:45:48Z</dc:date>
    </item>
    <item>
      <title>Re: Splunk and Cisco ASA No Event Data</title>
      <link>https://community.splunk.com/t5/Monitoring-Splunk/Splunk-and-Cisco-ASA-No-Event-Data/m-p/40289#M6944</link>
      <description>&lt;P&gt;You should not need to set any inputs.conf changes to get your Cisco ASA sourcetyped correctly. it should be set to syslog sourcetype by default, and then there's a transforms.conf that should force the sourcetype to cisco_asa by regexing a match against the incoming syslog data. Any syslog data with "%ASA-" in it should be automatically sourcetyped as cisco_asa (not cisco:asa like you have above, I believe.)&lt;/P&gt;

&lt;P&gt;There are a few apps out there that have a typo in them for the transforms.conf that does this, however. The stanza below is the correct one that should be in your transforms.conf under your app's default directory (check the one for the TA....). Note the commented out INCORRECT regex. The uncommented one is the one you want.&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;[force_sourcetype_for_cisco_asa]
DEST_KEY = MetaData:Sourcetype
REGEX = %ASA-\d+-\d+
#REGEX = %ASA--\d+-\d+
FORMAT = sourcetype::cisco_asa
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;Then check that your data is being sourcetyped correctly:&lt;/P&gt;

&lt;PRE&gt;&lt;CODE&gt;index=* %ASA | dedup sourcetype | table sourcetype
&lt;/CODE&gt;&lt;/PRE&gt;

&lt;P&gt;and you should be good to go.&lt;/P&gt;</description>
      <pubDate>Mon, 28 Sep 2020 15:45:49 GMT</pubDate>
      <guid>https://community.splunk.com/t5/Monitoring-Splunk/Splunk-and-Cisco-ASA-No-Event-Data/m-p/40289#M6944</guid>
      <dc:creator>jbrodsky_splunk</dc:creator>
      <dc:date>2020-09-28T15:45:49Z</dc:date>
    </item>
  </channel>
</rss>

