Thank you for your feedback.
Form temporarily unavailable. Please try again or contact docfeedback@servicenow.com to submit your comments.
Versions
  • Madrid
  • London
  • Kingston
  • Jakarta
  • Istanbul
  • Helsinki
  • Geneva
  • Store
Close

Configure event collection from NagiosXI

Log in to subscribe to topics and get notified when content changes.

Configure event collection from NagiosXI

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

Before you begin

Supported version: 5.4.11

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.

Role required: evt_mgmt_admin

Procedure

  1. Navigate to Event Management > Event Connectors (Pull) > Connector Instances.
  2. Click New.
  3. On the form, fill in the fields.
    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.

    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.
  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.
    1. initial_sync_in_days. Specify the number of days for which events must be collected at the first collection cycle. Default value 7 days.
    2. port. Default value 80.
    3. protocol. The default protocol type is http.
    4. time_zone. The default time zone is GMT.
  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.
Feedback