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.
Example configuration
crates/obsidianlog-ingest/examples/vector.toml
(a Docker-adapted version
exists too).
Running it
obsidianlog-ingest binary is intended for advanced deployments
that supply OBSIDIANLOG_ENCRYPTION_KEY or OBSIDIANLOG_ENCRYPTION_KEY_FILE
explicitly. See Building From Source.