--- sourceDocument: Yokohama IT Operations Management sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/it-operations-management Release : - yokohama ft:locale : - en-US ft:publication_title : - Yokohama IT Operations Management ft:clusterId : - itom bundleId : - itom workflow : - Technology --- # Review log data streaming status for an integration # Review log data streaming status for an integration {#ariaid-title1} * Release version: Yokohama * * Updated January 30, 2025 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Review the log data streaming status and streaming sources of an active integration for Health Log Analytics on the integration's Overview screen. From this tab, you can investigate streaming issues and refine the integration settings. Leverage the displayed data to refine how HLA reads the log data by adjusting the integration's configuration. ## Before you begin Confirm that the integration has been activated on the Integrations Launchpad. For more information, see [Set up integrations from Integrations Launchpad](https://servicenow-prod.fluidtopics.net/2hnWmSl1ix9h3FFG_7KA5g "Set up integrations for Health Log Analytics from the Event Management Integrations Launchpad in Service Operations Workspace for ITOM."). To access the Log Viewer from the Overview tab with context from the integration, you must have the ServiceNow Service Operations Workspace Log Analytics application installed. Role required: evt_mgmt_admin ## About this task For more information about the data shown in the Overview screen, see [Review log data streaming status for an integration](https://servicenow-prod.fluidtopics.net/dLK~lbQI1jwzDxj9wJ0N5g "Review the log data streaming status and streaming sources of an active integration for Health Log Analytics on the integration's Overview screen. From this tab, you can investigate streaming issues and refine the integration settings. Leverage the displayed data to refine how HLA reads the log data by adjusting the integration's configuration."). ## Procedure 1. Navigate to WorkspacesService Operations Workspace. 2. From the bottom of the navigation pane, select the ITOM AIOps configuration center icon ![](). The ITOM AIOps configuration center page appears. The configuration center is a centralized workspace that enables you to configure and manage AIOps features from a single place. 3. From the Integrate section, under Integrations, select Manage installed integrations. The Integrations Launchpad appears. 4. In the Installed integrations tab, search for an active integration and open it. The Overview screen displays, showing the integration's data streaming status and its log data sources data. Note: The ServiceNow System Logs Retriever integration doesn't run on a MID Server. Therefore, for this integration the Overview screen doesn't display the MID Server streaming status. 5. Analyze the provided data and investigate any data streaming issues. 6. **Optional:** Adjust the configuration of the integration, if needed. Use the options on the View menu (![View menu icon.]()) to navigate to the relevant table or the Log Viewer. Note: The View menu content changes dynamically depending on whether the referenced tables contain data. {#il-connector-overview-tab__table_wrd_plh_4dc__entry__2} | Option | Description | |-|-| | Data Input Mapping | Opens the Data Input Mapping page. On this page, you can map sources manually if HLA didn't discover properties automatically. For more information, see [Map raw log data](https://servicenow-prod.fluidtopics.net/ENjBmAW1AM2qvvmJSA_YiQ "Mapping raw log data that streams into your instance determines how the data is handled. Health Log Analytics automatically structures logs, creates metrics for anomaly detection, and presents alerts based on how your data is tagged."). | | Source Type Structure | Opens the Source Type Structures page. In the Source Type Structure, log data is classified and organized based on its origin or type. You can adjust the structure and verify that the HLA AI engine extracts properties properly and classifies them correctly. For more information, see [Source type structure adjustment](https://servicenow-prod.fluidtopics.net/QrL5WXM7uUk9ET5jegVJAw "Health Log Analytics enables you to reclassify auto-classified properties and change auto-mapped labels. These adjustments help Health Log Analytics machine learning to better understand your priorities."). | | Log Sources | Opens the Log Sources table. This table enables you to verify that HLA has created all your log sources. If a log source is missing, you can add it manually. For more information, see [Verify your log sources](https://servicenow-prod.fluidtopics.net/DGrefcABBkDqewX70S2G~Q "Verify that all your log sources are present and active after Health Log Analytics tagging has assigned a log to a service instance and components, and has automatically mapped the log to a source."). | | Log Viewer | Opens the Log Viewer, which shows the frequency of anomalies in the log data during a specific time period. For more information, see [Reviewing alert logs on the Log viewer](https://servicenow-prod.fluidtopics.net/xFTujkgfaGkZ_U_8Hazb~A "The Log viewer tab lets you browse the logs for an alert by timestamp or time range, and visualize anomaly frequency within a specific time period. Customizing the displayed data and adjusting time filters enables you to better understand the framework in which the anomaly occurred, helping you find the root cause faster."). Note: The Log Viewer option appears only if the Service Operations Workspace Log Analytics application is installed. | [Table 1. View menu options] {#il-connector-overview-tab__table_wrd_plh_4dc} 7. When you have resolved any data streaming issues and fixed the configuration, select Test and save. The system saves the updated configuration to the database and tests the configured port, returning either success or an error. If an error is returned, fix the configuration according to the suggestions on the screen and then select Test and save again. Once the test is successful, continue with the next step. 8. Reactivate the integration. {#il-connector-overview-tab__steps_jgf_fjx_4dc} *[\>]: and then