Importing the monitoring and alarm policies
The following table lists the monitoring policies that can be imported:
| Policy name | Description
| KMs used for the monitoring policy |
|---|---|---|---|
1 | Self-Monitoring-Discovery-Appliance-Linux-Monitor policy | To monitor the BMC Discovery using the Linux Remote KM. | |
2 | Self-Monitoring-Openshift-KM policy | To monitor and manage the availability and performance of your OpenShift environment. | |
3 | Self-Monitoring-Opensearch policy | To monitor the performance metrics of the configured Elasticsearch host. | |
4 | Self-Monitoring-Kafka policy | To monitor the availability and performance of your Kafka environment. | |
5 | Self-Monitoring-Redis policy | To monitor the Redis cache infrastructure to track the availability and performance of microservices that rely on it. | |
6 | Self-Monitoring-PostgreSQL policy | To monitor the availability and performance of the PostgreSQL database resources. | |
7 | Self-Monitoring-PostgreSQL-Pool-level | To monitor individual pools of the PostgreSQL pool pod. | |
8 | Self-Monitoring-Discovery-Script-KM-Linux policy | This policy uses the Scripting KM to monitor the service-up status of BMC Discovery. | |
9 | Self-Monitoring-Ceph-Storage policy | To ensure continuous monitoring of the distributed storage infrastructure's health and performance. This robust monitoring extends to individual components, providing transparency into data status and insights into overall system health. | |
10 | Self-Monitoring-Synthetic-Container-Agent-Discovery-Local-Login | To collect information related to the health of web-based applications using attributes such as availability, performance, execution time, response time, and so on. This policy also monitors the login time for the BMC Discovery appliance local login URL. | |
12 | Self-Monitoring-Victoria-Metric | To monitor the VictoriaMetric cluster. | How to import a KM into the repository |
13 | Self-Monitoring-VMWare | To monitor vMotion for the VMs within the ESX cluster hosting the OpenShift worker nodes. |
Here is a list of alarm policies that you must import:
- BMC_Self_Monitoring_All_Policies_Configuration_Monitoring_Status
- BMC_Self_Mon_Ceph_Monitoring
- BMC_Self_Mon_DiscoveryApplianceStatusMonitoring
- BMC_Self_Mon_Discovery_Appliance_Login_Logout
- BMC_Self_Mon_Import_SRE_Synthetic_KM
- BMC_Self_Mon_K8S_KM
- BMC_Self_Mon_Kafka_KM
- BMC_Self_Mon_Linux_KM_Global_Thresholds
- BMC_Self_Mon_Linux_KM_Global_Thresholds_All
- BMC_Self_Mon_Openshift_KM
- BMC_Self_Mon_Postgres_Global_Threshold
- BMC_Self_Mon_Postgres_Linux_KM_Global_Thresholds
- BMC_Self_Mon_Postgres_Openshift_Pod
- BMC_Self_Mon_Redis_Global_Threshold
- BMC_Self_Mon_Tools_Elastic_Search
- BMC_Self_Mon_Victoria_Metrics_Global_Thresholds
- BMC_Self_Mon_VMWare_Vmotion
- BMC_Self_Mon_Zookeeper_Policy
- BMC_Self_Mon_Zookeeper_Policy_Openshift
To import monitoring and alarm policies
- Download the file.
It contains the monitoring policies, alarm policies, scripts, and dashboards required to configure the monitoring solution. - Copy the downloaded .zip file to the helix-on-prem-deployment-manager/utilities/self-monitoring folder.
- Download the bhompolicymigrator-4.00.00.05-linux64-20250930-065049-bin tool zip file from Migrating TSOM Infrastructure Policies to BHOM with the bhompolicymigrator on BMC Community. You can find the bhompolicymigrator tool in the Notes & Attachments section.
- Unzip the file in helix-on-prem-deployment-manager/utilities/self-monitoring folder.
After you place the required files in the helix-on-prem-deployment-manager/utilities/self-monitoring folder, the policies are imported automatically.
Where to go from here