Collecting Data for Incident Escalation

Collecting Data for Incident Escalation

Here, the client has created a Runbook to gather OSPF data from their network. Once all of the data is collected and visualized, it will be made available to more senior members of the staff who are troubleshooting a network issue.

1. A custom Qapp is highlighting and gathering all of the routing information present on the designated environment, and compiling this information into several notes that are placed on the Dynamic Map. Here, in this example, all of the relevant OSPF information –
2. A second Qapp is monitoring the running status of OSPF – it’s simply highlighting the neighbor count and OSPF routes on the map.
3. A batch CLI node (which is the automated execution of CLI commands, more on that in #2) is collecting relevant information about these devices in order to have more useful information to be escalated to higher tier engineers.

First – this reduces the overhead involved in troubleshooting; team members no longer need to duplicate the retrieval of basic information from the network in order to do their job properly. It also enables multiple teams, like networking and security, to work together in the event of breaches or security incidents since everyone’s working from the same frame of reference.

Second – this Runbook also creates a snapshot of the network at a certain point in time and can be used when planning out future network changes to avoid possible errors or outages.

Higher visibility and monitoring of the environment, increased revenue by operator. Traffic load balancing across devices and links to ensure non peak period congestion and proper utilization of assets and resources across the ecosystem.