Configuring the monitoring and alarm policies

To configure alarm policies

1. Login to BMC Helix Operations Management.
2. From the Configuration menu, select Alarm Policies. 
   
3. Select an alarm policy; for example, BMC_Self_Mon_VMWare_Vmotion, and then click Edit.
4. On the Update Alarm Policy page, in the Alarm Generation Conditions area, edit the instance criteria for your Agent host name or tag.
   For example:
5. Repeat the steps to edit the instance criteria for your Agent host name or tag of all alarm policies.
6. Review the configurations and enable the policies.

To configure the Self-Monitoring-Discovery-Appliance-Linux-Monitor policy

1.  Login to BMC Helix Operations Management.
2. From the Configuration menu, select Monitoring Policies.
3. In the Monitoring Policies tab, search for Self-Monitoring-Discovery-Appliance-Linux-Monitor.
4. Click beside the Self-Monitoring-Discovery-Appliance-Linux-Monitor policy, and click Edit.
5. On the Edit Monitoring Policy page, specify the Agent Selection Criteria.
   Agent Host Name is the name of your BMC Helix Monitor Agent.
   
6. On the Monitoring tab, under Monitoring Solutions, click beside Linux, and select Edit.
   
7. In the Edit Monitoring Configuration pane, under Remote Host Configuration, click , and select Edit.
   
    
8. In the Remote Host Configuration pane, specify the host name and password in respective fields.
   Leave all other fields at their default values.
   
    
9. Click OK. 
10. Review the configurations and enable the policy.

To configure the Self-Monitoring-Openshift-KM policy

1. Login to BMC Helix Operations Management.
2. From the Configuration menu, select Monitoring Policies.
3. In the Monitoring Policies tab, search for Self-Monitoring-Openshift-KM.
4. Click beside the Self-Monitoring-Openshift-KM policy, and click Edit.
5. On the Edit Monitoring Policy page, specify the Agent Selection Criteria.
   
6. On the Monitoring tab, under Monitoring Solutions, click , and select Edit.
   
7. In the Edit Monitoring Configuration pane, click, and then select Edit.
   
8. In the OpenShift Cluster Details pane, specify the OpenShift environment name. 
   Leave all other fields at their default values.
   
    
9. Click OK.
10. Review the configurations and enable the policy.

To configure the Self-Monitoring-Opensearch policy

1. Login to BMC Helix Operations Management.
2. From the Configuration menu, select Monitoring Policies.
3. In the Monitoring Policies tab, search for Self-Monitoring-Opensearch.
4. Click beside the Self-Monitoring-Opensearch policy, and select Edit.
5. On the Edit Monitoring Policy page, specify the Agent Selection Criteria.
   Agent Host Name is the name of your BMC Helix Monitor Agent.
   
6. On the Monitoring tab, under Monitoring Solutions, click , and select Edit.
   
7. In the Edit Monitoring Configuration pane,  click , and select Edit.
   ​​​​
8. In the Elasticsearch Host Details pane, in the Label field, replace itom with BMC Helix ITOM namespace.
9. Leave all other fields at their default values.
   
10. Update the Authentication Details section.
    For example: bmcuser and Es_L0g#p@SS (unless changed)​​​​​​
11. Click OK.
12. Review the configurations and enable the policy.​​​​​​

To configure the Self-Monitoring-Kafka policy

1. Login to BMC Helix Operations Management.
2. From the Configuration menu, select Monitoring Policies.
3. In the Monitoring Policies tab, search for Self-Monitoring-Kafka.
4. Click beside the Self-Monitoring-Kafka policy and select Edit. 
5. On the Edit Monitoring Policy page, specify the Agent Selection Criteria.
   Agent Host Name is the name of your BMC Helix Monitor Agent.
   
6. On the Monitoring tab, under Monitoring Solutions, click , and select Edit.
   
7. In the Edit Monitoring Configuration pane, click , and select Edit.
   
8. In the Environment Configuration pane, specify the environment name according to your business need.
   The name can have 10 to 15 characters only. 
   Leave all other fields at their default values.
   
