<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Syslog on Danno Projects</title><link>https://www.dannoprojects.com/tags/syslog/</link><description>Recent content in Syslog on Danno Projects</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Tue, 14 Apr 2026 09:00:00 -0700</lastBuildDate><atom:link href="https://www.dannoprojects.com/tags/syslog/index.xml" rel="self" type="application/rss+xml"/><item><title>Sending Cisco Firewall Logs to CloudWatch Without Drowning in Noise</title><link>https://www.dannoprojects.com/posts/networking/asa-syslog-to-cloudwatch/</link><pubDate>Tue, 14 Apr 2026 09:00:00 -0700</pubDate><guid>https://www.dannoprojects.com/posts/networking/asa-syslog-to-cloudwatch/</guid><description>&lt;h2 id="overview"&gt;Overview&lt;/h2&gt;
&lt;p&gt;In an &lt;a href="https://www.dannoprojects.com/posts/networking/cisco-firepower-saml-mfa/"&gt;earlier post&lt;/a&gt; I set up SAML and MFA for VPN on a Cisco Firepower 1120 running ASA. Once that was in place, the next question was obvious: &lt;strong&gt;how do I know when something is wrong with the firewall without logging into ASDM every morning?&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;We already ran most of our infrastructure in AWS, so Amazon CloudWatch was the natural place to land firewall logs. The first attempt worked, and it also sent &lt;em&gt;everything&lt;/em&gt;. The log volume was noisy, expensive to keep, and useless for alerting. This post covers the version I ended up with: a small Linux syslog relay, a trimmed log stream, and a handful of metric filters that drive alarms and a dashboard.&lt;/p&gt;</description></item></channel></rss>