Contents IT Operations Management Previous Topic Next Topic Event collection via MID Server Subscribe Log in to subscribe to topics and get notified when content changes. ... SAVE AS PDF Selected Topic Topic & Subtopics All Topics in Contents 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 lets the MID Server run a script for event collection. 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). SolarWinds NPM is supplied by default with Istanbul. If you are experiencing issues with SolarWinds NPM but cannot upgrade to Istanbul, contact Support. Ask to upload and activate the update set attached to PRB690140. vRealize Provides connectivity to VMware vRealize Operations. 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. Configure event collection from NetcoolThe Netcool connector requires configuration prior to receiving events from IBM Netcool/OMNIbus Object Servers and Impact Servers. Configure alert collection from SCOMConfigure the SCOM connector instance prior to receiving alerts from the Microsoft System Center Operations Manager (SCOM). Configure event collection from SolarWindsThe SolarWinds connector instance requires configuration prior to receiving events from SolarWinds Service & Application Monitor. 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. 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 lets the MID Server run a script for event collection. 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). SolarWinds NPM is supplied by default with Istanbul. If you are experiencing issues with SolarWinds NPM but cannot upgrade to Istanbul, contact Support. Ask to upload and activate the update set attached to PRB690140. vRealize Provides connectivity to VMware vRealize Operations. 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. Configure event collection from NetcoolThe Netcool connector requires configuration prior to receiving events from IBM Netcool/OMNIbus Object Servers and Impact Servers. Configure alert collection from SCOMConfigure the SCOM connector instance prior to receiving alerts from the Microsoft System Center Operations Manager (SCOM). Configure event collection from SolarWindsThe SolarWinds connector instance requires configuration prior to receiving events from SolarWinds Service & Application Monitor. 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.
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 lets the MID Server run a script for event collection. 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). SolarWinds NPM is supplied by default with Istanbul. If you are experiencing issues with SolarWinds NPM but cannot upgrade to Istanbul, contact Support. Ask to upload and activate the update set attached to PRB690140. vRealize Provides connectivity to VMware vRealize Operations. 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. Configure event collection from NetcoolThe Netcool connector requires configuration prior to receiving events from IBM Netcool/OMNIbus Object Servers and Impact Servers. Configure alert collection from SCOMConfigure the SCOM connector instance prior to receiving alerts from the Microsoft System Center Operations Manager (SCOM). Configure event collection from SolarWindsThe SolarWinds connector instance requires configuration prior to receiving events from SolarWinds Service & Application Monitor. 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.
