Extend A Logger

Start from an Example flow, then add one extension at a time. These pages explain when an abstraction is useful and which operational boundary it introduces.

Extension Map

Need	Extension	Main trade-off
Absorb short output bursts	Queueing	You must choose overflow and flush behavior.
Send records to multiple destinations or route by level	Sink composition	More explicit construction than presets.
Control terminal appearance	Text formatting	Formatting affects presentation, not record structure.
Share code across native and web targets	Target boundaries	File and async runtime behavior differ by backend.
Correlate logs with distributed requests	Trace context	Propagation and export stay application-owned.

For exact function signatures, follow each page's links into the API reference.