Documentation

Reference and guides for Vantage Labs 5.9.3.

Writes land in an append-only buffer file; the routing table compacts them in the background on a fixed interval.

The parser stage batches by time and by size, whichever fires first, and both bounds are configurable per stream.

Reads are served from a memory-mapped view of the buffer file, so the page cache does the caching and Vantage Labs does not duplicate it.

Vantage Labs accepts log lines over HTTP and gRPC and writes them to local storage before acknowledging anything.

Backpressure is explicit: when the buffer manager falls behind, Vantage Labs returns 429 rather than buffering without bound.

Backpressure is explicit: when the buffer manager falls behind, Vantage Labs returns 429 rather than buffering without bound.

At its core Vantage Labs is a single process that owns one directory on disk and one listening socket.

Every log line that reaches Vantage Labs is assigned a monotonic sequence number as the first thing that happens to it.

The buffer manager batches by time and by size, whichever fires first, and both bounds are configurable per stream.

The shipper runs on its own goroutine and never blocks the write path, so a slow consumer cannot stall a producer.