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:


Built-in Self-Monitoring

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  View self-monitored process in operator console.

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  PATROL for TrueSight Self-Monitoring.  

Extended Self-Monitoring

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  Install the TrueSight Operations Management components on a single computer . 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. 

Step 1: Complete the TrueSight Operations Management component Install/Upgrade activities

As an IT architect or Solution Administrator, use this information to plan a new deployment of TrueSight Operations Management.

DescriptionProcedure
Planning activities include deployment options and sizing information for your environment.Planning
Download product components and then install and configure the productInstalling
Upgrade or migrate and configure product componentsUpgrading

Perform the required tuning settings for the product components

  • Remedy SSO benchmarking
  • Presentation Server
  • Infrastructure Management server



Benchmarking results for Remedy SSO

Performance tuning recommendations for the Presentation Server

Tuning the Infrastructure Management database for performance

Performance benchmarks and tuning for Infrastructure Management


Step 2: Set up BMC PATROL for TrueSight Self-Monitoring

The basis for Self-Monitoring is the BMC PATROL for TrueSight Self-Monitoring solution. As an IT architect or Solution Administrator, follow these steps to plan, install and configure the solution in your TrueSight Operations Management environment:

DescriptionProcedure
Concepts, architecture, deployment, planning, and system requirements

Planning to install PATROL for TrueSight Self-Monitoring

Installing Knowledge Modules

Installing the PATROL for TrueSight Self-Monitoring

Loading the predefined policies and configuring the solution

Configuring PATROL for TrueSight Self-Monitoring


Step 3: Set up Remedy SSO Self-Monitoring for PostgreSQL DB

You can configure the underlying PostgreSQL database of the Remedy SSO server for self-monitoring. Perform the following steps to extend the Remedy SSO Self-Monitoring capability to monitor the underlying PostgreSQL database of the Remedy SSO server:

DescriptionProcedure
Concepts, architecture, deployment, planning, and system requirements

Planning to install PATROL for PostgreSQL Database

Installing and migrating data for PATROL for PostgreSQL Database

Installing PATROL for PostgreSQL Database

Creating custom policies and configuring the solution

Understanding monitor types and attributes

Configuring PATROL for PostgreSQL Database

Configuring Self-Health Monitoring for Remedy SSO PostgreSQL


Step 4: Set up Presentation Server Self-Monitoring for PostgreSQL and Elasticsearch DBs

You can configure the underlying PostgreSQL database and Elasticsearch database of the TrueSight Presentation Server for self-monitoring. The TrueSight Presentation Server is composed of a PostgreSQL database, an Elasticsearch database, and the core TrueSight Presentation Server. The core server is monitored through the BMC PATROL for TrueSight Self-Monitoring solution. Perform the following steps to extend the TrueSight Presentation Server Self-Monitoring capability to monitor the underlying PostgreSQL and Elasticsearch databases:

Step 3.a: Set up PostgreSQL Database monitoring for the TrueSight Presentation Server Self-Monitoring

DescriptionProcedure

Concepts, architecture, deployment, planning, and system requirements

Planning to install PATROL for PostgreSQL Database

Installing and migrating data for PATROL for PostgreSQL Database

Installing PATROL for PostgreSQL Database

Creating custom policies and configuring the solution

Understanding monitor types and attributes

Configuring PATROL for PostgreSQL Database

Configuring Self-Health Monitoring for TrueSight Presentation Server PostgreSQL


Step 3.b: Set up Elasticsearch Database monitoring for the TrueSight Presentation Server Self-Monitoring

DescriptionProcedure

Concepts, architecture, deployment, planning, and system requirements

Planning to install PATROL for Elasticsearch

Installing and migrating data for PATROL for PostgreSQL Database

Installing PATROL for Elasticsearch

Creating custom policies and configuring the solution

Understanding monitor types and attributes

Configuring PATROL for Elasticsearch

Configuring Self-Health Monitoring for TrueSight Presentation Server Elasticsearch


Step 5: Set up Infrastructure Management Self-Monitoring for SQLAnywhere and Oracle DBs

You can configure the underlying SQL Anywhere database or Oracle database of the TrueSight Infrastructure Management for self-monitoring. The TrueSight Presentation Server is composed of a SQL Anywhere database or Oracle database and the core TrueSight Infrastructure Management. The core server is monitored through the BMC PATROL for TrueSight Self-Monitoring solution. The TrueSight Infrastructure Management server runs with either one of these two database types that you chose during the installation. Perform the following steps to extend the TrueSight Infrastructure Management Self-Monitoring capability to monitor the underlying SQL Anywhere or Oracle databases:

Tips

The TrueSight Presentation Server server comes with a built-in self-monitoring capability and are enabled by default. The metrics to be monitored are collected by the server, without the need to install a PATROL Agent with a KM. The self-monitoring capabilities include the collection of metrics and sending events that contain information about the health status of the server. The metrics collected are for the running server processes, such as CPU and Memory usage. Based on the metrics, the events are triggered. For example, when the connection between the different components are lost. For more details, see Viewing self-monitored processes in the operator console.

You can configure to receive email notifications for any disruptions in the system, even if core components are not functioning. To set up the email notification, see Monitoring the Presentation Server environment.


Step 3.a: Set up Oracle monitoring for the TrueSight Infrastructure Management server Self-Monitoring

DescriptionProcedure

Concepts, architecture, deployment, planning, and system requirements

Planning to install PATROL for Oracle Database

Installing and migrating data for PATROL for Oracle Database

Installing PATROL for Oracle Database

Creating custom policies and configuring the solution

Understanding Monitor types or application classes

Configuring PATROL for Oracle Database

Configuring Self-Health Monitoring for Infrastructure Management Server Oracle DB


Step 3.b: Set up SQL Anywhere monitoring for the TrueSight Infrastructure Management server Self-Monitoring

DescriptionProcedure

Concepts, architecture, deployment, planning, and system requirements

Planning to install PATROL for Sybase 11.0

Installing and migrating data for PATROL for PostgreSQL Database

Installing PATROL for Sybase 11.0

Creating custom policies and configuring the solution

Understanding monitor types and attributes

Configuring PATROL for Sybase 11.0

Configuring Self-Health Monitoring for Infrastructure Management Server SQL Anywhere DB





Was this page helpful? Yes No Submitting... Thank you

Comments

  1. John Clitheroe

    "The TrueSight Presentation Server is composed of a SQL Anywhere database or Oracle database" should say Infrastructure Management and not "Presentation Server"

    Jun 03, 2019 05:24