First of all thanks for sharing this really helpful crate. We have used it in the past to publish metrics to DataDog and after we migrated to New Relic, we are still benefiting from the dogstatsd crate.
On several locations, the library writes errors to stdout using the println! macro, example:
|
println!("Exception occurred when writing to channel: {:?}", error); |
Can these error logs be removed? These error logs are polluting our logs in certain scenarios.
In several occurrences, instead of logging the errors, the errors can be returned to the caller so that the caller can decide what to do with the errors. Or perhaps the error logs can be gated behind a Rust feature flag so they’re only emitted when the feature is enabled?
First of all thanks for sharing this really helpful crate. We have used it in the past to publish metrics to DataDog and after we migrated to New Relic, we are still benefiting from the dogstatsd crate.
On several locations, the library writes errors to stdout using the println! macro, example:
dogstatsd-rs/src/lib.rs
Line 966 in b1c936f
Can these error logs be removed? These error logs are polluting our logs in certain scenarios.
In several occurrences, instead of logging the errors, the errors can be returned to the caller so that the caller can decide what to do with the errors. Or perhaps the error logs can be gated behind a Rust feature flag so they’re only emitted when the feature is enabled?