Control SaaS logging costs by reducing low-value logs before they reach billable storage, setting retention for each log bucket or group, and verifying that essential events still reach the people and systems that need them. The controls differ by provider: Google Cloud Logging supports excluding a percentage of matching entries through sink exclusions, while the cited AWS guidance recommends filtering before ingestion without documenting an equivalent proportional log-sampling control.
Start by finding costly, low-value logs
Inventory the sources that feed your logging service, then identify the busiest log groups, buckets, and event types. Look for repetitive health checks, routine success events, or verbose debug output that adds little value during troubleshooting. Volume alone is not a reason to discard an event: decide first which records are needed for incident response, security investigations, audits, and operational support.
As an Amazon Associate I earn from qualifying purchases.
Write down the purpose of each source and the destinations it feeds. A pipeline may send the same records to more than one destination, and each destination can have separate billing and retention behavior. Establish what must remain available and for how long before changing filters or expiry settings; the sources do not establish a universal retention duration or sampling percentage.
Crashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minutePC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Filter before storage, and sample only where supported
Filtering upstream can prevent low-value entries from reaching billable storage. The exact control depends on the service. Google Cloud recommends sink exclusion filters; AWS recommends filtering logs before ingestion. Do not assume a sampling feature documented for one provider exists in another.
#1 Best Overall
Google Cloud Logging: use sink exclusions
Google Cloud sink exclusions can omit all entries matching a filter or only a percentage of them. Excluded entries are not streamed to the affected log buckets and do not count against the stated storage allotment. The Google Cloud guidance on optimizing logs recommends exclusions for low-value entries.
The exclusions API reference demonstrates the sample function with sample(insertId, 0.99) to exclude 99% of matching low-severity Cloud Storage bucket entries. That is an example, not a generally safe setting. Before applying a percentage exclusion, confirm the filter matches only the intended events and that the remaining sample is adequate for diagnosis. Keep critical security, audit, and incident-response events out of the exclusion rule. The Required sink cannot be modified or used to exclude logs.
Rank #2
- Smart Integration –– Easily connect the tester to your smartphone, tablet, or MacBook via Bluetooth with the ZenTest app for real-time measurement control, calibration, and advanced data management within a 30 ft range.
- Precision Measurement –– Featuring a double-junction pH/conductivity combo sensor and a separate ORP sensor for high accuracy and durability, ensuring precise measurements across pH, conductivity/TDS/salinity/resistivity, and ORP (redox).
- Cloud-Based Data Logging –– Securely log, manage, and share your test data with our cloud-based data management system, allowing for easy access and ensuring your data is always protected against loss.
- Hybrid Functionality –– Designed for versatility, our tester works as a standalone classic tester when not connected to a smart device, offering uninterrupted testing capabilities.
- Effortless Usability –– Tailored for professionals seeking efficiency and reliability, our tester combines easy-to-use features and fully customizable settings with robust performance, making it ideal for lab, field, or any testing environment.
Amazon CloudWatch Logs: filter before ingestion
AWS guidance recommends filtering logs before ingestion and setting retention on log groups to manage costs. Its documented 30-day retention command is an example value, not a recommendation for every workload. The cited guidance does not establish a proportional log-sampling feature equivalent to Google Cloud’s exclusion example; use only controls documented for your AWS pipeline.
The Tool Desk
Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Set retention for each bucket or log group
Retention determines how long stored logs remain available under a service’s policy. Set it per bucket or log group based on operational, security, audit, and organizational requirements. Document why the period fits the data’s purpose, and verify the configuration on the actual resource: defaults and available settings vary by provider, bucket, and scope.
Google Cloud Logging retention
Google Cloud Logging has bucket-specific defaults and configurable retention periods. The quotas and limits documentation says project-level _Default and user-defined buckets can be configured from 1 to 3650 days; other bucket and resource-scope combinations differ. For folder- or organization-level entries retained beyond 30 days, that documentation says to route them to a project log bucket. Check the current documentation and the configuration of the specific bucket before relying on a duration.
Amazon CloudWatch Logs retention
CloudWatch Logs retains data indefinitely by default until a retention policy is set on the log group. AWS marks events for deletion after they reach the configured retention point. Deletion typically takes up to 72 hours after that point and can rarely take longer, so a retention setting should not be treated as an exact-time deletion guarantee. See AWS’s log group and stream documentation.
Understand the cost and expiry trade-offs
Charges depend on the provider and the path logs take through the service. Compare ingestion, storage, extended retention, queries, alerts, exports, and delivery to other destinations—not just the headline ingestion rate. The published Google Cloud rates below are provider-specific figures from its pricing page, not general SaaS market prices; rates and effective dates are volatile, so check the live Google Cloud Logging pricing page before making a budget decision.
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Scan for outdated or missing drivers - takes under a minuteDriver Scan →| Google Cloud Logging charge | Published figure | Qualification |
|---|---|---|
| Logging storage other than vended network logs | $0.50/GiB; first 50 GiB per project per month free | Effective date listed as July 1, 2018; verify current pricing. |
| Vended network logs | $0.25/GiB | Effective date listed as October 1, 2024; verify current pricing. |
| Logs retained beyond 30 days | $0.01/GiB/month | Effective date listed as January 1, 2022; verify current pricing. |
Shortening Google Cloud bucket retention starts a seven-day grace period, according to the pricing documentation. During that period, expired logs cannot be queried or viewed; extending retention within the grace period can restore access. Treat a shorter retention setting as an availability change as well as a cost control.
Best Value
Choose CloudWatch Logs classes deliberately
CloudWatch Logs Infrequent Access has lower ingestion pricing than Standard but a reduced feature set; storage and Logs Insights charges are the same between the two classes. A log group’s class cannot be changed after creation, so review query, alerting, and operational requirements before selecting it. Delivery is a separate class for delivering Lambda logs to S3 or Firehose; it has a fixed two-day retention and does not support Logs Insights. Consult the AWS log classes documentation for the current feature distinctions and AWS CloudWatch pricing for current prices.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Protect log delivery pipelines from recursion
CloudWatch Logs subscription filters can create an infinite delivery loop if a workflow includes the log groups that record the workflow itself. AWS warns that this can sharply increase ingestion billing in both CloudWatch Logs and the destination. Exclude groups participating in the delivery pipeline from its subscription filters, as described in AWS’s recursion-prevention documentation.
Roll out changes and verify the result
- Inventory: list log sources, high-volume groups or event types, destinations, and their current retention policies.
- Set requirements: identify events that must remain available for troubleshooting, incident response, security, or audit, and document the retention rationale for each relevant source.
- Apply a narrow filter: exclude only identified low-value events using the provider’s documented controls. For percentage exclusions, validate filter semantics and confirm critical events are not affected.
- Configure retention: set the intended period on each applicable bucket or log group, accounting for provider-specific defaults and expiry behavior.
- Check tiers and pipelines: compare ingestion and storage charges alongside query, alerting, and delivery needs; check for recursive subscriptions and destination costs.
- Measure and inspect: monitor log volume and spend after the changes, then verify that required events still arrive and can be queried where expected.
There is no universal sampling rate or standardized validation procedure established by the cited provider documentation. Set exclusions according to the value and risk of each event stream, then verify the result in your own environment.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
