Log Search Scan Cost Calculator

Some log products charge for data scanned during queries. This calculator estimates monthly scan cost using your daily scanned GB and per-GB scan price, and lets you compare baseline vs peak query volume.

Maintained by CloudCostKit Editorial Team. Last updated: 2026-01-29. Editorial policy and methodology.

Best next steps

Use this calculator for the first estimate, then validate the answer with the closest guide or companion tool.

Log ingestion cost Log retention storage CloudWatch Logs Insights scan cost Guide: log costs

Inputs

GB scanned (per day)
Avg 74.07 Mbps scanning, 0.0093 GB/sec.
Scan price ($ / GB)
Queries (per day)
Avg GB per query
Est 300 GB/day.

Results

Monthly scan volume (est.)
24,320 GB
Estimated monthly scan cost
$121.60
Cost per GB scanned
$0.01 / GB

Scan cost is driven by query behavior, not just stored volume

Search and scan bills often surprise teams because stored logs feel passive, but dashboards, alerts, and ad hoc debugging turn them into an active, recurring workload. This page should be read as a model of query behavior, not just a model of retained bytes.

  • Automated queries: dashboards, alerts, and scheduled searches create the calm-month baseline.
  • Ad hoc investigations: incident response creates the expensive peak.
  • Main lever: query window size and refresh cadence often matter as much as data volume.

Where scan estimates usually drift

  • Teams model ingestion and retention but forget that dashboards are quietly scanning all day.
  • Average query scope is guessed without listing the top searches or their refresh cadence.
  • Incident-heavy search months are blended into the normal baseline.
  • Wide time windows and low-selectivity filters make search more expensive than users expect.

What to review before trusting the scan baseline

  • List the top dashboards and scheduled queries before estimating ad hoc usage.
  • Separate automated scan load from human troubleshooting and incident response.
  • Check whether query windows can be narrowed or pre-aggregated instead of scanning raw history each time.
  • Keep ingestion and retention adjacent, but separate, so you know whether search is truly the dominant problem.

Baseline vs incident-driven search scenarios

Scenario GB scanned/day Query scope Drivers
Baseline Expected Normal Dashboards
Peak High Wide Incident

How to review the first real scan-heavy month

  • Check billed scanned GB against dashboard cadence and incident query history before changing ingestion assumptions.
  • Review whether a few expensive queries or a broad automated baseline caused most of the bill.

Next steps

Guides All calculators Log ingestion cost Log retention storage CloudWatch Logs Insights scan cost Guide: log costs

Example scenario

  • 800 GB/day scanned at $0.005/GB = ~24,320 GB scanned/month and ~$122/month.
  • Compare baseline vs peak query months to understand scan cost risk.

Included

  • Scan cost estimate from GB scanned per day and $/GB scan pricing.
  • Useful when query scans are a meaningful line item on your log bill.

Not included

  • Ingestion charges and retention storage (model separately).
  • Provider-specific query minimums, caching, and index behavior.

How we calculate

  • Monthly scanned GB ~ GB scanned per day x 30.4.
  • Scan cost = monthly scanned GB x scan price per GB.
  • Use a peak multiplier when incident dashboards or wide queries spike scans.
  • This tool is scan-only (not ingestion or retention).

FAQ

How do I estimate GB scanned per day?
Use provider query/scan metrics, or approximate from typical query patterns and dataset size.
How do I reduce scan costs?
Limit time ranges, filter early, partition logs, and avoid dashboards that repeatedly run broad queries.

Related tools

Log ingestion cost Log retention storage CloudWatch Logs Insights scan cost Guide: log costs Guide: Logs Insights pricing Guide: estimate scanned GB Guide: reduce scan costs

Related guides

AWS CloudWatch Metrics Pricing & Cost Guide
CloudWatch metrics cost model: custom metrics, API requests, dashboards, and retention.
Cloud cost estimation checklist: build a model Google (and finance) will trust
A practical checklist to estimate cloud cost without missing major line items: requests, compute, storage, logs/metrics, and network transfer. Includes a worksheet template, validation steps, and the most common double-counting traps.
CloudWatch dashboards pricing: what to include (dashboard-month + API)
A practical guide to CloudWatch dashboard costs: dashboard-month charges plus the hidden drivers (metrics API requests, alarms, and high-cardinality metrics).
CloudWatch Logs Insights cost optimization (reduce GB scanned)
A practical playbook to reduce CloudWatch Logs Insights costs: measure GB scanned, fix query patterns, time-bound dashboards, and avoid repeated incident scans.
CloudWatch Logs Insights pricing: what to model (GB scanned)
A practical Logs Insights pricing checklist: the core unit is GB scanned. Model scanned GB from query habits, avoid dashboard re-scan traps, and validate with a measured baseline.
CloudWatch Logs pricing: ingestion, retention, and queries
A practical CloudWatch Logs pricing guide: model ingestion (GB/day), retention (GB-month), and query/scan costs (Insights/Athena). Includes pitfalls and a validation checklist.

Disclaimer

Educational use only. Not legal, financial, or professional advice. Results are estimates based on the inputs and assumptions shown on this page. Verify pricing and limits with your providers and documentation.

Last updated: 2026-01-29. Reviewed against CloudCostKit methodology and current provider documentation. See the Editorial Policy .