Real-time bug analysis for the 62 autonomous players

An analyser runs every 2 minutes over the logs and state of the 62 Pantheon characters: it detects anomalies, groups them by stable signature in a bug registry and decides when a batch of fixes should start.

Detectors

Death streaks, standing still for over 10 min (excluding resting, AFK, flights and the intended shared-pace hold), goals picked up and dropped in a loop.
Spells repeatedly refused, failed or interrupted; quests abandoned, impossible to turn in or failed; loot left behind.
Stagnating gold and gear, XP/h far below the median, characters offline when they should play, gaps of more than 2 levels from the average (death knights excluded while the others are below level 55).
Server side: crashes, exceptions, packet errors, world update times (core summaries).

Registry

Each anomaly has a signature without character names or exact coordinates: occurrences, affected characters and classes, three examples, severity (critical, normal, minor) and status (open, fixed, ignored).
A fixed bug that shows up again after its fix is reopened and flagged as a regression; bugs affecting several classes get a higher priority.
The planning field says whether to fix right away (critical bug), whether a batch is ready (three confirmed bugs or one open for 2 h) or whether minor bugs are waiting.

Metrics

One data point every 2 min (deaths/h, XP/h, blockages/h, quests/h, CPU, tick time), kept 14 days, to compare the 30 minutes before and after each deployment.