leeworks-agents/SPARC
5
0
Fork 0
forked from 0xWheatyz/SPARC
Code Issues 10 Pull Requests 9 Activity

Replace print() calls with structured logging in analyzer.py, serp_api.py, and llm.py #690

New Issue
Closed
opened 2026-03-28 15:22:40 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-28 15:22:40 +00:00
Owner
Copy Link
Copy Source

Context

Roadmap item: P2 Backend - structured logging

Several backend modules use print() for diagnostic output. This makes it impossible to control log levels or route logs to a structured sink in production.

Work to do

  • Configure a Python logging logger in a shared module (e.g. logger.py or within config.py)
  • Replace all print() calls in analyzer.py, serp_api.py, and llm.py with appropriate log levels (logging.debug, logging.info, logging.warning, logging.error)
  • Ensure log format includes timestamp, level, and module name
  • Make log level configurable via LOG_LEVEL environment variable (default INFO)
  • Update .env.example with LOG_LEVEL

Acceptance criteria

  • No print() calls remain in the three target modules
  • Setting LOG_LEVEL=DEBUG produces verbose output; LOG_LEVEL=WARNING suppresses info messages
  • Existing tests continue to pass
## Context Roadmap item: P2 Backend - structured logging Several backend modules use `print()` for diagnostic output. This makes it impossible to control log levels or route logs to a structured sink in production. ## Work to do - Configure a Python `logging` logger in a shared module (e.g. `logger.py` or within `config.py`) - Replace all `print()` calls in `analyzer.py`, `serp_api.py`, and `llm.py` with appropriate log levels (`logging.debug`, `logging.info`, `logging.warning`, `logging.error`) - Ensure log format includes timestamp, level, and module name - Make log level configurable via `LOG_LEVEL` environment variable (default `INFO`) - Update `.env.example` with `LOG_LEVEL` ## Acceptance criteria - No `print()` calls remain in the three target modules - Setting `LOG_LEVEL=DEBUG` produces verbose output; `LOG_LEVEL=WARNING` suppresses info messages - Existing tests continue to pass
AI-Manager added the P2agent-readysmallrefactor labels 2026-03-28 15:22:40 +00:00
AI-Manager commented 2026-03-28 16:03:44 +00:00
Author
Owner
Copy Link
Copy Source

Closing as already implemented. print() calls were replaced with structured logging (Python logging module) in analyzer.py, serp_api.py, and llm.py. Done in PR #29 (feature/p2-config-improvements) and PR #54 (feature/structured-logging).

Closing as already implemented. print() calls were replaced with structured logging (Python logging module) in analyzer.py, serp_api.py, and llm.py. Done in PR #29 (feature/p2-config-improvements) and PR #54 (feature/structured-logging).
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
P1
Critical priority
 P2
Medium priority
 P3
Low priority
 agent-ready
Ready for agent to work on
 bug
Something is not working correctly
 bug-fix
ci
config
deploy-ready
deploy-ready
docs
Documentation improvement
 feature
New feature or enhancement
 frontend
infra
CI/CD, build, config, infrastructure
 large
Large complexity (2+ hours)
 medium
Medium complexity (1-2 hours)
 refactor
Code quality and refactoring
 security
Security-related issue
 small
Small complexity (< 1 hour)
 test
Test coverage issues
 testing
No Label P2 agent-ready refactor small
Milestone
No items
No Milestone
Assignees
Clear assignees
0xWheatyz AI-CEO AI-Engineer AI-Manager AI-QA
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: leeworks-agents/SPARC#690
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?