GCP Cloud Logging cost: you pay per GB ingested

Quick answer

Cloud Logging charges about $0.50 per GB ingested after a 50 GB monthly free allowance, plus a retention charge for logs kept beyond the default retention. Cost tracks log volume, so exclusion filters that drop noisy logs before ingestion, and not storing what you will not query, are the main levers.

Cloud Logging aggregates logs from your GCP resources and applications, and you pay for the volume ingested. A generous free allowance covers small projects, but chatty applications and verbose infrastructure logs push past it quickly, and the fix is deciding what is worth ingesting.

Ingestion is the bill

After 50 GB per month free, ingested logs cost about $0.50 per GB. The default logs bucket retains logs for a set period included in the price; retaining longer, or using custom buckets with extended retention, adds cost. Volume, driven by how much your systems log, is the main variable.

Exclusion filters are the main lever

Cloud Logging lets you write exclusion filters that drop matching log entries before they are ingested and billed. High-volume, low-value logs, health-check requests, verbose debug lines, chatty load-balancer logs, are prime candidates. Excluding them cuts ingestion directly, which is the highest-impact control.

Route, sample, and retain deliberately

Lever	Effect
Exclusion filters	Drop noisy logs before ingestion
Sampling high-volume logs	Keep a representative subset
Route to cheaper storage	Sink to Cloud Storage or BigQuery for archives
Shorter retention	Avoid extended-retention charges

The same discipline applies as with CloudWatch Logs and Log Analytics: ingest what you will actually query, exclude or sample the noise, and route archives to cheaper storage rather than paying logging rates to keep them.

FAQ

How is GCP Cloud Logging priced?

About $0.50 per GB ingested after a 50 GB monthly free allowance, plus a retention charge for logs kept beyond the default retention. Cost tracks log volume, so how much your systems log drives the bill.

How do I reduce Cloud Logging cost?

Write exclusion filters to drop high-volume, low-value logs (health checks, verbose debug, chatty load-balancer logs) before ingestion, sample high-volume logs, route archives to cheaper storage like Cloud Storage or BigQuery, and keep retention no longer than needed.

What are Cloud Logging exclusion filters?

Filters that drop matching log entries before they are ingested and billed, so noisy, low-value logs never count toward the per-GB charge. They are the highest-impact cost lever, since they cut ingestion at the source rather than after the fact.

Does Cloud Logging retention cost extra?

The default logs bucket includes a set retention in the price. Retaining logs longer, via custom buckets with extended retention, adds cost. Keep retention to what you actually need, and route long-term archives to cheaper storage instead of paying logging rates.

Why did my Cloud Logging bill spike?

Usually a jump in ingested volume: a new verbose logging path, a burst of errors, or chatty infrastructure logs. Check the ingestion breakdown by resource and log name, then add exclusion filters or sampling for the high-volume, low-value sources.

Does C3X estimate Cloud Logging cost?

Cloud Logging cost is driven by ingested volume, a usage input. C3X prices the surrounding GCP infrastructure, and you model log volume to estimate the per-GB ingestion charge.

What to do next

Estimate the infrastructure behind your logging before you deploy. C3X reads your Terraform and prices your resources against a live catalog. Start with the quickstart.