Submit feedback on
Logging Buckets in Non-Production Environments Storing Info Logs
We've received your feedback.
Thanks for reaching out!
Oops! Something went wrong while submitting the form.
Close
Logging Buckets in Non-Production Environments Storing Info Logs
Yuval Goldstein
CER:
GCP-Other-2637
Service Category
Other
Cloud Provider
GCP
Service Name
GCP Cloud Logging
Inefficiency Type
Excessive Ingestion of Low-Value Logs
Explanation

Non-production environments frequently generate INFO-level logs that capture expected system behavior or routine API calls. While useful for troubleshooting in development, they rarely need to be retained. Allowing all INFO logs to be ingested and stored in Logging buckets across dev or staging environments can lead to disproportionate ingestion and storage costs. This inefficiency often persists because log routing and severity filters are not differentiated between production and non-production projects.

Relevant Billing Model

Cloud Logging charges for data ingestion and retained storage beyond the free tier. INFO-level logs can represent the majority of log volume, and in non-production environments — where they rarely drive operational decisions — these costs provide little return on value.

Detection
  • Identify non-production projects with Logging buckets configured to capture all log severities, including INFO
  • Review ingestion volume by log severity to quantify the share of INFO-level logs
  • Assess whether INFO logs are ever queried or analyzed in non-production environments
  • Determine if sink filters or routing policies apply uniform rules across production and non-production projects
Remediation
  • Adjust sink filters to exclude INFO-level logs in non-production environments
  • Establish environment-specific logging policies that retain only WARNING and ERROR logs in dev and staging projects
  • Route necessary INFO logs temporarily to low-cost storage (e.g., Cloud Storage with limited retention) for debugging purposes
  • Periodically review ingestion patterns to ensure filters remain aligned with operational needs and cost targets
Submit Feedback