Admin: the Stream checks chart shows whether your live games had a stream #108

Closed
opened 2026-11-07 23:48:58 -05:00 by cmoriarty · 2 comments
Owner

Part of #103. On the mockup canvas, Picked column: Stream checks · 1B.

What happens

The chart is the last hour's checks as bars, found or failed, and it raises questions it doesn't answer:

  • Does a failed check mean the system is failing, or is it a normal miss?
  • Are lots of found streams good?

It shows the app is busy, not whether it is doing its job. Most of the day's failures were "too early": the game hadn't started, so it had no stream yet.

The idea

Chart the outcome the owner cares about: did each followed live game have a working stream?

  1. A column every 15 minutes:
    • followed live games with a working stream (green);
    • live without one (red);
    • starting within 30 minutes (grey outline).
  2. A lane under the columns for how many checks ran.
  3. The header:
    • a range switch: 3 h, Today, 3 days;
    • a badge, 3 / 3 covered: green, or red when any followed live game has no stream;
    • the checks run and the average time per check, as icons with values.
  4. The legend's entries are toggles.
  5. Hovering a column gives its time, the counts and the names of the games without a stream.

Data it needs

New: a coverage history.

  • What it records: every 15 minutes, for followed games, the counts live with a stream, live without one and starting soon, plus the names of the games without one.
  • Where it is kept: on disk under DATA_DIR, so it survives a restart, for 3 days, the same as History.
  • The checks lane comes from the check events that already exist.

Done when

  • In the unit lane:
    • coverage is sampled every 15 minutes with its counts and names;
    • it is kept for 3 days and read back after a restart.
  • In the frontend tests:
    • the chart renders a day from a fixture;
    • the badge turns red when a followed live game has no stream;
    • a legend toggle hides its series.
Part of #103. On the [mockup canvas](https://claude.ai/artifact/81TFkGA3agPRSmkL38L4yJ), Picked column: **Stream checks · 1B**. ## What happens The chart is the last hour's checks as bars, found or failed, and it raises questions it doesn't answer: - Does a failed check mean the system is failing, or is it a normal miss? - Are lots of found streams good? It shows the app is busy, not whether it is doing its job. Most of the day's failures were "too early": the game hadn't started, so it had no stream yet. ## The idea Chart the outcome the owner cares about: did each followed live game have a working stream? 1. **A column every 15 minutes:** - followed live games with a working stream (green); - live without one (red); - starting within 30 minutes (grey outline). 2. **A lane under the columns** for how many checks ran. 3. **The header:** - a range switch: 3 h, Today, 3 days; - a badge, `3 / 3 covered`: green, or red when any followed live game has no stream; - the checks run and the average time per check, as icons with values. 4. **The legend's entries are toggles.** 5. **Hovering a column** gives its time, the counts and the names of the games without a stream. ## Data it needs New: a coverage history. - **What it records:** every 15 minutes, for followed games, the counts live with a stream, live without one and starting soon, plus the names of the games without one. - **Where it is kept:** on disk under DATA_DIR, so it survives a restart, for 3 days, the same as History. - **The checks lane** comes from the check events that already exist. ## Done when - **In the unit lane:** - coverage is sampled every 15 minutes with its counts and names; - it is kept for 3 days and read back after a restart. - **In the frontend tests:** - the chart renders a day from a fixture; - the badge turns red when a followed live game has no stream; - a legend toggle hides its series.
Author
Owner

Deployed 2026-11-08 06:11Z in PR #111 (merge a133e29, container 71367c5163eb); OpenSpec change archived in b4d5b94. Live now: coverage is sampled every 15 minutes (followed live games with a stream, without one, starting soon, and the checks run), kept 3 days in coverage.jsonl and charted with a range switch and a covered badge. It starts empty at this deploy; a game night fills it. Left open until then.

Deployed 2026-11-08 06:11Z in PR #111 (merge a133e29, container 71367c5163eb); OpenSpec change archived in b4d5b94. Live now: coverage is sampled every 15 minutes (followed live games with a stream, without one, starting soon, and the checks run), kept 3 days in coverage.jsonl and charted with a range switch and a covered badge. It starts empty at this deploy; a game night fills it. Left open until then.
Author
Owner

Closed at the owner's word (2026-11-08): the fix is merged to develop in PR #111 (merge a133e29) and deployed. A new issue will be opened if a problem shows up.

Closed at the owner's word (2026-11-08): the fix is merged to develop in PR #111 (merge a133e29) and deployed. A new issue will be opened if a problem shows up.
Sign in to join this conversation.
No labels
No project
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
cmoriarty/sports-breaker#108
No description provided.