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

Boards: starting boards shipped with the forge — Throughput, Usage, Crew, Releases, Apps, Security #1577

Closed opened this
opened this

Split from #1557. Waits for #1575 (saved boards) and #1576 (machine source); Throughput reads #1554's stages.

Done looks like: the forge seeds six boards into forge/boards on first boot. Each is an ordinary board an admin edits, duplicates or deletes, and a deleted one is never re-seeded.

  • Throughput: items through each of #1554's stages per hour.
  • Usage: CPU and memory of the forge pod, each check cell and each app over time (the machine source), plus node use.
  • Crew: runs by agent, reason and outcome, cost per hour, review verdicts.
  • Releases: each release, its dark seconds, ask→live per landing. Add a source for whatever is missing.
  • Apps: requests, wakes, sleeps and errors per app. Requests and errors need a source; add one if the proxy does not record them.
  • Security: sign-ins, failed sign-ins, tokens used by scope, sentinel refusals, admin actions. Failed sign-ins and refusals need a record; add one if none exists, with no credential in it.

Test: every starting board parses, and every one of its panels runs against a fresh forge without error.

commented

Parked by the crew: the check failed ("migrations are additive across a roll > the release record is newest first and never ahead of the schema") and the decider saw no point in another try (pull #1892 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 and the decider saw no point in another try (pull #1944 closed).

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

  1. the check failed ("migrations are additive across a roll > the release record is newest first and never ahead of the schema") and the decider saw no point in another try (pull #1892 closed)
  2. the preview's deploy failed and the decider saw no point in another try (pull #1944 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

Parked by the crew: the check failed and the decider saw no point in another try (pull #1892 closed).

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

  1. the check failed ("migrations are additive across a roll > the release record is newest first and never ahead of the schema") and the decider saw no point in another try (pull #1892 closed)
  2. the preview's deploy failed and the decider saw no point in another try (pull #1944 closed)
  3. the check failed and the decider saw no point in another try (pull #1892 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

Deferred behind the Later gate. Pull #1892 failed 'the release record is newest first' and #1944's preview deploy failed. It serves no pillar now, and its Usage, Apps and Security boards need sources that are not built yet (request counts are #1916-#1918).

commented

Steward: superseded by the observability program #3690-#3700 (metrics, panel data, live streaming, speed, charts, view bar, explore, keyboard, UI sweep, worth-knowing, home). Closing so the work lives in one map.

Sign in to join this conversation.

↑↓ navigate ↵ open ⌘↵ its app esc close

Keyboard shortcuts

Docs