The live rugnux run wrote its whole processing log into the broker's journal - every
[Rugnux] line of the library (tables included) plus a "rugnux:" line per step and note -
about 300 lines per collection, all of them results the user already gets through
/rugnux/status, the end message and the written files.
- Logger::ServiceLevel(service, level): every Logger of that name made afterwards keeps only
that level and above. The library makes its own Logger("Rugnux") (and
Logger("ScaleOnTheFly")) wherever it logs, so this is the one switch: the broker sets them
to error, or to debug with the existing `verbose` setting. The per-Logger "Version" line goes
with it. The rugnux CLI routes every Logger to its own sinks (RouteAll) and never calls
this, so its console and _log.txt are unchanged.
- The live observer feeds steps and notes to the live status only.
- The run's outcome is one line at the end: state, START -> first image and frame rate,
done after the last image, last image -> all written. The probe result, the warm-up time
and the cut reason go to debug (the cut is in the outcome line).
- Per-collection step chatter goes to debug: receiver init/teardown, thread start/stop,
"Wait for receiver done" and friends, the per-image mean processing time. The JFJochBroker
logger now follows `verbose` too, so these are available again with it.
- Kept: Start request, measurement start, receiving started/finished, receiver efficiency
(and the per-module packet counts on loss), calibration sequence, all warnings and errors.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PXc1zD1yxHqaR1DGdCTHL4
leonarski_fandClaude Opus 5.5
48c14b6d1b