Features Request: Enhance Connectivity Troubleshooting

[hotline007]

Hi Team,

First, I would like to thank you for your great effort, the status -d command output is something good for troubleshooting the peer connectivity and also for checking the connection type between peers. but this becomes a very difficult way, especially in 150, 200+ peers environment. and to retrieve that output I have to be physically or remotely with the user. sometimes even remote access is not possible for some users.

So it will be very handy to have this information in the portal under each peer, i should click on the peer and you can put another tab like the system info that allows us to see all the connected peers with their status and connection type. and search bar, filters would be great to search by name, IP, or connection status.

Thank you again and looking forward.

[jiangslee]

There is a temporary solution, I hope it can help you, and I also hope Netbird has a UI or in the portal to filter each peers connection information.

netbird status --json | jq '.peers.details[]|select(.status=="Connected" and .connectionType=="Relayed")'                                       

{
  "fqdn": "mypeer.netbird.selfhosted",
  "netbirdIp": "100.124.***.85",
  "publicKey": "uxKyCK6Fm5Amk***h1aAKvz0+Nj0=",
  "status": "Connected",
  "lastStatusUpdate": "2023-12-29T16:57:36.311651+08:00",
  "connectionType": "Relayed",
  "direct": false,
  "iceCandidateType": {
    "local": "relay",
    "remote": "relay"
  }
}