The data path
Tap a node to see what it does.
Ten ingest protocols. OTLP HTTP/gRPC are first-class; Vector, Fluent Bit, Prometheus remote_write, Loki push, Splunk HEC, Jaeger, Zipkin, and Syslog all land on the same write path.
Tap or hover a node to see what it does.
Three signals, one storage
Logs, metrics, and traces all serialize to Parquet on object storage. The columnar layout makes cross-signal filters and time-range prunes cheap.
Query engine
DataFusion plans SQL, PromQL, and VRL against Parquet. The planner does multi-tenant org-rewrite, so tenant isolation lives at the query layer rather than at the deployment layer.
Ingest protocols
Ten supported on day one: OTLP HTTP, OTLP gRPC, Vector, Fluent Bit, Prometheus remote_write, Loki push, Splunk HEC, Jaeger, Zipkin, Syslog.
- OTLP HTTPOpenTelemetry Protocol over HTTP/JSON
- OTLP gRPCOpenTelemetry Protocol over gRPC
- VectorVector source
- Fluent BitFluent Bit OTel/HTTP
- Prometheusremote_write (PromQL native query)
- Loki pushLoki-compatible push API
- Splunk HECSplunk HEC tokens
- JaegerJaeger thrift/proto
- ZipkinZipkin v2 JSON
- SyslogRFC5424 over UDP/TCP/TLS
Real-time alerts
Alerts with kind: realtime evaluate inline against the write path. Under 1 second from event to page.
Multi-tenancy
Tenants are rewritten at planner time. One process serves many orgs without prefix isolation hacks.
Performance
Benchmarks land with v1.0. Methodology: TSBS for metrics, custom log/trace harness against 1 TB/day. Track the work in the Roadmap.
Open questions
We're still figuring out cardinality limit policies for high-dimensional labels, and Parquet rotation under spiky ingest. If you're stuck on either, become a Design Partner.