Configure a pull connector
Configure a pull connector to schedule the frequency of event collection.
Before you begin
Before starting this procedure:
- Locate or define a connector definition.
- Create the credentials to connect to the event source.
- If the connector instance is to be used for the collection of Metric Intelligence metric data, the Metric Intelligence plugin must be activated.
Role required: evt_mgmt_admin
About this task
You can use a connector instance to control the location and manner in which events arrive from external sources. You can optionally select to collect Metric Intelligence information from the external sources that you are connecting to. The Metric Intelligence feature is for the analysis of trends, threshold definitions, and anomaly detection. You can run a test to confirm that connector instance parameters let the MID Server receive events from a supported external event source to the Event [em_event] table. The test also confirms:
- The MID Server is running.
- The host is running on the IP address that is in the Host IP field.
- Both the MID Server and the host are running in the same domain.
- The connector instance value fields are valid.
- A connection can be made to the event source, using API, to retrieve events.
Integrations Launchpad, available in the Service Operations Workspace, consolidates all Event Management connector integrations in one place. Use it to pull or push events from external or internal devices, create or manage connector configurations from a single interface.
Procedure
Navigate to All > Event Management > Integrations > Connector Instances.
Click New.
Fill in the fields, as appropriate.
| Field | Description |
|---|---|
| Name | A unique name for the connector instance record, such as the name of event source host. |
| Description | Any optional information that the administrator wants to use to identify this record. |
| Assignment Group | Designates which team is responsible for managing, maintaining, and responding to issues related to this connector instance. |
| Connector definition Note: Metric Intelligence connectors (such as the AWS CloudWatch and AzureConnector), appear in the base system only if the Metric Intelligence plugin (com.snc.sa.metric) is activated. | The vendor and protocol used to gather events from the external event source. Select the connector definition that matches the source of external events. The options available in the base system are, for example: - AWS CloudWatch - AzureConnector - HPOM - IBM Netcool - NagiosXI - NNMi - OMi - SCOM - SolarWinds - Op5 - PRTG - vCenter - Zabbix For a list of the connector definitions available in the base system, see Configure Event Management connectors. |
| Host IP | The IP address of the event source host. The system uses this IP address to select the appropriate MID Server for communicating with the event source host. |
| Credential | The record from the Credentials \[discovery\_credentials\] table containing valid credentials to the event source host. |
| Event collection last run time | The date and time of the most recent event import. The value of this field is automatically populated. |
| Last event collection status | The status of the last import. The value of this field is automatically populated. - None - A valid connection has not yet been established. - Success - A successful connection was established. - Error - A connection was established. However the external event source was not updated. |
| Event collection schedule \(seconds\) | The frequency in seconds that the system checks for new events from the external event source. This value cannot be lower than the minimum schedule property, which by default is 120 seconds. |
| Last error message | Last error message received by the connector. If the test connector fails, an error message appears in this field. |
| Active | This option appears only after the form has been saved. Do not select this check box until after you test the connection between the MID Server and the connector. Select this check box to enable pulling events from this external event source. |
| Bi-directional | Select to invoke the bi-directional option. This option is available only when the specified connector definition has been configured with bi-directional values. When selected, this option enables the bi-directional exchange of values to-and-from the external event source. The Last bi-directional status option appears only when this option is selected. This option appears only if the connector definition that is selected is SCOM. |
| Last bi-directional status | The value of this field is automatically populated. The status values are: - None - A valid connection has not yet been established. - Success - A successful connection was established. - Error - A connection was established. However the external event source was not updated. This option appears only if the connector definition that is selected is SCOM. |
| Metrics collection | Designates collection of Metric Intelligence metric data. Note: The metrics connector supports working against the SCOM database (MSSQL) that is configured to work with SSL. This option appears only if the connector definition supports metric collection, such as SCOM. |
| Metrics collection last run time | The date and time of the most recent metric data collection. The value of this field is automatically populated. |
| Last metrics collection status | Status of the metric data collection activity. The value of this field is automatically populated.This option appears only if the connector definition that is selected supports metric collection (such as SCOM) and if the Metrics collection option is selected. |
| Metrics collection schedule \(seconds\) | The time, in seconds, to repeat the metric data collection scheduled job.This option appears only if the connector definition that is selected supports metric collection (such as SCOM) and when the Metrics collection option is selected. |
| Metrics database host | Enter either the IP address or the host name of the metrics database host.This option appears only if the connector definition that is selected supports metric collection \(such as SCOM\). |
| Connect using a named instance | Select to specify the MSSQL named instance to connect to.This option appears only if the connector definition that is selected is SCOM. |
| Metrics database named instance | The name of the metrics database instance.This option appears only if the connector definition that is selected supports metric collection \(such as SCOM\). |
| Metrics database port | The port used by the metric database. The connection is made using JDBC. The base system value is 1,433.This option appears only if the connector definition that is selected supports metric collection \(such as SCOM\). |
| Database login with Windows authentication | Perform database login with the credentials of the log-on user that is defined on the MID Server service.This option appears only if the connector definition that is selected is SCOM. |
| Metrics collection running | When selected, indicates that the Metric Intelligence collection is running. This option appears only if the connector definition that is selected supports metric collection \(such as SCOM\). |
| Metrics database credential | Credentials for the metric database.This option appears only if the connector definition that is selected supports metric collection \(such as SCOM\). |
| Connector Instance Values | The related list containing connection parameters for the event source host. The list of parameters depends on the selected connector definition. |
| MID Servers for Connectors | The name of theMID Server to process events from the event server. |
Right-click the form header and select Save.
Click Test connector to verify that the MID Server can communicate with the external server host.
If the test fails, follow the instructions on the page to correct the problem and then run another test. The description of the reason for failure is shown in the MID Server log, according to the type of error, such as Events, Metrics, or Bi-Directional.
After a successful test, select the Active check box and then click Update.
Confirm that Event Management processes events using this connector instance by manually creating an event.
Configure a default MID Server for connectors
You can set a default MID Server for connectors to ensure that there is always a MID Server available to receive external events.- Configure the Dynatrace metrics connector instance
Configure the Dynatrace connector instance to receive Metric Intelligence raw data from the Dynatrace server. - Configure the Nagios metrics connector instance
Configure the Nagios metric connector instance to receive Metric Intelligence raw data from the Nagios server. - Configure the Zabbix metrics connector instance
Configure the Zabbix Metric connector instance to receive Metric Intelligence raw data from the Zabbix server. - Configure the SolarWinds metrics connector instance
Configure the SolarWinds connector instance to receive Metric Intelligence raw data from the SolarWinds server. - Configure event collection from HP OMi
Configure the HP Operations Manager (OMi) connector instance to receive alerts from the HP OMi server. - Configure event collection from HPOM
Configure the HPOM connector instance to receive events from HP Operations Manager (HPOM). - Configure event collection from Hyperic
Configure the Hyperic connector instance to receive events from the VMware vRealize Hyperic server. - Configure event collection from IBM Netcool
Configure the IBM Netcool_V2 connector to receive events from IBM Netcool/OMNIbus Object Servers and Impact Servers. The IBM Netcool_V2 connector uses REST API calls and is bidirectional. - Configure event collection from an Icinga2 connector
Configure the Icinga 2 (Icinga) connector instance to receive events while monitoring your network resources. - Configure event collection from Logicmonitor
The Logicmonitor pull connector sends information from Event Management to Logicmonitor. It sends responses received from a Push connector in a bi-directional environment to Logicmonitor. - Configure event collection from NNMi
Configure the HP Network Node Manager i (NNMi) connector instance to receive events while monitoring your network resources. - Configure event collection from NagiosXI
Configure the NagiosXI connector instance to receive events from the Nagios Core monitor. - Configure event collection from OBM
Configure the Operation Bridge Manager (OBM), also known as OMi v2, connector instance to receive alerts from the OBM server. The OBM connector script OBM v2 will be available after installing the Event Management Connectors app. - Configure OP5 or OP5_v2 connector
Configure the OP5 or OP5_v2 Monitor connector instance to receive alerts from an OP5 Monitor source. - Configure Opsview_v2 connector
Configure the Opsview_V2 connector instance to receive alerts from an Opsview Monitor source. - Configure PRTG connector
Configure the PRTG connector instance to receive alerts from a Paessler PRTG Network Monitor source. - Apache Kafka Consumer Connector
The Apache Kafka Consumer connector instance enables you to create events from messages collected from the Apache Kafka topic as a JSON payload that contains essential information in a data block. - Configure the Kafka metrics connector instance
Configure the Kafka metric consumer connector instance to read message send to Kafka server over topic. - Configure SAP Solution Manager connector
Configure the SAP Solution Manager (Solman) connector instance to enable communication between the SAP Solution Manager and Event Management. - Configure alert collection from SCOM
Alerts from the Microsoft System Center Operations Manager (SCOM) are collected using the SCOM connector instance. - Configure event collection from SolarWinds monitor
Configure the SolarWinds monitor connector instance to receive events from the SolarWinds monitor. - Configure event collection from vCenter
Configure the VMware vCenter Server (vCenter or vCenter_V2) connector instance to receive events from your VMware vSphere environment. - Configure event collection from vRealize
Configure the VMware vRealize Operations (vRealize or vRealize_V2) connector instance to receive events from the vRealize Operations Log and Event Management servers. vRealize uses basic authentication. vRealize_V2 uses token-based authentication. - Configure event collection from Zabbix server
Configure the Zabbix server connector instance to receiving alerts from the Zabbix server.
Parent Topic:Configure Event Management connectors
Related topics