# Excessive CloudWatch log volume from persistently enabled debugging Canonical: https://www.pointfive.co/efficiency-hub/inefficiencies/excessive-cloudwatch-log-volume-from-persistently-enabled-debugging Engineers often enable verbose logging (e.g., debug or trace-level) during development or troubleshooting, then forget to disable it after deployment. By: Trig Ghosh Updated: 2026-09-28 [Cloud Efficiency Hub](https://www.pointfive.co/efficiency-hub) # Excessive CloudWatch Log Volume from Persistently Enabled Debugging The short version Engineers often enable verbose logging (e.g., debug or trace-level) during development or troubleshooting, then forget to disable it after deployment. Trig Ghosh AWS service [AWS CloudWatch](https://www.pointfive.co/efficiency-hub/cloud-services/aws-cloudwatch) Category [Other](https://www.pointfive.co/efficiency-hub/service-category/other) Reference CER-0090 Type Inefficient Configuration ## Explanation Why the waste happens and who it affects. This results in elevated log ingestion rates - and therefore costs - even when the detailed logs are no longer needed. Because CloudWatch Logs charges per GB ingested, persistent debug logging in production environments can create silent but material cost increases, particularly for high-throughput services.In environments with multiple teams or loosely governed log group policies, this issue can go undetected for long periods. Identifying and deactivating unnecessary debug-level logging is a low-risk, high-leverage optimization. ## Billing model The pricing dimensions that drive this cost. CloudWatch Logs charges include: - Ingestion cost per GB of data sent to log groups - Storage cost based on retention period - Optional costs for subscription filters, insights queries, and cross-account delivery Log volume is driven directly by the application's logging configuration and verbosity. ## How to detect 4 checks to find it in your estate. - Identify log groups with consistently high ingestion volume over time - Review logging level configurations in application code, infrastructure-as-code, or service parameters - Correlate high-volume log groups with services not actively under debugging or incident investigation - Check whether log volume spikes correspond to elevated verbosity (e.g., debug/trace level output) ## How to fix 4 ways to remove the waste. - Reduce log verbosity from debug/trace to info or warn levels where appropriate - Implement logging configuration standards across environments, with production defaults - Use dynamic log level toggling (e.g., via environment variables or feature flags) to avoid persistent debug logging - Set up alerts for anomalous log ingestion volumes tied to specific services or log groups ## Documentation Vendor references for pricing and configuration. - [Amazon CloudWatch Logs Pricing aws.amazon.com](https://aws.amazon.com/cloudwatch/pricing/) - [Analyzing, optimizing, and reducing CloudWatch costs docs.aws.amazon.com](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/cloudwatch_billing.html) ## Related inefficiencies [Browse the library](https://www.pointfive.co/efficiency-hub) - AWS CloudWatch CER-0224 ### [Suboptimal Log Class Configuration in CloudWatch](https://www.pointfive.co/efficiency-hub/inefficiencies/suboptimal-log-class-configuration-in-cloudwatch) By default, CloudWatch Log Groups use the Standard log class, which has a higher per-GB ingestion price. AWS also offers an Infrequent Access (IA) log class designed for logs that are rarely queried - such as audit trails, debugging... Other - AWS CloudWatch CER-0382 ### [Unnecessary EC2 Detailed Monitoring](https://www.pointfive.co/efficiency-hub/inefficiencies/unnecessary-ec2-detailed-monitoring) EC2 basic monitoring publishes instance metrics to CloudWatch at 5-minute granularity at no charge. Detailed monitoring switches those metrics to 1-minute granularity, and each metric EC2 sends is then billed at the CloudWatch custom... Other - AWS CloudWatch CER-0233 ### [Overly Permissive VPC Flow Log Filters Sent to CloudWatch Logs](https://www.pointfive.co/efficiency-hub/inefficiencies/overly-permissive-vpc-flow-log-filters-sent-to-cloudwatch-logs) VPC Flow Logs configured with the ALL filter and delivered to CloudWatch Logs often result in unnecessarily high log ingestion volumes - especially in high-traffic environments. This setup is rarely required for day-to-day monitoring or... Other --- Source: the public page above. Product screenshots and illustrative interfaces are examples, not live customer data.