Skip to Content

Preparing to configure the monitoring solution

Perform the following checks before configuring the monitoring solution to monitor your on-premises BMC Helix IT Operations Management:

Related topics

Monitoring solution architecture and overview

To install a PATROL Agent

Install a PATROL Agent to monitor the VMWare vSphere of your Kubernetes or OpenShift cluster.
For more information, see BMC PATROL Agent for BMC Helix Operations Management.

The PATROL Agent collects and sends VMware metrics to BMC Helix IT Operations Management on the observability stack.

An admin user installing the PATROL Agent must have permission to create the cluster role and role-binding objects. The Agent utilizes the default service account for the PATROL Agent.

To download the container images

The BMC Helix ITOM container images are hosted on the BMC Docker Trusted Registry (DTR) which is available at containers.bmc.com.

Download the Log_Analytics_and_Agent_images.txt file.

To download the self-monitoring blueprint

You must download the blueprint for OpenShift self-monitoring to create service models to monitor your on-premises BMC Helix IT Operations Management in an OpenShift cluster.  

A default service blueprint is available on BMC Helix AIOps to monitor your on-premises BMC Helix IT Operations Management in a Kubernetes cluster.  

To verify the connectivity

Make sure there are no firewall restrictions that hinder the connectivity between the components:

  • Make sure the following components are deployed on the production stack can send data to the non-production stack:
    • BMC Helix Monitor Agent
    • Log Analytics connector for Kubernetes
    • Ceph server
  • Make sure the BMC Discovery deployed on the observability stack can communicate with the following components on the production stack:
    • vSphere that belongs to VCenter/ESX where the worker nodes are installed.
    • Ceph server if it is used.
    • SSH connection to the worker nodes.

To verify if the Ceph server is enabled with API support

Install the Ceph RESTful API (Ceph API) provided by the Ceph Dashboard module. The Ceph Server KM and BMC Discovery use the Ceph RESTful API to connect and monitor the Ceph servers.

For more information, see CEPH RESTFUL API in the Ceph documentation.

To verify the certificates and security

  • Create a BMC Helix Operations Management access key and secret key for the administrator user.
    You will need the keys to import policies and dashboards.
    For more information, see Setting up access keys for programmatic access in BMC Helix Portal documentation.

  • Get the BMC Discovery system user ID and password. You will need them to configure the Synthetic and Scripting KM and monitor the BMC Discovery status.
  • Get the BMC Discovery tideway user credentials. You will need them while conjuring the Self-Monitoring-Discovery-Appliance-Linux-Monitor policy for BMC Discovery.

  • Acquire your non-production stack tenant certificate. You must enter the tenant certificate information while configuring the BMC Helix Monitor Agent.
    For more information, in the BMC Helix Operations Management documentation, go to the topic Using BMC Helix Monitor Agent to collect data. Under Deploying BMC Helix Monitor Agent, expand the Chrome browser.

  • Create an observability stack tenant access key and secret key. You will need the keys to import policies and dashboards.
    For more information, see Setting up access keys for programmatic access in BMC Helix Portal documentation.

  • The pod security standard of the namespace where you will install BMC Helix Monitor Agent must be set to baseline.

    Warning

    Important

    The BMC Helix Monitor Agent namespace should be different from the BMC Helix ITOM namespace.

    If you cannot set the pod security standard of the namespace to privileged, you can set it to baseline instead. However, the OpenShift daemonset for network and filesystem monitoring will not function when you set the pod security standard of the namespace to baseline.

     

To install and configure the BMC Discovery Outpost

Install the BMC Discovery Outpost on the Windows server that has access to the production tenant URL to access the components in the production infrastructure.

  1. Install the BMC Discovery Outpost on the Windows server which can access the production tenant URL.
    See Installing the BMC Discovery Outpost in the BMC Discovery documentation.

  2. Configure the BMC Discovery Outpost.
    See Configuring the BMC Discovery Outpost in the BMC Discovery documentation.

  3. Register the BMC Discovery Outpost with BMC Discovery.
    See Managing BMC Discovery Outposts in the BMC Discovery documentation.

  4. Add and store login credentials.
    Login credentials such as usernames, passwords, SSH keys, and other authentication methods allow access to hosts. BMC Discovery requires these credentials to scan and manage hosts in the IT environment.
    See Adding credentials in the BMC Discovery documentation.

     

To discover your environment

  1. To discover Kubernetes management systems using an API provider, see Discovering Red Hat OpenShift clusters or Discovering Kubernetes clusters managed by Rancher in the BMC Discovery documentation.

  2. To discover the ESX and ESXi hosts in your environment, see Discovering ESX and ESXi hosts in the BMC Discovery documentation.

  3. (Optional) To discover the guest hosts that are managed by vCenter, see Discovering VMware guest hosts by using the vCenter API in the BMC Discovery documentation.

  4. To discover Ceph storage systems via Ceph Manager by scanning the Host, see Ceph Storage Systems in the BMC Discovery documentation.

  5. To discover SNMP devices, see Discovering SNMP devices in the BMC Discovery documentation.

Where to go from here

Importing the monitoring and alarm policies

 

 

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

BMC Helix IT Operations Management deployment 25.4