{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":30875,"path":"it-operations-management/health-log-analytics/il-connector-hla-edgedelta-rest.md","title":"Set up an Edge Delta REST integration for Health Log Analytics","bundle":null,"doc_type":null,"release":"australia","body":"\n# Set up an Edge Delta REST integration for Health Log Analytics\n\nSet up an Edge Delta REST integration to enable Health Log Analytics to process logs it receives from Edge Delta in a distinct format. These logs stream into your ServiceNow instance via REST.\n\n## Before you begin\n\n-   Verify that a MID Server is installed and configured with the Log Ingestion capability enabled. For more information, see [MID Server system requirements](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/r_MIDServerSystemRequirements.md).\n\n    \\[Omitted image \"hla-mid-log-ingestion.png\"\\] Alt text: MID Server configuration with Log Ingestion capability enabled.\n\n    **Important:** Health Log Analytics does not support IPv6. To work with the application, configure the MID Server to IPv4.\n\n-   Unless the MID Server and external clients are on the same network, the MID Server must have a public IP address. This is required when its IP is exposed through network address translation \\(NAT\\), a load balancer, or a similar device. The public IP address enables external clients, such as Filebeat agents located outside its network, to reach the MID Server. Private IP addresses aren't routable over the internet. Without a public IP, external clients can't connect to the MID Server even if they are configured with its address. In the MID Server properties, add a property named **mid.public\\_ip** with the public IP address as the value. For more information, see [Create a MID Server property](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/servicenow-platform/r_MIDServerProperties.md). If the MID Server and external clients are on the same network, connections can be made using the private IP address.\n\nRole required: evt\\_mgmt\\_admin\n\n## About this task\n\nIf your organization uses Edge Delta to handle large volumes of log data from multiple sources before sending it to Health Log Analytics, the log format HLA receives from Edge Delta is different from other types. The Edge Delta integration enables HLA to detect and separate transport headers from inner log messages in this format. It forwards only the inner message to the source type structure for processing.\n\nYou set up integrations through the Integrations Launchpad in Service Operations Workspace, which you access from the ITOM AIOps configuration center. The AIOps configuration center is a centralized workspace for configuring and managing AIOps features from a single place. The integrations setup process reduces implementation time compared to manual data input setup in the classic interface in Health Log Analytics. For more information, see [Integrations Launchpad in Service Operations Workspace for ITOM](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/integrations-launchpad.md).\n\n## Procedure\n\n1.  Navigate to **Workspaces** > **Service Operations Workspace**.\n\n2.  From the navigation pane, select the AIOps configuration center icon \\[Omitted image \"icon-itom-aiops-config.png\"\\] Alt text: ITOM AIOps configuration center icon.\n\n    The ITOM AIOps configuration center page appears. The configuration center is a centralized workspace. Use it to configure and manage AIOps features from a single place.\n\n3.  From the Integrate section, under Integrations, select **Add integration**.\n\n    The Integrations Launchpad appears.\n\n4.  In the **Browse integrations** tab, enter `Edge Delta` in the search field.\n\n5.  Select the Edge Delta REST integration tile.\n\n    **Note:** If you start an integration setup before meeting all prerequisites, a message appears. You can cancel the setup and complete the prior requirements first. Alternatively, you can continue in draft mode and complete the requirements later. Note that you can't activate the integration until you have completed all the prerequisites.\n\n6.  On the **Provide details** form, fill in the fields.\n\n    For a description of the fields, see [Edge Delta REST integration configuration fields](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/health-log-analytics/il-connector-hla-edgedelta-rest-fields.md).\n\n7.  Select **Next**.\n\n8.  Follow the instructions in the **Set-up instruction** page to install the integration in the third-party console.\n\n    1.  Copy the displayed URL.\n    2.  In Edge Delta, create an HTTP destination.\n    3.  Paste the copied URL into the HTTP destination.\n    4.  Add the following headers:\n        -   Authorization\n\n            Use either of the following:\n\n            -   Key <API\\_KEY>\n\n                Find the API\\_KEY by navigating to **All** > **MID Web Server API Key** > **View API Key**.\n\n            -   Basic <Base64 \\(username:password\\)>\n\n                **Note:** Verify that you use a username and password for a MID web server with Basic Auth enabled.\n\n        -   Content-Type: application/json.\n9.  Do one of the following.\n\n    -   If you completed all the prerequisites before starting the configuration, activate the integration either with or without AI-powered capabilities. Select the appropriate option.\n\n        -   **Activate with AI** enables AI-powered automatic parsing and mapping of log data to service instances and components for contextual alerts.\n\n            When the integration is activated successfully, the **Overview** tab is displayed. ServiceNow Otto for ITOM collects and analyzes log data. An AI icon indicates that AI is active.\n\n        -   **Activate** activates the integration without AI-powered mapping. The integration is activated and the **Overview** tab is displayed.\n        On the Integrations Launchpad, the integration tile is available in the **Installed integrations** tab.\n\n    -   If you didn't complete all the prior requirements, select **Save draft**.\n\n        The system saves the integration as a draft in the Integrations Launchpad **Installed integrations** tab, under **Waiting for your action**. At a later time, complete the prerequisites and activate the installation. For more information, see [Activate a draft integration in Health Log Analytics](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/health-log-analytics/il-connector-hla-activate-draft.md).\n\n\n## What to do next\n\nOn the **Overview** tab, do the following:\n\n-   Use the displayed information to refine how Health Log Analytics reads the log data. For more information, see [Review log streaming data and adjust integration settings in Health Log Analytics](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/health-log-analytics/il-connector-overview-tab.md).\n-   Use the More options menu \\(\\[Omitted image \"more-options.png\"\\] Alt text: More options menu icon.\\) to open the **Data Input Mapping**, **Source Type Structures**, or **Log Sources** pages with context from the integration. If your log data is not properly mapped, structured, or sourced, go back and adjust the configuration. If the Service Operations Workspace Log Analytics application is installed, the More options menu also provides direct access to the **Log Viewer**. Use the **Log Viewer** to review raw log messages ingested by the integration. For more information, see:\n    -   [Log data auto-mapping and mapping](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/health-log-analytics/hla-data-input-automapping.md)\n    -   [Source type structure adjustment](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/health-log-analytics/hla-source-type-structure-adjustment.md)\n    -   [Review alert logs on the Log viewer](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/health-log-analytics/hla-op-logs-log-viewer-concept-sow.md)\n\nIf you activated the integration with AI, verify that AI correctly auto-mapped log data to service instances and components. To do this, select **View mapping** under **Log context mapping**. You can override the AI mapping by selecting a different log field from each list. For more information, see [Map logs to service instances, components, source types](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/health-log-analytics/il-connector-hla-map-business-context.md).\n\n**Parent Topic:**[Set up Health Log Analytics on your ServiceNow instance](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/it-operations-management/health-log-analytics/hla-implement.md)\n\n"}}