Integrating with Prometheus to collect metrics

As a tenant administrator, perform the following steps to integrate with Prometheus , verify the integration, and view the collected data in various BMC products.

Before you begin

1. Have the egress IP of your tenant. Request the egress IP from BMC Software if you don't already have it.
2. Ensure that you have a firewall rule to allow traffic from the egress IP to the Prometheus host on the listening port (default port is 9090).

To integrate with Prometheus

1. In BMC Helix Intelligent Integrations, on the CONNECTORS tab, clickin the SOURCES panel.

2. Click the 

   Prometheus

    Metrics tile.

3. Specify the following details for the source connection:

   1. Specify a unique instance name.
      

      Important

      We recommend that you specify the instance name in the following format:

      <sourceType>_<sourceControllerServerName>{_<InstanceQualifier>}

      The instance qualifier helps you to distinguish the multiple instances configured from the same source server. For example, you can name your instances as Prometheus_Host_PROD, Prometheus_Host_TEST, and so on.

   2. Specify the Prometheus metrics host name.
   3. Specify the Prometheus HTTP or HTTPS port number depending on the connection protocol (default value is 9090).

   4. Select the HTTPS option to use an https connection to the Prometheus  metrics host.
      

      Warning

      We recommend that you do not select the Allow Unsigned Certificate option in a production environment.  You might want to select this option to allow unsigned certificates in a test environment. See the Prometheus documentation to learn how to install SSL certificates.

   5. Specify the number of maximum concurrent REST API requests that should be executed during a collection schedule (default value is 5).
   6. Specify the user name and password. Ensure that the specified user can access the Prometheus REST API.
   7. Click Proxy and specify whether you want to configure a proxy server.
      If yes, specify the host name and port number (default value is 8888).
4. Click VALIDATE AND CREATE.
   The specified connection details are validated and the corresponding source connection is created in the Source Connection list.

5. Select the source connection that you created from the list if it is not selected already.

   Important

   The destination host connection is created and configured automatically for each tenant when the source connection is created.

6. Click a data type and specify the configuration parameters in the Collectors section as described in the following table:
7. Click CREATE COLLECTORS to create the required collector streams for the selected data type.
8. Click a data type and specify the configuration parameters in the Distributors section as described in the following table:
   

1. Click CREATE DISTRIBUTORS to create the required distributor streams for the selected data type.
2. Click one of the following buttons:

1. • SAVE STREAM: Click this button if you want to edit the integration details before creating the instance. After you save the stream, the connector that you just created is listed in the SOURCES panel. Move the slider to the right to start the data stream.
   • SAVE AND START STREAM: Click this button if you want to save the integration details and start receiving data immediately.

          For more information about data streams, see Starting-or-stopping-data-streams.

To verify the integration

In BMC Helix Intelligent Integrations , on the SOURCES panel, confirm that the data streams for the integration you created are running. Data streaming is indicated by moving colored arrows.

A moving red arrow () indicates that metric data is being streamed. 

To view metrics in BMC Helix Operations Management

1. In BMC Helix Operations Management, select Monitoring > Devices.
2. Click the links for the required device.

3. On the Monitors tab, click the required monitor.
   The Performance Overview tab shows the metrics graph. For information about metrics, see Viewing collected data.