# Duplicate storage of logs in Cloud Logging | Cloud Efficiency Hub Canonical: https://www.pointfive.co/efficiency-hub/inefficiencies/duplicate-storage-of-logs-in-cloud-logging-bd625 Duplicate log storage occurs when multiple sinks capture the same log data - for example, organization-wide sinks exporting all logs to Cloud Storage... By: Yuval Goldstein Updated: 2026-09-28 [Cloud Efficiency Hub](https://www.pointfive.co/efficiency-hub) # Duplicate Storage of Logs in Cloud Logging The short version Duplicate log storage occurs when multiple sinks capture the same log data - for example, organization-wide sinks exporting all logs to Cloud Storage and project-level sinks doing the same. Yuval Goldstein GCP service [GCP Cloud Logging](https://www.pointfive.co/efficiency-hub/cloud-services/gcp-cloud-logging) Category [Other](https://www.pointfive.co/efficiency-hub/service-category/other) Reference CER-0241 Type Inefficient Configuration ## Explanation Why the waste happens and who it affects. This redundancy results in paying twice (or more) for identical data. It often arises from decentralized logging configurations, inherited policies, or unclear ownership between teams. The problem is compounded when logs are routed both to Cloud Logging and external observability platforms, creating parallel ingestion streams and double billing. ## Billing model The pricing dimensions that drive this cost. Cloud Logging charges a one-time storage fee per GiB of log data streamed into each log bucket (this includes 30 days of retention), plus a per-GiB-month retention charge for logs kept longer than 30 days. Routing logs through sinks is not charged, and logs in the \_Required bucket are free. When sinks with overlapping filters send the same entries to more than one log bucket, each copy is billed, and copies routed to Cloud Storage, BigQuery, Pub/Sub or an external platform are billed by that destination. These costs scale linearly with the number of redundant destinations. ## How to detect 4 checks to find it in your estate. - Analyze log sink filters across projects, folders, and the organization to identify overlapping export scopes - Review log destinations to confirm whether the same log types are stored in multiple buckets or BigQuery datasets - Assess whether central and project-level teams maintain independent sinks that duplicate the same data - Determine if redundant routing exists between Cloud Logging and external observability or SIEM platforms ## How to fix 4 ways to remove the waste. - Consolidate log routing and ensure filters define mutually exclusive export scopes - Remove or disable redundant sinks that replicate the same logs to multiple destinations - Implement centralized governance for sink management to avoid overlapping configurations across projects - Periodically audit all sinks at the organization level to ensure routing remains efficient and non-duplicative ## Documentation Vendor references for pricing and configuration. - [Route logs to supported destinations docs.cloud.google.com](https://docs.cloud.google.com/logging/docs/export/configure_export_v2) - [Google Cloud Observability pricing cloud.google.com](https://cloud.google.com/products/observability/pricing) - [Route log entries docs.cloud.google.com](https://docs.cloud.google.com/logging/docs/routing/overview) ## Related inefficiencies [Browse the library](https://www.pointfive.co/efficiency-hub) - GCP Cloud Logging CER-0262 ### [Suboptimal Storage for Logs](https://www.pointfive.co/efficiency-hub/inefficiencies/suboptimal-storage-for-logs-fd1d9) Many organizations retain all logs in Cloud Logging's standard storage, even when the data is rarely queried or required only for audit or compliance. Log bucket cost comes mainly from the per-GiB storage charge applied when logs are... Other - GCP Cloud Logging CER-0253 ### [Resources Generating Excessive INFO Logs](https://www.pointfive.co/efficiency-hub/inefficiencies/resources-generating-excessive-info-logs-6c920) Some GCP services and workloads generate INFO-level logs at very high frequencies - for example, load balancers logging every HTTP request or GKE nodes logging system health messages. While valuable for debugging, these logs can flood... Other - GCP Cloud Logging CER-0245 ### [Logging Buckets in Non-Production Environments Storing Info Logs](https://www.pointfive.co/efficiency-hub/inefficiencies/logging-buckets-in-non-production-environments-storing-info-logs-1edcf) 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... Other --- Source: the public page above. Product screenshots and illustrative interfaces are examples, not live customer data.