---
sourceDocument: Yokohama IT Operations Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Configure event collection from NagiosXI

# Configure event collection from NagiosXI {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read

Configure the NagiosXI connector instance to receive events
from the Nagios Core monitor.

## Before you begin

Supported version: 5.5.2.

The NagiosXI connector instance requires a credential that lets the instance access NagiosXI accounts. You can use an existing credential or create a new one. For more
information, see [Create Nagios XI server credentials](https://servicenow-prod.fluidtopics.net/8zXJ3XbWwX~_rE4gqV8Ucw "Create credentials to access Nagios XI server.").

Role required: evt_mgmt_admin

## Procedure

1. Navigate to AllEvent ManagementIntegrationsConnector Instances.
2. Click New.
3. On the form, fill in the fields.  
   {#configure-nagios-connector__table_usg_pq2_sbb__entry__2}

   | Field | Description |
   |-|-|
   | Name | Descriptive name for the Nagios connector. |
   | Description | Description for the use of the NagiosXI event collection instance. |
   | Host IP | Specify the Nagios XI IP address. |
   | Credential | Select the credential with basic authentication that you created for this connector. For more information, see [Create Nagios XI server credentials](https://servicenow-prod.fluidtopics.net/8zXJ3XbWwX~_rE4gqV8Ucw "Create credentials to access Nagios XI server."). Ensure that the user password contains the NagiosXI user API key, for example 04lquEPqf4JimWCm8RWbJokOpW8LYBUfEvJp9OSHSRYe4QDrHPFndYbWcCHapBpk. |
   | Event collection last run time | The last run time value is automatically updated. |
   | Last event collection status | The last run time status is automatically updated. |
   | Event collection schedule (seconds) | The frequency, in seconds, that the system checks for new events from Nagios. The default value is 120 seconds. |
   | Last error message | The last error message is automatically updated. |
   | Connector Definition | Select NagiosXI. |
   | MID Servers (MID Server for Connectors section) | Optional. Name of a MID Server. If no MID Server is specified, an available MID Server that has a matching IP range is used. In the MID Servers for Connectors section, specify a MID Server that is up and valid. You can configure several MID Servers. If the first is down, the next MID Server is used. If that MID Server is not available, the next is selected, and so on. MID Servers are sorted according to the order that their details were entered into the MID Server for Connectors section. |
   [ ]

   {#configure-nagios-connector__table_usg_pq2_sbb}
4. Right-click the form header and select Save.  
   The connector instance values are added to the form and the parameters that are relevant to the connector appear.
5. In the Connector Instance Values section, specify the Nagios values.  
   * initial_sync_in_days. Specify the number of days for which events must be collected at the first collection cycle. Default value <kbd class="ph userinput">7</kbd> days.
   * port. Default value <kbd class="ph userinput">80</kbd>.
   * protocol. The default protocol type is <kbd class="ph userinput">http</kbd>.
   * time_zone. The default time zone is <kbd class="ph userinput">GMT</kbd>; update this value to the Nagios timezone. For example, if Nagios is sending the events according to the EDT time zone, update this value to <kbd class="ph userinput">GMT-04:00</kbd> (abbreviations such as EDT are not supported).
   * severity_by_state_type. The default value is <kbd class="ph userinput">false</kbd>. When set to <kbd class="ph userinput">true</kbd>, the state_type is used along with the state to determine the severity which creates less critical events as shown in the following mapping table.

   {#configure-nagios-connector__ul_pc5_c2r_lvb} {#configure-nagios-connector__table_usn_5cz_lvb__entry__4}

   | _state_type(Connector definition parameter) | State (Nagios JSON payload attribute) | State_type (Nagios JSON payload attribute) | ServiceNow Severity |
   |-|-|-|-|
   | false | 2 | 0/1 | 1 (Critical) |
   | false | 1 | 1 | 1(Critical) |
   | false | 1 | 0 | 2(Major) |
   | false | 0 | 0/1 | 5(OK) |
   | true | 0 | 0/1 | 5(OK) |
   | true | 1 | 0 | 4 (Warning-soft -\> Warning) |
   | true | 2 | 0 | 2(Critical-soft -\> Major) |
   | true | 3 | 0 | 4(Unknown-soft-\> Warning) |
   | true | 1 | 1 | 3(Warning-hard -\> Minor) |
   | true | 2 | 1 | 1(Critical-hard -\> Critical) |
   | true | 3 | 1 | 3(Unknown-hard -\> Minor) |
   [Table 1. Mapping Table]

   {#configure-nagios-connector__table_usn_5cz_lvb}
6. Right-click the form header and select Save.
7. Click Test Connector to verify the connection between the MID Server and the connector.
8. If the test fails, follow the instructions that the error issues to correct the problem and then run another test.  
   If this message appears: Connection test failed: Failed to connect to Nagios on test connector. Invalid API Key, then enter the API Key for the specific user to be able to read the Nagios events.  
   Note:  
   Use a network tool, such as ping, to verify credential correctness and network connectivity from the MID Server to the Nagios Core monitor.
9. After a successful test, select the Active check box and then click Update.
{#configure-nagios-connector__steps_sz4_wz1_kz}
* **[Create Nagios XI server credentials](https://servicenow-prod.fluidtopics.net/8zXJ3XbWwX~_rE4gqV8Ucw)**   
  Create credentials to access Nagios XI server.

*[\>]: and then