coder / coder/vscode-coder

Networking troubleshooting for end users is unclear

Abierto
#402 2 comentarios 1 reacción 1 asignado Reclamado por @EhabY Ver en GitHub
waiting-for-info
Lenguaje dominante
TypeScript
Estrellas
130
Forks
48
Merge medio
3 d 3 h
PR fusionados (30 d)
15

Descripción

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.

Guía de contribución

Abrir la guía de contribución

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.