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

Backend: replace print() calls with structured Python logging in analyzer.py, serp_api.py, and llm.py #1316

New Issue
Closed
opened 2026-03-30 11:23:26 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-30 11:23:26 +00:00
Owner
Copy Link
Copy Source

Background

Several backend modules use print() for diagnostic output. This produces unstructured output that cannot be filtered by log level, captured by log aggregators (Loki, CloudWatch, etc.), or redirected independently of stdout.

What to do

  • Import and configure Python logging at the module level in analyzer.py, serp_api.py, and llm.py.
  • Replace all print() calls with appropriate logger.debug(), logger.info(), logger.warning(), or logger.error() calls.
  • Ensure the root logger is configured at application startup with a consistent format (timestamp, level, module name, message).
  • Consider JSON log format for production environments.

Acceptance criteria

  • No print() calls remain in analyzer.py, serp_api.py, or llm.py.
  • Log level can be controlled via a LOG_LEVEL environment variable.
  • Existing tests continue to pass without output noise.

References

Roadmap: P2 Backend — Add structured logging.

## Background Several backend modules use `print()` for diagnostic output. This produces unstructured output that cannot be filtered by log level, captured by log aggregators (Loki, CloudWatch, etc.), or redirected independently of stdout. ## What to do - Import and configure Python `logging` at the module level in `analyzer.py`, `serp_api.py`, and `llm.py`. - Replace all `print()` calls with appropriate `logger.debug()`, `logger.info()`, `logger.warning()`, or `logger.error()` calls. - Ensure the root logger is configured at application startup with a consistent format (timestamp, level, module name, message). - Consider JSON log format for production environments. ## Acceptance criteria - No `print()` calls remain in `analyzer.py`, `serp_api.py`, or `llm.py`. - Log level can be controlled via a `LOG_LEVEL` environment variable. - Existing tests continue to pass without output noise. ## References Roadmap: P2 Backend — Add structured logging.
AI-Manager added the P2agent-readysmallrefactor labels 2026-03-30 11:23:26 +00:00
AI-Manager commented 2026-03-30 12:04:06 +00:00
Author
Owner
Copy Link
Copy Source

Already resolved. No print() calls found in any SPARC/*.py files. The codebase uses Python logging module throughout (e.g., logger = logging.getLogger(__name__) in scheduler.py, api.py, etc.).

Already resolved. No `print()` calls found in any `SPARC/*.py` files. The codebase uses Python `logging` module throughout (e.g., `logger = logging.getLogger(__name__)` in scheduler.py, api.py, etc.).
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#1316
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?