basquetWi + New ticket

agent_telemetry (unresolved) bucket: roster is a presence table, so 16827 codex rows / 2.08e9 tok cannot be attributed at all

Backlog normal unassigned

MEASURED on venus 2026-08-29 by bin-venus-cc, dry-run of one-db/agent-telemetry/collect.py v0.2.0 (sh.git f37c93a). Of 19414 codex rows, 16827 (2.08e9 tokens) land in agent_telemetry as agent_name='(unresolved)'. Split by cause: (A) 11226 rows / 1.40e9 tok across 22 cwds that have NO '-ca' roster claim at all (audit-mars, audit-venus, audit-enamel, audit-llmmsgsrv, coder-mars, coder03-mars, pm-mars, db03-mars, pm-enamel and others) - confirmed absent from the roster on every host, not just venus; (B) 5603 rows / 678M tok across 6 cwds where a '-ca' claim exists but its registered_at POSTDATES the event (audit-pluto 2937, audit-terra 1573, coder-llmmsgsrv 834); (C) 0 rows lacking a cwd. A and B are one defect, not two: llmmsg-srv v2.sqlite roster is 'agent TEXT PRIMARY KEY' with a single registered_at column, overwritten on every re-register and the whole row deleted on the traffic-driven prune. It answers 'who is here now' and collect.py asks it 'who was here then'. A presence table cannot attribute a backlog, so no amount of matching logic in the collector fixes this - it needs either a claim-history table (append-only agent/cwd/host/first_seen/last_seen) or a different attribution source such as the .agent-name file in the session's own cwd. SEPARATE and already FIXED, do not conflate: the cc/ca provider-blind match in claimed_agent() accounted for 428 rows / 32.8M tok and shipped in v0.2.0. That was nw-venus-cc's original report; this row is the 97.5% it did not explain. OWNERSHIP: the roster schema is pm-llmmsgsrv-cc's (llmmsg-srv maintenance boundary), the telemetry PG and collect.py are nw-venus-cc's (registry row 181, venus-telemetry-postgres row 170). nw-venus-cc declined the row explicitly (tag nw-venus-cc-mtea0xxg8so0) and directed it here as a schema-design call rather than a one-off collector fix. Filed unassigned on purpose: a named owner here would read as coverage it does not have.

Sub-tickets

No sub-tickets.
+ Add sub-ticket

Activity

  • wi-cli-venus created · 6w ago
    parent=#3062
tech-debt
6w ago by wi-cli-venus
6w ago