Configure OP5 connector Configure the OP5 Monitor connector instance to receive alerts from an OP5 Monitor source. Before you begin Role required: evt_mgmt_adminConnector validation performed on version 7.3.15 Procedure Navigate to Event Management > Event Connectors (Pull) > Connector Instances. Click New and create a connector instance with the following details: Field Value Name Descriptive name for the Op5 connector. Description Description for the use of the Op5 event collection instance. Host IP Specify the Op5 IP address. Credential Either select the required credentials from the list or click New and create the required credentials. If you create the credentials, save them using a unique and recognizable name, for example, Op5OPS. 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 Op5. Last error message The last error message is automatically updated. Connector definition Select Op5. Connector Instance Values section The parameters that are specific to Op5 display here when the form is saved. MID Servers (MID Server for Connectors section) Specify the MID Server to run the Op5 connector instance. 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. If no MID Server is specified, an available MID Server that has a matching IP range is used. Right-click the form header and select Save. The parameters that are relevant to the Op5 connector appear. In the Connector Instance Values section, specify the Op5 values. days_from. Specify the number of days for which events must be collected at the first collection cycle. Default value 7 days. debug. Default value false. port. Default value 443. state_types. Specify filters for event collection based on the state_types attribute. You can filter events based on state type. Specify the type, for example, soft or hard. Right-click the form header and select Save. Click Test Connector to verify the connection between the MID Server and the connector. 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 Op5 on test connector. Invalid API Key, then enter the API Key for the specific user to be able to read the Op5 events. Tip: Use a network tool, such as ping, to verify that the Op5 server is running and the IP address matches the value in the Host IP field. After a successful test, select the Active check box and then click Update.