9. Click OK. 
10. Review the configurations and enable the policy.

To configure the Self-Monitoring-Redis policy

1. Login to BMC Helix Operations Management.
2. From the Configuration menu, select Monitoring Policies.
3. In the Monitoring Policies tab, search for Self-Monitoring-Redis.
4. Click beside the Self-Monitoring-Redis policy and select Edit. 
5. On the Edit Monitoring Policy page, specify the Agent Selection Criteria.
   Agent Host Name is the name of your BMC Helix Monitor Agent.
   
6. On the Monitoring tab, under Monitoring Solutions, click , and select Edit.
   
7. ​​​​In the Edit Monitoring Configuration pane, click , and select Edit.
   
8. In the Redis Server Details pane, in the Host Name/IP Address field, replace itom with your BMC Helix ITOM namespace.
9. Leave all other fields at their default values.
   
   Do not change the port number.
   
10. Click OK. 
11. Review the configurations and enable the policy.

To configure Self-Monitoring-PostgreSQL policy

1. Login to BMC Helix Operations Management.
2. From the Configuration menu, select Monitoring Policies.
3. In the Monitoring Policies tab, search for Self-Monitoring-PostgreSQL.
4. Click beside the Self-Monitoring-PostgreSQL policy and select Edit. 
5. On the Edit Monitoring Policy page, specify the Agent Selection Criteria.
   Agent Host Name is the name of your BMC Helix Monitor Agent.
   
6. On the Monitoring tab, under Monitoring Solutions, click , and select Edit.
   
7. In the Edit Monitoring Configuration pane, click , and select Edit.
   
8. In the Environment Configuration pane, perform the following steps:
   1. Enter an environment name.
   2. In the PostgreSQL host field, replace itom with your BMC Helix ITOM namespace.
   3. Set the password to pGTest2020.
      The password must match the password set in the secrets.txt. 
   4. Leave all other fields at their default values.
      Do not change the port number.
      
9. Scroll down to the Custom SQL queries section, click , and select Edit.
   
10. In the Custom SQL queries pane, in SQL query field, replace the tenant ID with your tenant ID.
    
11. Click OK. 
12. Review the configurations and enable the policy.

To configure the Self-Monitoring-PostgreSQL-Pool-level

1. Login to BMC Helix Operations Management.
2. From the Configuration menu, select Monitoring Policies.
3. In the Monitoring Policies tab, search for Self-Monitoring-PostgreSQL-Pool-level.
4. Click beside the Self-Monitoring-PostgreSQL-Pool-level policy and select Edit. 
5. On the Edit Monitoring Policy page, specify the Agent Selection Criteria.
   Agent Host Name is the name of your BMC Helix Monitor Agent.
   
6. On the Monitoring tab, under Monitoring Solutions, click , and select Edit.
   
7. In the Edit Monitoring Configuration pane, click , and select Edit.
   
8. In the Edit Monitoring Configuration pane, add your environment name, update the IP address of your PostgreSQL pod, and then set the password as pGTest2020.
   ​​​​​Note: The password must match the password set in the secrets.txt.The [confluence_tip] macro is a standalone macro and it cannot be used inline. Click on this message for details.
   This macro generates standalone content. As a consequence you need to make sure to use a syntax that separates your macro from the content before and after it so that it's on a line by itself. For example in XWiki Syntax 2.0+ this means having 2 newline characters (a.k.a line breaks) separating your macro from the content before and after it.

1. Scroll down to the Custom SQL queries section. Click , and select Edit.
2. 
3. In the SQL query field, update the tenant ID.
   
4. Click Save.
5. Repeat the steps to update the environment configurations (environment name, IP address of your PostgreSQL host, password, and tenant ID) for all the policies in all the pods.
   Example: In the following image, there are two pods. Update the environment configurations for the policies in both pods.
   
6. Review the configurations and enable the policy.

To configure the Self-Monitoring-Discovery-Script-KM-Linux policy

