By default, non blocking appenders are lossy. Should the crate documentation call this out explicitly?
The crate docs are enough to get a working example, but it misses an important caveat. Silently, losing logs in a production environment is hard to diagnose, and should not be a default.
Further programs using asynchronous logging are probably fast enough where they might be silently running into this scenario.
Proposal
Add another Note beside the current note for WorkerGuard.
Note: non_blocking appenders are lossy by default and will drop events once internal buffers are filled. See non_blocking module for more details.
Alternatives
lossy may be disabled by default, but this might cause regression in environments where log loss actually occurs.
Feature Request
Crates
tracing-appender
Motivation
By default, non blocking appenders are lossy. Should the crate documentation call this out explicitly?
The crate docs are enough to get a working example, but it misses an important caveat. Silently, losing logs in a production environment is hard to diagnose, and should not be a default.
Further programs using asynchronous logging are probably fast enough where they might be silently running into this scenario.
Proposal
Add another Note beside the current note for WorkerGuard.
Alternatives
lossy may be disabled by default, but this might cause regression in environments where log loss actually occurs.