The log and diagnostic information available to you depends on the method you use for code scanning in your repository. You can check the type of code scanning you're using in the Security tab of your repository, by using the Tool drop-down menu in the alert list. To access this page, see Assessing code scanning alerts for your repository.
Logs on GitHub
You can see analysis and diagnostic information for code scanning run using CodeQL analysis on GitHub.
- Analysis information is shown for the most recent analysis in a header at the top of the list of alerts. See Assessing code scanning alerts for your repository.
- Diagnostic information is displayed in the GitHub Actions workflow logs and consists of summary metrics and extractor diagnostics. To access these logs, see Viewing code scanning logs from GitHub Actions.
Summary metrics
Summary metrics include:
- Lines of code in the codebase (used as a baseline), before creation and extraction of the CodeQL database
- Lines of code in the CodeQL database extracted from the code, including external libraries and auto-generated files
- Lines of code in the CodeQL database excluding auto-generated files and external libraries
Source code extraction diagnostics
Extractor diagnostics only cover files that were seen during the analysis, metrics include:
- Number of files successfully analyzed
- Number of files that generated extractor errors during database creation
- Number of files that generated extractor warnings during database creation
You can see more detailed information about CodeQL extractor errors and warnings that occurred during database creation by enabling debug logging. See Logs are not detailed enough.
Logs for the CodeQL CLI
If you're using the CodeQL CLI outside GitHub, you'll see diagnostic information in the output generated during database analysis. This information is also included in the SARIF results file.
Logs in VS Code
Progress and error messages are displayed as notifications in the bottom right corner of the Visual Studio Code workspace. These link to more detailed logs and error messages in the "Output" window.
You can access separate logs for the CodeQL extension, language server, query Server, or tests. The Language Server log contains more advanced debug logs for CodeQL language maintainers. You should only need these to provide details in a bug report.
To access these logs, see Accessing logs for CodeQL in Visual Studio Code.