We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
We feed ntpd-rs' logs into a log search product.
While it works, it contains ansi escape codes.
For example,
#033[2m2024-10-31T18:38:56.000846Z#033[0m #033[32m INFO#033[0m #033[2mntp_proto::algorithm::kalman#033[0m#033[2m:#033[0m Offset: -0.098332274256776+-0.2337313649729611ms, frequency: 0.04341250045413119+-0.07468081620691763ppm
While this is tolerable, and we could probably even post-process the logs, it would be nice to be able to opt-out of this.
I think in ntpd/src/daemon/tracing.rs, in tracing_init, we'd want a way to set .with_ansi(false) in the same way as the level filter.
ntpd/src/daemon/tracing.rs
tracing_init
.with_ansi(false)
The text was updated successfully, but these errors were encountered:
No branches or pull requests
We feed ntpd-rs' logs into a log search product.
While it works, it contains ansi escape codes.
For example,
While this is tolerable, and we could probably even post-process the logs, it would be nice to be able to opt-out of this.
I think in
ntpd/src/daemon/tracing.rs, intracing_init, we'd want a way to set.with_ansi(false)in the same way as the level filter.The text was updated successfully, but these errors were encountered: