Context
The daemon currently discards all log output and there's no visibility into activity info, errors, or warnings. Logs should be written to OS typical locations instead, with automatic rotation so they don't grow indefinitely.
Goal
Route daemon logs to the appropriate OS log file (or sink service), with rotation handled either by the OS or in-process.
Acceptance criteria
Out of scope
- Configurable log paths or retention policies;
- Log shipping or aggregation (no Datadog, Splunk or other remote collectors at the moment).
Context
The daemon currently discards all log output and there's no visibility into activity info, errors, or warnings. Logs should be written to OS typical locations instead, with automatic rotation so they don't grow indefinitely.
Goal
Route daemon logs to the appropriate OS log file (or sink service), with rotation handled either by the OS or in-process.
Acceptance criteria
tracing-journald; rotation is handled by journald automatically — no configuration required from ringdrop;log_depth_daysfield in config.json controls how many daily log files are retained on macOS and Windows; defaults to7;~/Library/Logs/ringdrop/daemon.logviatracing-appender;%APPDATA%\ringdrop\logs\daemon.logviatracing-appender;RUST_LOGstill controls the verbosity level on all platforms;README.mddocuments where logs are written on each platform.Out of scope