Synced from Hive. This page is pulled from hivecommons/hive@v5 during the docs build. Edit the canonical source in the Hive repository.

Hub Fleet activity page

The Fleet activity page at https://<hub>/activity is a read-only board of the open issues and pull requests that the hives you can see are working on. It is the hub-side view of the Activity Monitor: each spoke attaches a bounded activity digest to its heartbeat, and the hub merges the digests of your hives into one board.

Open it from the 📡 Fleet activity link next to 🔬 Evidence on the dashboard’s Fleet quadrant card, or go to /activity directly. You must be signed in; a browser without a hub session is sent to /login.

The design is RFC #15861 by @hanthor, delivered in #15965 and its children. The page itself is #16063; its display mode is #16064.

Who sees what

The page shows exactly what GET /api/hub/activity returns for you. That endpoint decides access per hive on the server before it reads any data:

  • A hub admin sees every registered hive.
  • Everyone else sees the hives they own and the hives they hold an unexpired grant for.
  • Another hive’s rows, counts and freshness never reach your browser, so they are not in the page and not in its ETag.

The page itself carries no fleet data. It is a static shell that loads the board from the endpoint.

Reading the board

Each row is one open issue or PR:

ColumnShows
HiveA colour chip per hive. The colour is stable per hive id. The chip opens that hive’s own dashboard and tracker through the hub’s hive route (/api/saas/hives/<id>/open), which signs you in or explains why it cannot.
Itemowner/repo#N and whether it is an issue or a PR. It links to the item on GitHub.
TitleThe item title as plain text, capped at 200 characters by the hub. A leading [agent] tag is drawn as a chip.
StageThe strip column the spoke tracker would light (Open, Actionable, Claimed, PR in progress, CI / Review, Merge gate, Merged) and the stage slug.
Authorhuman, clanker or hive when the spoke knows it.

Rows are ordered like the spoke tracker’s default sort: furthest strip column first; within a column, rows with a modifier or parked on a person first and held or draft rows last; then longest in stage. am.sort and am.dir change the order (see Display mode and URL views).

Group by hive is on by default. It draws one header row per hive, even when the hive has no open items. The header shows:

  • the item count, plus the hive’s tracked total when the digest held some back;
  • freshness:
    • fresh: the hive’s activity report is recent;
    • stale: the last activity report is older than two missed heartbeats (more than 4 minutes);
    • not reporting: the hive heartbeats but sends no activity block. Upgrade it to report activity;
    • missing: you hold a grant for a hive the hub registry does not know.

Turn grouping off for one flat list. The Hive column still tells rows apart.

What the board leaves out

The list above the table is always visible. It never hides in a tooltip. It names every gap in the data:

  • items left out by the hub’s response cap;
  • items a hive’s own digest cap left out (truncated);
  • events dropped before they reached the hub (events_dropped);
  • stale, not-reporting and missing hives.

When nothing is missing it says so: “All N hives reporting; nothing left out”.

Refresh

The page polls GET /api/hub/activity every 15 seconds with If-None-Match. The hub answers 304 Not Modified while nothing in your view changed, and the board is redrawn only when the ETag changes. Polling pauses while the tab is hidden and resumes, with an immediate refresh, when you come back. The status line shows when the data last changed and when it was last checked. If your session expires, the page sends you to /login.

Display mode and URL views

The page takes the same display parameters as the spoke Activity Monitor (see Display mode and URL views). They are the spoke’s own parameters, read by the spoke’s own code: the hub serves a byte-identical copy of the spoke’s URL-view and playlist helpers (src/pkg/webassets/trackerview). There are no hub-only display parameters.

ParameterOn /activity
kiosk=1Unattended screen: hides the hub header, the description and the Group by hive toggle, and hides the cursor. The status line and the coverage list stay. A kiosk never rotates a playlist.
display=1Attended wall screen: the same chrome-less board, with the cursor. Esc (unless the browser is in full screen) or d leaves display mode and keeps the rest of the URL. kiosk=1 wins when both are set.
am.*The board’s view, with the spoke’s keys and values. See the table below.
am.view, intervalA playlist, in display mode only. Each am.view is a URL-encoded am.* query string, and every entry is a hub-activity view: this board under that entry’s am.* state. interval is Ns or Nm, clamped to 10 s – 1 h, default 60 s. With fewer than two valid entries the board does not rotate.

