Tiered Log Storage Cost Calculator (Hot + Archive)

How to use this in a real estimate

• Split logs into classes (access/app/audit) and decide what you actually need to retain long-term.
• Keep a small hot window for troubleshooting and dashboards; archive only what you must.
• Validate what the vendor bills for cold tiers (stored bytes vs ingested bytes, plus retrieval charges).

Log storage is mostly a retention-policy problem

This page is less about raw ingestion math and more about policy design. Once logs exist, storage cost is shaped by how long they stay hot, how much moves cold, and whether archive really means low-cost retained evidence or an expensive pile of data nobody reads until an incident.

• Hot window: expensive but immediately searchable retention for active troubleshooting.
• Cold window: longer-lived retained data with different access expectations.
• Archive fraction: only the log classes that truly need long memory should survive into cold storage.

Where storage estimates usually drift

• Every log class gets archived by default, even when debug or low-value logs have no long-term use.
• Hot retention days are mistaken for total retention policy, hiding the cold-storage footprint.
• Compression and billed stored-bytes rules are guessed instead of checked against vendor behavior.
• Retrieval or rehydration events are ignored until an investigation month creates a second storage bill.

What to review before trusting storage policy

• Split audit, security, application, and debug logs before choosing archive fraction.
• Confirm which days are truly hot-searchable versus merely retained for compliance or forensics.
• Check whether your vendor bills on ingested bytes, stored bytes, or compressed cold bytes.
• Model retrieval-sensitive months separately if cold data is actually read during incidents or audits.

Baseline vs archive-policy scenarios

How to review the first real storage month

• Confirm hot retention days and archive fraction in actual policy settings, not just in planning docs.
• Validate billed stored GB against the vendor's storage-billing rules before changing retention assumptions.
• Track retrieval or rehydration charges separately after audit- or incident-heavy months.