Ga naar de hoofdinhoud

Log enough to debug tomorrow

Add operationally useful logs to a Python automation without leaking sensitive data.

python-for-automation5 min read

The nightly updater finishes with a wrong output, and the current logs do not show source identity, row counts, external write results, or failure reasons. OWASP-style event logging: capture when, where, who, what, result, and reason while excluding sensitive data. The common shortcut is printing progress messages that feel useful during development but cannot support an incident later. Before print('started'), print('done'), and an unstructured stack trace in the scheduler output. After Structured run events include run ID, input hash, validation counts, write counts, status, and reason codes. Step 1 Create a run_id and log script version, run mode, and input…

Read the full lesson

Sign up free: one personalized lesson every day, matched to your role and goals.

← Back to library

Neem contact op