As a follow up to JBEAP-215, this bug report is a member of a series addressing crucial CLI management capabilities.

Display node's protocol://hostname:port

At the moment, this is all there is to see:

"balancer" => {
    "qa_balancer" => {"node" => {"worker-2" => {
        "load" => 89,
        "status" => "NODE_UP",
        "context" => {"/clusterbench" => {
            "requests" => 0,
            "status" => "enabled"
        }}
    }}},
...

Call to action

We need to display node's connection details, e.g. ajp://karm.brq.redhat.com:8019 or https://192.168.1.100:8009.

I set Blocker priority, because without this information available, it is impossible to test anything more than rudimentary smoke-test scenarios. From the user's perspective, inability to identify JVMRoutes (node names) with their connection strings renders any larger enterprise setup very hard to manage and maintain.