Skip to content

feat: add comprehensive structured logging across project#9

Open
ghostyappbeta[bot] wants to merge 2 commits intomainfrom
feat/structured-logging
Open

feat: add comprehensive structured logging across project#9
ghostyappbeta[bot] wants to merge 2 commits intomainfrom
feat/structured-logging

Conversation

@ghostyappbeta
Copy link

@ghostyappbeta ghostyappbeta bot commented Feb 20, 2026

This pull request was generated by @kiro-agent 👻

Comment with /kiro fix to address specific feedback or /kiro all to address everything.
Learn about Kiro autonomous agent


Summary

Replaces all print() statements across the codebase with Python's built-in logging module, providing structured, configurable logging throughout the project.

Changes

  • New logger_config.py — centralized logging configuration module providing:

    • setup_logging(name, log_level, log_file) for entry points (console + file handlers)
    • get_logger(name) convenience wrapper for submodules
    • Format: 2024-01-15 14:30:00 [INFO] arat-rl: Starting testing...
    • LOG_LEVEL environment variable support (DEBUG/INFO/WARNING/ERROR)
  • 40 files modified across entry points, morest submodule, proxy, and utility scripts

    • 42 hierarchically-named loggers (e.g., morest.fuzzer, morest.model.method)
    • Log levels carefully assigned: DEBUG for verbose/internal state, INFO for operational progress, WARNING for errors/timeouts
    • Entry point scripts write to dedicated log files (e.g., arat-rl.log)
  • Zero new dependencies — uses only Python stdlib logging

Configuration

Set log verbosity via environment variable:

LOG_LEVEL=DEBUG python3 arat-rl.py spec/features.yaml http://localhost:30100/ 3600

Default level is INFO. Each entry point also writes to a log file for post-run analysis.

kiro-agent and others added 2 commits February 20, 2026 01:31
…try point scripts

- Create logger_config.py with setup_logging() and get_logger() functions
- Replace all print() calls with structured logger calls in 5 entry scripts
- Add logging at key points: startup, iteration progress, errors, completion
- Support configurable log levels via LOG_LEVEL environment variable
- Support dual output to console (stderr) and optional log file

Co-authored-by: Myeongsoo Kim <codingsoo93@gmail.com>
…ith structured logger calls

- Add logging to helper scripts: run.py, run_tool.py, run_service.py, parse_log.py, verify_setup.py
- Add logging to all morest submodule files: fuzzer, model, validator, utils, ga, generator, experiment_utils
- Replace logging.basicConfig in normal_executor.py and mutation_executor.py with per-module loggers
- Create morest/logger_config.py as a copy of root logger_config.py for submodule imports
- Add setup_logging() calls in entry points: morest/fuzzer.py, parse_log.py
- Replace all active print() calls with appropriate logger levels (debug/info/warning/error)
- 34 files modified, 42 loggers created across the entire codebase

Co-authored-by: Myeongsoo Kim <codingsoo93@gmail.com>
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