Log storage & retention
How Sazabi stores the data you send — managed storage, the retention window, the region your project uses, and how data leaves.
Sazabi stores the data you send in managed log storage and queries it for you during investigations. There is no storage backend to choose, provision, or tune: you connect sources, and Sazabi handles intake, indexing, retention, and query optimization.
Where your logs live
Every project uses Sazabi-managed storage. Logs, metrics, traces, and events all land in the same place as searchable records, so the agent has one place to look. You do not provision a cluster, maintain schemas, or route the agent to a separate system.
Retention
How long records are kept depends on your plan — different plans include different retention periods. See the pricing page for the retention each plan includes. Records older than your plan's retention window are removed automatically during routine cleanup, and retention changes apply going forward, not retroactively.
Regions
You choose a region when you create a project, and your data is stored in that region. Pick the region closest to where your systems run, or the one your compliance needs require. See Choosing a region for the available regions and how to decide.
How the agent queries your data
When you investigate, the Sazabi agent searches your stored records directly — full-text search, structured filtering by attributes, and time-series analysis — without you writing a query language. See Log search for how the agent uses stored data as evidence.
How data leaves
- Retention expiry. Records age out of storage automatically at the end of the retention window.
- Deleting a stream. Deleting a log stream stops future ingestion; records already stored remain until they age out. See Manage log streams.
- Deleting a project. Removing a project removes its stored data.