Viewing logs for GitHub Copilot in your environment

Collecting log files

The location of the log files depends on the JetBrains IDE you are using. For more information, see Configuring GitHub Copilot in your environment.

These steps describe how to view and collect the log files for the following JetBrains IDEs:

• IntelliJ IDEA
• Android Studio
• GoLand
• PhpStorm
• PyCharm
• RubyMine
• WebStorm

The GitHub Copilot extension logs to the IDEA log location for IntelliJ plugins.

1. In your JetBrains IDE, open the Help menu.
2. Go to Show Log in Finder.
3. Open the idea.log in your preferred editor and look for any errors related to GitHub or GitHub Copilot.

For more information, see the Locating IDE log files in the IntelliJ documentation.

Collect log files from Rider

1. In Rider, open the Help menu.
2. Go to Diagnostic Tools.
3. Go to Show Log in.
4. Open the idea.log in your preferred editor and look for any errors related to GitHub or GitHub Copilot.

Enabling debug mode

If you find the log file doesn't contain enough information to resolve an issue, it may help to enable debug logging temporarily. This can be especially helpful for debugging network-related issues.

1. In the menu bar, click Help, select Diagnostic Tools, and click Debug Log Settings....

   

2. In the "Custom Debug Log Configuration" window, add a new line with the following content, then click OK.

   Text

   #com.github.copilot:trace
   

3. Keep using your IDE until you encounter the issue again, then collect the log file as described in Collecting log files.

4. When you have the information you need, disable debug mode by removing #com.github.copilot:trace from the "Custom Debug Log Configuration" window.

Viewing network connectivity diagnostics logs

If you encounter problems connecting to GitHub Copilot due to network restrictions, firewalls, or your proxy setup, use the following troubleshooting steps.

1. In the menu bar, click Tools, select GitHub Copilot, and click Log Diagnostics.
2. The idea.log file should open in the JetBrains IDE with the diagnostics output. Alternatively, you can open the idea.log file in your preferred editor.
3. Check the section on Reachability to determine if GitHub Copilot can access the necessary services.

Troubleshooting certificate-related errors

If you're using a custom certificate, ensure the certificate is installed correctly in the operating system, see Troubleshooting network errors for GitHub Copilot. Then use the following troubleshooting steps.

1. In the menu bar, click Tools, select GitHub Copilot, and click Log CA Certificates.
2. The idea.log file should open in the JetBrains IDE with the trusted CA certificates logged in PEM format. You may need to refresh the idea.log file to view all of the output. Alternatively, you can open the idea.log file in your preferred editor.
3. Check to see if the expected custom certificate is included in the certificate list output.

:Copilot status