{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":30292,"path":"it-operations-management/event-management/catchpoint-event-collection.md","title":"Integrate Catchpoint events","bundle":null,"doc_type":null,"release":"australia","body":"\n# Integrate Catchpoint events\n\nIntegrate Catchpoint with Event Management by adding an alert webhook in the Catchpoint platform.\n\n## Before you begin\n\nEnsure that the Event Management Connectors \\(sn\\_em\\_connector\\) plugin is installed on the ServiceNow AI Platform instance.\n\nRole required: evt\\_mgmt\\_admin\n\n## About this task\n\nConfigure the Event Management environment for the collection of events from Catchpoint by authenticating Catchpoint as a data source. In the Catchpoint platform, set your ServiceNow AI Platform as the rest endpoint using a webhook.\n\n## Procedure\n\n1.  In the Catchpoint platform, create an alert webhook destination.\n\n    1.  Login to the Catchpoint platform.\n\n    2.  Navigate to **Catchpoint** &gt; **Setting** &gt; **API** &gt; **Alert Data Webhook** to set the webhook endpoint.\n\n    3.  In the API Alert Webhook, provide the following details.\n\n<table id=\"table_fs2_xss_2tb\"><thead><tr><th>\n\nField\n\n</th><th>\n\nValue\n\n</th></tr></thead><tbody><tr><td>\n\nName\n\n</td><td>\n\nAny name based on your requirement.\n\n</td></tr><tr><td>\n\nURL\n\n</td><td>\n\nThe default format of the URL to push events from Catch Point to the ServiceNow AI Platform instance, `https://<username>:<password>@<instance-name>.service-now.com/api/sn_em_connector/em/inbound_event?source=catchpoint`.\n\n</td></tr><tr><td>\n\nOn Failure Alert\n\n</td><td>\n\nThe email address for the API Alert webhook.\n\n</td></tr><tr><td>\n\nNotification Trigger\n\n</td><td>\n\nSelect based on your requirement. The default value is 3.\n\n</td></tr><tr><td>\n\nAdd the following headers\n\n</td><td>\n\n-   Authorization: **Basic \\{Base 64 \\| username:password\\}**\n-   Content-Type: **application/json**\n\n\n</td></tr><tr><td>\n\nFormat\n\n</td><td>\n\nSelect **Template** and add the following template:```\n{\n\"Source\": \"CatchPoint\",\n\"severity\": \"${notificationLevelId}\",\n\"alertType\": \"${AlertType}\",\n\"time_of_event\": \"${alertCreateDateUtc(YYYY-MM-DD HH:MI:SS)}\",\n\"monitorType\": \"${Switch(${MonitorTypeId},'0', 'IE','2', 'Object','3','Emulated','8', 'Ping','9', 'Tracert','10', 'DNS-Traversal','11', 'Ping-TCP','12', 'DNS-Exp', '13','DNS-Direct', '14','Tracert-UDP', '15', 'Port-TCP','16', 'FTP','17', 'Data-Push-API','18', 'Chrome','19', 'Playback', '20', 'Playback-Mobile', '21', 'SMTP', '22', 'Port-UDP', '23', 'Ping-UDP', '24', 'Streaming', '25', 'API', '26', 'Mobile',\n '27', 'SFTP', '28', 'SSH', '29', 'Tracert-TCP')}\",\n\"testName\": \"${TestName}\",\n\"testId\": \"${TestId}\",\n\"testUrl\": \"${TestUrl}\",\n\"testPath\": \"${testPath}\",\n\"testLink\": \"${testLink}\",\n\"productName\": \"${ProductName}\",\n\"clientId\": \"${ClientId}\",\n\"productId\": \"${productId}\",\n\"nodeName\":\"${nodeDetails(\"${nodeName}\")}\",\n\"nodeClientServerAddress\":\"${nodeDetails(\\\"${NodeClientAddress},\\\"),}\",\n\"nodeServerAddress\":  \"${nodeDetails(\\\"${nodeServerAddress},\\\"),}\",\n\"Labels\" : \"${testLabels}\",\n\"addtionalInformation\": \"Test initial URL: ${testUrl}\\n\\nAlert type: ${AlertType}\\n\\nScatter Chart: ${scatterplotChartURL}\\n\\nWaterfall Chart: ${waterfallChartURL}\\n\\nTest properties: ${testLink}\\n\\nTest time of run / Test time of alert (Central Time): ${reportDateLocal(YYYY-MM-DD HH:MI:SS)} / ${alertCreateDateLocal(YYYY-MM-DD HH:MI:SS)}\"}\n\n```\n\n</td></tr></tbody>\n</table>2.  For the HTTP Endpoint monitoring tests, in the ServiceNow instance, create a CI.\n\n    **Note:** The Catchpoint connector supports multiple types of monitoring tests such as Endpoint, Networking, and others. The following steps apply only to the HTTP Endpoint monitoring tests.\n\n    1.  Navigate to **Configuration** &gt; **CI Class Manager**.\n\n    2.  Click **Hierarchy** and search for **HTTP\\(S\\) Endpoint**.\n\n    3.  In the CI Type field, select **cmdb\\_ci\\_endpoint\\_http**.\n\n    If the services are not modeled, then you should manually add the CIs under the \\[cmdb\\_ci\\_endpoint\\_http\\] table. Also, the manual endpoint should be removed before the automatic discovery of services. For other type tests CI bindings, you can create Event rules based on their requirements.\n\n\n## Result\n\nAlerts start flowing from the Catchpoint connector into the Event Management plugin. The following table shows how the Catchpoint severity mapping translates into the ServiceNow mapping.\n\n|Catchpoint severity|ServiceNow severity|\n|-------------------|-------------------|\n|0|Warning|\n|1|Critical|\n|2/3|Clear|\n\n**Parent Topic:**[Integrate with push connectors](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/event-management/configure-listener-transform-script.md)\n\n"}}