Deployment Monitoring
Monitor deployment status, heartbeats, and the event timeline.
After installation, the deployment detail page provides real-time visibility into the health and activity of your edge gateway.
Status overview
The deployment detail page displays four status cards at the top:
| Card | Description |
|---|---|
| Status | Current deployment status with a color-coded badge |
| VPN IP | The private VPN address assigned to the gateway, or "Not connected" |
| Last Heartbeat | Time elapsed since the last heartbeat, or "Never" |
| Architecture | The CPU architecture selected during creation (amd64 or arm64) |
Deployment statuses
| Status | Badge color | Description |
|---|---|---|
| Pending | Gray | Deployment created but the bootstrap command has not been run |
| Deploying | Blue | Bootstrap script has started; waiting for the first heartbeat |
| Online | Green | Gateway is running and sending regular heartbeats |
| Offline | Red | No heartbeat received for five or more minutes |
| Error | Red | A bootstrap or runtime error occurred |
The status updates automatically as the gateway progresses through its lifecycle.
Heartbeats
The config agent on the edge gateway sends a heartbeat to the cloud every 60 seconds. Each heartbeat includes:
- Deployment ID — identifies the gateway
- VPN IP — the current private VPN address
- Edge version — the version of Fleetera Edge running on the gateway
- Service statuses — the health of each Docker container (running, stopped, or error)
When a heartbeat is received, the deployment status is automatically set to Online. If no heartbeat arrives within five minutes, the status changes to Offline.
The Last Heartbeat card on the detail page shows the elapsed time since the most recent heartbeat (for example, "2 minutes ago").
Event timeline
The deployment detail page includes an event log that records key lifecycle events in reverse chronological order. Each entry shows a timestamp, event type, and a descriptive message.
Event types
| Event | Description |
|---|---|
| Created | Deployment was created |
| Token Generated | A bootstrap token was generated |
| Token Regenerated | The bootstrap token was regenerated |
| Token Used | The bootstrap token was consumed during installation |
| Registered | The edge gateway registered successfully with the cloud |
| VPN Connected | The VPN connection was established, with the assigned IP address |
| Services Started | Fleetera Edge services started on the gateway |
| Heartbeat | A regular heartbeat was received |
| Offline | The gateway stopped sending heartbeats |
| Error | An error occurred during bootstrap or runtime |
Events are color-coded by severity — green for success events, amber for warnings like going offline, and red for errors. Heartbeat events appear in a muted style to keep the timeline readable.
Detail page layout
Below the status cards, the deployment detail page is organized into three sections:
Configuration
Displays the deployment settings:
- Site name (with a link to the site)
- Architecture
- Alias and VPN hostname
- Creation date
- Auto-publish configuration toggle
- Docker Compose download button (when available)
Config sync status
Shows the current state of configuration synchronization:
- Sync status badge (in sync, pending, applying, or error)
- Desired version versus applied version
- Published and applied timestamps
- Device services summary with profile and device counts
- Error details if synchronization failed
- A Publish Config button to manually trigger a new configuration push
This card auto-refreshes every 30 seconds when the deployment is online.
Event log
A scrollable timeline of deployment events, showing the most recent events first. Each entry includes the time, event type, and message.
Installation command
The deployment detail page also displays the installation command with the current bootstrap token. You can copy the command directly from this section. If the token has expired or been used, you can regenerate it from this page (see Edge Installation for details).
Token regeneration is only available when the deployment is in Pending, Offline, or Error status.