Periodically the support team will ask for a specific trace to be enabled. Many of these traces can produce a lot of data if left on very long. The approach in this article will capture the problem and minimize the information captured.
Preparing to recreate the issue
You will need an administrator and the person having the error. They need to be both use their own browsers on separate systems.
The person creating the error condition needs to get ready to recreate it. For example, when capturing issues at login, they should be on the login screen. For an issue with a specific viewlet, they should be on the dashboard that contains that viewlet. And so on.
Activating the trace
Once they are ready, the administrator needs to open the workspace and select the corresponding WGS Properties. Navigate to the Trace Tab
Enable the required trace and press Ok. At this point the properties dialog will close and the trace will be active.
Have the user recreate the issue by logging in or refreshing the viewlet or running the action, etc.
Deactivate the trace
Select Properties again and view the Trace tab
Turn off the trace activated and press Ok again.
Collect the logs required
Note the time and collect the WGS log from the server by copying to another location.
You should ensure that the log starting and ending time stamps cover the period intended. If not, it may have rolled and be in one of the archived logs. In some case, multiple logs may be required.
Provide the logs, the id of the user recreating the issue and the time as part of the support ticket.