Installing BMC Helix Monitor Agent

To install and configure BMC Helix Monitor Agent on the monitored stack

1. On the production stack, go to the self-monitoring directory under installation:
   helix-on-prem-deployment-manager/utilities/self-monitoring

2. Update the self_monitoring.config file.

   Parameter	Description
   NAMESPACE	Specify the name of a namespace where you want to install the BMC Helix Monitor Agent. This is the namespace that monitors the BMC Helix IT Operations Management namespace.  If you do not specify a namespace, it automatically uses the same BMC Helix IT Operations Management  namespace.
   AGENT_NAME	Specify a name that will be published in BMC Helix Operations Management for the BMC Helix Monitor Agent for hostname.
   IMAGE_REGISTRY_ORG	Specify the repository under which the PATROL Agent container image is available. The default value is Ip411.
   ENABLE_NODE_OS_MONITORING	Defines if you want to deploy PATROL Agents on individual nodes to monitor the operating system of the nodes. Set this value to true. This deploys two sets of PATROL Agents on the cluster: a deployment PATROL Agent which monitors all infrastructure components, including the topology defined through OpenShift or Kubernetes. a daemon set that reaches each running node and pulls the operating system matrix. If you  set the ​​​​parameter to false, the daemon set will not be deployed, and you cannot monitor node level data.  However, you can monitor other metrics at the cluster level.
   APIKEY	Specify the API Key. You can copy the API key from the observability stack, BMC Helix Operations Management console, by navigating to Administration > Repository. For more information, see Using API keys for external integrations in the BMC Helix Operations Management documentation.
   BHOM_TENANT_URL	Specify the BMC Helix Operations Management tenant URL of the observability stack in the following format: https:<BHOM tenantURL>:443 For example: https:tenant5-itom-demo.example.com:443
   CERTIFICATE	Copy the contents of the certificate from /opt/bmc/Patrol3/security/certificates/mca_ca.cer file in any existing BMC Helix Monitor Agent from BMC Helix Operations Management observability stack. If you do not have BMC Helix Monitor Agent deployed, see Using BMC Helix Monitor Agent to collect data.
   ACCESS_KEY	Create the access key and secret key. On the BMC Helix portal, select the Access Keys tab. Click Add Key. Enter the key details such as key name, type, and expiry (select Never expires). Click Confirm. Assign permissions to the Groups and Roles. In the Assignments section, click Select next to Groups and select Administrators and click Confirm. In the Assignments section, click Select next to Roles and select Administrator and click Confirm. Copy the key details from the created key and paste them into the ACCESS_KEY field.

3. Run the self-monitoring script.

   ./configure-selfmonitoring.sh

   This creates a namespace and deploys the PATROL Agent. You can see the status of the PATROL Agents which are running. You can verify the established connection between the UI and the deployed PATROL Agents on the BMC Helix Operations Management ​​​​​console > Configuration> Agents. 

Where to go from here

Configuring the monitoring and alarm policies