Skip to Content
Information
Unsupported content Version 2.7.41 of the product is in limited support, while versions 2.7.43 and 2.7.44 are fully supported. This documentation includes content for all versions. You will not be able to leave comments for version 2.7.41.

 

Remote monitoring FAQs

This section addresses common questions about using the BMC PATROL Knowledge Module for Log Management for remote monitoring.

PATROL KM for Log Management currently supports remote log monitoring on and from UNIX computers only. Remote log monitoring is an integral part of remote monitoring of UNIX and Linux computers. For information about remote monitoring

of UNIX and Linux computers, see Configuring-PATROL-KM-for-Log-Management-for-remote-log-monitoring.

Which version of PATROL KM for Log Management supports remote monitoring?

PATROL KM for Log Management supports remote monitoring in version 2.7.00 and later. This version is shipped with version 3.1.00 and later of the BMC Performance Manager for Servers solution.

Warning

Note

Support for remote monitoring of logs using BMC ProactiveNet Central Monitoring Administration is available with version 2.7.10 of PATROL KM for Log Management.

Which data collection method is used by remote monitoring?

Remote monitoring uses the PATROL Scripting Language (PSL) data collection method to discover instances and to get data through the remote External PSL Call (XPC).

Is remote log monitoring possible without installing BMC PATROL KM for UNIX and Linux?

No. Remote log monitoring functionality is an integral part of remote monitoring of UNIX and Linux platforms.

What is the role of pukremotexec.xpc in remote monitoring?

PATROL KM for Log Management uses an XPC-based collection mechanism to support monitoring of the remote hosts. The pukremotexec.xpc stand-alone executable communicates with PATROL Agent through standard input (stdin) and output (stdout) channels connected with pipes. The communication between PATROL Agent and the XPC server is handled by the SDK libraries through PSL function calls.

pukremotexec.xpc is an XPC-based SSH2 client that opens sessions with remote hosts, runs commands on those hosts, and returns the output to the PSL collectors. For the PSL collectors, the command execution is transparent and the same PSL collectors work well with the local host and the remote host.

pukremotexec.xpc also copies the required platform-specific pmgreader binary file from the PATROL Agent computer to the remote host that is being monitored using Secured Copy (SCP).

Warning

Note

pukremotexec.xpc is packaged with PATROL KM for UNIX and Linux.

What are the pre-requisites to enable remote log monitoring?

For information about the pre-requisites for remote log monitoring, see the following questions in the BMC PATROL KM for Unix and Linux online documentation portal:

What hardware do I need to monitor multiple UNIX computers remotely?

What are the pre-requisites for enabling remote monitoring?

Warning

Note

You must have version 9.10.00 or later of BMC PATROL KM for UNIX and Linux installed to enable remote log monitoring with version 2.7.00 or later of BMC PATROL KM for Log Management.

What is the role of the pmgreader binary that runs on the remote host?

The pmgreader binary that runs on the remote host, collects data for all monitored log files, that are configured for monitoring on the remote host.

When is pmgreader copied to the remote host?

The pmgreader binary is copied to the remote host when:

  • You configure a remote log instance for the first time.
  • PATROL Agent is initialized or re-initialized when log instances have already been configured.
  • The pmgreader binary is not present on a remote host before the PATROL KM for Log Management is configured for remote log monitoring.
Warning

Note

BMC recommends that you use pre-loaded KMs for remote log monitoring. Otherwise, the pmgreader binary will be copied to the remote host each time the connection between the PATROL Agent and the PATROL Console is broken or updated.

If you are using BMC ProactiveNet Central Monitoring Administration, you do not have to preload the KM for remote log monitoring. For more information, see Configuring a policy for the remote host in BMC ProactiveNet Central Monitoring Administration.

When is pmgreader deleted from the remote host?

BMC PATROL KM for Log Management deletes the pmgreader binary from the remote host if you delete all of the log instances that you had configured for it. By default, the KM waits for ten minutes after you delete the last log instance before deleting pmgreader from the remote host, unless you configure a new log instance.

Which authentication mechanisms are used in remote monitoring?

The following types of authentication mechanisms are supported:

Warning

Some content is unavailable due to permissions.

Which application classes are supported for remote monitoring?

The remote log monitoring functionality in version 2.7.00 or later of PATROL KM for Log Management, which is shipped with version 3.1.00 or later of the BMC Performance Manager for Servers solution, supports the following application classes:

  • LOG
  • LOGT
  • LOGMON
  • PMGDEBUG

Does remote log monitoring support all file scan priorities?

No, PATROL KM for Log Management supports only Normal priority file scans for remote log monitoring.

How many remote hosts can one PATROL Agent monitor?

