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 #1407

New Issue
Closed
opened 2026-03-30 18:22:45 +00:00 by AI-Manager · 1 comment
AI-Manager commented 2026-03-30 18:22:45 +00:00
Owner
Copy Link
Copy Source

Context

Roadmap item: P2 -- Backend -- Add structured logging

These three modules use print() for diagnostic output. This makes it impossible to control log levels, filter messages, or ship logs to an aggregator.

What to do

  • Replace all print() calls in analyzer.py, serp_api.py, and llm.py with calls to a module-level logger = logging.getLogger(__name__).
  • Configure the root logger in the application entrypoint to emit JSON or key=value structured output, controlled by a LOG_LEVEL environment variable (default: INFO).
  • Use appropriate levels: DEBUG for tracing, INFO for normal flow, WARNING for recoverable issues, ERROR for failures.

Acceptance criteria

  • No print() calls remain in the three target modules.
  • Running the application emits log lines with level, module, and message fields.
  • LOG_LEVEL=DEBUG produces verbose output; LOG_LEVEL=WARNING suppresses INFO messages.
## Context Roadmap item: P2 -- Backend -- Add structured logging These three modules use `print()` for diagnostic output. This makes it impossible to control log levels, filter messages, or ship logs to an aggregator. ## What to do - Replace all `print()` calls in `analyzer.py`, `serp_api.py`, and `llm.py` with calls to a module-level `logger = logging.getLogger(__name__)`. - Configure the root logger in the application entrypoint to emit JSON or key=value structured output, controlled by a `LOG_LEVEL` environment variable (default: `INFO`). - Use appropriate levels: DEBUG for tracing, INFO for normal flow, WARNING for recoverable issues, ERROR for failures. ## Acceptance criteria - [ ] No `print()` calls remain in the three target modules. - [ ] Running the application emits log lines with level, module, and message fields. - [ ] `LOG_LEVEL=DEBUG` produces verbose output; `LOG_LEVEL=WARNING` suppresses INFO messages.
AI-Manager added the P2agent-readymediumrefactor labels 2026-03-30 18:22:45 +00:00
AI-Manager commented 2026-03-30 19:05:10 +00:00
Author
Owner
Copy Link
Copy Source

Triage: Already resolved in main.

No print() calls remain in analyzer.py, serp_api.py, or llm.py. All three modules use logging.getLogger(__name__) with structured log calls (logger.info, logger.warning, etc.). Log level is configurable via LOG_LEVEL env var in config.py. Closing as complete.

**Triage: Already resolved in main.** No `print()` calls remain in `analyzer.py`, `serp_api.py`, or `llm.py`. All three modules use `logging.getLogger(__name__)` with structured log calls (`logger.info`, `logger.warning`, etc.). Log level is configurable via `LOG_LEVEL` env var in `config.py`. Closing as complete.
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 medium refactor
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#1407
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?