Configuring PATROL for TrueSight Self-Monitoring policies using predefined policy templates

There are several PATROL for TrueSight Self-Monitoring policies that you can import into the TrueSight console.

These predefined monitoring policies act as templates that enable you to quickly add monitoring capabilities for TrueSight Presentation Server and TrueSight Infrastructure Management devices. These include operating system policies work with local or remote hosts. Plus, there is an additional policy available to to remotely monitor the Presentation server's Java process and Elasticsearch service.

To use these predefined monitoring policies, you need to import them from the base or extended repository, make copies of the policies that you want to use, and then provide a few configuration details for the new monitoring policies to work.

Before you begin

You must import the base or extended repositories to use the predefined monitoring policies.

The base repository includes operating system KMs, and predefined policies that you can use to monitor local and remote TrueSight Presentation servers and TrueSight Infrastructure Management server devices. These predefined policies include basic metrics for CPU, disk space, and memory usage.

The extended repository has all of the KMs found in the base repository plus additional KMs. It also has additional predefined policies for the Generic Java Server KM that you can leverage to monitor the Java process and Elasticsearch service of the Presentation Server and TrueSight Infrastructure Management devices.

The extended repository has additional KMs and predefined policies, including Generic Java Server policy that is leveraged to monitor TrueSight Presentation servers and TrueSight Infrastructure Management server java processes.

Importing and configuring PATROL for TrueSight Self-Monitoring predefined monitoring policies video

The following video provides a summary of how to import and configure predefined monitoring policies.

For the PATROL for TrueSight Self-Monitoring KM, the base and extended repositories include the following predefined monitoring policies.

Policy Name	Description	Key metrics
Base Repository
TS-Self-Monitoring-Linux-Remote	Monitor from a remote agent the TrueSight Presentation Server and Infrastructure Management installed on Linux systems	Infrastructure Management monitored processes: httpd jserver mcell pronet_agent pronet_cntl Rate Services Presentation Server monitored processes: Elsaticsearch Presentation Server Java process Presentation Server PostgreSQL database process
TS-Self-Monitoring-Linux-TSIM	Monitor local TrueSight Infrastructure Management installed on a Linux system	Infrastructure Management monitored processes: httpd jserver mcell pronet_agent pronet_cntl Rate Services
TS-Self-Monitoring-Linux-TSPS	Monitor local TrueSight Presentation Server installed on a Linux system	Presentation Server monitored processes: Elasticsearch Java process Presentation Server Java process Presentation Server Postgres Database process
TS-Self-Monitoring-Windows-Remote	Monitor from a remote agent the TrueSight Presentation Server and Infrastructure Management installed on Windows systems	Infrastructure Management monitored processes: httpd jserver mcell pronet_agent pronet_cntl Rate Services Presentation Server monitored processes: Elsaticsearch Java process Presentation Server Java process Presentation Server PostgreSQL database process
TS-Self-Monitoring-Windows-TSIM	Monitor local TrueSight Infrastructure Management installed on a Windows system	Infrastructure Management monitored processes: httpd jserver mcell pronet_agent pronet_cntl Rate Services
TS-Self-Monitoring-Windows-TSPS	Monitor local TrueSight Presentation Server installed on a Windows system	Presentation Server monitored processes: Elsaticsearch Java process Presentation Server Java process Presentation Server PostgreSQL Database process
Extended Repository
TS-Self-Monitoring-JVM	Monitor locally or remotely the TrueSight Presentation Server and the ElasticSearch Java processes	Heap Memory Usage Garbage Collector metrics Class Loader metrics Plus additional metrics

To import the monitoring policies from the base repository

To import the monitoring policy to the TrueSight console, you must complete the procedure for importing the full repository with predefined packages and policies..

To import the monitoring policies from the extended repository

You must complete the procedure for importing the full repository.
On the Presentation Server host, go to the bin directory that contains the policy migration utility and run the following command:
- Windows
  cd /D "%TRUESIGHTPSERVER_HOME%\truesightpserver\bin"
- Linux
  cd $TRUESIGHTPSERVER_HOME/truesightpserver/bin
From the bin directory, run the relevant command, based on your operating system:
- Windows
  cmapolicymigration.bat <import options> <policy data files>
- Linux
  cmapolicymigration.sh <import options> <policy data files>

Import options	Description
-d	Location of policy data files to import When not specified, the current directory is assumed
-f	Overwrites the current policy

Import examples

cmapolicymigration.bat import -d "C:\Program Files\BMC Software\TrueSightPServer\truesightpserver\modules\cma\pproxy\depot_directory\bmc_products\SamplePolicies\ksm\1.0.00"

cmapolicymigration.bat import -f "C:\Program Files\BMC Software\TrueSightPServer\truesightpserver\modules\cma\pproxy\depot_directory\bmc_products\SamplePolicies\ksm\1.0.00"

After the monitoring policies are imported, they appear as infrastructure policies in the the TrueSight console.

Infrastructure policies

Infrastructure policies.png

Note

For further information about the TrueSight console's Infrastructure Policies page, seeManaging policies

To copy a monitoring policy

Before you begin configuring an imported policy, it is recommended that you make a copy of the policy. This way you always have an original copy of the policy in case you want to configure additional policies or make a mistake while you are configuring a policy.

Next to the imported monitoring policy, click the policy action menu and select Copy.
Policy action menu
In the Create Monitoring Policy page, ensure that the Monitoring tab is selected.
You can see that the policy name and many other elements are already defined in the General Properties and PATROL Agents section.
It is a requirement that TS-Self-Monitoring is defined as a PATROL agent.
Create Monitoring policy
Enter a name for the new monitoring policy and click Save.

The new policy is added to the infrastructure policy list and is ready to be configured.

To configure a monitoring policy

After a monitoring policy is copied, you must enable and configure some parameters.

Next to the monitoring policy name, click the policy action menu and select Edit.
Policy action menu
In the Edit Monitoring Policy page, ensure that the Monitoring tab is selected.
You can see that the policy name and many other elements are already defined in the General Properties and PATROL Agents section.
It is a requirement that TS-Self-Monitoring is defined as a PATROL agent.
Edit Monitoring policy
Click Enable Policy to enable the monitoring policy.
If you are enabling a Windows or Linux local monitoring policy, click Save.
If you are enabling a JVM or Windows/Linux remote monitoring policy, click the action menu next to the monitoring solution name, select Edit, and enter the following details:
For the Apache Tomcat and Generic Java Server policy, click here...
Click on the action menu next to the TSPS_Server [ envName ] or TSPS_Elasticsearch [ envName ] environment name, click Edit, and enter the following parameters:
Host/IP
Port
User Name
Password
Click OK on the Configure Generic JVM Envrionments panel.
For the Linux remote policy, click here...
Click on the action menu next to the $HOSTNAME environment name, click Edit, and enter the following parameters:
Host Names/File Path
User Name
Password
Click OK on the Remote Host Configuration panel.
For the Windows remote policy, click here...
Click on the action menu next to the $HOSTNAME environment name, click Edit, and enter the following parameters:
Host Names/File Path
User Name
Password
Click OK on the Remote Host Configuration panel.
Click Save on the Edit Monitoring Configuration panel.
Associate the self-monitoring policy to a TrueSight group by clicking on the Server tab and entering a group name in the Add Agent Montors to Group field. Use the same group name for all of your self-monitoring policies. The monitors that you create as a result of these policies appear under this group on the Infrastructure Management server.
Click Save on the the Edit Monitoring Policy page.
.