<?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: logging asdm in Network Security</title>
    <link>https://community.cisco.com/t5/network-security/logging-asdm/m-p/4072898#M1069458</link>
    <description>&lt;P&gt;The "logging asdm errors" line will only send that severity level (or higher) syslog messages to ASDM.&lt;/P&gt;
&lt;P&gt;Typically you would make it more verbose during troubleshooting and then turn it back down for normal operations. The downside of leaving it more verbose is that significant issues may not be apparent when you glance at ASDM logging since you are typically overwhelmed with the volume of messages otherwise.&lt;/P&gt;
&lt;P&gt;The buffer will fill up and discard older messages either way, just more quickly when it's more verbose.&lt;/P&gt;</description>
    <pubDate>Fri, 24 Apr 2020 03:14:00 GMT</pubDate>
    <dc:creator>Marvin Rhoads</dc:creator>
    <dc:date>2020-04-24T03:14:00Z</dc:date>
    <item>
      <title>logging asdm</title>
      <link>https://community.cisco.com/t5/network-security/logging-asdm/m-p/4072871#M1069456</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I cannot see&amp;nbsp; informational&amp;nbsp; logs&amp;nbsp; ,even if choose debugging&amp;nbsp; under real time logging&amp;nbsp; in monitor&amp;nbsp; tab&amp;nbsp;&lt;/P&gt;&lt;P&gt;current logging&amp;nbsp; section is below .&amp;nbsp;&lt;/P&gt;&lt;P&gt;logging enable&lt;BR /&gt;logging timestamp&lt;BR /&gt;logging trap informational&lt;BR /&gt;logging history critical&lt;BR /&gt;&lt;STRONG&gt;logging asdm errors ,&amp;nbsp;&lt;/STRONG&gt; Is it because of&amp;nbsp; logging asdm set to errors ?&amp;nbsp;&lt;/P&gt;&lt;P&gt;is there any pros and cons if I change&amp;nbsp; to informational .&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I&amp;nbsp; dont' want so many logs permanently on asdm . I need only when I&amp;nbsp; choose real-time logging&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thanks&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Fri, 24 Apr 2020 02:41:09 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/logging-asdm/m-p/4072871#M1069456</guid>
      <dc:creator>kp-tkr2014</dc:creator>
      <dc:date>2020-04-24T02:41:09Z</dc:date>
    </item>
    <item>
      <title>Re: logging asdm</title>
      <link>https://community.cisco.com/t5/network-security/logging-asdm/m-p/4072898#M1069458</link>
      <description>&lt;P&gt;The "logging asdm errors" line will only send that severity level (or higher) syslog messages to ASDM.&lt;/P&gt;
&lt;P&gt;Typically you would make it more verbose during troubleshooting and then turn it back down for normal operations. The downside of leaving it more verbose is that significant issues may not be apparent when you glance at ASDM logging since you are typically overwhelmed with the volume of messages otherwise.&lt;/P&gt;
&lt;P&gt;The buffer will fill up and discard older messages either way, just more quickly when it's more verbose.&lt;/P&gt;</description>
      <pubDate>Fri, 24 Apr 2020 03:14:00 GMT</pubDate>
      <guid>https://community.cisco.com/t5/network-security/logging-asdm/m-p/4072898#M1069458</guid>
      <dc:creator>Marvin Rhoads</dc:creator>
      <dc:date>2020-04-24T03:14:00Z</dc:date>
    </item>
  </channel>
</rss>

