--- 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 --- # Use Case: Proactive monitoring of your ServiceNow instance # Use Case: Proactive monitoring of your ServiceNow instance in Health Log Analytics {#ariaid-title1} * Release version: Yokohama * * Updated July 31, 2025 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Proactive Monitoring of Your ServiceNow Instance in Health Log Analytics Health Log Analytics (HLA) enables proactive monitoring of your ServiceNow instance, allowing organizations to detect and resolve issues before they affect users. The integration with the ServiceNow System Logs Retriever automates the identification of errors and anomalies in system logs, streamlining issue management for operators. Show full answer Show less ## Key Features * **Automatic Detection:** Starting with version 35.0.26, HLA utilizes the System Logs Retriever to automatically detect platform issues. * **Express List Management:** Operators can view, manage, and filter alerts by impacted services within the Express List. * **Now Assist Integration:** Provides in-depth analysis of alerts and potential resolutions in human-readable language, leveraging AI-driven insights. * **MID Server Data Input:** Admins can create specific data inputs for selected MID Servers, enhancing monitoring capabilities. * **Log Viewer:** Offers a visual representation of system logs for deep analysis, allowing customization through filters. ## Key Outcomes By combining anomaly detection with Now Assist's generative AI capabilities, HLA equips users with a robust toolkit for identifying and addressing platform issues effectively. This proactive approach minimizes disruptions, ensuring a smoother experience for ServiceNow platform users. Use Health Log Analytics to detect and resolve emerging issues in your organization's ServiceNow instance before they negatively impact users. ## Using the ServiceNow System Logs Retriever integration to detect platform issues automatically {#hla-use-case-syslogs__section_wjh_gxh_jfc} Starting with version 35.0.26 of Health Log Analytics, you can use the [ServiceNow System Logs Retriever integration](https://servicenow-prod.fluidtopics.net/l3nPQD834OQs2gTCDJxT2w "Set up an integration for streaming log data from your ServiceNow platform's System Log table to the HLA engine.") to automatically detect errors and anomalies in your ServiceNow instance's system logs. As an operator you can view, manage, and respond to the generated alerts in the [Express List](https://servicenow-prod.fluidtopics.net/bhN9tpP8s~hCtbJBdqBk3g "You can monitor incoming alerts in Service Operations Workspace. You can also monitor and manage alerts in the Event Management interface."). Filter the list to show only alerts for the impacted service. Then, use [Now Assist](https://servicenow-prod.fluidtopics.net/am5xySJOhGlHEuyZXdBzlw "View an alert analysis created by ServiceNow Now Assist using generative AI. Alert analyses include a human-readable brief of the alert and technical information to help you investigate the alert more effectively.") to get an in-depth analysis of the alert and potential resolutions in straightforward, human-readable language. This AI-driven tool demonstrates a deep understanding of the Glide system and offers actionable insights. Combining HLA's anomaly detection with Now Assist's GenAI capabilities provides a comprehensive toolkit for identifying and resolving platform system issues more effectively. This collaboration enables Health Log Analytics to help prevent system issues from impacting your platform users. ## Using the MID Server and System Logs Retriever data inputs together to monitor your instance {#hla-use-case-syslogs__section_nc4_cvc_3fc} You can also stay ahead of disruptions to your ServiceNow environment by using the [MID Server data input](https://servicenow-prod.fluidtopics.net/lhM9BSmNpq96MRmH_puB2Q "Configure a data input for collecting and streaming MID Server log messages to your ServiceNow instance.") and the [ServiceNow System Logs Retriever data input](https://servicenow-prod.fluidtopics.net/M5EttoAQBxYmq4dzTmqIbg "Configure a data input for streaming log data from the ServiceNow System Log table to the Health Log Analytics AI engine (Occultus).") together. As an admin, you select a MID Server from the MID Servers list. Under Related Links, choose Create MID Server Data Input using HLA to create a data input specific to the selected MID Server. Then activate the System Logs Retriever data input and configure it to collect your ServiceNow instance's system logs. As an operator, you navigate to the [Express List](https://servicenow-prod.fluidtopics.net/bhN9tpP8s~hCtbJBdqBk3g "You can monitor incoming alerts in Service Operations Workspace. You can also monitor and manage alerts in the Event Management interface.") and select an alert from the Alerts list. Review the alert details, including duration and impacted services, and analyze the logs that surround the anomaly. Use [Now Assist](https://servicenow-prod.fluidtopics.net/am5xySJOhGlHEuyZXdBzlw "View an alert analysis created by ServiceNow Now Assist using generative AI. Alert analyses include a human-readable brief of the alert and technical information to help you investigate the alert more effectively.") to get an in-depth analysis of the alert and potential resolutions in straightforward, human-readable language. If needed, for further investigation, you can navigate to 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.") for a visual presentation of the system logs. Select System Logs Retriever from the components drop-down list to view all the errors that have occurred in the ServiceNow instance. You can customize the visualization by using filters. By drilling down into the alert and MID Server logs, you can quickly identify the issue and resolve it before it affects your platform users.