BMC PATROL KM for Log Management v2.7.00 has been enhanced with the following changes and new features.
Added remote log monitoring functionality on UNIX
With 2.7.00 release, you can use BMC PATROL KM for Log Management to monitor log files that are located on remote hosts.
BMC PATROL KM for Log Management currently supports the remote log monitoring functionality on UNIX and Linux platforms only. You do not have to install any software on the remote host for the PATROL Agent to connect to it.
The remote log monitoring functionality remains disabled by default till you configure a remote instance for the first time, or until a previously-configured remote instance is detected when the PATROL Agent is initialized.
- BMC recommends to use pre-loaded KMs for remote log monitoring.
- BMC recommends to use remote log monitoring along with the remote UNIX monitoring. Before configuring remote log instances, ensure that the ConnectionStatus parameter of the COLLECTORS application class is in OK state.
Merged pmgpipereader with pmgreader
The pmgpipereader binary has been merged with the pmgreader binary. With this release, all former pmgpipereader functions are supported by the pmgreader binary. Pmgpipereader is no longer included as an individual component when you install or upgrade to version 2.7.00 or later of BMC PATROL KM for Log Management.
Statically linked libraries enabled for pmgreader on UNIX
The pmgreader binary no longer utilizes dynamically linked library files, such as Xerces library files on UNIX platforms. The Xerces library is now statically linked with pmgreader, and is no longer included as an individual component when you install or upgrade to version 2.7.00 or later of BMC PATROL KM for Log Management.
Changed the way pmgreader is installed on the monitored host on UNIX
On UNIX, when you install BMC PATROL KM for Log Management, multiple versions of the pmgreader binary are saved in separate folders in the $patrol_home/pmg directory on the PATROL Agent computer. Each folder contains a platform-specific version of the pmgreader binary.
When you add a remote host for log monitoring, depending on the remote host operating system, the required platform-specific version of pmgreader is installed on the remote host in the $HOME/BMCPatrol directory.
Implemented pipe in pukremotexec.xpc using SSH protocol
The SSH protocol is now used by the pukremotexec.xpc binary to create and maintain a pipe between the PATROL Agent computer and the remote host that is being monitored. This function is performed by the remotePipeColl collector parameter.
Implemented Session Control Protocol (SCP) protocol in pukremotexec.xpc to copy the pmgreader binary to the remote host
The Session Control Protocol (SCP) protocol is now used by the pukremotexec.xpc binary to copy the required platform-specific pmgreader binary file from the PATROL Agent computer to the remote host that is being monitored. This function is performed by the LOGSCPColl collector parameter.
Added the delPmgreaderAfterMin pconfig variable
This release supports the new delPmgreaderAfterMin pconfig variable. This pconfig variable enables you to set the time in minutes that BMC PATROL KM for Log Management waits before deleting the pmgreader binary from a remote host, if you delete all of the instances that you had configured. The default value is 10.
If you directly remove a remote host on which log monitoring is configured, the pmgreader binary is not deleted. Only the pmgreader process is stopped on the remote host.
New parameters in 2.7.00 release
This release supports the new parameters listed in table below:
Displays the collection status for a monitored host. The parameter goes into an alarm state when collection fails.
Is used to copy pmgreader to the remote host. This parameter also checks whether the pmgreader process is running on the remote host, and if the binary file is valid. If an invalid pmgreader binary file is found on the remote host, or if pmgreader has not been copied to the remote host, PATROL KM for LOG Management copies the required binary file to the remote host and any existing file is overwritten. The pmgreader binary is located in the $HOME/BMCPatrol/ directory on the remote host. This folder is created by the KM.
This parameter is inactive by default. It becomes active when you configure a remote instance for the first time, or when a remote instance is discovered for the first time.
This parameter is available only for log monitoring on remote hosts.
pmgreader cannot be copied to the remote host if it is already running. In this case, a notification is displayed.
Is used internally by PATROL KM for LOG Management application for normal priority scan on remote hosts. This parameter is available only for log monitoring on remote hosts.
Executes the pmgreader binary with the pipe argument to monitor named pipe instances. This parameter is available only for log monitoring on remote hosts.
Log in or register to comment.