---
sourceDocument: Zurich IT Operations Management
sourceDocumentLink: https://www.servicenow.com/docs/r/zurich/it-operations-management

 Release :

    - zurich

ft:locale :

    - en-US

ft:publication_title :

    - Zurich IT Operations Management

ft:clusterId :

    - itom

bundleId :

    - itom

workflow :

    - Technology


---

# Configure the Nagios metrics connector instance

# Configure the Nagios metrics connector instance {#ariaid-title1}

* Release version: Zurich
* 
* Updated August 11, 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Configure the Nagios metric connector instance to receive Metric Intelligence raw data from the Nagios server.

## Before you begin

To activate metric collection, ensure that the MID Server that retrieves metrics is configured with the Metric Intelligence extension and that the extension is in Started mode. See [Manually configure the Metric Intelligence extension](https://www.servicenow.com/docs/HAsJDjwq~LomU8Loa9TSOQ "Configure the MID Server Metric Intelligence extension to enable the MID Server to pull raw metrics from external systems, to detect anomalies and report anomalies to the instance along with raw data. This MID Server Metric Intelligence extension is required and must be running in order for your system to be able to collect Metric Intelligence data.").  
* Create basic authentication credentials on ServiceNow instance with Nagios SQL database username and password.
* ServiceNow does not support discovery for Nagios. Therefore, create the CI entry manually in the respective table using the hostname configured on the Nagios platform.
{#configure-nagios-metrics-connector__ul_kv5_r1z_zbc}

Role required: evt_mgmt_admin

## About this task

By default, CI binding will occur for the following entities:

* HOST HTTP Endpoint: The event rule applies to the Nagios metric HTTP if you are running a check that includes command_name as service_http.
* MySQL Instance: The event rule applies to the Nagios metric MySQL if you are running a check that includes command_name as mysql.
{#configure-nagios-metrics-connector__ul_ffk_fr3_dcc}

If you are running any other checks on HTTP endpoints or MySQL, you can edit the existing event rule to add the command_name. For other entities, configure event rules based on CI binding requirements.

## Procedure

1. Navigate to Event ManagementIntegrationsConnector Instances.
2. Select New and create a connector instance.  
   For details on the connector instance fields displayed on the page, see [Nagios connector instance form](https://www.servicenow.com/docs/fTBJBkjW4LuP7IHDh3aOPA "The Nagios connector instance form displays the fields you must fill in when creating a Nagios connector instance.").
3. Select and hold (or 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.
4. **Optional:** In the Connector Instance Values section, you can edit the values of the mandatory Nagios parameters.  
   For details on the connector instance value parameters, see [Nagios connector instance value parameters](https://www.servicenow.com/docs/F5Jl5R4d_phvKnbnTEiKzw "The following table displays the Nagios connector instance value parameters that you can fill in, as needed, when creating a Nagios connector instance.").
5. In the MID Servers for Connectors section, add a MID Server for the Nagios connector to use.
6. Ensure that the CIs related to the metrics exist in the instance.
7. Create an event rule to perform CI binding, as needed.  
   For details, see [Create or edit an event rule](https://www.servicenow.com/docs/qqixBhAL7aFh34Z6gednqg "You can create event rules to generate alerts for tracking and remediation. Use team-based integrations in event rules to make sure that connector ownership and execution of rules give precedence to general rules. Teams can maintain consistency and hierarchy while offering flexibility and customization options.").
8. Select Test Connector to verify the connection between the MID Server and the connector.
9. After a successful test, select the Active check box and then select Update.
{#configure-nagios-metrics-connector__steps_ik1_ffx_t2c}

*[\>]: and then