Agent durability
The agent buffers locally and never guesses about someone else's data.
When the brain is unreachable the agent buffers events to local storage and drains them on reconnect, so a control-plane outage costs you visibility rather than history. The buffer is deliberately conservative about what it adopts: each process generation writes its own sealed file, and only a buffer it can prove belongs to this deployment and is exclusively held gets recovered automatically. Anything foreign, unreadable, incomplete, or unlockable is left exactly where it is for a human to look at, because silently draining a file that might belong to another process is worse than leaving it alone.
Ships with
- Events buffer locally when the brain is unreachable and drain on reconnect
- Each process generation seals its own buffer before examining older ones
- Only an exclusively held, same-deployment buffer is recovered automatically
- Foreign or unreadable buffers are left in place, never emitted and never deleted
- On filesystems that cannot lock reliably, the agent relocates to a private path and logs it rather than refusing to start
Highlights
- The agent never blocks or crashes the application it runs inside
- A second independent lock probe catches filesystems where locking silently does nothing
Related