Docs menu

From the open engine’s docs (traza 0.28.0), index generated. Engine routes reach a Traza Cloud project through the gateway.

Operations

Every page in the engine’s docs/operations/ directory.

  • Administration — Authentication, retention, compaction, and payload offloading — the things you configure once and then live with. Flag syntax and defaults are in the configuration reference;…
  • Backup and restore — Backup is pin, verify, copy — with the server running. Restore is install. Both are the same mechanism seen from two ends: a generation, which is one immutable, self-describing…
  • Capacity and performance — Provenance, stated per source rather than as a blanket claim.
  • Deployment — One process, one data directory, one port. There is no database to provision, no queue to run in front, and no coordinator. traza-server links the storage engine directly; the…
  • Durability — An acknowledged write means what –durability says it means — no more, and no less. The mode is chosen per deployment, announced at startup, echoed in every ingest response, and…
  • Monitoring — Two endpoints. GET /v1/metrics is the Prometheus scrape; GET /v1/stats is the store’s own summary and the natural health check.
  • Object-storage snapshot archive (preview) — The archive publishes a verified pin — the same immutable file set backup produces — to S3-compatible object storage as one explicitly named, immutable snapshot, and reads it…