Use Case: Proactive monitoring of your ServiceNow instance in Health Log Analytics

  • Release version: Australia
  • Updated March 12, 2026
  • 2 minutes to read
  • Summarize
    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) empowers ServiceNow customers to proactively detect and resolve emerging issues within their ServiceNow instances before these issues impact users. By leveraging automated integrations and AI-driven analysis, HLA facilitates early identification and streamlined resolution of platform errors and anomalies, ensuring optimal platform performance and user experience.

    Show full answer Show less

    Key Features

    • ServiceNow System Logs Retriever Integration: Starting with version 35.0.26 of HLA, this integration automatically detects errors and anomalies from your ServiceNow instance’s system logs, generating actionable alerts.
    • Express List for Alert Management: Operators can view and filter alerts by impacted services, enabling focused monitoring of critical platform areas.
    • ServiceNow Otto AI Integration: Otto provides in-depth, human-readable analysis of alerts with potential resolutions, leveraging AI understanding of the Glide system to support efficient problem diagnosis and remediation.
    • MID Server and System Logs Retriever Combined Monitoring: Administrators can configure MID Server data inputs alongside the System Logs Retriever to enhance monitoring coverage. This combined approach enables detailed log collection and anomaly detection specific to selected MID Servers.
    • Log Viewer and Visualization: Operators can review alert logs visually in the Log Viewer, filter errors by components such as the System Logs Retriever, and drill down into detailed logs for thorough investigation.

    Key Outcomes

    • Early detection of platform issues reduces the risk of user impact by enabling timely intervention.
    • AI-driven insights from ServiceNow Otto simplify complex log analysis, improving operator efficiency and decision-making.
    • Comprehensive monitoring through combined MID Server and System Logs Retriever inputs provides a holistic view of system health.
    • Customizable alert filtering and log visualization empower operators to focus on the most relevant issues and accelerate root cause identification.
    • Proactive management of your ServiceNow instance enhances platform reliability and ensures smoother operational continuity for your organization.

    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

    Starting with version 35.0.26 of Health Log Analytics, you can use the ServiceNow System Logs Retriever integration 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. Filter the list to show only alerts for the impacted service. Then, use ServiceNow Otto 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 anomaly detection with ServiceNow Otto AI 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

    You can also stay ahead of disruptions to your ServiceNow environment by using the MID Server data input and the ServiceNow System Logs Retriever data input 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 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 ServiceNow Otto 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 Review alert logs on the Log viewer 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.