How each am.* key applies here:

KeyEffect on the hub board
am.kindpr or issue only.
am.repoOne owner/repo, exact match.
am.qTitle text, or the item number (123 or #123).
am.authorhuman, clanker or hive.
am.sort, am.dirfurthest (default), waiting (longest in stage) or number; asc / desc. newest needs an opening time the digest does not carry, so it sorts as furthest.
am.groupnone turns grouping off. Grouping by hive is the default and is never written into the URL. A spoke value the hub board has no grouping for (repo) falls back to the default, as an unknown value does on the spoke.
am.labels, am.needsHuman, am.onHold, am.attention, am.age, am.actedNot applied: the activity digest carries no labels or verdicts for them. They stay in the URL, so the link still works on a spoke, and the coverage list names them under Not applied on the hub.

A link copied from a spoke display therefore opens on the hub with the same view where the hub has the data for it, and says which parts it could not apply. Turning Group by hive on or off rewrites am.group in the address bar, so the address is always a link to the current view; credentials in the URL never survive that rewrite.

The playlist follows the spoke’s rules:

  • The current view follows the wall clock, so a reload resumes on the same view. Rotation happens in memory: it does not navigate, refetch or change the URL.
  • A thin bar at the top shows the time until the next view. With reduced motion it is a static N/M · next in Ns label instead.
/activity?display=1&am.view=am.kind%3Dpr&am.view=am.group%3Dnone%26am.repo%3Dhivecommons%2Fhive&interval=2m

The spoke-only wall options density=tv and shift=1 are ignored here.

Public-safe view

https://<hub>/activity/public is the same board served to anyone, without a session (#15966). It is the source of the twitch.tv/hivecommonsfleet broadcast (Streaming the Activity Monitor). On that path the page polls GET /api/hub/activity/public with credentials: 'omit', and the endpoint never reads a cookie, token or Authorization header, so a signed-in browser or an admin gets the same rows as an anonymous visitor.

The view is filtered on the hub before it is built:

  • Only hives the registry lists as public (the flag the public registry and leaderboard use) on public github.com. A hive with no public flag, or on a GitHub Enterprise host, is left out.
  • Only items and events the spoke marked public. A spoke marks a repository private unless it knows it is public, so unknown visibility is left out.
  • No totals, digest truncated or events_dropped, since those can count private items, and no hive owner.
  • No per-user grants: your own access never widens it.

The body is served from a hub-side cache: it is built at most once every 2 seconds per parsed filter and shared by every anonymous caller, so rows, generated_at and the ETag can lag the latest heartbeat by up to 2 seconds, and a client polling faster than that gets 304 until the next build. Query strings that parse to the default view share one entry. Toggling a hive’s visibility drops the cache immediately.

What the page does not do

  • It has no action menus. The hub is visibility-only: act on an item on GitHub, or from the hive’s own tracker.
  • /activity is not a broadcast source. Display mode only changes how the signed-in page looks; the page still needs a hub session and shows only your hives. Broadcast only the public-safe view.

Security

  • The page is served with its own Content-Security-Policy. Scripts and styles load only as files from the hub ('self'). Inline scripts, inline event handlers and inline style attributes are refused, and the page loads nothing from other origins.
  • Titles and every other value from a spoke are written as text, never parsed as HTML.
  • The page, its script and the shared row-presentation and view assets are revalidated on every load (Cache-Control: no-cache with a content ETag), so a hub upgrade is picked up on the next visit.
  • /activity (including /activity/public) is marked noindex and is disallowed in robots.txt.

For operators

  • A spoke publishes its digest only when hub.activity.enabled is on. It is on by default for hosted spokes and opt-in for self-hosted ones. A hive that heartbeats without it shows as not reporting.
  • Digests live in hub memory only. After a hub restart, hives show not reporting until a later heartbeat carries a full digest again.
  • Rows are drawn with the tracker’s own row-presentation asset (src/pkg/webassets/trackerrow), which the hub serves under /activity/assets/. The page defines the stage constants that asset reads, with the spoke’s values, so a hub row lights the same column as the spoke tracker.