Maintenance outage for upgrade on Sunday, September 22

This site, docs.bmc.com, will be inaccessible for two hours starting at 8 AM CDT, Sunday, September 22, for a platform upgrade.

Page tree

Maintenance outage for upgrade on Sunday, September 22

This site, docs.bmc.com, will be inaccessible for two hours starting at 8 AM CDT, Sunday, September 22, for a platform upgrade.

Skip to end of metadata
Go to start of metadata

Self-health monitoring includes monitoring the health of:

  • TrueSight Infrastructure Management Server
  • Integration Service
  • PATROL Agent

The health of a component is usually affected by resource depletion which can occur because of a heavy load on the resources or because of crossing scalability limits. Resource monitoring can provide early insights into the health of a component and makes it possible to measure the load on components such as instances, attributes, and so on.Thisinturn,provides an early insight into scalability issues.

Infrastructure Management displays the health of the following components in the Truesight Infrastructure Health node of the operator console:

When a detailed understanding of a KM’s functionality and how it is configured cannot be understood without analyzing the KM using the BMC PATROL Console, perform the analysis in a development environment.

To view the self-health of an Infrastructure Management component

In the navigation tree of the Infrastructure Management operator console, click Global > Event Collectors to view the Truesight Infrastructure Health node. 


Infrastructure Management generates an event and displays it in the Truesight Infrastructure Health node if one or all of the scenarios mentioned below occur:

  • The BMC PATROL Agent crashes and is disconnected from the Integration Service.
  • A KM that is configured to collect data cannot do so because of extraneous reasons such as a time mismatch or clockaskew.
  • The connection between the Integration Service and the local or remote cell is lost.
    When the cell is disconnected from the Integration Service, an event is generated.
    When the cell is reconnected to the Integration Service, the event is closed and is displayed at Global > Event Collectors Truesight Infrastructure Health > By Status > Closed.

  • The connection between the Integration Service and the BMC PATROL Agent is lost.
  • The Integration Service rejects the connection from an incompatible version of the BMC PATROL Agent (for example, BMC PATROL Agent version 9.0 and earlier). For information about compatible versions of the BMC PATROL Agent, see the SPAC tool.
  • The Central Server loses connection with a Child Server.
  • A Child Server loses connection with the Central Server.
  • The connection between the BMC TrueSight Infrastructure Management Server and the Integration Service is lost. This may happen if the Integration Service crashes, or the computer in which the Integration Serviceis installedcrashes, or the network connection between the BMC TrueSight Infrastructure Management Server and the Integration Service is lost.
  • The database pruner job that runs automatically every 15 minutes generates an event that is closed and is displayed at Global > Event Collectors Truesight Infrastructure Health > By Status > Closed.

You can configure the severity for these events by performing the following steps:

  1. Open the installationDirectory/pw/custom/conf/pronet.conf file. 
  2. Add the following parameters for respective components and set the value to one of CRITICAL, MAJOR, or WARNING.
    • Integration Service disconnecting from Server: pronet.selfmonitoring.is_disconnect_severity
    • PATROL AGENT disconnecting from Server: pronet.selfmonitoring.pa_disconnect_severity
    • Cell associatedto Integration Service disconnecting from Server: pronet.selfmonitoring.cell_disconnect_severity
      For example, pronet.selfmonitoring.is_disconnect_severity=CRITICAL   
  3. Save and close the pronet.conf file.
  4. Restart the BMC TrueSight Infrastructure Management Server.

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 in the following figure.

For information about the information that you can view and obtain from the Details notebook, see Viewing the Event Details Notebook.

For a use case in the context of which viewing self-monitored events is useful and what you can do with such events, see Detect problems using the automated self-health monitoring capability.