Using BMC Helix Monitor Agent to collect data
BMC Helix Monitor Agent is a light-weight containerized collector that is pre-configured and is ready to be deployed. It has the following advantages:
- No Agent configurations are required after deployment.
- Knowledge modules (KMs) are already deployed within the container.
Following KMs are pre-configured with the BMC Helix Monitor Agent . You can start monitoring by creating policies.
KM | Version |
---|---|
PATROL for Amazon Web Services | 22.4.00 |
PATROL for Apache Tomcat and Generic Java Server | 3.1.02 |
PATROL for Elasticsearch | 1.0.10 |
PATROL for Kubernetes | 22.4.00 |
PATROL for Linux | 22.4.00 |
PATROL for Microsoft Azure | 22.4.00 |
PATROL for MongoDB | 1.1.30 |
1.0.01 | |
1.1.01 | |
3.1.02 | |
1.1.01 | |
4.0.31 |
System requirements
Container orchestration | The following cluster environments are supported:
Note Managed Kubernetes services, such as Azure Kubernetes Service (AKS), Amazon Elastic Kubernetes Service (EKS), and Google Kubernetes Engine (GKE) are not supported. |
Package manager | Helm 3.2.3 and later are supported. What is Helm? Helm is a package manager for Kubernetes. Helm is the Kubernetes equivalent of yum or apt. Helm deploys charts, which you can think of as a packaged application. It is a collection of all your versioned, pre-configured application resources which can be deployed as one unit. For more information, see Installing . |
Container host operating system | BMC Helix Monitor Agent has no specific dependencies on the underlying Linux OS or releases running on your worker nodes. You can use any x86_64 GNU/Linux OS supported by your Kubernetes or OpenShift platform and release version. |
Docker registry requirements
Direct access to BMC's Docker Trusted Repository (DTR) at https://containers.bmc.com is available. You can also use Local Harbor 2.1 or later synchronized with BMC's Docker Trusted Repository.
Best practice
BMC highly recommends that you install a local repository. A local repository provides the following benefits:
- Improved performance
The container images are cached and accessed locally during deployments and upgrades. - Security
You can implement your own security scan of containers before deployment. - Access control
You can control access to the local repository by using authentication and authorization. - Air-gap support
You can replicate the local repository to support environments that do not have internet access.
For information about installing a local Harbor repository synchronized with the BMC DTR, see Setting up a Harbor repository.
Note: The local Harbor repository is recommended
BMC does not manage any repository other than Harbor and recommends that you use the local Harbor repository to pull the container image. However, if you are using any other repository, make sure that the repository is configured to connect to the BMC DTR to pull the container image.
Downloading the BMC Helix Monitor Agent chart and container images
To download the helm chart and token
- Log in to EPD by using your Support user ID and password. You might also be prompted to complete the Export Compliance Form. If you are accessing this site for the first time, create a new EPD profile to specify the languages and platforms that you want to download. For assistance with EPD, see EPD site help .
Download the helm chart
Helix-monitor-agent-22.4.00.00.tar
to a temporary directory.- Download the container-token.bmc file containing the Docker token.
Download link for the installation file
EPD link to the product | Description of the content |
---|---|
BMC Helix Monitor Agent-Containerized Download the token again even if you have downloaded it for an earlier release. | Helix-monitor-agent-22.4.00.tar |
BMC Helix Monitor Agent-Containerized | Helix-monitor-agent-22.4.00.tgz |
Kubernetes multi-node deployment | Helix-monitor-agent-k8s-22.4.00.tgz |
Container images
BMC containers images are distributed from https://containers.bmc.com . You can access the containers for the licensed products by using your registered support account and a new password. This password is saved in a file which is downloaded with this PDF file. The password is shared among all the containerized BMC software that you have access to.
Check your downloads directory for the container-token.bmc file that contains your generated password. For step-by-step instructions on how to use this password to obtain the BMC container images, see Setting up a Harbor repository .
To deploy BMC Helix Monitor Agent
- Copy the downloaded file (
Helix-monitor-agent-22.4.00.tar
) to the controller or bastion machine from where the Kubernetes cluster is accessible. Extract thetar
file. Create Kubernetes image pull secret by using the following command:
kubectl create secret docker-registry <image pull secret name> --docker-server=containers.bmc.com --docker-username=<docker registry user name> --docker-password=<docker registry password> --docker-email=<docker registry email>
For local repository, ensure that you change the
docker-server
value in this command.- There are two (2) helm charts available in the downloaded file. Extract the required file from the downloaded files by running the following command:
tar -zxf <filename>
.
The default yaml file is helix-monitor-agent/values.yaml . You must replace all values starting and ending with __. Also, replace image pull secret name with the newly created secret name. Open the
values.yaml
file in a text editor and edit the following details:Yaml parameters
Configuration Details registryhost
The docker registryhost containing the Helix Monitor Agent. The default value is contaniers.bmc.com.
namespace
Specify the namespace where you want to deploy the Helix Monitor Agent container.
imagePullSecrets
Secret to authenticate with a container registry to pull an image. For more information, see Pull an Image from a Private Registry.
name
The name of Secrets. Replace image pull secret name with the newly created secret name.
enabled
Set it true when you want to enable imagePullSecrets.
Image
repository
The location on the registry where the container image exists. Modify the parameter if you are using a local repository.
pullPolicy
Image pull policy for pod.
Options available:
- Always
- IfNotPresent
- Never
tag (Optional)
Container image tag. Modify the parameter only if you have created custom tags on containers.
Service
name
The Kubernetes deployment name. This name must be unique in a namespace.
ports (Optional)
The port used by PATROL Agent. API Key - In BMC Helix Operations Management , navigate to Administration > Repository.
Click Copy API key and paste it in the
values.yaml
file.
If you have configured a rotation interval for the API key in BMC Helix Portal , make sure that you use the latest API key each time the key rotates. For instructions about configuring a rotation interval, see Using API keys for external integrations.
BHOM tenant URL Enter
https:<
BMC Helix Operations Managementtenant URL>:443
.
For example,https:example-hostname.bmc.com:443
.Certificate Publishhostname The hostname by which PATROL Agent is displayed in BMC Helix Operation Management. There should not be any other existing Agent with the same host name.
Tags (Optional) Tags with which PATROL Agent identifies in the server.
maxlogsize (optional) The maximum amount of ephemeral storage container consumes on kubernetes for the logs folder.
Resources (Optional) Limits (CPU, memory) The upper limit of CPU and memory resources allotted for the container. For more information, see Resource Management.
Requests (CPU, memory) The minimum CPU and memory resources allotted for the container. For more information, see Resource Management.
Forward Proxy configuration If you have configured forward proxy server, enter the username, password, and the forward proxy URL. Multi-node specific Kubernetes variable enableNodeDeployment Set the variable to true. Tags Tags with which PATROL Agent identifies in the server. ( Use tag name in agent selection criteria while creating monitor policy)
Run the following command:
helm3 install -f <override values yaml file path> <helm deplyoment name> <container file name>
helm3 install -f helix-monitor-agent/values.yaml k8s-agent helix-monitor-agent-22.4.00.tgz
To verify the deployment
Run the following command to check the helm chart deployment status:
helm3 list
- In BMC Helix Operations Management , navigate to Configuration > Agents.
- Search for
BMC Helix Monitor Agent
by entering its name in the search box.
For a BMC Helix Monitor Agent , the version ends with letter c.
To uninstall BMC Helix Monitor Agent
- Run the following command:
helm3 uninstall <deployment name>
To verify the uninstallation, run the following command:
helm3 list
Comments
Log in or register to comment.