R12.3-2026Apr21

Data View and Add the diagnosis data to Runbook

The diagnosis data can be added to a runbook for reuse and can also be viewed on the map through the following options:

  1. Data View
  2. Add to Runbook

Data View

If a query was executed without using any existing map, click Data View provided in the deep diagnosis pane to visualize the results on the context map.

When a diagnosis is executed on the context map, the dataview is by default ON. And when the deep diagnosis is completed, it will auto-apply the dataview to the map. You can toggle Data View ON or OFF using the same button. When switching between diagnosis, the dataview is turned OFF by default.

Add to Runbook

Add to Runbook button connects Deep Diagnosis and Runbook, allowing you to seamlessly move from automated diagnosis to guided, step-by-step troubleshooting.

  • Deep Diagnosis acts as an AI-driven diagnostic engine that automatically identifies root causes.

  • Runbook Companion provides a transparent, editable workflow where you can continue investigation, validate findings, or take remediation actions.

With this feature, you can start with deep diagnosis and then reuse all collected evidence and automations inside a runbook without redoing any work.


When does the button Add to Runbook appears?

It appears in the Deep Diagnosis result pane when the diagnosis is completed.

Creating a Runbook from Deep Diagnosis

Once the diagnosis is completed:

  1. Click Add to Runbook and a new runbook is created and stored (for future use) under the context map.

    2. All automations used during the diagnosis are added as runbook nodes and all the results from the diagnosis are included. To keep the runbook clean and readable, automations are grouped as follows:

    1. CLI commands are merged into a single Execute CLI Command node (until limits are reached).
    2. Replicate Intent from NIT, ADT Intent, Published Intent and Golden Intents are added as Intent nodes.
    3. Golden Config and Configlet added as Configlet nodes. If a node reaches its maximum capacity (for example, configlets), additional nodes are created automatically
    4. Runbook template and Map are skipped

  2. Opening an Existing Runbook: If a runbook is already associated with the diagnosis, the button changes to Open Runbook. On clicking the button, it opens:

    1. The Default context map.
    2. The existing runbook.
    3. The AI Runbook pan.

    This lets you resume troubleshooting exactly where you left off in the previous session.

Deep Diagnosis Operational Flow Manager - Deep Diagnosis