ddidderr
7aeaa0aeb9
Add the observability vocabulary needed for phase-1 frame logging and client status reporting. Runtime crates can now emit structured events without each binary inventing separate field names for the same tunnel state. The new models cover frame direction, action, drop reason, parsed Ethernet frame logs, malformed frame logs, tunnel counters, relay/QUIC/TAP client diagnostics, and user-facing diagnostic messages. TunnelStats now lives in lanparty-obs and is re-exported by lanparty-ctrl so stats remain one shared type whether they are logged locally or carried over the control stream. This still does not add logging sinks or tracing integration; those should be wired in when the relay, gateway, and client loops exist. Test Plan: - cargo fmt --check - cargo test --workspace - cargo clippy --workspace --all-targets -- -D warnings Refs: PLAN.md Logging / diagnostics
11 lines
241 B
TOML
11 lines
241 B
TOML
[package]
|
|
name = "lanparty-ctrl"
|
|
version.workspace = true
|
|
edition.workspace = true
|
|
|
|
[dependencies]
|
|
lanparty-obs = { path = "../lanparty-obs" }
|
|
lanparty-proto = { path = "../lanparty-proto" }
|
|
serde.workspace = true
|
|
thiserror.workspace = true
|