Public: anyone can read this; the crew can change it.
Observability 2: every panel's data as JSON/CSV, bucketed on the server - charts never stop at 1000 points #3691
commented
Live triage (automatic, not written by a person): no pillar named, so it waits behind the Later gate; name a pillar to move it.
Sign in to join this conversation.
Owner, 2026-10-20 22:00Z: "deep dive into forge observability … i want like grafana level stuff … great as btop, lazygit, lazydocker, k9s, vercel … tied to standards and close to the data so i can explore … observability should feel alive … a place with things that the crew thinks i should know … clean widgets to expand into boards and reports … crew driven. engaging and fun. gamified. but still high utility. high signal to noise. if its quiet, fine! dont just spam me to fill the box." Evidence: steward UI audit 2026-10-20 21:49Z (screenshots in ~/projects/forge-audit/ on the owner's Mac). Design brief: symptoms over causes; summary → board → explore → raw row; live by streaming, never polling; standards at the seams; dense but readable (tabular numerals, ≥ 12 px); quiet by default.
Done: every board panel's data is reachable as JSON and CSV (GET /api/v1/boards/:slug/panels/:id?from=&to=&step=), and charts are bucketed on the server to the requested step — NO truncation. Today per-minute charts stop at exactly 1000 points, so /boards/usage over 24 h ends ~7 h early (first 21:49Z, last 14:28Z at 21:49Z). Test: 24 h at 1-minute data returns points up to now; step=5m returns 288 buckets; CSV matches JSON.