Share This:

We are using monitoring tools to monitor our servers, but what monitors the monitoring tool? The answer is simple with BPPM. BPPM has its own built in self-monitoring.


The BMC ProactiveNet Self-monitoring Service (also known as the local agent) is a local service dedicated to monitoring the health of the BMC ProactiveNet Server. This will help ensure that the BMC ProactiveNet Server runs at peak performance. The Self-Monitoring Service, which is automatically installed on the BMC ProactiveNet Server, collects metrics about only the BMC ProactiveNet Server performance.


When you install the BMC ProactiveNet Server, several out-of-the-box processes are created and monitored by default. These processes include the Apache server, the database installed, and the monitors corresponding to the operating system, and so on. This type of default monitoring is called self-monitoring.




Due to conflicts with the BMC ProactiveNet Server and the drain on the resources of the BMC ProactiveNet Self-Monitoring Service, BMC Software does not recommend enabling the BMC ProactiveNet Integration Service on the same computer where the BMC ProactiveNet Server is installed. BMC does not recommend using the BMC ProactiveNet Self-Monitoring Service for monitoring anything other than the BMC ProactiveNet Server.

Also, take note, that when you upgrade to a later version of BMC ProactiveNet Server, these monitors continue to exist. However, if you have deleted these monitors in the earlier version, they are not recreated.


The following is a list of self-monitored processes:

PnAgent - The BMC ProactiveNet Agent running on the server

PwTray (only in Microsoft Windows)- The tray process, which indicates the status of the BMC ProactiveNet


acell - The administrative cell

dbsrv - The Sybase SQL Anywhere server process

httpd - The Apache server process

jserver - The main BMC ProactiveNet Server process

mcell - The master cell, which processes the events in the BMC ProactiveNet Server

pronet_cntl - The agent controller process, which communicates with the remote Agent/Integration

Server systems

rate - Processes the collected data services

tunnelproxy - The process, which allows connection to the agent, behind a firewall Windows System, Linux System, or Solaris System

Web URL – Refers to the IP of the device. The Web URL process monitors the default page of the BMC

ProactiveNet web console.

ProactiveNet Agent Status - Refers to the monitoring of the local ProactiveNet Agent. The ProactiveNet Agent Status indicates whether the server was able to communicate with the ProactiveNet Agent or not.

Database related monitors such as Sybase query and Sybase Intelliscope monitor the health of the BMC ProactiveNet Server back-end databases. For BMC ProactiveNet Server with Oracle as the back-end database, Oracle Query and Oracle Intelliscope monitors are used.


Here is the Solaris specific setting for the JRE BMC ProactiveNet Self-monitoring Service - Solaris Edition



Here is the Windows specific setting for the JRE BMC ProactiveNet Self-monitoring Service – Windows Edition




How do I enable debug for Self-Monitoring?
If you run pw debug list-a ProactiveNet_Server_hostName_or_IPaddress in BPPM 9.5, it lists the status of all visible subsystems being run by the BMC ProactiveNet Self-monitoring Service on the BMC ProactiveNet Server. This information can then be used for setting debug levels on individual processes and visible subsystems on the BMC ProactiveNet Server or any Integration Service.


The following pw debug commands are available:
pw debug file
pw debug list
pw debug on|off


Do I need to install the Monitor the Monitor KM on Integration Service hosts?

The Monitor the Monitor KM is not needed on Integration Service 9.5 hosts and it will not monitor the Integration Service processes. The KM was designed for the older Integration Service processes. In-built self-monitoring replaces the KM in version 9.5. You must also install a PATROL Agent and an OS KM on the Integration Service nodes so that you can monitor the Integration Service processes externally.


How do I check on the health of the BMC ProactiveNet components?

BMC ProactiveNet displays the health of the following components in the ProactiveNet Health node of the BMC

ProactiveNet Operations Console:

BMC ProactiveNet Cell

BMC ProactiveNet Integration Service


BMC ProactiveNet Central Server and Child Server In the navigation tree of the Operations Console, click Global > Event Collectors to view the ProactiveNet Health node.


The following figure shows the ProactiveNet Health node as it appears in the Operations Console.



You can use the different notebooks to see the details regarding the health status events displayed in the Operations Console.  For example: The Details notebook displays detailed information about the system for which the event was generated. Such events as classified as self-monitoring events and are displayed as such in the Summary notebook as shown below:


When you use Self-Monitoring you would need to be sure that if you  have changed the database configuration by using the pw dbconfig set command, then ensure that you use the new credentials to edit the database related self-monitoring processes such as Sybase Query, Oracle Query, Sybase Intelliscope, and Oracle Intelliscope.


