Contents IT Operations Management Previous Topic Next Topic Event collection via MID Server ... SAVE AS PDF Selected Topic Topic & Subtopics All Topics in Contents Other Share Event collection via MID Server Configure connector instances to use script instructions that enable the MID Server to connect to external servers to obtain event information. Connector definitions are script instructions that enable the MID Server to connect to external servers to obtain event information. Use one connector instance for each type of event server that sends events via a MID Server. You can configure connector instances to use the default connector definitions for supported event sources. Alternatively, you can create a custom definition that enables the MID Server to run a script for event collection. Events are collected from external servers using a pull operation. The schedule for the pull interval is set in the Schedule field of the connector instance. Users of the external servers must have read permission. However, if the connector instance is also configured to be bi-directional, the external server users must also have write permission. After configuring the connector instance, use the Test connector to verify the connection with the external source. Thereafter, set the connector instance to Active and events start to be received from the external server according to the pull interval schedule. Table 1. Default connector definitions Connector definition Description HPOM Provides connectivity to HP Operations Manager. Hyperic Provides connectivity to VMware vRealize Hyperic servers. IBM Netcool Provides connectivity to an IBM Netcool/OMNIbus ObjectServers and Impact Servers. SCOM Provides connectivity to Microsoft System Center Operations Manager (SCOM). SolarWinds Provides connectivity to: SolarWinds Service & Application Monitor (SAM) Network Performance Monitor (NPM) vRealize Provides connectivity to VMware vRealize Operations. Zabbix Provides connectivity to Zabbix servers. Connector instancesConnector instances use script instructions that enable the MID Server to connect to external servers to obtain event information. Each connector instance is specific to an event source vendor.Configure a default MID Server for connectorsYou can set a default MID Server for connectors to ensure that there is always a MID Server available to receive external events. Configure event collection from HPOMThe HPOM connector instance requires configuration prior to receiving events from the HP Operations Manager (HPOM).Configure event collection from VMware vRealize HypericThe Hyperic connector instance requires configuration prior to receiving events from the VMware vRealize Hyperic (Hyperic) server. Alert collection from SCOMAlerts from the Microsoft System Center Operations Manager (SCOM) are collected using the SCOM connector instance. Configure event collection from NetcoolThe Netcool connector requires configuration prior to receiving events from IBM Netcool/OMNIbus Object Servers and Impact Servers. Configure event collection from SolarWindsThe SolarWinds connector instance requires configuration prior to receiving events from the SolarWinds server. Configure event collection from VMware vRealize OperationsConfigure the VMware vRealize Operations (vRealize) connector instance to receive events from the vRealize Operations Log and Event Management servers. Configure event collection from ZabbixThe Zabbix connector instance requires configuration prior to receiving alerts from the Zabbix server. On this page Send Feedback Previous Topic Next Topic
Event collection via MID Server Configure connector instances to use script instructions that enable the MID Server to connect to external servers to obtain event information. Connector definitions are script instructions that enable the MID Server to connect to external servers to obtain event information. Use one connector instance for each type of event server that sends events via a MID Server. You can configure connector instances to use the default connector definitions for supported event sources. Alternatively, you can create a custom definition that enables the MID Server to run a script for event collection. Events are collected from external servers using a pull operation. The schedule for the pull interval is set in the Schedule field of the connector instance. Users of the external servers must have read permission. However, if the connector instance is also configured to be bi-directional, the external server users must also have write permission. After configuring the connector instance, use the Test connector to verify the connection with the external source. Thereafter, set the connector instance to Active and events start to be received from the external server according to the pull interval schedule. Table 1. Default connector definitions Connector definition Description HPOM Provides connectivity to HP Operations Manager. Hyperic Provides connectivity to VMware vRealize Hyperic servers. IBM Netcool Provides connectivity to an IBM Netcool/OMNIbus ObjectServers and Impact Servers. SCOM Provides connectivity to Microsoft System Center Operations Manager (SCOM). SolarWinds Provides connectivity to: SolarWinds Service & Application Monitor (SAM) Network Performance Monitor (NPM) vRealize Provides connectivity to VMware vRealize Operations. Zabbix Provides connectivity to Zabbix servers. Connector instancesConnector instances use script instructions that enable the MID Server to connect to external servers to obtain event information. Each connector instance is specific to an event source vendor.Configure a default MID Server for connectorsYou can set a default MID Server for connectors to ensure that there is always a MID Server available to receive external events. Configure event collection from HPOMThe HPOM connector instance requires configuration prior to receiving events from the HP Operations Manager (HPOM).Configure event collection from VMware vRealize HypericThe Hyperic connector instance requires configuration prior to receiving events from the VMware vRealize Hyperic (Hyperic) server. Alert collection from SCOMAlerts from the Microsoft System Center Operations Manager (SCOM) are collected using the SCOM connector instance. Configure event collection from NetcoolThe Netcool connector requires configuration prior to receiving events from IBM Netcool/OMNIbus Object Servers and Impact Servers. Configure event collection from SolarWindsThe SolarWinds connector instance requires configuration prior to receiving events from the SolarWinds server. Configure event collection from VMware vRealize OperationsConfigure the VMware vRealize Operations (vRealize) connector instance to receive events from the vRealize Operations Log and Event Management servers. Configure event collection from ZabbixThe Zabbix connector instance requires configuration prior to receiving alerts from the Zabbix server.
Event collection via MID Server Configure connector instances to use script instructions that enable the MID Server to connect to external servers to obtain event information. Connector definitions are script instructions that enable the MID Server to connect to external servers to obtain event information. Use one connector instance for each type of event server that sends events via a MID Server. You can configure connector instances to use the default connector definitions for supported event sources. Alternatively, you can create a custom definition that enables the MID Server to run a script for event collection. Events are collected from external servers using a pull operation. The schedule for the pull interval is set in the Schedule field of the connector instance. Users of the external servers must have read permission. However, if the connector instance is also configured to be bi-directional, the external server users must also have write permission. After configuring the connector instance, use the Test connector to verify the connection with the external source. Thereafter, set the connector instance to Active and events start to be received from the external server according to the pull interval schedule. Table 1. Default connector definitions Connector definition Description HPOM Provides connectivity to HP Operations Manager. Hyperic Provides connectivity to VMware vRealize Hyperic servers. IBM Netcool Provides connectivity to an IBM Netcool/OMNIbus ObjectServers and Impact Servers. SCOM Provides connectivity to Microsoft System Center Operations Manager (SCOM). SolarWinds Provides connectivity to: SolarWinds Service & Application Monitor (SAM) Network Performance Monitor (NPM) vRealize Provides connectivity to VMware vRealize Operations. Zabbix Provides connectivity to Zabbix servers. Connector instancesConnector instances use script instructions that enable the MID Server to connect to external servers to obtain event information. Each connector instance is specific to an event source vendor.Configure a default MID Server for connectorsYou can set a default MID Server for connectors to ensure that there is always a MID Server available to receive external events. Configure event collection from HPOMThe HPOM connector instance requires configuration prior to receiving events from the HP Operations Manager (HPOM).Configure event collection from VMware vRealize HypericThe Hyperic connector instance requires configuration prior to receiving events from the VMware vRealize Hyperic (Hyperic) server. Alert collection from SCOMAlerts from the Microsoft System Center Operations Manager (SCOM) are collected using the SCOM connector instance. Configure event collection from NetcoolThe Netcool connector requires configuration prior to receiving events from IBM Netcool/OMNIbus Object Servers and Impact Servers. Configure event collection from SolarWindsThe SolarWinds connector instance requires configuration prior to receiving events from the SolarWinds server. Configure event collection from VMware vRealize OperationsConfigure the VMware vRealize Operations (vRealize) connector instance to receive events from the vRealize Operations Log and Event Management servers. Configure event collection from ZabbixThe Zabbix connector instance requires configuration prior to receiving alerts from the Zabbix server.
