{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":30332,"path":"it-operations-management/event-management/configure-obm-connector.md","title":"Configure event collection from OBM","bundle":null,"doc_type":null,"release":"australia","body":"\n# Configure event collection from OBM\n\nConfigure 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.\n\n## Before you begin\n\nRole required: evt\\_mgmt\\_admin\n\nSupported versions: 10.01, 10.10, 10.11, 10.12, 10.60, 10.61, and 11.01.\n\n## About this task\n\nStarting from the Xanadu release, the OOTB \\(Out-Of-The-Box\\) event rules provided with the connector, which you have not previously used \\(i.e., neither activated, deactivated, nor modified\\), will now have the **Apply additional matching rules** check box set to true. Previously, this check box was disabled. This change allows you to execute more event rules or automation using the same filter conditions for the events.\n\n**Note:** This feature applies only to active event rules.\n\n## Procedure\n\n1. Navigate to **All** > **Event Management** > **Event Connectors \\(Pull\\)** > **Connector Instances**.\n\n2. Click **New** and create a connector instance with the following details:\n\n\n
\n\nField\n\n\n\nValue\n\n
\n\nName\n\n\n\nDescriptive name for the OBM connector.\n\n
\n\nDescription\n\n\n\nDescription for the use of the OBM event collection instance.\n\n
\n\nHost IP\n\n\n\nSpecify the OBM IP address.\n\n
\n\nCredential\n\n\n\nSelect 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 OBMOPS.\n\n
\n\nEvent collection last run time\n\n\n\nThe last run time value is automatically updated.\n\n
\n\nLast event collection status\n\n\n\nThe last run time value is automatically updated.\n\n
\n\nEvent collection schedule \\(seconds\\)\n\n\n\nFrequency in seconds that the system checks for new events from OBM. The default value is 120 seconds.\n\n
\n\nLast error message\n\n\n\nThe last error message is automatically updated\n\n
\n\nConnector Definition\n\n\n\nSelect **OBM V2**.**Note:** This script will be available after installing the Event Management connector scoped app.\n\n
\n\nMID Servers \\(MID Server for Connectors section\\)\n\n\n\nSpecify the MID Server to run the OBM connector instance. You can configure several MID Servers. If the first server is down, the next MID Server 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.\n\n
3. Right-click the form header and select **Save**.\n\n The parameters that are relevant to the OBM connector appear.\n\n4. In the Connector Instance Values section, specify the OBM values.\n\n 1. **days\\_from**.\n\n Specify the number of days for which events must be collected on the first collection cycle. The default value is `7` days and data can only be pulled a maximum of 7 days from the OBM system.\n\n 2. **debug**.\n\n The default value is `false`. To enter debug mode, change the value to `true`.\n\n 3. **port**.\n\n The default value is `80`.\n\n 4. **protocol**.\n\n The default value is `http`.\n\n 5. **query\\_filter**.\n\n The default value is false. If you do want to use this extra filter to query events, specify the event attributes. For example, `assigned_user = \"admin\" AND title = \"My Title\"`. The query filter criteria are:\n\n - A filter property that specifies an event attribute, such as, `related_ci`\n - A supported operator, for example, `OR` or `AND`\n - A value for the filter property, for example, `admin` or `integrator`\n Everything from the query\\_filter field undergoes URL encoding and is then passed as a parameter to the OBM API call. For detailed information on how to build the filter query, see “Filtering by Event Attributes: query” in the OBM Extensibility Guide. For example, to query the events for a list of events that are assigned to the admin user, specify:\n\n `event_list?query=assigned_ user%20EQ%20\"admin\"`\n\n To nest query\\_filter event attributes, specify the hierarchy using square brackets \"\\[ \\]\".\n\n 6. **inclusion list**.\n\n The default value is `false`. Specify a comma-separated list to include this feature to add attributes that should be collected and added to the Event Management **Additional information** field.\n\n5. Right-click the form header and select **Save**.\n\n6. Click **Test Connector** to verify the connection between the MID Server and the connector.\n\n7. If the test fails, follow the instructions that the error issues to correct the problem and then run another test.\n\n **Note:** Use a network tool, such as ping, to verify that the OBM server is running and the IP address matches the value in the **Host IP** field.\n\n8. After a successful test, select the **Active** check box and then click **Update**.\n\n\n**Parent Topic:**[Configure a pull connector](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/event-management/t_EMConfigureConnectorInstance.md)\n\n"}}