Source 3: perf stat collector #5

New issue

Closed

opened 2026-04-30 00:10:47 -05:00 by max · 0 comments

max commented

2026-04-30 00:10:47 -05:00

Owner

docs/data-model.md specifies a third oracle source — perf stat -p <qemu_pid> — that is not yet implemented. Sources 1, 2, 4, 5 are live as of b80986d.

Needed:

collectors/perf_qemu.py with the same shape as proc_qemu.py and qmp.py (run_loop, telemetry-perf.jsonl with the schema from docs/data-model.md).
Wire into EpisodeRunner alongside the others.
Probably shells out to perf stat -I 100 -j -p <pid> and parses the JSON event stream.

Not urgent — sources 1+2 already cover most of the oracle signal — but this is the gap to fill before claiming the full 5-source telemetry vision.

docs/data-model.md specifies a third oracle source — `perf stat -p <qemu_pid>` — that is not yet implemented. Sources 1, 2, 4, 5 are live as of b80986d. Needed: - `collectors/perf_qemu.py` with the same shape as `proc_qemu.py` and `qmp.py` (run_loop, telemetry-perf.jsonl with the schema from docs/data-model.md). - Wire into EpisodeRunner alongside the others. - Probably shells out to `perf stat -I 100 -j -p <pid>` and parses the JSON event stream. Not urgent — sources 1+2 already cover most of the oracle signal — but this is the gap to fill before claiming the full 5-source telemetry vision.