Monitor → Tools (Network Diagnostics)
The Tools tab on the Monitor page is an on-demand network diagnostics console. You pick a tool, fill in its parameters, choose which workers should run it, and see each worker’s result side by side. Because the tests run from your workers — which sit close to the managed environments — you can check reachability and behaviour from the vantage point that actually matters, not just from your own browser.
Available tools
| Tool | Checks |
|---|---|
| Ping | Reachability and round-trip time to a host. |
| Trace | The network path (hops) to a host. |
| DNS | Name resolution for a hostname or record. |
| Port | Whether a TCP port is open. |
| HTTP | An HTTP(S) request and its response. |
| SSL | A server’s TLS certificate and handshake. |
| MTU | The largest packet size that reaches a host without fragmentation. |
| iperf3 | Throughput between two workers (or a worker and a host). |
| Subnet | A sweep of an address range. |
| NTP | Time-server reachability and offset. |
| Whois | Registration data for a domain or address. |
Common tasks
Run a diagnostic
- Click a tool card in the toolbar. Its parameter form appears on the left, with a short description of what the tool does.
- Fill in the parameters (for example, the target host and port).
- Under Workers, select between one and five workers. (iperf3 has no separate Workers block — its source picker chooses where the test runs.)
- Click Run.
- Results stream into the right-hand panel as each worker reports back — one card per worker, showing its name, location, status (pending, running, success, failed), and output.
Read the results
Each result card can be expanded to show the full output. Comparing cards across workers tells you whether a problem is local to one site or estate-wide — for instance, a host that pings from one region but not another.
Measure throughput with iperf3
iperf3 needs two endpoints. Choose the source and destination workers (or a worker and a target host), then Run. The result reports the measured bandwidth between them.
Notes
- Tools dispatch work to your workers, so a tool can only run where at least one selected worker is online.
- Worker choices are available globally, even when your resource permission is limited to specific locations. This lets you test connectivity from the most useful network vantage point.
- Most tools observe network behaviour. The HTTP tool can also send POST, PUT, PATCH, or DELETE requests; these methods may change the target. Every request originates from the selected worker and can reach destinations available from that worker’s network.
Permissions
- Open the Tools tab and run diagnostics:
app.resources.execute.