1. Login to BMC Helix Operations Management.
2. From the Configuration menu, select Monitoring Policies.
3. In the Monitoring Policies tab, search for Self-Monitoring-Discovery-Script-KM-Linux.
4. Click beside the Self-Monitoring-Discovery-Script-KM-Linux policy and select Edit. 
5. On the Edit Monitoring Policy page, specify the Agent Selection Criteria.
   Agent Host Name is the name of your BMC Helix Monitor Agent.
   
6. On the Monitoring tab, under Monitoring Solutions, click , and select Files.
   

1. In the Monitor Configuration Files pane, perform the following steps:
   1. Make a note of the file path Customer_URLs.in. 
   2. Delete the Customer_URLs.in file.
      

1. 
   
   1. Click Add. 
      
   2. In the Target File Path field, enter the file path you copied, /opt/bmc/Customer_URLs.in.
   3. Click Attach file, browse to the location where you downloaded the script files, select a file, and click Add.
      For more information, see Installing-BMC-Helix-Monitor-Agent.
      

1. Repeat the steps to add the /opt/bmc/discovery_rest_monitoring-V2.py file.
2. Click Save.
3. In the Edit Monitoring Configuration pane, click , and select Edit.
   

1. In the Devices pane, in the Scripts section, click , and select Edit.
   

1. In the Scripts pane, in the Script Path field, update the version of the Self-Monitoring-Discovery-Script-KM-Linux.
   
    
2. Click Ok.
3. Review the configurations and enable the policy.

9. To configure the Self-Monitoring-Ceph-Storage policy

1. Login to BMC Helix Operations Management.
2. From the Configuration menu, select Monitoring Policies.
3. In the Monitoring Policies tab, search for Self-Monitoring-Ceph-Storage.
4. Click beside Self-Monitoring-Ceph-Storage policy to edit it.
5. On the Monitoring tab, under Monitoring Solutions, click , and select Edit.
   

1. In the Edit Monitoring Configuration pane, click beside the monitoring policy and select Edit.
   

1. In the Ceph Environment Configuration pane, specify the manager server name, Ceph server API port, and password in respective fields.
   Leave all other fields at their default values.

   

2. Click OK. 
3. Review the configurations and enable the policy.

To configure the Self-Monitoring-Synthetic-Container-Agent-Discovery-Local-Login

1. Login to BMC Helix Operations Management.
2. From the Configuration menu, select Monitoring Policies.
3. In the Monitoring Policies tab, search for Self-Monitoring-Synthetic-Container-Agent-Discovery-Local-Login. 
4. Click beside the Self-Monitoring-Synthetic-Container-Agent-Discovery-Local-Login policy, and click Edit.
5. On the Edit Monitoring Policy page, specify the Agent Selection Criteria.
   Agent Host Name is the name of your BMC Helix Monitor Agent.
   
6. On the Monitoring tab, under Monitoring Solutions, click , and select Files.
   

1. In the Monitor Configuration Files pane, perform the following steps:
   1. Make a note of the file path Login-logout-discovery-local-v2.py.
   2. Delete the Login-logout-discovery-local-v2.py file.
      
   3. Click Add.
      

1. 
   
   1. In the Target File Path field, enter /opt/bmc/Patrol3/stm/bin/Login-logout-discovery-local-v2.py
   2. Click Attach file, browse to the location where you downloaded the script files, select a file, and click Add.
      For more information, see Installing-BMC-Helix-Monitor-Agent.
      

1. 
   
   1. Click Save.
2. On the Monitoring tab, under Monitoring Solutions, click ,and select Edit.
   
3. In the Edit Monitoring Configuration pane, click beside password and select Edit.
   

1. In the Secret Variable List pane, update the passwords and click OK.
   

1. Click OK and then click Save.
2. Review the configurations and enable the policy.

To configure the Self-Monitoring-Zookeeper-Prometheus-Script-KM

1. Login to BMC Helix Operations Management.
2. From the Configuration menu, select Monitoring Policies.
3. In the Monitoring Policies tab, search for Self-Monitoring-Zookeeper-Prometheus-Script-KM.
4. Click beside the Self-Monitoring-Zookeeper-Prometheus-Script-KM policy, and click Edit.
5. On the Edit Monitoring Policy page, specify the Agent Selection Criteria.
   Agent Host Name is the name of your BMC Helix Monitor Agent.
   
