Areas grouped by infrastructure domain: compute, storage and backup, facilities and power, telecom and connectivity, cloud and operations. Every category ends with Add Other for an area of your own. You tick the areas involved and, for each one, give its technical data, the problems observed, the failed tests (expected and actual result), the successful tests and your observations, then rank the problems by urgency. The AI correlates the evidence, builds hypotheses (failed tests strengthen them, successful tests eliminate them), starts with your most urgent problem, sets the investigation path and, for each problem, guides the root cause analysis and gives the best correction now and the corrective action decision.
Contents
1. Evidence Correlation
2. Problem Prioritization
3. Root Cause Hypotheses
4. Optimal Investigation Path
5. Problem-by-Problem Resolution
6. Missing Diagnostic Information
What you provide
Relevant areas — The areas concerned by the incident.
Physical Servers — Server name, vendor and model, hardware status, then the problems seen and the tests run.
Virtualization — Platform, cluster / host, vMs impacted, then the problems seen and the tests run.
Containers — Platform, namespace / workload, pod state, then the problems seen and the tests run.
Operating Systems — Operating system and version, hosts concerned, system disk free space (%), then the problems seen and the tests run.
Additional component (Compute) — A component not listed above: its name, role, vendor and configuration, then the problems seen and the tests run.
Storage (SAN / NAS) — Array / NAS, protocol, capacity used (%), then the problems seen and the tests run.
Backup & Recovery — Backup solution, job concerned, last successful backup, then the problems seen and the tests run.
Additional component (Storage & Backup) — A component not listed above: its name, role, vendor and configuration, then the problems seen and the tests run.
Power / UPS — UPS, uPS state, battery runtime (min), then the problems seen and the tests run.
Cooling — Room temperature (°C), humidity (%), cooling units concerned, then the problems seen and the tests run.
Data Center — Site / room, racks concerned, physical event, then the problems seen and the tests run.
Additional component (Facilities & Power) — A component not listed above: its name, role, vendor and configuration, then the problems seen and the tests run.
ISP / WAN Links — Provider, circuit ID, link state, then the problems seen and the tests run.
Cellular (4G / 5G) — Operator, signal RSSI (dBm), technology, then the problems seen and the tests run.
Satellite Links — Provider, signal quality (dB), weather at the site, then the problems seen and the tests run.
GPS / Time Synchronisation — Time source, clock offset (ms), stratum, then the problems seen and the tests run.
Additional component (Telecom & Connectivity) — A component not listed above: its name, role, vendor and configuration, then the problems seen and the tests run.
Cloud Platform — Provider, region, resources impacted, then the problems seen and the tests run.
Monitoring & Management — Monitoring tool, alerts raised, first alert time, then the problems seen and the tests run.
Additional component (Cloud & Operations) — A component not listed above: its name, role, vendor and configuration, then the problems seen and the tests run.
Problem prioritisation — The analysis investigates the problems in this order, weighed by their business impact.
