Integrating with Naemon



Naemon is the monitoring suite that gives a clear view of the state of your network and applications.

You can view the collected data in various BMC Helix applications and derive the following benefits:

BMC Helix application

Type of data collected or viewed

Benefits

BMC Helix Operations Management

Metrics

Use alarm and variate policies to detect anomalies and eliminate false positives for more accurate results while monitoring the health of your system.

For more information, see Detecting anomalies by using static and dynamic thresholds.

BMC Helix Dashboards

 Metrics

Create dashboards to get a consolidated view of data collected from third-party products across your environment. 

Improve the efficiency of your system by monitoring the key performance metrics and respond to issues quickly to minimize the down time.

For more information, see Creating custom dashboards.

As a tenant administrator, perform the following steps to configure a connection with Naemon, verify the connection, and view the collected data in BMC Helix Operations Management.

Connector steps.png

Planning for the connection

  • Depending on the location (SaaS, on-premises) of the third-party product, choose one or more BMC Helix Intelligent Integrations deployment modes and review the corresponding port requirements. For information about various deployment modes and port requirements, see Deployment-scenarios.
  • Based on the deployment modes, use the BMC Helix Intelligent Integrations SaaS deployment or the BMC Helix Intelligent Integrations on-premises gateway or both. For more information about the gateway, see Deploying-the-BMC-Helix-Intelligent-Integrations-on-premises-gateway.
  • The on-premises gateway must be able to reach the third-party product on the required port (default is 443).

In the preceding list, third-party product refers to Naemon

Configuring the connection with Naemon

  1. Access BMC Helix Intelligent Integrations:
    • BMC Helix Intelligent Integrations SaaS – Log on to BMC Helix Portal, and click Launch on BMC Helix Intelligent Integrations.
    • BMC Helix Intelligent Integrationson-premises gateway – Use the following URL to access BMC Helix Intelligent Integrations:
      https://<hostName>:<portNumber>/swpui
  2. On the CONNECTORS tab, clickadd_icon.pngin the SOURCES panel.
  3. Click the Naemon tile.
  4. Specify the following details for the source connection:
    1. Specify a unique instance name.

      Best practice
      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 Naemon_Host_PROD, Naemon_Host_TEST, and so on.


    2. Specify the Naemon metrics host name.
    3. Specify the Naemon port number (default value is 80).
    4. Select the Allow Unsigned Certificates option to allow HTTPS to use the self-signed certificate. Select this option only for the test environment.
    5. Select the HTTPS option if an SSL or TLS certificate is installed in the Naemonhost.

    1. Specify the number of maximum concurrent REST API requests that should be executed during a collection schedule (default value is 20).
    2. Specify the user name and password. Ensure that the specified user can access the Naemon REST API.
    3. 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).

      Important

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

  1. Click VALIDATE AND CREATE.
    The specified connection details are validated and the corresponding source connection is created in the Source Connection list.
  2. Select the source connection that you created from the list if it is not selected already.
  3. Click a data type and specify the configuration parameters in the Collectors section as described in the following table:

    The [confluence_table-plus] macro is a standalone macro and it cannot be used inline. Click on this message for details.

  4. Click CREATE COLLECTORS to create the required collector streams for selected data types.
  5. Configure the distributors for the metrics data type by clicking the data type in the Distributors section and specifying the parameters for the metrics type, as explained in the following table:

    The [confluence_table-plus] macro is a standalone macro and it cannot be used inline. Click on this message for details.

  6. Click CREATE DISTRIBUTORS to create the required distributor streams for the selected data types.
  7. Click one of the following buttons:
    • 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.


Verifying the connection

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.

Naemon_Connector.png

A moving red arrow (MetricsStream_Icon.pngindicates that the metric stream is running. Metric data will be pushed according to the configured Collection Schedule interval.

Viewing data in BMC Helix applications

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. 
    Metrics_Naemon.png

For information about metrics, see Viewing collected data

 

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