Skip to content

fix: emit runtime timing logs at info level - #188

Merged
afaryy merged 1 commit into
mainfrom
feature/sai-74-cloud-logging
Aug 30, 2026
Merged

fix: emit runtime timing logs at info level#188
afaryy merged 1 commit into
mainfrom
feature/sai-74-cloud-logging

Conversation

@afaryy

@afaryy afaryy commented Aug 30, 2026

Copy link
Copy Markdown
Contributor

Why

The public Cloud Run app records stage timing in code, but Python defaulted to WARNING and suppressed the INFO record before it reached Cloud Logging.

What changed

  • Configure the runtime root logger at INFO during Cloud Run startup.
  • Preserve existing handlers; add a default handler only when none exists.
  • Add a regression test proving an INFO timing record reaches root handlers.

Privacy

The timing line contains only durations. It does not log concerns, case IDs, contact details, or model output.

Verification

  • Python tests: uv run pytest -q — 281 passed
  • Python lint: uv run ruff check src tests
  • Frontend tests: run from frontend — 31 passed
  • Frontend lint and production build: passed

@afaryy
afaryy merged commit 3306faa into main Aug 30, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant