Skip to content
LogluneconsoleSign in

Data

Your retention and portability controls: prune versions you no longer keep, read the full change and reproduction history, and export everything Loglune holds for this tenant.

Prune old versions

Drop every non-pinned version below a cutoff and its stored copy. Pinned versions are always kept. Retention is your choice — Loglune fixes no period; your contract governs how far back to keep.

Change history

#WhenWhoChange
12026-08-01 09:00 UTCjordan@example.comCreated flag checkout-v2
22026-08-01 09:00 UTCjordan@example.comCreated segment beta-users
32026-08-01 09:00 UTCjordan@example.comCreated config checkout-timeout-ms
42026-08-08 14:30 UTCsam@example.comUpdated flag checkout-v2
52026-08-08 14:30 UTCsam@example.comCreated flag new-pricing
62026-08-20 11:15 UTCjordan@example.comUpdated flag checkout-v2
72026-08-20 11:15 UTCjordan@example.comUpdated config checkout-timeout-ms

To change what is live now, edit it in Author; to see or compare the state a version shipped, use Overview.

Reproductions · 2026-08

WhenVersionReproduction IDActions
2026-08-24 10:05 UTCVersion 3ex-repro-1
2026-08-22 16:40 UTCVersion 3ex-repro-2
2026-08-19 08:12 UTCVersion 2ex-repro-3

Export tenant data

Download everything Loglune holds for this tenant — the full change log, every published version, and each version’s resolved ruleset — as one portable JSON bundle. Read-only; it changes nothing and is never billed.

Erase tenant data

Delete every surface Loglune holds for this tenant — the change log, all versions and their stored copies, reproduction history and counters, SDK and operator credentials, the Slack connection, and the AI ledger with its proposed diffs. Pinned versions go too: a pin excludes a version from pruning, it is not a veto on an explicit erasure. This cannot be undone, so export first if you want the data back. Type erase to confirm.