Part 6 – Logging and Observability

Integrate structured, consistent logging (console/file); make outputs report-ready.

Learning Objectives

• Define a minimal, consistent log taxonomy for PoC tooling.

• Instrument routes and lifecycle transitions with meaningful, parseable logs.

• Configure dual sinks (stdout + file) for both live feedback and artifact capture.

Goals

• Integrate a lightweight logger with severity levels and consistent prefixes.

• Optionally support dual sinks (stdout + file).

• Capture timestamps and key metadata (route, remote IP, filename, size).

Key Terms

• Severity: Log level indicating importance (info, success, warn, error, status).

• Dual Sink: Logging to console and file simultaneously.

• Correlation: Using counters/IDs to tie related events together.

What You’ll Build

• Logging calls in each route and in lifecycle transitions.

• A simple, uniform log format tailored to PoC reporting.

Sections

• Log Taxonomy: info, success, warn, error, status.

• Placement: Before/after critical actions; include counters and limits.

• Artifacts: Where to write logs; filename pattern; rotation considerations.

• Milestone: Logs show a clear timeline of actions for a single run.

Exercises

• Run a full cycle (download or exfil) and capture a clean log excerpt for notes.

• Add minimal correlation IDs if chaining multiple tools.

What’s Next

• Assemble the parts into the final FileTransferServer class with ergonomic configuration.