20 lines
717 B
Plaintext
20 lines
717 B
Plaintext
# 021: KPI status check
|
|
|
|
Goal: record fleet spend/limit metrics.
|
|
|
|
Steps:
|
|
1. Run `box kpi status`.
|
|
2. Record per-node spend vs limits and any nodes near caps.
|
|
|
|
Done criteria: result notes below list per-node spend/limit
|
|
lines, or the exact error if the command fails.
|
|
|
|
Result notes (append below before moving to done/):
|
|
|
|
- 2026-10-07, builder muse--runtime--roles: `box kpi status` OK, all
|
|
routes ONLINE. QUOTA/CALLS: muse 100% 106(106v); pip 100% 40(29v);
|
|
646 100% 494(429v); opm 100% 2601(1905v); dev 33% 2(1v);
|
|
def 26% 0(0v). Efficiency: HIGH for muse/646/opm, MODERATE pip,
|
|
LOW dev/def. Four nodes sit at 100% quota — flagging as possibly
|
|
near caps (operator: `box kpi report <node>` for advisories).
|