Importing the monitoring and alarm policies

You need monitoring policies to monitor and collect metrics for your on-premises BMC Helix IT Operations Management. You also need alarm policies to generate events when the metrics exceed the set thresholds.

Use the information in this section to import the monitoring and alarm policies in the observability stack.

 

Related topics

Monitoring-solution-architecture-and-overview

The following table lists the monitoring policies that you must import:

 

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

 

  1. Download and extract the Self-Monitoring-V25.2.​​​​zip file.
    It contains the monitoring policies, alarm policies, scripts, and dashboards required to configure the monitoring solution.​​​​​​
  2. Open each folder and replace the following default values with the actual values in all the files:

    Default values

    Replace with

    BMC Helix Monitor Agent name
    Example: self-mon-agent1.example.bmc.com

    BMC Discoveryload balancer name
    Example: env9-disc-private-poc.example.bmc.com

    vSphere server name
    Example: pe-aus-lab079.example.bmc.com

    replace-clustername

    Your cluster name. This is only an identifier for your cluster name.
    Example: env9-adeonprem

    (If applicable) Your Ceph server name
    Example: vl-pun-cep-vm2.bmc.com

    replace-envname

    An identifier for your environment name
    Example: env9-dev

    replace-namespace-name

    Your namespace name that is monitored.
    Example: adeonprem

    replace-tenant-id

    Your tenant ID
    Example: 318920956

    SRECNTRAgent tag name
    OPENSHIFTCNTROpenShift agent tag name

    ​​​​​​Example: Open the Self-Monitoring-Kafka.mo file and replace replace-agent-name.bmc.com
    with your BMC Helix Monitor Agent name (self-mon-agent1.example.bmc.com).
    24.4_Screenshot1.png

     

  3. Import the monitoring policies by using the latest version of the bhompolicymigrator tool.
    For more information, see Migrating TSOM Infrastructure Policies to BHOM with the bhompolicymigrator on BMC Community. You can find the bhompolicymigrator tool in the Notes & Attachments section.

  4. Ensure that the KM solution version in the monitoring & alarm policies matches the version at
    BHOM > Administration tab> Repository > Installation components.

    Create the access key and secret key.

    1. On the BMC Helix portal, select the Access Keys tab.
    2. Click Add Key.
    3. Enter the key details such as key name, type and expiry (select Never expires).
    4. Click Confirm.
      1741684647616-657.png
  5. Assign permissions to the Groups and Roles.
    1. In the Assignments section, click Select next to Groups and select Administrators and click Confirm.
    2. In the Assignments section, click Select next to Roles and select Administrator and click Confirm.
      1741684647625-612.png

  6. To import the monitoring policies, run the following command:

    bhompolicymigrator importmonitoringpolicy [-pc --policy_criteria POLICY_INCLUDE_CRITERIA] -s --bhomserver BHOM_SERVER_HOST -p --bhomport BHOM_SERVER_PORT -t --bhomtenant BHOM_SERVER_TENANT -ak --bhomaccesskey BHOM_ACCESS_KEY -sk --bhomsecretkey BHOM_SECRET_KEY

    Example:

    bhompolicymigrator importmonitoringpolicy --bhomserver itom-private-poc.seal.bmc.com  --bhomport 443 --bhomtenant 1538205466 --bhomaccesskey PRGYEDLSY4F439FFLATXNXI6RP9QXU  --bhomsecretkey w3toqgLuKHgNS03DUklDDQsoZjGppkzjLtWUbw8EG4qIIqdjE7

  7. To import the alarm policies, run the following command:

    bhompolicymigrator importalarmpolicy [-pc --policy_criteria POLICY_INCLUDE_CRITERIA] -s --bhomserver BHOM_SERVER_HOST -p --bhomport BHOM_SERVER_PORT -t --bhomtenant BHOM_SERVER_TENANT -ak --bhomaccesskey BHOM_ACCESS_KEY -sk --bhomsecretkey BHOM_SECRET_KEY

    Example:

    bhompolicymigrator importalarmpolicy --bhomserver itom-private-poc.seal.bmc.com  --bhomport 443 --bhomtenant 1538205466 --bhomaccesskey PRGYEDLSY4F439FFLATXNXI6RP9QXU  --bhomsecretkey w3toqgLuKHgNS03DUklDDQsoZjGppkzjLtWUbw8EG4qIIqdjE7

  8. Extract the \Self-Monitoring-V25.2.zip file, and go to \scripts\synthetic\Login-logout-discovery-local-v1.py, replace the tenant URL with your BMC Discovery load balancer URL:

    https://<BMC Discovery load balancer URL>/ui/LocalLogin

    Example: https://itom-disc-private-poc.seal.xyz.com/ui/LocalLogin

  9. In the Customer_URLs.in file, set the name of your BMC Discovery load balancer URL.

    Example: env9-discovery-lb.bmc.com

You need the scripts to upload in the Self-Monitoring-Synthetic-Container-Agent-Discovery-Local-Login policy.
For more information, see Configuring-the-monitoring-and-alarm-policies.

Where to go from here

Configuring-the-monitoring-and-alarm-policies

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*