Scan Health — example output

███╗ ██╗ ██████╗ ██╗ ██╗ █████╗ ██╗ ██╗ ██╗██╗████████╗ ████╗ ██║██╔═══██╗██║ ██║ ██╔══██╗██║ ██║ ██╔╝██║╚══██╔══╝ ██╔██╗██║██║ ██║██║ █╗ ██║ ███████║██║ █████╔╝ ██║ ██║ ██║╚████║██║ ██║██║███╗██║ ██╔══██║██║ ██╔═██╗ ██║ ██║ ██║ ╚███║╚██████╔╝╚███╔███╔╝ ██║ ██║██║ ██║ ██╗██║ ██║ ╚═╝ ╚══╝ ╚═════╝ ╚══╝╚══╝ ╚═╝ ╚═╝╚═╝ ╚═╝ ╚═╝╚═╝ ╚═╝ ✦ NowAIKit — The #1 AI App for ServiceNow - Running scan-health in direct mode (ollama)... ``` INSTANCE HEALTH REPORT ========================================== Instance: demo2 | Version: Zurich-2025-Patch6-Hotfix1 | Scan scope: full Scan date: 2026-02-10 EXECUTIVE SUMMARY - Critical issues: 0 - Warnings: 5 - Informational: 3 - Overall health: DEGRADED FINDINGS BY CATEGORY --------------------- --- SYSTEM PROPERTIES & INSTANCE INFO [INFO] Instance Identity Confirmed Evidence: glide.buildtag=glide-zurich-07-01-2025__patch6-hotfix1-02-05-2026, glide.war dated 02-09-2026 Impact: Instance version identified but environment type (dev/test/prod) not confirmed Recommendation: Verify environment classification; demo2 name suggests test/demo environment [INFO] Branding Configuration Standard Evidence: Product logo and icon settings configured normally Impact: Minimal - UI consistency maintained Recommendation: No action required [WARNING] WAR File Future Date Evidence: glide.war shows build date 02-09-2026 (appears to be demo/test instance) Impact: Confirms demo environment status - acceptable for testing but document environment type Recommendation: Document as TEST environment; verify production data isolation --- SCHEDULED JOB HEALTH [HIGH] Jobs Running Without Dedicated Run-As User Evidence: 5+ jobs have run_as="" (empty string) including "Sync Instance Metadata", "Disconnected Chat Timeout", "Test ValueResults Sync" Impact: If admin account disabled or quota limits reached, these jobs will fail. Security best practice violation. Recommendation: Assign dedicated service accounts to critical jobs; review inactive jobs for cleanup [MEDIUM] Inactive Jobs Not Reviewed Evidence: 3 inactive jobs including "Update remediation status for stale test results", "Populate new CR Count Column", "Delete Old Resource Types" Impact: May indicate incomplete cleanup or abandoned functionality Recommendation: Review inactive jobs; either reactivate needed functions or remove to reduce system load [LOW] Multiple Jobs Using Same Run-As User Evidence: Multiple jobs reference sys_user 6816f79c (appears to be same admin account) Impact: Single account dependency increases risk of single point of failure Recommendation: Distribute job ownership across multiple service accounts --- SYSTEM LOG ANALYSIS [CRITICAL] Log Query Failed Evidence: get_sys_log_error returned "Failed to query records: This operation was aborted" Impact: Unable to assess error trends, authentication failures, or quota violations Recommendation: Escalate to platform admin; this may indicate transaction lock, quota exceeded, or system instability [MEDIUM] Incomplete Log Data Evidence: Only 15 system properties returned; logs could not be retrieved Impact: Cannot assess error frequency, slow queries, or authentication issues Recommendation: Re-attempt log collection; check transaction quota limits --- TABLE HEALTH [INFO] Table Counts Not Available Evidence: No table count data provided in scan results Impact: Unable to assess row growth, attachment size, or orphaned data Recommendation: Run get_table_record_count for critical tables when log access is restored [INFO] Attachments Not Analyzed Evidence: Attachment table data not included in provided dataset Impact: Unable to identify orphaned attachments or size growth Recommendation: Monitor sys_attachment for orphaned references to inactive tables --- QUEUE SIZES & BACKLOGS [WARNING] Queue Data Not Collected Evidence: No queue metrics (sysevent, sys_email, ecc_queue) provided Impact: Unknown depth on event, email, or import queues Recommendation: Monitor queue depths during peak periods; address if backlog exceeds 10k records --- PERFORMANCE INDICATORS [INFO] Performance Metrics Unavailable Evidence: No transaction time, cache hit, or semaphore data provided Impact: Unable to identify performance bottlenecks Recommendation: Implement performance monitoring; track transaction times >500ms --- NODE & CLUSTER STATUS [INFO] Cluster Data Not Collected Evidence: sys_cluster_state data not provided Impact: Unknown node health or replication status Recommendation: Verify cluster state if multi-node deployment confirmed SEVERITY LEGEND ---------------- CRITICAL — Immediate action required; service impact likely HIGH — Action needed within 24-48 hours MEDIUM — Plan remediation within 1-2 weeks LOW — Housekeeping; address during next maintenance window INFO — No action required; noted for awareness TREND INDICATORS ----------------- Status: STABLE (based on available data) Notes: Log collection failure may indicate emerging stability issue Recommendation: Schedule follow-up scan after log access restored ... (42 more lines — full output truncated for screenshot)