FluxDeployDocs
Topics: Dashboard

Dashboard

The Dashboard (/) is the default landing page and gives an at-a-glance view of the health of the deployment environment. It surfaces problems first and keeps the rest of the UI quiet when everything is working.

Attention List

There is exactly one to-do list on this page, at the top, headed "N things need attention". It is the only place the Dashboard tells you to do something, and it consolidates:

  • Health issues from the weighted score (license expiry or node overage, unreachable relay sites, certificate expiry, storage, database)
  • Any health topic that is failing, linking to that topic's view further down the page
  • Jobs that failed in the last 24 hours (boot image builds, image customizations, driver downloads)
  • Outstanding setup steps on an install that is not configured yet (see below)

Topics that are only warning stay on the topic pills below and do not repeat here: the pills are the status overview, the list is the action list, so any one issue appears once on the page. When there is nothing to do the list is replaced by a single All systems ready line.

One line per topic

Each topic gets at most one line, however many objects are involved. Four unreachable relays and one outdated relay are one row reading "Relay Sites - 4 sites unreachable, 1 outdated", not five - and a relay that is both unreachable and outdated is counted once in each fact rather than taking two rows of its own. Click the row to see the individual objects on the page that owns them.

Lines are ordered so that the most serious come first: critical before warning, then by subsystem (a site that is down outranks a certificate that expires next month), with setup steps last because they are not failures. If there are more than four lines, the rest fold behind a Show N more link that expands in place. The heading always counts every item, so the number never hides anything the list does.

Stat Cards

Six summary cards show the current state of the system:

  • Machines - Total registered
  • Deploying - Currently in progress
  • Completed (24h) - Successful deployments in the last day
  • Failed (24h) - Failed deployments in the last day
  • Relay Sites - Online / Total (Core only)
  • PXE Status - Core PXE listener state (Enabled, Disabled, or error)

Each card is clickable and navigates to the relevant page (Devices, Sites, or PXE settings).

Relay Sites Table (Core)

On Core servers the dashboard includes a condensed relay site table showing each site's name, status, last heartbeat, and sync state. This is a read-only summary - use Sites for management actions.

Force Check-In (Relay)

On Relay servers the dashboard replaces the sites table with a Force Check-In button that triggers an immediate heartbeat to Core. Useful when troubleshooting a newly registered site or a manifest change that hasn't propagated yet.

Setup Steps

On a new install the outstanding setup steps (install a relay site, upload an ISO, set the local admin password, create a boot image, create a Windows image, create a recipe) appear in the attention list as one line - "Finish setup (N steps remaining)" - which links to the next step. When only one step is left it shows that step's own description instead. Setup always sorts to the bottom of the list, because an unfinished step is not a failure.

Setup retires itself once the install is configured - that is, once there is at least one relay site, at least one Windows image and at least one recipe. The optional steps do not hold it open: an install with no ISO left in the library and no boot image is a perfectly normal configured install.

A Dismiss setup steps link below the list removes them earlier. Dismissal is stored in AppSetting["QuickStartDismissed"] and applies to all users.