incident-response

Triage AEMaaCS Dispatcher runtime incidents by collecting MCP evidence from logs, traces, cache, and config validation to determine if the issue originates from Dispatcher, CDN, or edge policy. The process outputs an incident report with containment and rollback steps.

Classify cloud incident scope by executing MCP tools like trace_request and inspect_cache to validate HTTPD configuration and compare runtime behavior against edge policy. This evidence-driven approach distinguishes Dispatcher module faults from CDN routing issues for targeted remediation.

Yes, you can use MCP tools including tail_logs, inspect_cache, monitor_metrics, and trace_request for AEMaaCS incident triage. These tools gather runtime evidence from the Dispatcher environment to quantify impact and draft containment plans.

Generate a containment and rollback plan by executing the MCP tool set to collect runtime evidence, validate configurations, and inspect cache state. Findings are translated into structured incident reports detailing actionable mitigations and associated risks.

No, this incident triage process is scoped exclusively to AEM as a Cloud Service environments. It relies on cloud-service runtime guards and MCP tool contracts to gather evidence and validate Dispatcher configurations.

Validate Dispatcher configuration during a cloud runtime incident to determine if HTTPD rules or cache settings are causing the observed behavior. SDK-based checks and lint tools identify configuration errors that require rollback or containment actions.