nickberens360/nickberens-astro

chore(logging): replace print() with logging in routes and services

Open

#238 opened on Sep 13, 2025

View on GitHubContributor guide
 (0 comments) (0 reactions) (0 assignees)Python (0 forks)github user discovery
backendchoregood first issueobservability

Repository metrics

Stars
 (1 star)
PR merge metrics
 (No merged PRs in 30d)

Description

Replace print() calls in runtime backend code with structured logging for consistent observability.

Scope

  • Primary: backend/routes/health.py error paths (status/rate-limits/welcome-questions).
  • Secondary: scan backend/** (exclude backend/scripts/, backend/knowledge/, and tests) for print(.

Acceptance Criteria

  • No print() calls remain in backend runtime code paths.
  • Errors/exceptions logged via module logger; unexpected exceptions include exc_info=True.
  • pytest -q passes.

Notes

  • Keep prints in CLI utilities under backend/scripts/ and tests.

Contributor guide

Research direction
Identify all print() calls in backend/routes/health.py and then scan other backend runtime files excluding scripts and knowledge. Replace each with appropriate logger calls, ensuring error paths include exc info=True where necessary. Run pytest to verify.
Tech stack
python
Domain
backend
Issue type
Chore
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Python
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
85