Movses AslanyanandClaude Opus 5.5 7be54a6ff9 Emit JSON logs through structlog, including uvicorn and stdlib loggers ...

configure_logging now builds one processor chain shared by structlog
calls and foreign stdlib records (uvicorn, the consumers' getLogger),
rendered as one JSON object per line on stdout. Tracebacks stay inside
their line instead of splitting into one Docker log entry per frame.

uvicorn.access is deliberately left untouched: --no-access-log works by
disabling its propagation, and re-enabling it would bring access logs
back (and inflate the healthz/lookup line counts the tests rely on).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

2026-10-13 20:27:34 +03:30

..

__init__.py

Implement Phase 0b base project against the frozen test contract

2026-09-05 08:12:30 +03:30

chaos_flags.py

Implement Phase 0b base project against the frozen test contract

2026-09-05 08:12:30 +03:30

db.py

Implement Phase 0b base project against the frozen test contract

2026-09-05 08:12:30 +03:30

http.py

Replace X-Request-Id with the trace ID and retire the guard suite

2026-10-13 19:48:27 +03:30

logging_config.py

Emit JSON logs through structlog, including uvicorn and stdlib loggers

2026-10-13 20:27:34 +03:30

redis_client.py

Implement Phase 0b base project against the frozen test contract

2026-09-05 08:12:30 +03:30

settings.py

Implement Phase 0b base project against the frozen test contract

2026-09-05 08:12:30 +03:30

telemetry.py

Propagate traces over HTTP and add Redis spans

2026-10-13 11:28:03 +03:30