| Crates.io | ya-packet-trace |
| lib.rs | ya-packet-trace |
| version | 0.1.0 |
| created_at | 2023-05-23 07:37:01.426739+00 |
| updated_at | 2023-05-23 07:37:01.426739+00 |
| description | Utility library for tracking VPN packets in yagna |
| homepage | https://github.com/golemfactory/ya-packet-trace |
| repository | https://github.com/golemfactory/ya-packet-trace |
| max_upload_size | |
| id | 871774 |
| size | 67,504 |
Utility for tracing VPN packets
At any interesting point in the flow of VPN packets, invoke the macro like so:
packet_trace!(
"possibly-slow-subsystem-before",
{
// code returning AsRef<[u8]> corresponding to the packet payload
}
);
packet_trace_maybe!(
"whatever",
{
// code returning Option<AsRef<[u8]>> corresponding to the packet payload
}
);
Then, if the ya-packet-trace is compiled with the enabled feature, a log like
possibly-slow-subsystem-before,<HASH>,<TS> will be printed at TRACE level
to target packet-trace.
<HASH> is 16-character, 0-padded hex-digest of FxHash output<TS> is current datetime as formatted by chrono
with the following format string: %Y-%m-%dT%H:%M:%S%.6f%z.