There is no maximum limit to the number of remote hosts that one PATROL Agent can monitor. However, in the PATROL Performance, Scalability and Reliability (PSR) lab, the largest configuration tested was 25 hosts. 5 log files were monitored on each host, and each log file contained 2 search criteria.

Can I use an earlier version of PATROL Agent?

Yes. You can use any of the earlier PATROL Agent versions supported. BMC recommends you to use the latest version of the PATROL Agent for better performance.

Can I monitor log files on UNIX and Linux systems from PATROL Agent for Windows?

No, you cannot monitor log files on UNIX or Linux systems from a Microsoft Windows computer.

What is the difference between local and remote log monitoring?

The following diagram indicates the functional difference between log monitoring on a local host and log monitoring on a remote host.

Local and remote monitoring.png

How do I configure PATROL KM for Log Management for remote log monitoring?

Remote log monitoring is supported only by the PSL collection method. If you are currently using the DCM collection method, switch to the PSL collection method by right-clicking UNIX_OS application and choosing Knowledge Module Admin > Toggle PSL/DCM Collection.

After changing the data collection method, load the REMOTE.kml file.

Error
Warning

You should not use multiple PATROL Agents to monitor the same remote host. 

To add a remote host for log monitoring

  1. Install PATROL Agent and PATROL KM for Log Management version 2.7.00 or later on a computer.
  2. In the PATROL Console, add the computer described in step 1 as a Managed Node.
  3. Load LOG.kml, UNIX_OS.km, and Remote.kml files.
    By default, all the application classes in the DCM collection method are discovered.
  4. Switch to the PSL collection method by right-clicking UNIX OS and selecting KM Commands > Knowledge Module Admin > Toggle PSL/DCM Collection.
  5. After full discovery, right-click the Remote Monitoring container and select KM Commands > Manage List of Monitored Hosts.
    When the Manage List of Monitored Hosts dialog box appears, the Add New Host option is selected by default.
  6. Click OK.

  7. In the Add New Host dialog box, provide the host name, user name, and password of the remote host to be monitored.

    Warning

    Note

    The remote host can also be added by using a profile, and public and private keys.

To modify a remote host

  1. Right-click the Remote Monitoring container and select KM Commands > Manage List of Monitored Hosts.
  2. In the Manage List of Monitored Hosts dialog box, select the remote host that you want to modify, and select the Modify Host option.
  3. Click OK.
  4. Edit the host information as required.
  5. Click OK.

To delete a remote host

  1. Right-click the Remote Monitoring container and select KM Commands > Manage List of Monitored Hosts.
  2. In the Manage List of Monitored Hosts dialog box, select the remote host that you want to modify, and then select the Delete Host option.
  3. Click OK.

Can I specify a different polling cycle for each monitored log file?

No, you cannot specify a different polling cycle for each monitored log file.

What instance hierarchy is displayed for remote hosts?

The instance hierarchy that is displayed for a remote host is the same as that of a local host.

How are remote hosts discovered by BMC ProactiveNet if it is integrated with PATROL KM for Log Management?

BMC ProactiveNet discovers remote hosts the same way that PATROL KM for Log Management does.

Does remote log monitoring use a dedicated SSH session?

Remote UNIX and Linux monitoring and remote log monitoring share a single, persistent SSH session when they are both done on the same remote host.

What are the Performance and Scalability metrics for remote monitoring?

The following table lists the metrics based on 2 processors and 2 GB of RAM for 25 remote hosts monitored for 96 hours.

Performance and Scalability metrics for remote monitoring with PATROK KM for Log Management

Operating system

Average CPU (in %)

Average Memory (in MB)

Network

PATROL

Agent

pukremotexec.xpc

PATROL

Agent

pukremotexec.xpc

In (Kilo

Bytes per

second)

Out (Kilo

Bytes per

second)

Oracle Solaris 10

10

1

99

41

18

5

Red Hat Enterprise Linux 5.6 (x86)

5

9

120

37

17

10

IBM AIX 7 PowerPC

26

1.2

55

8

32

11

HP-UX 11.23 ia64

45

1.5

28

10

22

7

Can I directly configure a policy for monitoring logs on the remote host in BMC ProactiveNet Central Monitoring Administration?

No, before configuring a policy to monitor remote logs in BMC ProactiveNet Central Monitoring Administration, you must perform the following actions:

  • Install the PATROL KM for UNIX and Linux
  • Define the monitoring policy for the remote host by using the Monitoring Policy Configuration wizard available for PATROL KM for UNIX and Linux in BMC ProactiveNet Central Monitoring Administration.
    For more information, see Configuring-a-monitor in the BMC PATROL for UNIX and Linux online documentation portal.

 

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

BMC PATROL for Log Management 2.7