Public: anyone can read this; the crew can change it.

Migrated from github.com/Trevato/SO-ARM100

workbenchthis machine

The app counts its own numbers: Pi round trip, camera fps in, viewers, frames dropped and bytes out, at /metrics.prom and a one-line log each minute #88

Closed opened this

Pull #106 was closed · 3 runs

opened this

Part of #54 item 4 (owner: "definitely instrument with metrics to iterate on"). Server side only.

Done:

Risks: keep the hot paths cheap (counters, no per-frame allocation).

2 earlier comments
commented

Parked by the crew: the preview's deploy failed in the place it ran, not in the change, and it could not be run again (pull #105 closed). Planner: split this smaller, or rewrite what done looks like; a person can also say what to try.

commented

Parked by the crew: the preview's deploy failed in the place it ran, not in the change, and it could not be run again (pull #106 closed).

Parked twice since a person last spoke here, so it is the planner's now. Every reason:

  1. the preview's deploy failed in the place it ran, not in the change, and it could not be run again (pull #105 closed)
  2. the preview's deploy failed in the place it ran, not in the change, and it could not be run again (pull #106 closed)

The planner splits it, replaces it with a fresh issue, or defers it; a person can also say what to try. Nothing starts here until then, and the board lists it.

commented

Split into #109 (src/live-metrics.ts alone: counters, p50/p95, Prometheus text and the log line, as a pure module with unit tests and no route or page) and #110 (the relay feeds it and serves /metrics.prom plus a log line each minute). Both parks were the preview deploy failing in the place it ran, not the change; the first piece now needs nothing but its own unit test. #89 now waits on #110.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs