Integrating with Nagios Core

Use the BMC Helix Intelligent Integrations Nagios Core connector to collect events and metrics data from Nagios Core , and view the collected data in the following BMC Helix applications and derive actionable insights:

BMC Helix Operations Management(Events and metrics)
BMC Helix Operations Management displays alerts as events.
BMC Helix AIOps(Situations)

Related topics

Editing-and-deleting-integrations

Monitoring-the-on-premises-gateway-node-for-streaming-interruptions-and-node-health

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 ( Nagios Core alerts are received as 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	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 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 Nagios Core, verify the connection, and view the collected data in various BMC Helix applications.

- The [confluence_layout-cell] macro is a standalone macro and it cannot be used inline. Click on this message for details.
  This macro generates standalone content. As a consequence you need to make sure to use a syntax that separates your macro from the content before and after it so that it's on a line by itself. For example in XWiki Syntax 2.0+ this means having 2 newline characters (a.k.a line breaks) separating your macro from the content before and after it.
On the CONNECTORS tab, click in the SOURCES panel.
Click the Nagios Core tile.
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 Nagios_Host_PROD, Nagios_Host_TEST, and so on.
  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 Nagios_Host_PROD, Nagios_Host_TEST, and so on.
2. Specify the Nagios Core host name.
3. Specify the HTTP or HTTPS port number depending on the connection protocol. The default port number is 443.
4. Select the HTTPS option to use an https connection to the Nagios Core host.
5. Specify the number of maximum concurrent REST API requests that should be executed during a collection schedule (default value is 5).
6. Enter the username and password for the Nagios Core host.
  Important
  Ignore the Timezone field. It does not take effect.
7. Click Proxy and specify if you want to configure a proxy server. If yes, specify the host name and port number (default value is 8888)
Click VALIDATE AND CREATE.
The specified connection details are validated and the corresponding source connection is created in the Source Connection list.
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.
Ensure that the options for the datatypes for which you want to collect data are selected.
Configure the collectors for the selected data types by clicking the respective data type in the Collectors section. Specify the parameters for the selected data type, as explained in the following table:

Note: The ✅️ symbol indicates that this field is applicable to the data type and ❌️ indicates that this field is not applicable to the data type.
1. Click CREATE COLLECTORS to create the required collector streams for the selected data types.
2. Configure the distributors for the selected data types by clicking the respective data type in the Distributors section. Specify the parameters for the selected data type, as explained in the following table:
3. Click CREATE DISTRIBUTORS to create the required distributor streams for the selected data types.
4. 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.
  ImportantFor a data stream, the Run Latency (max/avg), Items (Avg per Run), and Last Run Status columns on the Streams page might show the status as No Runs during the data collection process. After completion of the process, these columns are updated with an appropriate status.
  ImportantFor a data stream, the Run Latency (max/avg), Items (Avg per Run), and Last Run Status columns on the Streams page might show the status as No Runs during the data collection process. After completion of the process, these columns are updated with an appropriate status.
  For more information about the data streams, see Starting-or-stopping-data-streams.

Task 3: To verify the connection

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

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

To view data in BMC Helix applications

View data in Nagios Core in multiple BMC Helix applications.

To view events in BMC Helix Operations Management

In BMC Helix Operations Management, select Monitoring > Events.
Filter the events by the NagiosCoreAlert class.

Incoming events from Nagios Core are processed in BMC Helix Operations Management through a set of deduplication rules to determine whether the incoming event is a duplicate event or a new event. 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

In BMC Helix Operations Management, select Monitoring > Devices.
Click the links for the required device.
On the Monitors tab, click the required monitor.
The Performance Overview tab shows the metrics graph.

Important
As the Nagios Core connector collects only the current data, i f you pause data streaming, you will see discontinuation in the metrics graph in BMC Helix Operations Management.

For information about metrics, see Viewing collected data.

To view situations in BMC Helix AIOps

Before you view situations in BMC Helix AIOps , c reate a Business Service model in BMC Helix Discovery . For information about creating models, see Managing models

In BMC Helix AIOps, go to the Overview page.
View the Situations for the events received from Nagios Core .

For information about situations, see Monitoring situations.