obsidianlog serve - ObsidianLog

This starts the HTTP ingest server using the encryption key and backend configuration obsidianlog init created. It runs in the foreground until stopped (Ctrl-C, or the process is otherwise shut down).

Flags

Flag	Description
`--bind <ADDR>`	Address to bind the HTTP ingest endpoint to. Overrides the value in `config.toml`.

Plus the global --config <FILE>.

Endpoints

Route	Method	Purpose
`/ingest`	`POST`	Accepts a JSON array of log events. Write-then-ack: returns `200` only after a durable, encrypted, hash-chained write, and `5xx` on failure, so an upstream shipper’s retry logic just works.
`/health`	`GET`	Liveness check.

/ingest has no request authentication. It’s designed to sit behind a trusted network boundary (e.g. bound to 127.0.0.1, or reached only by Vector on the same host/private network). See Security Model.

Example

obsidianlog serve
obsidianlog serve --bind 0.0.0.0:7080 --config /etc/obsidianlog/config.toml

Send it a batch:

curl -s -X POST http://localhost:7080/ingest \
  -H 'content-type: application/json' \
  -d '[{"timestamp":"2026-07-06T10:00:00Z","service":"api","level":"info","msg":"hello"}]' \
  -w '%{http_code}\n'

A successful ingest has an empty body, so -w is what actually prints something, a 200 on its own line. Without it, a successful request looks identical to a hung one: no output either way. See Sending Logs with Vector to ship real logs instead of a one-off curl.