logging-conventions

Structured logging standardizes logger usage via getLogger or structlog, mandating fields like category and error_code to produce machine-readable container logs that enable reliable error detection and traceability.

Silent failures occur due to unstructured logging and poor exception handling. Enforcing standardized logging practices with mandated fields and proper error patterns reduces silent failures and improves incident response visibility.

The best way to standardize logging for API routes and jobs is applying consistent logger instantiation like getLogger or structlog across the codebase, forbidding silent or unstructured logging to ensure observability.

Yes, the logging convention applies to backend Python services, API endpoints, background jobs, LLM integration, and frontend TypeScript code that relies on backend logs, enforcing consistent practices across the entire stack.

Make container logs machine-readable by enforcing structured logging with required fields like category and error_code. Using standardized loggers ensures outputs are parseable by container-log-audit tools for reliable error detection.

You should not bypass logging conventions when modifying any backend or frontend code, as unstructured or silent logging breaks automated audit trails, reduces traceability, and prevents reliable incident response.