Configuring Self-Health Monitoring capability for TrueSight Operations Management
This document describes procedures to set up the self-health monitoring for some of the TrueSight Operations Management server components. The set up steps are listed for the following server components:
- The Remedy SSO Server, which provides authentication services to the overall TrueSight Operations Management environment.
- The TrueSight Presentation Server, which is responsible for providing end-user access to the system
- The TrueSight Infrastructure Management server, which collects, stores, and manages data and events to serve specific purposes.
All these servers are again composed of different components. For example, the TrueSight Presentation Server uses an Elasticsearch database to store the event information and a Tomcat server to provide the user interface functionality.
Self-Health Monitoring (SHM) capability
It is important that all these servers and their underlying components are running, available, and performing at their optimum levels. To ensure that the system is available, the system must proactively monitor and inform the problems that might be occurring. This proactive self-monitoring activity is referred to as Self-Health Monitoring (SHM) or Self-Monitoring. We have the following self-monitoring capabilities available with the TrueSight Operations Management products and components:
There are multiple sources that measure the health of your TrueSight infrastructure. Both the TrueSight Presentation Server and the TrueSight Infrastructure Management server have the built-in monitoring capabilities. These two components can measure the health of the core processes and send out events about the status of the system. The built-in monitoring enables the administrators to receive emails when the key infrastructure components fails without any additional the dependencies. This is the key difference between the self-monitoring capability and setting up monitoring of components using a self-monitoring Knowledge Module (KM). Monitoring using a KM requires the core infrastructure to be running in order to be able to create events in case of an infrastructure failure. For example, if an Event Manager (cell) is no longer running, the built-in self-monitoring can send you an email, while a KM cannot raise this event through the infrastructure as the event management is not running. The built-in Self-Monitoring events are marked with a Icon in the TrueSight console. For viewing self-monitoring processes in the Infrastructure Management, see
Self-Monitoring using KM
BMC provides a KM (PATROL for TrueSight Self-Health Monitoring) that focuses on monitoring the health of the BMC-specific components. This KM is vital in monitoring the key performance and availability parameters of the TrueSight environment such as the connection status of Integration Servers. Administrators can configure this KM for the end-users to see proactive alerts about the performance and health of their TrueSight environment. For more information, see
Besides monitoring the BMC-specific components, the TrueSight servers contain generic third-party components, such as databases and applications servers, which needs to be monitored. It is equally important to monitor the health and performance of these third-party components. We will refer to this in this document as Extended Self-Monitoring.
Self-Health Monitoring content available in this release
The section on extended self-monitoring currently does not include IT Data Analytics Self-Monitoring and Application Visibility self-monitoring. However, the TrueSight Operations Management supports self-monitoring capabilities for these two components as well.
Self-Health Monitoring Process — At-a-glance
This diagram gives you an overview of setting up the self-health monitoring as described in this document.
Set up process
In a test environment, you can . Follow the guidelines to avoid conflicts in the port numbers between the components.
In a production environment, follow the sequence below. If your license does not entitle you to certain components, or if you are not installing certain components, skip that step and proceed to the next.
We assume that you have completed the installation of the Remedy SSO and the Presentation Server to create a basic setup, and also the required data providers, such as Infrastructure Management, App Visibility manager, and any other components based on your license entitlements to complete the solution installation.