BMC Software, Inc., Confidential and Proprietary Information
5-2 PATROL for BEA WebLogic User Guide
Understanding Logs
All messages generated by component subsystems are written to log files
on the local server. The most critical of these are also written to the
domain-wide log files on the administration server. Monitoring the
domain log file is a good way to develop an overall performance view of
your entire WebLogic environment.
Rotation
Some log files (including domain and server logs) are periodically
archived and a new log file initiated for current messages. The process of
retiring a log file and re-initiating it is called rotation. Rotation can be
done periodically, or whenever the log file reaches a certain size. Use
rotation to keep log files from reaching unmanageable sizes.
Note
File rotation may conflict with sniff patterns. You will usually need to
choose one function or the other for a particular log file.
Severity
All WebLogic messages contain a severity code. You can use these codes
when viewing logs or defining sniff patterns to isolate those messages
that you want most to see. You can also have these messages trigger
events that can be managed through the PATROL Event Manager.
There are 7 severity levels, ranging from Informational (normal
operational messages), to Emergency (severe system failure). The levels
are:
• Informational
• Warning
• Error
• Notice
• Critical
