User goals and features

he PATROL for BMC ProactiveNet Self Monitoring product provides a Knowledge Module (KM) that helps you to discover instances, collect performance metrics and, thereby, monitor the BMC ProactiveNet Server and the BMC ProactiveNet Integration Service along with their associated components. This product provides the following key features:

• Operating system-level monitoring:
  You can monitor instances of the BMC ProactiveNet Server and Integration Service at an operating system (OS) level to check the health of OS entities such as the file system resources, memory resources, and the processes. The BPPM_MTM application class provides parameters that examine the following areas of the operating system:
  • Physical memory usage (memory status)
  • Virtual memory usage (Memory status)
  • Processor utilization (processor status)
  • Disk space usage (filesystem status)
  • Disk utilization (filesystem status)

• Component-level monitoring:
  You can monitor critical processes, which are required for the BMC ProactiveNet Server and Integration Service to function properly. The BPPM_MTM_COMPONENT application class provides parameters that monitor components (critical processes) of the BMC ProactiveNet Server and the Integration Service.These parameters examine the following areas of the components:
  • Processor utilization
  • Handle count
  • Thread count
  • Aggregate process status
  • Memory utilization

    Note

    1. The handle count and thread count parameters are not monitored on the UNIX platform.
    2. On Solaris, non-global zone systems, DCM (Data Collection of BMC PATROL Knowledge Module for UNIX) is not available. So component monitoring of Self Monitoring KM will be disabled.
       1. To enable component monitoring on the Integration Service, set the following configuration variable to 1:
          /PBP__P4PNetSelfMon/IS/0/Components/enabled
       2. To enable component monitoring on the Server, set the following configuration variable to 1:
          /PBP__P4PNetSelfMon/SERVER/Components/enabled

PATROL Agent status monitoring:
In addition to monitoring at the OS level and the component level, this product helps you to monitor PATROL Agent connection and collection status for all the PATROL Agents connected to the Integration Service that is being monitored. This includes metrics such as the number of PATROL Agents connected (or disconnected), the overall connection and collection status of PATROL Agents, and so on. The BPPM_MTM_CONNECTION_PROFILE application class provides parameters that monitor the PATROL Agent collection and connection status.

• Failover configuration for Integration Services:
  With minimum configuration, you can add associated failover nodes for Integration Services so that the product accounts for PATROL Agent failover to a different Integration Service. In case of a PATROL Agent failover, the Knowledge Module (KM) provided by this product only detects that the PATROL Agent is disconnected. It does not detect that after disconnecting from the first Integration Service node, the PATROL Agent has moved to some other Integration Service node. In fact, if it detects that the PATROL Agent has remained in the disconnected state for more than the maximum allowed disconnected time (10 minutes, by default), then it generates an alarm. To avoid this, you must monitor failover nodes. For more information configuring failover, see Configuring failover for Integration Services.

• Email notification configuration:
  You can configure email notification for all the parameters available in this product. This is an alternative form of notification, where the product sends out an email notification to the designated email ID with detailed information about the alert (when a parameter goes into an alarm state). For more information about email notification configuration, see Configuring email notification.
• Configuration by using PATROL Configuration Manager:
  This product is fully configurable through the PATROL Configuration Manager. With the exception email notification configuration, the default settings allow it to function properly requiring no additional configuration in most cases. For more information about a list of PATROL Agent configuration variables available, see PATROL Agent configuration variables.