Configure

Logpacer is configured by intent, not by pipeline. You don't write per-source rules, size indexes, or tune sampling. Two questions — how long to keep data, which compliance frameworks you report against — and everything downstream follows.

Retention

Set a single retention window. Storage is managed and compression runs by default, so a long window stays affordable — you aren't trading retention against cost. Retention is a window, not a sampling rate. Nothing inside it is thinned or dropped.

Compliance presets

Pick the frameworks you answer to — GDPR, ISO 27001, SOC 2, CFCS — and the relevant log categories are grouped, with tags carried through to retention and audit. Presets organise and document your coverage. They don't make collection decisions on your behalf, and they don't replace your own compliance judgement.

A preset maps to log categories across families — application, system, access, network, and the rest — so whether you're covering what a framework expects becomes a legible answer instead of a spreadsheet exercise.

The audit trail

Whatever you collect lands in immutable storage. The audit trail can't be quietly rewritten after the fact — not even by your own engineers. Configuration is where you decide what "kept and provable" means for your estate; the rest of Logpacer enforces it.