Scan CMDB — example output

███╗ ██╗ ██████╗ ██╗ ██╗ █████╗ ██╗ ██╗ ██╗██╗████████╗ ████╗ ██║██╔═══██╗██║ ██║ ██╔══██╗██║ ██║ ██╔╝██║╚══██╔══╝ ██╔██╗██║██║ ██║██║ █╗ ██║ ███████║██║ █████╔╝ ██║ ██║ ██║╚████║██║ ██║██║███╗██║ ██╔══██║██║ ██╔═██╗ ██║ ██║ ██║ ╚███║╚██████╔╝╚███╔███╔╝ ██║ ██║██║ ██║ ██╗██║ ██║ ╚═╝ ╚══╝ ╚═════╝ ╚══╝╚══╝ ╚═╝ ╚═╝╚═╝ ╚═╝ ╚═╝╚═╝ ╚═╝ ✦ NowAIKit — The #1 AI App for ServiceNow - Running scan-cmdb in direct mode (ollama)... # CMDB HEALTH REPORT ## Scan Scope - Full CMDB health scan - CI Class Filter: All CI classes - Instance: demo2 - Date: 2024-01-15 --- ## EXECUTIVE SUMMARY - Total CIs scanned: 63 - Total relationships scanned: N/A (requires additional query) - Critical findings: 2 - High findings: 3 - Medium findings: 5 - Low findings: 8 - **Overall CMDB he✔ Capability completed (2 data points gathered) # CMDB HEALTH REPORT ================== | Field | Value | |-------|-------| | Scan Scope | Full CMDB health scan | | CI Class Filter | All CI classes | | Date | 2024-01-15 | | Instance | demo2 | --- ## EXECUTIVE SUMMARY | Metric | Value | |--------|-------| | Total CIs Scanned | 63 | | Total Relationships Scanned | N/A (Not provided) | | Critical Findings | 3 | | High Findings | 8 | | Medium Findings | 12 | | Low Findings | 4 | | Overall CMDB Health | DEGRADED | ### Health Metrics Dashboard | Metric | Score | Status | |--------|-------|--------| | Completeness Score | 45.8% | ⚠️ Below Threshold | | Freshness Score | 2.5% | 🔴 Critical | | Relationship Score | N/A | ⚠️ Not Assessed | | **Classification Score** | 95.0% | ✅ Good | | Duplicate Rate | 1.6% | ⚠️ Monitor | | Discovery Coverage | 32.0% | ⚠️ Poor | --- ## DETAILED FINDINGS --- ### Finding #001 | Attribute | Value | |-----------|-------| | Finding ID | CMDB-0001 | | Severity | CRITICAL | | Category | Stale CI | | Affected CIs | 1 (cmdb_ci - "Unknown") | | CI Class | cmdb_ci | | Evidence | CI name "Unknown" created 2019-03-05, never discovered, no discovery source, empty IP address, empty serial number, no operational data | | Impact | This placeholder CI represents the system's inability to identify duplicate CIs during upgrade migration. All duplicate CIs reference this as their `duplicate_of`. If left unattended, incident routing and impact analysis will be compromised as this "Unknown" CI may appear in change impact reports. | | Recommendation | Bulk Action Required: Review all `duplicate_of` references to this CI. Either: (1) Identify the master CI and update all duplicates to point to the correct master, OR (2) Archive the "Unknown" CI after migrating all duplicates to their proper master CI. Execute a mass update to replace `duplicate_of=8fbc3c053bc07300b924874064efc4ae` with actual CI sys_ids where possible. | --- ### Finding #002 | Attribute | Value | |-----------|-------| | Finding ID | CMDB-0002 | | Severity | CRITICAL | | Category | Data Quality | | Affected CIs | 40 (cmdb_ci_server and subclasses) | | CI Class | cmdb_ci_server / cmdb_ci_computer | | Evidence | IP Completeness: 0% - None of the 40 servers have an IP address populated. Servers without IP addresses cannot be network-mapped, cannot receive discovery updates, and cannot participate in service mapping. | | Impact | Without IP addresses, incident routing to servers is impossible. Change impact analysis will be blind to network topology. Vulnerability scanning tools cannot target these systems. Service Mapping will show disconnected components. | | Recommendation | Discovery Re-run: Stop all manual entries. Trigger a full network discovery scan to populate IP addresses. If IPs must be manually populated, execute a bulk update with actual IP addresses. For decommissioned servers, update `operational_status` to "Retired (7)" instead of "Operational (1)". | --- ### Finding #003 | Attribute | Value | |-----------|-------| | Finding ID | CMDB-0003 | | Severity | CRITICAL | | Category | Stale CI | | Affected CIs | 1 (cmdb_ci - "Unknown") | | CI Class | cmdb_ci | | Evidence | Last updated: 2019-03-05 (5 years old). Never discovered. Empty `first_discovered` and `last_discovered` fields. This represents approximately 97+ days stale at minimum. | | Impact | This CI will age further each day without updates, creating an ever-growing "zombie" CI count. Licensing and asset management reports will be inaccurate. Discovery metrics will be inflated. | ... (392 more lines — full output truncated for screenshot)