{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":30473,"path":"it-operations-management/event-management/lightstep-event-collection.md","title":"Integrate ServiceNow Cloud Observability Events","bundle":null,"doc_type":null,"release":"australia","body":"\n# Integrate ServiceNow Cloud Observability Events\n\nIntegrate ServiceNow Cloud Observability with Event Management by adding a standard webhook in the ServiceNow Cloud Observability platform. Download the Event Management Connector plugin from the ServiceNow Store so you can integrate with ServiceNow Cloud Observability.\n\n## Before you begin\n\n-   Role required: evt\\_mgmt\\_integration\n\n## About this task\n\nAuthenticate ServiceNow Cloud Observability as a data source to enable Event Management to collect events from ServiceNow Cloud Observability. In your ServiceNow Cloud Observability platform, use a standard webhook to set your ServiceNow AI Platform instance as the rest endpoint.\n\n**Note:** Ensure the evt\\_mgmt\\_integration role is assigned to the selected user. To ensure proper authentication, use the least privileged user with the evt\\_mgmt\\_integration role, rather than a high privileged user.\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.  Create a CI.\n\n    **Note:** Discovery for ServiceNow Cloud Observability services isn’t supported. Create a CI manually in a Service Instance \\(cmdb\\_ci\\_service\\_auto\\) table to enable binding.\n\n    1.  Navigate to **All** &gt; **Configuration** &gt; **Application Service**.\n\n    2.  Select **New**.\n\n    3.  In the form, enter the name.\n\n        The name must be the service name provided in the ServiceNow Cloud Observability platform.\n\n    4.  From the Operational Status list, set the operational status to **Operational**.\n\n    5.  Select **Next**.\n\n    6.  Select **Done**.\n\n2.  In your ServiceNow Cloud Observability platform, create a notification destination.\n\n    1.  From the navigation bar, select **Alerts**.\n\n    2.  Select the **Notification destinations** tab.\n\n    3.  Select **Create a destination**.\n\n    4.  Select **ServiceNow** or **webhook**.\n\n        Use the ServiceNow destination to connect only with the ServiceNow platform. If you have any issues with the ServiceNow destination, then use the **webhook** destination option.\n\n        \\[Omitted image \"choose-webhook.png\"\\] Alt text: Choose ServiceNow\n\n3.  In your ServiceNow Cloud Observability platform, create a ServiceNow notification destination.\n\n    1.  In the **Name** field, enter a name for the ServiceNow destination.\n\n    2.  In the **URL** field, provide the ServiceNow instance URL.\n\n        This is the default format of the URL to push events from ServiceNow Cloud Observability to the ServiceNow AI Platform instance. Use this format: `https//<instance-name>.servicenow.com/api/sn_em_connector/em/inbound_event?source=lightstep`\n\n    3.  In the **Username** field, enter your ServiceNow user name.\n\n    4.  In the **Password** field, enter your ServiceNow user password.\n\n        \\[Omitted image \"lightstep-servicenow-destination.png\"\\] Alt text: ServiceNow Cloud Observability ServiceNow Destination\n\n        **Note:** In a ServiceNow instance, CI binding occurs only if the name of the service in the ServiceNow Cloud Observability platform value matches the name fields of the CI you created in the **cmdb\\_ci\\_service\\_auto** table.\n\n    5.  Select **Save**.\n\n4.  **Note:** If you have any issues with the ServiceNow destination in the previous step, then use the **webhook** destination option.\n\n    In your ServiceNow Cloud Observability platform, create a **webhook** notification destination.\n\n    1.  In the **Name** field, enter a name for the webhook destination.\n\n    2.  In the **URL** field, provide the webhook URL.\n\n        This is the default format of the URL to push events from ServiceNow Cloud Observability to the ServiceNow AI Platform instance. Use this format: `https//&lt;username>:&lt;password>@&lt;instance-name>.service-now.com/api/sn_em_connector/em/inbound_event?source=lightstep`\n\n    3.  Select **Payload Template**.\n\n    4.  Select the **ServiceNow Event Management** option.\n\n        \\[Omitted image \"lightstep-webhook-destination-payload-template.png\"\\] Alt text: ServiceNow event management template\n\n        **Note:** In a ServiceNow instance, CI binding occurs only if the name of the service in the ServiceNow Cloud Observability platform value matches the name fields of the CI you created in the **cmdb\\_ci\\_service\\_auto** table.\n\n    5.  If you selected the **Default Template** option in the previous substep, then select **New Header** and in the **Headers** field, enter the **service-name** and define its **value**.\n\n        **Note:** In a ServiceNow instance, CI binding occurs only if the **service-name** header value matches the name fields of the CI you created in the **cmdb\\_ci\\_service\\_auto table**.\n\n        \\[Omitted image \"create-webhook.png\"\\] Alt text: Create a Webhook\n\n    6.  Select **Create**.\n\n5.  In the ServiceNow Cloud Observability platform, configure an alert.\n\n    1.  From the navigation bar, select **Alerts**.\n\n    2.  Select **Create an Alert** and enter an alert name.\n\n    3.  In the Alert Configuration area, define the threshold.\n\n    4.  According to the destination that you created, in the **Notification Rules** area, in the **Send Notifications to** field, select your notification destination type and search for the destination name.\n\n        \\[Omitted image \"lightstep-send-alert-notification-types.png\"\\] Alt text: Send notification destinations type\n\n    5.  Select **Save**.\n\n        The default severity for stream-based alerts is **Critical**. You can change the default in the Push Connector Configuration area of an ServiceNow AI Platform instance. The valid severity values are:\n\n        -   1- Critical\n        -   2- Major\n        -   3- Minor\n        -   4- Warning\n        -   5- Info\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"}}