Integrating with Icinga


Icinga is designed to monitor the availability of network resources and proactively generate alerts about the outages and performances of hosts and services. As a tenant administrator, it's important that you can monitor the connected systems and quickly identify and resolve any issues. The BMC Helix Intelligent Integrations Icinga connector collects events and metrics fromIcinga.

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

Events

Use a centralized event view to monitor and manage events, perform event operations, and filter events. Identify actionable events from a large volume of event data by processing events.

For more information, see  Monitoring events and reducing event noise.

BMC Helix Operations Management

Metrics

Detect anomalies and eliminate false positives. Use alarm and variate policies to detect anomalies through static and dynamic thresholds.

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

BMC Helix AIOps

Situations
(created from events)

Improve the mean time to resolve (MTTR) based on the situation-driven workflow.

Lower the mean time to detect or discover (MTTD) and the time required for investigating tickets.

For more information, see Monitoring situations.


As a tenant administrator, perform the following steps to configure a connection with Icinga, verify the connection, and view the collected events and metrics data in various BMC Helix applications.

Connector steps.png

Supported versions

This connector supports Icingaversion 2.x for data collection.

Planning for the connection

Review the following prerequisites to help you plan and configure a connection with Icinga.

Icinga prerequisites

Ensure that the user account that you plan to use while configuring a connection with Icinga has the following permissions:

  • config/query 
  • events/* 
  • objects/query/*
  • status/query 
  • types
  • variables

BMC Helix Intelligent Integrations prerequisites

In the following list, third-party product refers to Icinga.

  • 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 5665).


Configuring the connection with Icinga

  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 one of the following URLs to access BMC Helix Intelligent Integrations:
      • http://<hostName>:<portNumber>/swpui
      • https://<hostName>:<portNumber>/swpui
  2. On the CONNECTORS  tab, click add_icon.pngin the SOURCES panel.
  3. Click the Icinga tile.
  4. Specify the source connection details:
    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 distinguish the multiple instances configured from the same source server. For example, you can name your instances ICINGA_PROD, ICINGA_TEST, and so on.

    2. Specify the Icinga host name and port number (default value is 5665).
  5. Click VALIDATE AND CREATE.
    The specified connection details are validated and the corresponding source connection is created in the Source Connection list.
  6. 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.

  7. Ensure that the options for the data types for which you want to collect data are selected.
  8. Click a data type and specify the configuration parameters in the Collectors section as described in the following table:

  9. Click CREATE COLLECTORS to create the required collector streams for the selected data types.
  10. Click a data type and specify the configuration parameters in the Distributors section as described in the following table:
  11. Click CREATE DISTRIBUTORS to create the required distributor streams for the selected data types.
  12. 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.

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


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.

Icinga_stream.png

  • A moving dark blue arrow (EventsStream_Icon.png ) indicates that the event stream is running. Event data will be pushed according to the configured Collection Schedule interval.
  • A moving red arrow (MetricsStream_Icon.png ) indicates that the metric stream is running. Metric data will be pushed according to the configured Collection Schedule interval.

Viewing data in BMC Helix applications

View data collected from Icinga in multiple BMC Helix applications.

Important

If the event or metric data is ingested by using BMC Helix Intelligent Integrations, and the topology data is ingested through some other means, all the use cases in BMC Helix AIOps might not work as expected because the external IDs generated by BMC Helix Intelligent Integrations and BMC Helix Discovery differ. In addition, host name might differ in both the products. 

To view events in BMC Helix Operations Management

  1. In BMC Helix Operations Management, select Monitoring > Events.
  2. Filter the events by IcingaEvent class.
    Icinga_events_BHOM.png

Incoming events from Icinga are processed in BMC Helix Operations Management through a set of rules to determine whether the incoming event contains the results of the same test on the same node and then processed accordingly. For more information, see Event-deduplication-suppression-and-closure-for-reducing-event-noise.

For information about events, see Monitoring and managing events.

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 Monitors tab shows the list of service names that are specified in Icinga for service monitoring. Additionally, you can also see Icinga's internal services to monitor host performance.
    The Performance Overview tab shows the metrics graph.
    Icinga_metrics.png

For information about metrics, see Viewing collected data .

Mapping of attributes between Icinga and BMC Helix Operations Management

The following table shows the mapping between Icinga and BMC Helix Operations Management:

Event attribute

Icinga

BMC Helix Operations Management

Timestamp

originTimestamp

creation_time

Event Id

Hash Code is generated using the title and timestamp.

_identifier

Title

<service> on <host>

message

Description

check_result.output

details

Severity

OK

OK

Warning

Warning

Critical

Critical

Not Connected

Unknown

Status

Open

Open

Not applicable

Closed

In BMC Helix Operations Management the status is updated from Open to Closed via event policy.


 

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