Skip to main content
All products
Code security

This version of GitHub Enterprise was discontinued on 2023-07-06. No patch releases will be made, even for critical security issues. For better performance, improved security, and new features, upgrade to the latest version of GitHub Enterprise. For help with the upgrade, contact GitHub Enterprise support.

Logs are not detailed enough

In this article

If you'd like to increase the level of detail in your logs, try these steps.

Code scanning is available for organization-owned repositories in GitHub Enterprise Server. This feature requires a license for GitHub Advanced Security. For more information, see "About GitHub Advanced Security."

If your logs are not detailed enough, there are several steps you can take to make them more useful.

Enable step debug logging

You can enable step debug logging in GitHub Actions to increase the verbosity of a job's logs during and after a job's execution. For more information, see "Enabling debug logging."

Creating CodeQL debugging artifacts

You can obtain artifacts to help you debug CodeQL. The debug artifacts will be uploaded to the workflow run as an artifact named debug-artifacts. The data contains the CodeQL logs, CodeQL database(s), and any SARIF file(s) produced by the workflow.

These artifacts will help you debug problems with CodeQL code scanning. If you contact GitHub support, they might ask for this data.

Creating CodeQL debugging artifacts using a workflow flag

You can create CodeQL debugging artifacts by using a flag in your workflow. For this, you need to modify the init step of your CodeQL analysis workflow file and set debug: true.

- name: Initialize CodeQL
  uses: github/codeql-action/init@v2
  with:
    debug: true