Diagnostics#
Observe → Diagnostics: connection tracking, network tools, neighbours, processes, time and packet capture. The page opens on the Health tab, and returns to it when it is reloaded.
| Tab | What it shows | What it changes |
|---|---|---|
| Health | Whether the router's connection table is coping, judged over the last ten minutes, and the counters behind the verdict. | Connection tracking settings: table size, hash size and connection accounting. |
| Tools | Traceroute and DNS lookup, run from the router. | Wake-on-LAN sends a wake-up packet to a device on the network. |
| Neighbours | What the switches and routers next to the router announce over LLDP, and the IPv4 neighbour table. | LLDP: on or off, on which interfaces, and its options. |
| Processes | The processes running on the router. | Nothing. |
| Time | The time servers, the router's uptime beside your browser's clock, and how well the router is synchronised. | The list of time servers. |
| Capture | A packet capture on one interface, as it runs. | Nothing in the router's settings. It starts, stops, downloads and deletes a capture. |
Settings and actions#
The settings on this page are edited like any other: an editor adds its changes to the pending changes, and Apply changes in the bar at the bottom of the page applies them. Nothing changes on the router until then. Editing needs the operator role and a licence.
The actions below happen at once and change no settings:
| Action | Tab | Role |
|---|---|---|
| Trace | Tools | Operator |
| Look up | Tools | Any role |
| Wake device | Tools | Operator |
| Start capture, Stop capture, the file's Download link, Delete | Capture | Operator |
None of them needs a licence. Every Wake-on-LAN attempt and every capture that is started, stopped, downloaded or deleted is recorded in the audit log.
How often each tab refreshes#
| Read | Interval |
|---|---|
| Health: connection tracking | 5 seconds |
| Neighbours: IPv4 neighbours | 10 seconds |
| Neighbours: LLDP | 15 seconds |
| Processes | 10 seconds |
| Time | 30 seconds |
| Capture | Every second while a capture runs, and every 15 seconds while its file is on the router |
What the page does not do#
- No ping. The tools are traceroute, DNS lookup and Wake-on-LAN.
- No IPv6 neighbours. They are on the IPv6 page.
- No history. The Health verdict covers the last ten minutes; everything else is the current value. To keep figures over time, collect the agent's metrics (Telemetry).
For automation#
| Tab | Calls |
|---|---|
| Health | GET /api/conntrack/stats, GET /api/sessions |
| Tools | POST /api/diagnostics/traceroute, GET /api/diagnostics/lookup, POST /api/diagnostics/wake-on-lan |
| Neighbours | GET /api/lldp, GET /api/neighbors |
| Processes | GET /api/processes |
| Time | GET /api/ntp, GET /api/system |
| Capture | POST /api/capture, GET /api/capture, POST /api/capture/stop, DELETE /api/capture, GET /api/capture/download |
Each tab's page lists the roles and answers of its calls. Setting changes go through the pending changes, as every editor's do; the automation guide shows the calls.