Either before or after loading the PATROL KM for Log Management, you must load the PATROL KM for UNIX. The PATROL KM for Log Management application classes appear beneath the UNIX OS application class. If the PATROL KM for UNIX is not loaded, you will not be able to view the application classes for the PATROL KM for Log Management.
The PATROL KM for Log Management needs no special configuration to begin collecting data immediately after it has been installed and loaded.
Almost all the functionality of the PATROL KM for Log Management must be accessed using a PATROL Console in developer mode. If a configuration task requires a console in developer mode, it will be noted in the instructions for that task.
For details about using the PATROL KM for Log Management, see the BMC PATROL for Log Management Online Documentation.
The PATROL KM for Log Management allows you to define recovery actions when a log file reaches a specified size. The available recovery actions for log files are:
The backup file is written to the same directory with an incremental number appended to the log file name each time the file is backed up. For example, the first time that the error_log.txt reaches its size limit, PATROL creates a backup file named error_log.txt1. The next time that it reaches its limit, PATROL creates a backup file named error_log.txt2 and so on.
It is recommended that you periodically move the backup files to another location. The PATROL recovery action checks to make sure that the backup file name is not already in use. If hundreds or even thousands of backup files exist in the log directory, PATROL might take some time to complete this recovery action.
Recovery actions run automatically by default; however, they can be configured to require user confirmation if the Run Attended option is set to Yes.
To define a recovery action that will take place when the log file exceeds a defined file size, follow these steps: