|
In this section: |
The Log Files page displays links to all log files in a single location, where you can review or capture copies of them instantaneously when required to provide records of system events to the Customer Support Team to support troubleshooting or system analysis in response to production issues.
The main grid lists log files, in alphabetical order, by name. Next to each Log Name entry is a list of Logger Names, that is, those pages or events that contribute entries to that log. For example, the audit.log file captures events from com.ibi.uoa, com.ibi.config, com.ibi.content, and others.
Log files contain records of system events. The Log Level field, next to each Logger, identifies the level of events captured by that contributor.
Log levels are cumulative. Events captured by a higher level are included when you select a lower level. For example, if you set the level to WARN, you will capture FATAL level and ERROR level events, as well as events that generate a warning.
The levels are defined below:
For more information about the log and trace files and events they capture see Logging.
The log levels assigned to the audit log files are preset, and are not available for updates. You can adjust the log level assigned to any of the other log files. However, when you recycle the application server, all log levels revert to their default value.
To help you identify problem conditions quickly and easily, log entries for WARN, ERROR, and FATAL events are highlighted as follows:
Color-coded highlights support reviews and troubleshooting by distinguishing log entries of events capturing errors or problem conditions from those capturing routine system events. The use of a consistent color for each of the three event categories helps narrow the search for problem events of a specific level of severity.
Because these highlights are applied by the log file viewer, they appear only when you open and review log files from the Log Files page. Highlights are not saved in zipped copies of the log files, and they do not appear when you open and review log files in a different text editor.
The Zip All button saves copies of all log files and the systeminfo.xml file into a single zip file. You can use this button to capture records of system events and system information whenever necessary.
The Reset All to default button restores the default log levels to all settings that allow you to adjust the logging level.
The log files include records of events from the start of the current day until the time you create the zip file. Event records captured in the log files support troubleshooting and analysis.
The systeminfo.xml file contains a snapshot of the values assigned to system information settings at the time you create the file, including JVM Property Information page values, Application Setting page values, and License Information. The info-date tag at the beginning of the file records the date and time at which the file was created and the values in it were captured.
Note: The Log Files page does not display Web Services traces or client traces. To view these traces, open the Session Viewer or the Session Monitor. For more information about these two features, see Viewing WebFOCUS Sessions or Monitoring WebFOCUS Sessions.
Log pages list detailed records of system events that were captured in a log file in order of the time of their occurrence, from the earliest event on the day of the log to the most recent.
To open a log file for review, click a link from the Log Name column on the Log Files page. The page for your selected log file opens in a separate window.
The name of the log file appears at the top of the page. A list of earlier versions of that log file also appears at the top of the page. This list contains all previous versions of that log file that are currently available in the drive:\ibi\WebFOCUS82\logs directory. The number of days to retain a log file is defined in the setting Days Until Logs Are Deleted (IBI_LOG_RETAIN_DAYS) found on the Application Directories page of the Configuration tab of the Administration Console.
The New trace lines link appears beneath the file name. Click this link to refresh the log page with entries for system events that occur after you open it. New records are posted to a log file automatically. To protect the integrity of this information, no one can use a log page to update or change log file records.
The Bottom link takes you directly to the last entry in the file. This link is useful when you must review a file with a large number of entries, and you want to move directly to the most recent event. Similarly, the Top link, that appears below the last entry, returns you to the first entry in the log file and the features that appear on the top of the page.
The list of individual event entries begins below the Bottom link. Individual entries start with the date and time, in hours, minutes, seconds, and milliseconds, that an event took place. A code name identifying the category of event and the specific event itself follows the date and time. A full description of the event comes next. This description includes any messages generated by the system in response to the event.
You can use the log page to review and search for records of specific events in response to a query from a customer service support team member. The Find command in your browser can help you search for an event by a unique message, event name, or timestamp. You can also scroll through records to locate an event.
When your review is complete, close the log page window. You can use the Save or Print command in your browser to save or print a copy of the log page, or you can capture a zipped copy of it using the Zip All button from the Log Files page.