6. On the Monitoring tab, under Monitoring Solutions, click , and select Files.
   

1. In the Monitor Configuration Files pane, perform the following steps:
   1. Make a note of all the file path settings.ini.
   2. Delete the settings.ini file.
      
   3. Click Add.
      

1. 
   
   1. In the Target File Path field, enter /home/patrol/settings.ini.
   2. Click Attach file, browse to the location where you downloaded the script files, select a file, and click Add.
      For more information, see Installing-BMC-Helix-Monitor-Agent.
      

1. Repeat the process to attach the following files:
   BHOMRestClient.py
   ZooKeeperRestClient.py
   zookeeper.py
   logger.conf

1. On the Monitoring tab, under Monitoring Solutions, click and select Edit.
   
    
2. In the Devices pane, do not change the device name. It must be localhost.
3. In the Edit Monitoring Configuration pane, click beside localhost and select Edit.
4. In the Edit Monitoring Configuration pane, click beside zookeeper.py and select Edit.
   

5. In the Scripts pane, in the Script Path field, specify the complete script path:
   /usr/bin/python zookeeper.py -z thanos-querier.openshift-monitoring.svc.cluster.local -zp 9091 -s <tenant url> -p <tenant port> -ak <access key> -sk <secret key> -t <tenant id> -d
   Example:
   /usr/bin/python zookeeper.py -z thanos-querier.openshift-monitoring.svc.cluster.local -zp 9091 -s seal5-itom-demo.onbmc.com -p 443 -ak Z7OIB8RI2SZCCSLOUL7681JAULWNWT -sk BXmb5xZGoVe8mlqShD9U9Kiw7npZOfrcwI4EaMjzF62i9cv3Dh -t 151128433 -d
   For more information, see Using API keys for external integrations in BMC Helix Portal documentation.
   Leave all other fields at their default values.
   
   

6. Click OK. 
7. Review the configurations and enable the policy.

To configure the Self-Monitoring-Victoria-Metric policy

1. Login to BMC Helix Operations Management.
2. From the Configuration menu, select Monitoring Policies.
3. In the Monitoring Policies tab, search for Self-Monitoring-Victoria-Metric.
4. Click beside the Self-Monitoring-Victoria-Metric policy, and click Edit.
5. On the Edit Monitoring Policy page, specify the Agent Selection Criteria.
   Agent Host Name is the name of your BMC Helix Monitor Agent.
   
6. On the Monitoring tab, under Monitoring Solutions, click , and select Edit.
   
7. In the Edit Monitoring Configuration pane, click beside the monitoring policy and select Edit.
   
8. In the Victoria Metric Account Details pane, specify a cluster name.
   Make sure the name is short and suites your business application.
   Leave all other fields at their default values.
   

1. Click OK. 
2. Review the configurations and enable the policy.

To configure the Self-Monitoring-VMWare policy

1. Login to BMC Helix Operations Management.
2. From the Configuration menu, select Monitoring Policies.
3. In the Monitoring Policies tab, search for Self-Monitoring-VMWare. 
4. Click beside the Self-Monitoring-VMWare policy, and click Edit.

5. On the Edit Monitoring Policy page, specify the Agent Selection Criteria.
   Specify the Agent that you deployed outside the Kubernetes cluster and has access to the vSphere configuration you are entering when configuring this policy.

   

6. On the Monitoring tab, under Monitoring Solutions, click , and select Edit.
   
7. In the Edit Monitoring Configuration pane, click beside the monitoring policy and select Edit.
   

1. In the vCenter/ESX server Details pane, specify the vSphere details.
   If required, you can change the port.
   Leave all other fields at their default values.
   

1. Scroll down and expand the Object Filtering Details. Update the filters for all VMWare entities.
   

1. Click OK and then click Save.
2. Review the configurations and enable the policy.

Where to go from here

Importing-the-BMC-Helix-Dashboards-for-monitoring