coder / coder/vscode-coder

Networking troubleshooting for end users is unclear

Ouverte
#402 2 commentaires 1 réaction 1 personne assignée Réclamée par @EhabY Voir sur GitHub
waiting-for-info
Langage dominant
TypeScript
Étoiles
130
Forks
48
Merge moyen
3 j 3 h
PR mergées (30 j)
15

Description

Our enterprise customers have noted that diagnosing networking latency from within the VSCode extension is difficult. The extension shows real-time latency, but does not offer assistance on how to improve performance.

Since many developers interact with Coder exclusively through VSCode, this is a great location to add finer-grained diagnostic tooling, or simply links to documentation on how to troubleshoot networking problems as a user.

This could be as simple as linking our [Networking Troubleshooting](https://coder.com/docs/admin/networking/troubleshooting) documentation. We could link to the most relevant section of this documentation given a user's connection type as it's already detected by the extension.

Guide de contribution

Ouvrir le guide de contribution

Évaluation

Cette issue n'a pas encore été évaluée.

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.