Observability Dashboard
The Observability Dashboard provides a consolidated view of a single edge device's health and performance. Unlike earlier versions that embedded external Grafana dashboards, this page queries VictoriaMetrics directly via PromQL and renders the data natively in the SecureLink UI.
Edge Selector
Use the dropdown at the top to select the edge you want to inspect. All panels below update to show data for the selected device.
System Status Cards
A row of status cards shows the latest point-in-time readings:
| Card | Metric | Description |
|---|---|---|
| Uptime | edge_uptime_seconds | Time since the edge agent last started |
| MQTT | edge_mqtt_connected | Broker connection status (Connected / Disconnected) |
| CPU | edge_cpu_usage_percent | Current processor load with colour threshold |
| Memory | edge_memory_bytes / edge_memory_total_bytes | Usage as a percentage of total |
Time-Series Charts
Below the status cards, multiple time-series panels cover the last hour (configurable):
Resource Utilisation
- CPU History —
edge_cpu_usage_percentover time - Memory History —
edge_memory_bytes/edge_memory_total_bytesas percentage
Network I/O
- Interface RX/TX — per-interface byte rates (
edge_interface_rx_bytes_total,edge_interface_tx_bytes_total) - Errors — RX/TX error rates (
edge_interface_rx_errors_total,edge_interface_tx_errors_total) - Drops — RX/TX drops (
edge_interface_rx_dropped_total,edge_interface_tx_dropped_total)
WireGuard
- Server Enabled — whether the wg0/wg1 instance is active
- Peer Count — total configured peers vs established peers
- Server Port — listening port (51820/51821)
- Peer Count History — time series of peer count changes
- Established Peers History — time series of established peer count
VPP Dataplane
- VPP RX/TX — byte counters from VPP interfaces
- VPP Errors/Drops — VPP-level error and drop counters
Auto-Refresh
The dashboard refreshes automatically every 30 seconds. Background refreshes do not trigger the global loading overlay.
All metrics are sourced from VictoriaMetrics via the agent's 15-second MQTT push cycle. Metric data is retained according to the configured retention policy.