Skip to main content
ObsidianLog’s ingest endpoint is Vector-compatible: Vector reads your logs, then its HTTP sink POSTs them (as a JSON array) to the ObsidianLog ingest server. ObsidianLog uses write-then-ack. It returns 200 only after a durable, encrypted, hash-chained write, and 5xx on failure, so Vector owns buffering, backpressure, and retry. A 5xx is simply retried. This page is the config reference for a real, ongoing deployment. Want to see it proven end to end first, a scratch test file, a real Vector run, and the archived data queried back, before wiring up a production config? See Trying Out Vector.

Example configuration

The full example lives at crates/obsidianlog-ingest/examples/vector.toml (a Docker-adapted version exists too).

Running it

Vector needs its data_dir folder (set in the config above) to already exist, create it once before the first run.
See obsidianlog serve for the endpoints Vector’s sink talks to. The standalone obsidianlog-ingest binary is intended for advanced deployments that supply OBSIDIANLOG_ENCRYPTION_KEY or OBSIDIANLOG_ENCRYPTION_KEY_FILE explicitly. See Building From Source.