Operations Dashboard

Purpose#

The Operations Dashboard is the app's landing page at /, headed "Real-time command center for every pipeline, connection, and byte across the platform." It answers three questions without leaving the page: is the platform healthy, is data moving, and is anything broken right now.

The dashboard is a widget grid, not a fixed report. Thirty widgets ship across ten categories; you decide which ones you look at and in what order, and that choice is stored against your user account.

Before you begin#

• Required role: any authenticated role. viewer sees the dashboard.
• Two widgets need admin to show their data (see Widgets that degrade for non-admins).
• Arranging needs a viewport of 768 px or wider.

Your layout is yours alone — there is no shared or team dashboard, and no role can edit another user's layout.

Reading the page#

Data refreshes every 15 seconds. On large deployments some history widgets read from sampled history rather than every row; when that happens the widget carries a note saying so, so a smoothed curve is never mistaken for the raw truth.

Note. A widget with no data renders its own empty state. That is a statement about your deployment (no streams configured, no email feeds), not a failure — check the matching surface in the left nav before treating it as an incident.

Tasks#

Add a widget#

1. Select Add widget in the toolbar.
2. The drawer titled "Add a widget" opens, listing every currently hidden widget grouped by category.
3. Select Add next to the widget you want.
4. The widget is appended to the bottom of the grid. Drag it into place with Arrange if the position matters.

When nothing is hidden the drawer shows its empty state: "All widgets are on the dashboard. 🎉"

Hide a widget#

1. Open the ⋯ menu on the widget's header.
2. Choose Hide.

Hiding is not deleting. The widget moves into the "Add a widget" drawer and can be brought back at any time — it returns at the bottom of the grid, not at its old position. No widget is ever destroyed, and the nine always-on widgets have no Hide entry in their menu at all.

Reorder widgets#

For a single step, use the ⋯ menu's Move up / Move down.

For bigger changes:

1. Select Arrange in the toolbar — the grid becomes draggable and resizable, and the control changes to Done.
2. Drag widgets to new positions, or drag a widget's corner to resize it.
3. Select Done to leave arrange mode.

Below 768 px the control is disabled and reads "Arranging is disabled on small screens" — the grid stays a single readable column on a phone rather than becoming a drag target.

Reset the dashboard#

Select Reset to discard your customisations and return to the shipped default layout: default visibility, default order, default sizes. Reset affects only your own layout.

How your layout is saved#

Persistence uses GET and PUT /api/v1/me/dashboard-layout. Any authenticated role may call it, and only for their own layout — there is no endpoint for reading or writing someone else's dashboard. Writes are debounced by 500 ms, so a burst of drags becomes one save.

Tip. If a change seems not to have stuck, finish the gesture and let go. Nothing is saved mid-drag by design; the save fires when the drag or resize ends.

Widget catalogue#

Ten categories, thirty widgets. "Default" is what a brand-new user sees before customising.

Always-on widgets#

Nine widgets cannot be hidden, because a dashboard without them can hide an outage: platform-health, live-data-flow-map, pipeline-executions-24h, total-jobs, job-runs-7d, job-success-rate, job-failed-7d, connection-health, and alerts-issues.

You can still move and resize them — they simply have no Hide action, and Reset always brings them back to their default place.

Widgets that degrade for non-admins#

Two widgets read admin-only data. For a viewer or editor the widget still renders, in place, with an explanation instead of content:

This is deliberate: the widget does not vanish, so nobody wastes time hunting for a panel a colleague can see. If you need the data, you need the role — see Roles and permissions.

Failure modes#