What do I do if I want to monitor BMC ProactiveNet Server Components externally?
PATROL for BMC ProactiveNet Self-Monitoring product provides a Knowledge Module (KM) that helps you discover instances, collect performance metrics and thereby monitor the BMC ProactiveNet Server and the BMC ProactiveNet Integration Service along with their associated components. The BMC Monitor the Monitor KM can be used if external monitoring of ProactiveNet components is needed.

It can monitor BPPM, IS and its components as well. Refer the Self-monitoring guide for more details:


The basic overview of the “Monitor the Monitor” or PATROL for BMC ProactiveNet Self-Monitoring KM is as follows:


Operating system (OS) level monitoring: This product provides an OS level monitoring of the BMC ProactiveNet Server and the BMC ProactiveNet Integration Service. It helps you monitor the health of OS entities such as file system resources, memory resources, and the processor. The BPPM_MTM application class parameters provide OS level monitoring.


Component monitoring: This product provides component level monitoring of some critical processes related to the BMC ProactiveNet Server and the Integration Service. The BPPM_MTM_COMPONENT application class parameters provide component level monitoring.


Status monitoring and data collection: This product provides monitoring of the PATROL Agents connected to the Integration Services that are being monitored. It monitors metrics such as the number of PATROL Agents connected (or disconnected) to the Integration Service, the data collection and connection status of the PATROL

Agents associated with the Integration Service, and so on. The BPPM_MTM_CONNECTION_PROFILE application class parameters provide status monitoring.


Failover configuration: This product provides you with the capability of handling failover for Integration Services operating in a failover environment. With this, the product accounts for PATROL Agent failover to a different Integration Service.


Email notification configuration: This product helps you configure email notification for all the parameters available with version 1.1.00 of the product. With this, if a parameter goes into an alarm state, an email notification is sent to the designated email ID with detailed information about the alert.


NOTE: If you are running a version prior to 9.5, you can use the Monitor the Monitor KM but 9.5 forward does not require it.


The BMC Monitor the Monitor KM does not discover and monitor the 9.5 Integration Service and must not be used with the 9.5 Integration Service. Built-in self-monitoring is significantly enhanced in version 9.5 and the BMC Monitor the Monitor KM is no longer needed. However, BMC recommends that you use the PATROL Agent and operating system KMs for additional self-monitoring. Built-in self-monitoring replaces the KM in version 9.5. You must also install a PATROL Agent and an OS KM on the Integration Service nodes so that you can monitor the Integration Service processes externally.






Newly Published Knowledge Articles - New Content has been added over the last month!

KA403507 - BPPM is generating large hprof files in the pw\pronto\logs directory.

KA408342 - BPPM CMDB extensions install is hanging at step CDM-Extensions.

KA409463 - BPPM 9.5 instance hierarchy is showing the PATROL Agent and KM for a device. This is different behaviour to BPPM 9.0

KA410247 - BPPM 9.5 - Time of events in event view are 1 hour ahead of when they actually occurred.

KA410356 - When configuring Atrium CMDB in the operations console or with integrate_atrium_cmdb script, connection to UDDI fails if UDDI is configured for https

KA410757 - With BPPM 9.5, is it possible to use the IS on the central server as a staging IS?

KA410773 - The mcell-log shows undefined class messages for BMC_SI_CI_PATTERN and BMC_SI_REL_PATTERN.

KA410795 - After an upgrade from SIM to BPPM, it is not possible to create/delete/edit a CI or impact relationship in IMD.



Popular Knowledge Articles

KA308615 - How to configure ProactiveNet integration with BMC PatrolAgent using PATROL Proxy Server?

KA321519 - Network Ports used with and for Proactivenet   

KA374546 - Old mcdb files are not being automatically deleted by statbld which can result in a full filesystem.

KA347978 -How can I ensure that a BPPM PATROL adapter has automatic workflow disabled?

KA366333 -BMC ProactiveNet Event Adapters is not running properly as a service.  The service starts, but no events are received, and task manager does not show any perl.exe nor msend.exe processes for the adapters.



“In the Know”…Do you know?


Have you joined our Customer Support Community yet? If not, head on over to the link and learn how you can help us by providing feedback to enhance your Customer Support experience.



Do you use Chat to get quick answers to product questions? If not, check it out as this is another channel of support available to customers. Join us for a quick chat and we’ll get you started on resolving your concerns. Learn more about Chat


Have you heard of the AMIGO program? Looking to upgrade in the near future? Get on board with AMIGO and we’ll help you plan your upgrade to ensure a smooth transition to the next version of the products you are using.


We have our Intelligent Ticketing Community space available now! You can also access Intelligent Ticketing documentation here.


Don’t forget our Webinars! Check out the details here: BMC ProactiveNet Performance Management (BPPM) 9.5 Best Practices Webinar Series


Looking for a previous blog posting? Find them here:  BMC ProactiveNet Pulse Blogs





Tell us how we are doing. Use the rating system at the bottom of this blog to rate this post! Comments and feedback are welcome!