When a cloud browser test reaches your application through a mabl Link 3.0 tunnel, the Network tab in the test output now shows which Link Agent carried each request. If a request failed or was slow, you can now tell whether one agent, one tunnel, or your network's proxy was responsible without matching timestamps against agent logs.
Use the new Link Agent details in test output to dig deeper into networking issues:
- Find out whether a test that fails on some runs always failed through the same agent.
- See why a connection failed, such as a DNS lookup that failed on the agent's host or a proxy that refused the connection.
- Give mabl support the exact Link Agent host behind a failing request.
Link Agent details are recorded for cloud runs through Link 3.0 tunnels. Requests through legacy Link 2.x tunnels don't include them.
Check it out
On a browser test's output page, open a step's Network tab. A Link Agent column names the machine that served each request by its host name and IP address. Hover over it to see the agent's ID, operating system, distribution, agent version, and worker version. Requests through a personal tunnel read Personal tunnel for followed by the tunnel owner's name.
mabl records these details when the test runs. An agent's ID changes each time it reconnects, so the host name still identifies the machine after the agent has gone away. While the agent is still connected, the name links to that agent in Settings > Networking.
Expand a request to see its mabl Link route. The route lists each connection attempt and shows:
- Tunnel: the tunnel the request used, linked to its settings.
- Link Agent: the agent that handled the attempt.
- Result: whether the agent connected, or why it couldn't. Possible reasons include Connection refused, DNS lookup failed, Connection timed out, Blocked by the agent's connection filter, and Rejected by your network's proxy.
- Route from agent: whether the agent reached your application directly or through your network's proxy.
- Duration (ms): how long the connection took.
If a connection needed more than one attempt, the tooltip gives the number of attempts and the route shows each one.