Skip to content

Improve observability: add structured logging to tournament, analyze, and verify_parity #157

Description

@lukeinglis

Add structured logging calls to functions in tournament.py, analyze.py, verify_parity.py, eval.py, and lab_forecaster.py that currently lack observability instrumentation.

Motivation

The observability eval dimension scores logging coverage at 18% (43/236 functions). Adding structured logger.info() calls to key entry-point functions in mutable modules increases coverage and log density, making the system more debuggable in production and improving the observability score.

Scope

  • tournament.py — add structlog logger + log calls to all public functions
  • analyze.py — add log calls to analysis functions missing them
  • verify_parity.py — add structlog logger + log calls to all check functions
  • eval.py — add log calls to save_result, load_previous_results, split_held_out, list_rounds, print_leaderboard_comparison
  • lab_forecaster.py — add log calls to _parse_probability (failure path) and _extract_probabilities
  • tests/test_logging_config.py — add test for newly instrumented modules

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions