For a building-permit workflow, which logging strategy best records behavior without drowning operators in noise?
Select an answer to reveal the explanation.
Short Explanation
Log the plot twists—submitted, paid, approved—at info. Leave the play-by-play debug chatter for local or tight sampling so production stays readable.
Full Explanation
An effective strategy records meaningful business or state transitions at appropriate levels (for example info for submitted/paid/approved) while keeping high-volume debug out of steady-state production. Flooding fatal traces, disabling logs, or logging secrets increases noise or risk without improving operability.