This article from InSource shows Intermediate Troubleshooting Techniques Using the Wonderware Logger – Log Flag Editor
- Author: Peter Farrell
- Published: 06/13/2018
- Applies to: All versions
If you encounter a problem or unexpected event, the Wonderware Logger is usually the first place to go to find clues as to what might have happened. This is where background events, warnings, and errors are published. However, due to the volume of background events that occur, the logger by default does not log and publish all events, warnings, and errors.
Although the example screen shot of a Wonderware Logger below is showing multiple information, warning, and error level messages, it may not display enough information for you to determine the cause of a problem.
If you have encountered a problem, and after looking at the Wonderware Logger, you are unable to find any evidence of the cause of the problem, you may be able to surface more data by turning on additional log flags for the Wonderware component that you suspect might be involved.
Open the Wonderware System Management Console (SMC) and look for the Log Viewer in the tree view of the SMC.
Expand Log Viewer > Default Group > Local
Right Click Local and select Log Flags. The Log Flag Editor will now display.
Scroll through the components displayed to the left side of the editor to locate the component for which you need to expose more background events, and click on the component to put it into focus.
You can now select additional Log Flags for the component selected from the "Log Flags for [component name]" pane in the upper right of the Log Flag editor. A common and often useful log flag to add to your Logger is the “Trace” log flag. After selecting additional; log flags, click on File > Apply
IMPORTANT – Make a note of all additional log flags selected and applied so that after troubleshooting is complete you can go back and turn them off. Adding log flags to your Wonderware Logger can bloat the size of the log and make it more difficult to find information at a future time about issues unrelated to the component that you are currently troubleshooting.
In the example below you will see a new log flag called race for the component MobileReportingConnector which provides detailed information, although not necessarily warnings or errors, about the suspect component.
If a Logger message is longer than can be displayed in its column, you can double-click on the line to display more information in a popup version of the entire message.
Remember to go back and turn off any log flags added to your Logger after troubleshooting is complete.