Fleet and Releases
This is where you watch every deployment in the field and control what software it runs: the fleet dashboard with heartbeat freshness, maintenance windows, releases and feature flags.
Who can do this:
- support — fleet dashboard and alerts, maintenance windows.
- release_manager — releases, maintenance windows and feature flags (
releases.manage,maintenance.manage,flags.manage).
Fleet monitoring
Section titled “Fleet monitoring”The Fleet dashboard (fleet → GET /fleet) lists every deployment with its heartbeat freshness — re-derived live, never mocked. A deployment whose heartbeat goes stale surfaces as an alert.
- Deployment detail (
fleet/deployment/:id), plus regions, heartbeats and fleet settings. - Fleet alerts (
fleet/alerts) — open an alert and Acknowledge it (POST /fleet/alerts/:id/acknowledge). The acknowledgement is audited.
Heartbeats and the on-prem grace/lockdown behaviour are covered in Licensing.
Maintenance windows
Section titled “Maintenance windows”Schedule downtime and tell customers about it:
- Open Maintenance (
releases/maintenance). - Create a window (
releases/maintenance-new→POST /maintenance). - Broadcast it (
POST /maintenance/:id/broadcast) so affected tenants are notified. Schedule and broadcast both persist and audit.
Releases
Section titled “Releases”Manage the software customers run:
- Releases (
releases) lists releases; open one for detail. - Create a release (
releases/release-new→POST /releases). - Set a tenant’s update channel (
PUT /tenants/:id/channel) to control which release line they receive.
Creating a release requires releases.manage and is audited.
Feature flags
Section titled “Feature flags”Toggle features per the rollout plan:
- Open Feature Flags (
releases/feature-flags). - Edit a flag (
PUT /feature-flags). Changes persist and audit; editing requiresflags.manage.