feat: add structured control tracing
This commit is contained in:
parent
63ea36bb51
commit
d9031b995d
4 changed files with 477 additions and 9 deletions
|
|
@ -444,6 +444,13 @@ not reachable. It checks config parsing, local daemon socket health,
|
|||
validity, and representative peer grants when local metadata is available. Use
|
||||
`--json` for scripts.
|
||||
|
||||
Daemon logs are emitted through `tracing` and are controlled with standard
|
||||
`RUST_LOG` filters. Local control requests log structured fields for command,
|
||||
peer node, resource, capability, stream, and stable error code where those
|
||||
fields apply. Logs intentionally classify requests instead of formatting full
|
||||
payloads, so bearer tokens, private key paths, packet/message payloads, and
|
||||
document JSON are not logged by the request tracer.
|
||||
|
||||
See `docs/automation-examples.md` for shell, Python JSON, and user-service
|
||||
automation examples.
|
||||
See `docs/conflict-semantics.md` for the current per-resource conflict behavior
|
||||
|
|
|
|||
Loading…
Reference in a new issue