Areas grouped by tier: front end, back end, data, integration, delivery 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.
Web Front End — Application, uRL, browsers affected, then the problems seen and the tests run.
Mobile App — Platform, app version, oS versions affected, then the problems seen and the tests run.
Additional component (Front End) — A component not listed above: its name, role, vendor and configuration, then the problems seen and the tests run.
Application Server — Server / instance, runtime and version, hTTP 5xx rate (%), then the problems seen and the tests run.
Business Logic / Jobs — Process or job, schedule, last success, then the problems seen and the tests run.
Additional component (Back End) — A component not listed above: its name, role, vendor and configuration, then the problems seen and the tests run.
Database — Engine, instance, connections used (%), then the problems seen and the tests run.
Cache & Message Queue — Technology, queue depth / lag, memory used (%), then the problems seen and the tests run.
Additional component (Data) — A component not listed above: its name, role, vendor and configuration, then the problems seen and the tests run.
APIs & Integrations — Endpoint or partner, hTTP status, response time (ms), then the problems seen and the tests run.
Identity & SSO — Identity provider, protocol, error shown, then the problems seen and the tests run.
Additional component (Integration) — A component not listed above: its name, role, vendor and configuration, then the problems seen and the tests run.
Deployment & Changes — Release / version, deployed at, change ticket, then the problems seen and the tests run.
Configuration & Secrets — Environment, setting suspected, secret recently rotated, then the problems seen and the tests run.
Logs & Monitoring — Monitoring / APM tool, alerts raised, trace / correlation ID, then the problems seen and the tests run.
Additional component (Delivery & 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.
