<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Logs on LeanerCloud</title><link>https://leanercloud.com/tags/logs.html</link><description>Recent content in Logs on LeanerCloud</description><generator>Hugo</generator><language>en</language><lastBuildDate>Thu, 20 Aug 2026 02:08:40 +0200</lastBuildDate><atom:link href="https://leanercloud.com/tags/logs/index.xml" rel="self" type="application/rss+xml"/><item><title>Cutting CloudWatch Logs costs hiding in a few log groups</title><link>https://leanercloud.com/blog/2024-04-09-cutting-cloudwatch-logs-costs.html</link><pubDate>Tue, 09 Apr 2024 17:05:18 +0000</pubDate><guid>https://leanercloud.com/blog/2024-04-09-cutting-cloudwatch-logs-costs.html</guid><description>&lt;h2 id="a-line-item-that-is-easy-to-ignore"&gt;A line item that is easy to ignore&lt;/h2&gt;
&lt;p&gt;CloudWatch Logs rarely shows up as a headline on an AWS bill, which is exactly why it is worth checking. The cost is spread across ingestion, storage, and retention, and it accumulates quietly on log groups that were configured once and never revisited. By the time it is real money, it is buried among hundreds of other log groups.&lt;/p&gt;
&lt;h2 id="one-log-group-8000-a-year"&gt;One log group, $8,000 a year&lt;/h2&gt;
&lt;p&gt;On one client the biggest single offender was a VPC flow log. Flow logs can be extremely verbose, and this one group had accumulated 2TB of data, costing about $8,000 a year on its own.&lt;/p&gt;</description></item></channel></rss>