A runbook consists of one or multiple action nodes. Each action node can be executed individually and repetitively to automate data analysis.
The following table lists the types of action nodes that can be assembled in a runbook.
Action |
Description |
---|---|
Run a single Qapp to perform an automation task. |
|
Run a built-in Qapp to monitor your network health. |
|
Run a group of contextualized Qapps for multistage troubleshooting. |
|
Retrieve live data by executing CLI commands. |
|
Retrieve device data by executing CLI commands or selecting built-in data types, and save the data. |
|
Test the connectivity from one endpoint to another, |
|
Discover and map a routing path between two endpoints. |
|
Path |
Refer to Mapping an A/B path. |
Compare data changes between two different time points, or between two versions of device data. |
|
Run a Ansible task to allow developers and IT operation teams to query information on multiple hosts or push bulk network configurations more easily and quickly. |
|
Free Text |
Annotate a text based on needs, such as describing the usage of each branch. |
Data View Template |
Run a data view template to visualize concerned parser variables. Refer to Applying a Data View Template. |
Verify A-B paths for key applications. |
|
Describes a network design for a specific network device, what these design baselines are like, and how to verify design works properly |