Skip to content

v0.9.2 - Logging Optimization (2025-12-27)

What Changed?

This release optimizes structured logging to prevent log file bloat during long-running event collection. Removed verbose debug and info logs that were generated on every event read and response parse, reducing log file size by approximately 32%. All critical error logging and exception handling remain intact for debugging purposes.

What's New

Main Feature: Reduced Log File Bloat

What it does: Removes unnecessary verbose logs that were causing log files to grow excessively during event collection operations.

Impact:

  • Log files reduced by ~32% (230,000+ lines removed per typical session)
  • Faster log file processing and analysis
  • Maintained all critical debugging information (errors, warnings, timeouts)

What was removed:

  • "Waiting for response" debug log in device.py (repeated every receive call)
  • "Response received" and "Response processed" logs in device.py (repeated every successful response)
  • "Reading event" debug log in measure.py (repeated every event read attempt - 163,675 instances)
  • "Event read successfully" info log in measure.py (repeated every successful read - 22,098 instances)
  • "JSON parsed successfully" debug log in parser.py (repeated every response parse - 22,172 instances)
  • "Response validation successful" debug log in parser.py (repeated every validation - 22,172 instances)

What was kept:

  • All error and warning logs
  • Exception handling logs with stack traces
  • Timeout logs with retry context
  • Connection and initialization logs

Installation

Quick Start

# Get the release
git checkout v0.9.2

# Setup
task env:setup

# Run CLI
uv run kazunoko --help

What's Different from the Last Version?

🔧 Changed

  • Removed verbose logging in device.py (receive_response method)
  • Removed verbose event reading logs in measure.py (_read_event helper)
  • Removed verbose parsing logs in parser.py (parse_line and validate_response methods)
  • Log files now ~32% smaller during typical event collection sessions

Is It Safe to Upgrade?

Backward Compatible: Yes

  • No API changes
  • No behavior changes
  • Only logging output reduced
  • All error diagnostics preserved

Tests Passed

  • ✅ Builds without errors
  • ✅ All existing functionality works unchanged
  • ✅ Error logging still captures failures with stack traces
  • ✅ Manual verification of log file size reduction

Release Details

  • Date: 2025-12-27
  • Version: v0.9.2
  • Files Changed: 3 (device.py, measure.py, parser.py)
  • Commits:
  • 95d98df refactor(device): remove verbose debug log in receive_response
  • f7ce0e8 refactor(device): remove verbose response logs in receive_response
  • dafc936 refactor(measure): remove verbose event reading logs
  • c7b75b4 refactor(parser): remove verbose JSON parsing log
  • e1946c1 refactor(parser): remove verbose response validation log

Next Steps

  • Monitor log file sizes in production use
  • Consider implementing log level configuration for user control
  • Evaluate additional logging optimizations if needed