1
0
mirror of synced 2025-12-20 10:28:40 -05:00
Files
docs/content/code-security/codeql-for-vs-code/troubleshooting-codeql-for-vs-code/accessing-logs.md
2025-03-05 11:35:19 +00:00

41 lines
1.6 KiB
Markdown

---
title: 'Accessing logs'
shortTitle: 'Access logs'
versions:
fpt: '*'
ghec: '*'
ghes: '*'
topics:
- Code Security
- Code scanning
- CodeQL
type: reference
intro: 'If you need to troubleshoot problems with {% data variables.product.prodname_codeql %} for {% data variables.product.prodname_vscode %}, there are several logs you can access.'
allowTitleToDifferFromFilename: true
---
## About logs
Progress and error messages are displayed as notifications in the bottom right corner of the {% data variables.product.prodname_vscode %} workspace. These link to more detailed logs and error messages in the "Output" window.
You can access the following logs:
* {% data variables.product.prodname_codeql %} Extension
* {% data variables.product.prodname_codeql %} Language Server
* {% data variables.product.prodname_codeql %} Query Server
* {% data variables.product.prodname_codeql %} Tests
> [!NOTE]
> The {% data variables.product.prodname_codeql %} Language Server log contains more advanced debug logs for {% data variables.product.prodname_codeql %} language maintainers. You should only need these to provide details in a bug report.
## Accessing logs
1. In {% data variables.product.prodname_vscode %}, open the "Output" window.
1. Use the dropdown to select the log view you need. For example, "{% data variables.product.prodname_codeql %} Extension Log".
![Screenshot of the "Output" window in VS Code (as highlighted in dark orange). The dropdown is also highlighted, with "CodeQL Extension Log" selected.](/assets/images/help/security/codeql-for-vs-code-access-logs.png)