net-diagnose-incident

Automated network incident diagnosis is achieved by orchestrating NETTOOLS adapters to normalize inputs, select a playbook, and generate a structured report. It sequences lower-level tools automatically to resolve single-client, area-based, or site-wide issues.

The best way to generate a machine-readable diagnosis report is to use an orchestrator that sequences network diagnosis tools and evaluates stop-conditions. This approach outputs structured evidence and audit trails suitable for automated processing and replay.

Yes, you can replay a network incident diagnosis workflow because the orchestration process produces deterministic outputs. It records a comprehensive audit trail and evaluates stop-conditions to ensure the replayed sequence yields identical diagnostic results.

To start a network incident diagnosis workflow for site-wide issues, provide a site-id and initial incident context. The orchestrator validates these inputs, selects an appropriate playbook, and sequences the necessary lower-level network adapters.

Automated incident orchestration supports single-client, area-based, and site-wide network problems. It normalizes the varying input contexts for each scope and applies a matching playbook to coordinate the required network diagnosis components.

A playbook-based approach for network diagnosis relies on predefined sequences and stop-condition evaluations. While it provides deterministic orchestration and replayability, it requires appropriate lower-level NETTOOLS adapters to exist for the specific network components being diagnosed.