Writer instructions

Page title

For most spaces, this page must be titled Space announcements.

For spaces with localized content, this page must be titled Space announcements l10n.

Purpose

Provide an announcement banner on every page of your space.

Location

Move this page outside of your home branch.

Guidelines

Announcement Support for this product will end on November 3, 2025. We recommend that you use PATROL for Linux, PATROL for AIX, or PATROL for Solaris to monitor operating systems.

Configuring the PATROL KM for Log Management

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.

Note

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. 

 Configure Recovery Actions for a Log File

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:

  • Reduce the log file to 0 MB by deleting all the messages in the log file when the file reaches the size limit
  • Back up the file into the pmg_backup subdirectory located in the same directory as the monitored log file and reduce the log file to 0 MB

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.

Note

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.

Before You Begin

Configure a Recovery Action for a Log File Based on File Size

To define a recovery action that will take place when the log file exceeds a defined file size, follow these steps:

  1. Type a value in the Size Limit field (the value is in bytes - for example, 100 equals 100 bytes).
  2. Select Action to specify a recovery action for PATROL to take when the log file reaches the specified size limit
    • Nothing --PATROL continues monitoring the log file but does not attempt to reduce its size.
    • Delete --PATROL reduces the log file to 0 MB by deleting all the messages in the log file when the file reaches the size limit.
    • Backup and Delete -- PATROL backs up the existing log file and reduces the log file to 0 MB
  3. Click the Yes or No to indicate whether PATROL should Run Attended (prompt an operator for confirmation before performing a recovery action).

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*