Crates.io | tracing-logrotate |
lib.rs | tracing-logrotate |
version | 0.1.0 |
created_at | 2025-08-17 09:04:06.024203+00 |
updated_at | 2025-08-17 09:04:06.024203+00 |
description | tracing logfile writer with rotation and expiry |
homepage | |
repository | https://salsa.debian.org/dgit-team/tag2upload-service-manager |
max_upload_size | |
id | 1799255 |
size | 62,339 |
Improved replacement for tracing_appender::rolling
Like tracing_appender::rolling
but:
rotate
not the unidiomatic roll
.*.log
.Appender
.Debian's tag2upload-service-manager
uses rocket
so we tried to use tracing
for logging.
However, we have come to the conclusion that tracing
is not fit for purpose.
One of the biggest issues is that the model is not documented.
The composition of the various pieces is confusing, and, we strongly suspect, not fully coherent.
See
#2141;
this also seems to be generating many bug reports from confused users
who haven't analysed the situation as thoroughly as was done there.
For this reason, we don't want to try to have multiple Subscriber
s
or try to use Layer
s.
Instead, we do all the level filtering directly, here.
We tried using RollingFileAppender
but tripped over a bug
that broke the tests:
it doesn't rotate logfiles until the first entry is written
(#2937).
Other tickets in the upstream tracker aren't encouraging,
eg #1932.