This documentation supports an earlier version of BMC Helix Operations Management.

To view the documentation for the latest version, select 23.2 from the Product version picker.

Collecting data

Data is referred to as the information that you are monitoring in your environments such as the Oracle database or the Windows operating system. You monitor these environments with the help of PATROL Agents and knowledge modules (KMs). Use the collected metrics to monitor the health of the monitored environments and proactively eliminate issues that might harm the environment.

As an administrator, collect data from monitored environments as explained in the following table:

1Begin data collection by planning your monitoring requirements. Decide what environments you want to monitor and in those environments what information you want to monitor. For example, you want to monitor CPU and memory utilization of your Windows operating systems.Administrator/Operator

List of supported KMs Open link


Based on the information that you plan to monitor, create a deployable package. A deployable package contains a combination of a PATROL Agent and KMs. When you create the package for the first time, it must contain the PATROL Agent. In the future, the package might only contain KMs. All KMs are bundled into a repository.


Creating deployable packages


3Next, deploy the package that installs its components. When you deploy the package with the PATROL Agent, the agent is added to the Agents page where you can manage agents and perform actions like restarting or reloading them.Administrator

Deploying packages

Viewing and filtering agents

4After the packages are deployed, configure the KM how to connect to the environment that you want to monitor and what information to collect. For this purpose, create monitoring policies in all the KMs that you have deployed.AdministratorCreating monitor policies

When you have configured monitoring policies, the KM starts sending data to BMC Helix Operations Management . You can view the collected data on the Monitoring > Devices page. Devices are created with the same name as the PATROL Agent that collects data.

Administrator/OperatorViewing collected data

In addition, you can import events by using:

  • BMC Helix Developer Tools  - uses a Fluentd-based framework for integration with BMC and third-party products to ingest event, CI, and topology data for monitoring in BMC Helix AIOps . It enables you to build custom integrations for the third-party products for which out-of-the-box integrations are not available, and collects logs from files. For more information, see Integrating by using BMC Helix Developer Tools Open link .
  • BMC Helix Intelligent Integrations - uses REST APIs and Webhook mechanism for integration with BMC and third-party products to ingest event, CI, and topology data for monitoring in BMC Helix AIOps . It provides a click-and-connect capability to configure an integration. For more information, see Integrating by using BMC Helix Intelligent Integrations Open link .
  • Event APIs - enable you to collect event data from third-party applications. For more information, see Managing events with REST APIs.

You can also import events from TrueSight Operations Management and third parties that have custom slots.

Was this page helpful? Yes No Submitting... Thank you