observability.hopl

Controls the sampling intervals for each Eye domain and the Analysis mode configuration. Hot-reloaded via /auroraoptimizer policy reload.

eye:
  observation:
    # Interval is expressed in server ticks (20 ticks = 1 second)
    server:   { enabled: true,  interval: 20  }  # Every 1 second
    worlds:   { enabled: true,  interval: 60  }  # Every 3 seconds
    chunks:   { enabled: true,  interval: 40  }  # Every 2 seconds
    entities: { enabled: true,  interval: 60  }  # Every 3 seconds
    players:  { enabled: true,  interval: 20  }  # Every 1 second
    network:  { enabled: true,  interval: 20  }  # Every 1 second
    mechanics:{ enabled: true,  interval: 100 }  # Every 5 seconds
    plugins:  { enabled: false, interval: 72000} # Every 1 hour (expensive)
    advanced: { enabled: false, interval: 40  }  # Requires ProtocolLib

analysis:
  enabled: false
  export-path: observations.log
  report-path: analysis-report.txt

# Per-domain tracking options (example for the mechanics domain)
mechanics:
  track-redstone: true
  track-pistons: true
  track-hoppers: true
  track-random-ticks: true
  track-mob-spawning: true
  track-combat-events: false   # Very high overhead — diagnostics only
  track-physics-events: false  # Very high overhead — diagnostics only

Analysis Mode

When analysis.enabled: true, the Eye operates at maximum resolution and exports all observation data to disk. At the end of the session it generates analysis-report.txt with configuration recommendations based on the observed load patterns.

Important: Analysis mode has higher performance overhead than normal mode. Use it exclusively in bounded diagnostic sessions (30–60 minutes), not permanently in production.