You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
There is currently no straightforward way to determine whether a connection to a node is routed via TURN, especially on mobile clients/apps. This lack of visibility can make troubleshooting and diagnosing network issues challenging.
Describe the solution you'd like
Add an option for the client to collect connection statistics, specifically whether TURN was used, along with key metrics such as Time/Duration and RX/TX bytes per connection. If TURN was used, it would also be helpful to log which TURN server was utilized.
Additionally, an option could be provided to share these statistics with the management server for centralized observability.
For privacy reasons, both options (local collection and sharing with the management server) should be strictly opt-in.
Describe alternatives you've considered
The only other solution I'd see is an outside / third party traffic analyzer.
Additional context
This feature would assist in detecting potential configuration issues, provide troubleshooting insights for both consumers and Netbird developers and operators, and help optimize deployments by offering greater visibility into connection behavior.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
There is currently no straightforward way to determine whether a connection to a node is routed via TURN, especially on mobile clients/apps. This lack of visibility can make troubleshooting and diagnosing network issues challenging.
Describe the solution you'd like
Add an option for the client to collect connection statistics, specifically whether TURN was used, along with key metrics such as Time/Duration and RX/TX bytes per connection. If TURN was used, it would also be helpful to log which TURN server was utilized.
Additionally, an option could be provided to share these statistics with the management server for centralized observability.
For privacy reasons, both options (local collection and sharing with the management server) should be strictly opt-in.
Basic example:
Describe alternatives you've considered
The only other solution I'd see is an outside / third party traffic analyzer.
Additional context
This feature would assist in detecting potential configuration issues, provide troubleshooting insights for both consumers and Netbird developers and operators, and help optimize deployments by offering greater visibility into connection behavior.
The text was updated successfully, but these errors were encountered: