Device Status
The Device Status page provides a real-time overview of all edge devices managed within your tenant. Toggle between table view and grid view using the view selector in the toolbar.
Status Indicators
Each device displays a color-coded status indicator based on its heartbeat activity:
| Status | Indicator | Meaning |
|---|---|---|
| Online | Green | The device is actively reporting. Heartbeat received within the expected threshold. |
| Offline | Red | No heartbeat has been received from the device. It may be powered off, disconnected, or unreachable. |
| Warning | Yellow | CPU or memory usage exceeds the warning threshold (derived from telemetry). |
| Error | Red | CPU or memory usage exceeds the critical threshold, or the device is unreachable. |
Devices report their status via periodic heartbeats. Dedicated edges and MTGEs send an inform message every 60 seconds containing VPP interface statistics. Connectors send a keepalive every 30 seconds.
Device Information
For each device, the status page displays:
- Device Name and Serial Number -- Identifies the device in your network.
- Last Seen -- The timestamp of the most recent heartbeat or inform message from the device. This tells you exactly when the device last reported in.
- WAN IP -- The current public IP address of the edge, extracted from the VPP interface inform data. This is useful for verifying the device's internet-facing address, especially after network changes.
- Config Sync Status -- Shows whether the device's running configuration matches the orchestrator's desired configuration. Possible states include:
- In Sync -- The device has confirmed receipt and application of the latest configuration.
- Pending Sync -- A configuration change has been made but not yet delivered to the device.
- Sync Failed -- The device reported an error applying the configuration.
Toolbar Controls
| Control | Description |
|---|---|
| View toggle | Switch between table (rows) and grid (cards) layout |
| Status filter | All / Online / Offline / Warning / Error |
| Auto-refresh | Off, 30s, 1m, or 5m polling intervals |
| CSV Export | Download the current filtered view as a CSV file |
Click on any device row (or card) to navigate to its detail page.
Config Sync Status
The Config column shows the synchronisation state between the orchestrator and the edge:
- Synced (green) — running config matches desired config
- Pending (blue) — a change has been made but not yet delivered
- Failed (red) — the edge reported an error applying the config
- Drift (amber) — the edge's live VPP state diverges from the expected config (count shown in badge)
If a device appears offline unexpectedly, check its physical connectivity and power status first. You can also use the Diagnostic Tools to test reachability once the device comes back online.
How Online/Offline Detection Works
The dashboard uses a dual-check approach to determine whether a device is online. Both of the following conditions must be true for a device to show as online:
- Telemetry presence — The orchestrator queries the metrics database for recent CPU usage data from the device. If metric data exists, the device has been reporting telemetry recently.
- Last seen recency — Every time a device sends a heartbeat or status report, its "Last Seen" timestamp is updated. The dashboard considers a device offline if this timestamp is more than 5 minutes old.
This dual-check approach prevents false positives. For example, if cached metrics exist in the database but the device has actually stopped reporting, the stale "Last Seen" timestamp will correctly cause it to show as offline.
Heartbeat Intervals
Different device types report at different intervals:
| Device Type | Report Type | Interval | What It Contains |
|---|---|---|---|
| Dedicated Edge | Inform | Every 60 seconds | VPP interface statistics, WAN IP address |
| MTGE | Keepalive | Every 30 seconds | Heartbeat signal (updates last-seen time) |
| MTGE | Inform | Every 60 seconds | VPP interface statistics, WAN IP address |
| Connector | Keepalive | Every 30 seconds | Heartbeat signal (updates last-seen time) |
If a device misses several consecutive heartbeats and its last-seen timestamp exceeds 5 minutes, the dashboard transitions its status to Offline.
For a deeper look at how telemetry flows from edge devices through the observability pipeline — including metrics, logs, IPFIX flows, and alerting — see Observability Pipeline in the Admin Guide.