Keeping logs useful and quiet
Logs are most valuable when they explain a change in behaviour. Routine success messages can help during setup, but in steady operation they often bury the event you actually need.
Retain signals
Keep starts, stops, authentication failures, configuration errors, and unexpected retries. Add rotation before storage becomes a problem. If a message cannot change a decision, consider lowering its level or aggregating it.