Observability
Unified Log Plane
Structured events land on a lock-free shared-memory ring and stream into a dedicated writer daemon for delivery to the observability stack of your choice.
GA
HOW IT WORKS
Walk through a single flow
- 1The engine publishes events to a single-producer, single-consumer shared-memory ring.
- 2A dedicated log-plane worker drains the ring and delivers to the configured sinks.
- 3A write-ahead log and checksum validation guarantee durability across restarts.
- 4Under backpressure, adaptive sampling preserves high-priority events first; a circuit breaker isolates misbehaving sinks from the hot path.
UNDER THE HOOD
Technical notes
Sinks available today
File, syslog, SQLite, and Elasticsearch destinations ship today. Additional destinations — including message-broker and compressed object-store exports — are on the near-term roadmap.
Operational isolation
The log plane exposes its own telemetry surface and runs fully out of the inspection path. A slow destination cannot back-pressure the engine.
RELATED