Implemented in the documented source
Implemented · Release forthcoming
- Worker-backed stream, file, rotation, socket, and HTTP output.
- Named logger hierarchy, restricted configuration, and callback filtering.
- Inline structured fields and scoped context through named loggers.
- Rust log/tracing bridges behind optional features.
The next assumed release is 0.2.0-beta1. These statements describe revision f5bcaa8, not an already published beta.
Planned work
Planned · No delivery date
- Formatter registration. Named formatter identifiers that resolve to working formatters, not exported placeholders.
- Batching. Handler-side batches that amortize transport cost without hiding drops or reordering.
- Benchmark reporting. Published results backed by runnable artefacts and workload metadata.
- Observability exporters. Journald and OpenTelemetry sinks, configured explicitly. The tracing bridge is a separate capability.
Read the upstream roadmap at the documented revision. Check the live roadmap for subsequent progress.
What-ifs from the field station
Exploratory · Ideas in the petri dish
The cultures below are design questions, not commitments. Each names what would have to be proven before it could become planned work.
Exploratory · Culture 01
Context that follows the task
A contextvars-backed scope could keep fields isolated across awaits. It needs cancellation, nesting, and bridge-boundary tests before replacing thread-local context.
Exploratory · Culture 02
Batches with an accountable boundary
A batch-aware handler could amortize transport cost. Ordering, partial failure, flush barriers, and overflow accounting must remain explicit.
Exploratory · Culture 03
A closer instrument view
A future inspection surface could expose queue pressure without inventing durability guarantees. Any visualization must report observed counters and their scope.
The concepts suggest alternative futures. They do not set release promises.