This article applies to:
Question:
- How do I setup an SWG into debug mode?
Procedure:
When trouble shooting an issue, there might be a need to gather extended logs from the SWG. By default these “debug” logs are not turned on. Follow the instructions below to turn on Debug logs and then reproduce the issue that you are seeing.
- Log into the Management console and go to Administration -> System Settings -> Debug log.
- Set the debug log level to 1 (full trace). Save and commit.
Now you will want to reproduce the issue by surfing to the site that is exhibiting the issue while going through the SWG proxy.
Once the issue is reproduced, go back into the GUI and set the debug log level back to 6 (fatal errors only), then you will need to immediately save the support logs by going to the limited shell and type the command save_support_logs. To collect the support logs, please see the following KB article.
Note:
*It’s very important that the logs are saved directly after the issue is reproduced. While in debug mode the logging profile is greatly increased so that they will record all data that goes through the system. Since this is the case, the logs on the system will rotate out very fast, if too much time is given between the issue and when the logs are gathered, the log containing the issue could rotate out and the data that is needed will be lost
