Skip to content

Phase 5c: links' Kuma monitors become monitor widgets - #52

Merged
cerebrate merged 1 commit into
masterfrom
feature/phase5c-link-widgets
Oct 17, 2026
Merged

cerebrate merged 1 commit into
masterfrom
feature/phase5c-link-widgets

Conversation

@cerebrate

Copy link
Copy Markdown
Member

Summary

Links' Uptime Kuma MonitorId badges become h2s's own monitor widgets. Kuma's badge images are gone from tiles, and links no longer need their monitor on a published status page.

Migration (ConvertLinkMonitorsToWidgets)

  • Each link's monitor becomes an uptime-kuma/monitor widget, first among its widgets, with the kind's defaults: status, response time, and uptime over the connection's window.
  • A link gets no new widget when it already has a monitor widget for the same monitor, with the ID stored as a number or as text, so earlier widget experiments aren't doubled. It also gets none when it already has ten widgets.
  • Without a Kuma connection the IDs are dropped, since their badges weren't shown either.
  • Then the Links.MonitorId column is dropped. Down restores each link's first monitor widget's ID and keeps the widgets.

Backup format 8

  • Exported links no longer carry monitorId.
  • Older files' monitor IDs convert the same way on import (UseMonitorWidgets), using the file's first Kuma connection.

UI

  • Removed: the tile's badge image and its CSS, LinkTile.StatusBadgeUrl, the link dialog's monitor field, and the monitorId handler parameters and JSON.
  • The list view's Monitor column is now a sortable Widgets count, shown whether or not Kuma is set up.
  • The Kuma card's description and the README are updated.

Kept until 5d: the status bar's badges, monitor-picker.js, KumaMonitors and MonitorIdParser, which the infrastructure groups still use. The seed drops its dormant monitor IDs, as it has no Kuma connection.

Test plan

  • New migration tests:
    • plain links, links with other widgets (which are shifted down), duplicates stored as a number and as text, another integration's widget, the ten-widget limit
    • no connection
    • Down
  • New backup tests: v7 conversion with the same duplicate rules, no Kuma, and no monitorId in exports.
  • Full suite passes: 598 tests. The Release build with ContinuousIntegrationBuild=true is clean. Two full jb cleanupcode passes gave identical results.
  • Migrated a scratch copy of the prod database through every migration:
    • all 9 monitor links became widgets
    • the column was dropped and the foreign key check is clean
    • the dashboard shows the pills, with only the status bar's badges left
    • the list view counts widgets, and the dialog has no monitor field
  • Soak on prod (export a backup first).

🤖 Generated with Claude Code

Each link's MonitorId becomes an uptime-kuma/monitor widget, first among
its widgets, with the kind's defaults. A link that already has a monitor
widget for that monitor (its ID stored as a number or as text) or ten
widgets gets none, and without a Kuma connection the IDs are dropped.
The ConvertLinkMonitorsToWidgets migration does this, then drops the
column; backup format 8 drops links' monitorId and converts older files
the same way on import.

The tile's badge image, the link dialog's monitor field and the list
view's Monitor column go; the list view counts widgets instead. The
status bar keeps its badges, the monitor picker and KumaMonitors until
5d. The seed drops its dormant monitor IDs, having no Kuma connection.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@cerebrate
cerebrate merged commit 56c1b4b into master Oct 17, 2026
7 checks passed
@cerebrate
cerebrate deleted the feature/phase5c-link-widgets branch October 18, 2026 02:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant