opensource/coder
3
0
Fork 0
mirror of https://github.com/coder/coder.git synced 2026-09-24 15:04:27 +08:00
Code Issues Packages Projects Releases Wiki Activity

docs: document VS Code local telemetry (#26215)

Browse Source 
Document local telemetry behavior, diagnostics commands, support bundle contents, and the VS Code telemetry event reference.
This commit is contained in:
Ehab Younes
2026-06-11 19:08:08 +03:00
committed by GitHub
parent 9b550cbfe9
commit c883db9ee4
2 changed files with 75 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/support/support-bundle.md
+8
View File
@@ -53,6 +53,7 @@ A brief overview of all files contained in the bundle is provided below:
| `workspace/template.json` | The template currently in use by the selected workspace. |
| `workspace/template_file.zip` | The source code of the template currently in use by the selected workspace. |
| `workspace/template_version.json` | The template version currently in use by the selected workspace. |
| `vscode-logs/` | Only present when generated from the VS Code Coder Remote extension. Includes logs, redacted settings, and local telemetry files. |
## How do I generate a Support Bundle?
@@ -76,6 +77,13 @@ A brief overview of all files contained in the bundle is provided below:
prompt. The support bundle will be generated in the current directory with
the filename `coder-support-$TIMESTAMP.zip`.
If you use VS Code, you can also run **Coder: Create Support Bundle** from
the Command Palette. The VS Code Coder Remote extension runs
`coder support bundle` and appends recent VS Code diagnostics to the
generated archive. Bundles created with the CLI alone do not include
`vscode-logs/`. Learn more about
[VS Code diagnostics](../user-guides/workspace-access/vscode.md#diagnostics-and-support-bundles).
> [!NOTE]
> While support bundles can be generated without a running workspace, it is
> recommended to specify one to maximize troubleshooting information.