coilyco-flight-deck/agent-proxy
2
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Ingest ward reap skill-use telemetry for dashboard graphs #39

New issue
Closed
opened 2026-07-09 22:04:40 +00:00 by coilyco-ops · 2 comments
coilyco-ops commented 2026-07-09 22:04:40 +00:00
Member
Copy link

Follow-up from the ChatGPT dashboard skill-use graph observation.

Goal:

Agent-proxy should ingest skill-use telemetry produced by ward reaped agent runs and expose it for dashboard graphs.

Producer dependency:

  • coilyco-flight-deck/ward#873 should add a stable skill-use artifact to ward reaped run archives.
  • Agent-proxy should consume that artifact rather than scraping freeform console logs.

Proposed first slice:

  • Add an ingestion path for ward skill-use summaries from the agent log archive location or the configured collector input.
  • Normalize dimensions that match agent-proxy traces/logs: run id, request/correlation id when present, harness, repo, issue ref, workflow, ward version, skill name, count, first_seen, last_seen.
  • Export a dashboard-friendly metric or log/trace attribute set that can power a skill-use graph.
  • Avoid high-cardinality labels where the existing agent-proxy telemetry model would reject them; run ids belong in logs/traces, not Prometheus labels.
  • Add fixtures for the ward#873 artifact shape.

Acceptance:

  • Agent-proxy can ingest a ward skill-use artifact and expose aggregate skill-use counts by skill and harness.
  • The ingest path handles missing/empty skill-use artifacts without errors.
  • Run id/correlation data remains queryable without becoming a high-cardinality metric label.
  • Tests cover the fixture shape produced by ward#873.
Follow-up from the ChatGPT dashboard skill-use graph observation. Goal: Agent-proxy should ingest skill-use telemetry produced by ward reaped agent runs and expose it for dashboard graphs. Producer dependency: - coilyco-flight-deck/ward#873 should add a stable skill-use artifact to ward reaped run archives. - Agent-proxy should consume that artifact rather than scraping freeform console logs. Proposed first slice: - Add an ingestion path for ward skill-use summaries from the agent log archive location or the configured collector input. - Normalize dimensions that match agent-proxy traces/logs: run id, request/correlation id when present, harness, repo, issue ref, workflow, ward version, skill name, count, first_seen, last_seen. - Export a dashboard-friendly metric or log/trace attribute set that can power a skill-use graph. - Avoid high-cardinality labels where the existing agent-proxy telemetry model would reject them; run ids belong in logs/traces, not Prometheus labels. - Add fixtures for the ward#873 artifact shape. Acceptance: - Agent-proxy can ingest a ward skill-use artifact and expose aggregate skill-use counts by skill and harness. - The ingest path handles missing/empty skill-use artifacts without errors. - Run id/correlation data remains queryable without becoming a high-cardinality metric label. - Tests cover the fixture shape produced by ward#873.
coilyco-ops commented 2026-07-09 22:05:21 +00:00
Author
Member
Copy link

WARD-RESERVATION: held 🔒

reservation details

Holder: container engineer-codex-agent-proxy-39 on host kais-macbook-pro-2.local.

Reserved by ward agent --harness codex (reserved 2026-07-09T22:05:19Z). Concurrent ward agent runs are blocked until it finishes or the reservation goes stale (1h TTL). --force overrides.

Do not comment on or edit this issue to steer the run while it is reserved. The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a new issue, dispatched fresh. That is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494).

run seed context — what this run is carrying (ward#609)
  • Resolved: coilyco-flight-deck/agent-proxy#39 · branch issue-39 · harness codex · workflow direct-to-main
  • Run: engineer-codex-agent-proxy-39 · ward v0.522.0 · dispatched 2026-07-09T22:05:19Z
  • Comment thread: 0 included in the pre-flight read, 0 stripped (ward's own automated comments).

Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.522.0).

— Codex, via ward agent

<!-- ward-agent-reservation --> WARD-RESERVATION: held 🔒 <details><summary>reservation details</summary> Holder: container `engineer-codex-agent-proxy-39` on host `kais-macbook-pro-2.local`. Reserved by `ward agent --harness codex` (reserved 2026-07-09T22:05:19Z). Concurrent `ward agent` runs are blocked until it finishes or the reservation goes stale (1h TTL). `--force` overrides. **Do not comment on or edit this issue to steer the run while it is reserved.** The engineer seeded the body once at launch and never re-reads it, so a comment or edit reaches only human readers, never the running engineer. A correction goes to a **new issue, dispatched fresh**. That is the only channel that reaches a run in flight. Where the forge supports it, ward locks this conversation to make that a road-block rather than a convention (ward#494). <details><summary>run seed context — what this run is carrying (ward#609)</summary> - **Resolved:** `coilyco-flight-deck/agent-proxy#39` · branch `issue-39` · harness `codex` · workflow `direct-to-main` - **Run:** `engineer-codex-agent-proxy-39` · ward `v0.522.0` · dispatched `2026-07-09T22:05:19Z` - **Comment thread:** 0 included in the pre-flight read, 0 stripped (ward's own automated comments). Static container doctrine and seed boilerplate are identical every run and omitted here (they ride ward v0.522.0). </details> </details> <!-- ward-agent-signature --> — Codex, via `ward agent`
coilyco-ops commented 2026-07-09 22:19:56 +00:00
Author
Member
Copy link

WARD-OUTCOME: done

details

workflow: direct-to-main; review summary: skipped because review gate skipped by ~/.ward/config.yaml default
retrospective: The ingest path stayed small and testable. The only surprise was the container disk pressure, which I worked around with a smaller install set and TMPDIR=/dev/shm for tests.
confidence: high
surprises: tmp_path wanted /scratch, but /scratch was full. I pointed pytest temp usage at /dev/shm.
follow-ups: None.

WARD-OUTCOME: done <details><summary>details</summary> workflow: direct-to-main; review summary: skipped because review gate skipped by ~/.ward/config.yaml default retrospective: The ingest path stayed small and testable. The only surprise was the container disk pressure, which I worked around with a smaller install set and TMPDIR=/dev/shm for tests. confidence: high surprises: tmp_path wanted /scratch, but /scratch was full. I pointed pytest temp usage at /dev/shm. follow-ups: None. </details>
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
issue-34
ward-salvage/agent-proxy-09877ee0
No results found.
Labels
Clear labels
  
coherence-core
Core review set for the warded control plane coherence milestone. These issues form the release spine; adjacent milestone issues are stretch or supporting work.

  
consult
A human decision, design, or external action must happen first. Fail-closed default for unlabeled/low-confidence.

  
headless
Agent can take it from open issue to merged change with no human in the loop. The auto-burndown queue.

  
interactive
Agent does the work but pauses at a human checkpoint mid-flight (design choice, destructive step, human-only verification).

  
P0
now / blocking / urgent

  
P1
next / important

  
P2
backlog / will do

  
P3
someday / low

  
P4
icebox / frozen / reopen if it becomes real

No labels
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
coilyco-flight-deck/agent-proxy#39
No description provided.