udp-logger-rs
Log macro for log's kv-unstable backend.
Motivation
I wanted to build key/value context into my structs and log it when logging within an impl fn. Beyond that, I also wanted to separate the responsiblity of logging from log file management and any associated business logic.
Consider an architecture with multiple containers running on the same host. One being a server, the other being a log processor. Through this separation, the server performs logging and is insulated from the processing of that logging. Meanwhile, the log processor determines how log messages are processed, which can itself become quite complex.
Additionally, I decided that one might want to map the log level to a source port, and/or destination port. The thought here is that it might simplify processing, as the source and/or destination port implies the log level.
Finally, by separating them, server development can use a different log processor than production and production log processing can be tested independent of the server.
Examples
use info;
The UDP client can be as trivial as:
use Async;
use ;
use UdpSocket;
Installation
Safety
This crate uses #![forbid(unsafe_code)]
to ensure everything is implemented in
100% Safe Rust.
Contributing
Want to join us? Check out our "Contributing" guide and take a look at some of these issues:
References
None.
License
MIT OR Apache-2.0