Add a since-you-last-looked summary, 30-day uptime ribbons, a maintenance timeline and hover timestamps

- Dashboard card on what changed since the user pressed Got it (users.last_looked_at,
  migration 0021), folding each problem and its recovery into one line.
- Uptime ribbons on servers and integrations, built from the audit log; integrations'
  failing/working-again moments are now recorded.
- Timeline of running and scheduled maintenance windows on the Maintenance page.
- TimeAgo component: relative times with the exact time in the chosen format on hover.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
This commit is contained in:
bobbanandClaude Sonnet 5.5 committed 2026-10-16 21:55:04 +02:00
1 parent 3945c60681
commit 906220040e
32 files changed
+3380 -15

No files matched your search

+30
View File
@@ -395,6 +395,36 @@ the problems themselves, and each integration's status, refreshing every 30
seconds with the screen kept awake where the browser allows. Esc returns to the
app.
**Since you last looked.** The dashboard opens with a card on what happened
since you last pressed "Got it" (the first time, the last day; never more than
two weeks): servers that stopped reporting or filled a disk, services that
stopped answering, and maintenance that began or ended — each problem and its
recovery folded into one line ("elsa was offline for 12 min — reporting again";
a problem that hasn't ended says "still offline"). Operators and admins also see
how many changes other people made, with a link to the audit log. Nothing to say
means no card. The mark is stored on your user, so it follows you to any browser.
**Uptime ribbons.** Servers (list, cards and the server's page) and integration
cards show a strip of one bar per day for the last 30 days — green for a day with
nothing wrong, amber for some time down, red for half a day or more, grey where
nothing is known — and the share of time up. It is worked out from the moments
the health checks write in the audit log (a server stopped reporting / reported
again; an integration's calls started failing — the same threshold as the failure
alert — / worked again), so it can only be as old as those records: servers go
back to when they were added, integrations to the first time this version ran.
Integrations are tracked per kind of service, as the health checks are.
**Maintenance timeline.** The Maintenance page draws the running and scheduled
windows along a time axis (the next 24 hours, 7 days or 30 days), one row per
server, integration or DNS provider and a top row for "anything in
maintenance", so overlaps and gaps are visible. Windows mirrored from Uptime
Kuma are striped. The tables below still list the same windows.
**Times as people say them.** "Last seen", sync times, session activity and
similar columns read "5 min ago" and show the exact date and time, in the format
chosen under Settings → Display, on hover. Exports and the audit log keep exact
times.
**Activity.** Operators and admins see an Activity card on each server's page:
what changed on it and who changed it, the moments the health check saw it stop
reporting (and report again) or a disk fill (and recover) — now written to the