Skip to main content

Crate tael_server

Crate tael_server 

Source
Expand description

tael-server: OTLP ingest, tiered storage, and the REST/gRPC query API.

Shipped as a library so the tael binary can embed it behind tael serve (a single cargo install), while still being usable as a standalone crate. run is the default CLI-style entrypoint; run_embedded starts the same server in quiet mode for in-process integrations. ServerConfig configures the listeners and storage.

Structs§

BlobStore
A content-addressed blob store over a pluggable object backend.
FanoutStore
A Store that scatters reads across N shard stores and gathers/merges the results. See the module docs for routing vs. fan-out semantics.
LogRecord
MetricPoint
RemoteStore
A Store backed by another tael-server’s REST API over HTTP.
RemoteWalSink
ServerConfig
ServerRunOptions
Options for running the server process beyond listener/storage config.
Span
SpanEvent
TaelBackend
TraceQuery

Enums§

LogSeverity
MetricType
ServerOutputMode
Controls output that the tael-server library owns directly.
SpanKind
Span kind. Mirrors the OpenTelemetry SpanKind, plus a synthetic Llm variant that marks spans carrying a typed [LlmSpan] extension.
SpanStatus
StorageBackend
Selected storage backend. TaelBackend (the purpose-built tiered engine) is the default; pass --storage duckdb or set TAEL_STORAGE=duckdb to use the legacy embedded-DuckDB backend instead.

Traits§

Store
Storage backend for all telemetry signals. The server depends on Arc<dyn Store>, so backends (DuckDB today, TaelBackend next) are swappable without touching the API, ingest, or query layers.
WalSink
A replication target for the WAL. The leader hands each appended record’s framed bytes (the wire format below) to every registered sink before its write returns — the replicate-before-ack guarantee that lets a standby survive the leader’s loss, not just its crash (docs/tael-server-scaling-ha.md §5.1). A sink’s append_framed must only return once the record is durable at the sink (a standby ack, an fsync).

Functions§

run
Start the server with the default user-facing output behavior.
run_embedded
Start the server in quiet mode for in-process integrations.
run_with_options
Start the server with explicit run options.