Using Runbook to Document Map-Based Activities

NetBrain Runbook represents an automated workflow. It provides a visual way to codify a network troubleshooting process into an executable, reusable, and documentable workflow, to elevate collaboration efficiency.

Besides, tribal leaders can digitize their knowledge into a runbook template to streamline best practices for the entire team. The three primary scenarios of using a runbook are illustrated as follows:

Record Activities and Process
For example, end users run Qapps, execute CLI commands, or use Ping/Traceroute to troubleshoot a problematic area. These actions are instantly recorded in a Personal Runbook, and each action can be annotated with thoughts or analysis to document the diagnosis process.
Example: Execute a Runbook to Troubleshoot A/B Path Issue

Share Knowledge and Know-How
For example, to proactively take measures for network problems that might re-occur, power users create a Runbook Template and continue to improve it, to share best practices and know-how with junior engineers.

Re-executable to Maximize Data Value
For example, Tier 1 engineers execute CLI commands to troubleshoot problematic devices on a map, document the diagnosis and escalate the issue by mentioning next-level users in the runbook. Tier 2 engineers re-execute the runbook, and continue to add a Compare node to evaluate data changes between the two CLI outputs, and then escalate to Tier 3. Each Tier can continue to build on top of what has been done previously by checking analysis results and notes.

This chapter covers the following topics:

Executing a Runbook Template

Creating a Runbook

Action Manager

Personal Runbook

Adding a Note

Saving as Runbook Template

Merging Duplicated Action Nodes

Moving Action Nodes


See also:

Sharing a Runbook

Using Data View to Decode Network Design