Automation is being applied across just about every aspect of IT operations to increase speed and efficiency, improve availability, and foster agility and innovation. One area where automation is lagging, however, is network troubleshooting, which accounts for a as much as 65% of a NetOps engineers time according to recent studies.
Here’s a typical workflow for responding to an IT event — for example, a slow application:
So, the question is, “What can we do to shift this workflow to the left?” Because as this workflow progresses and the issues escalate, the teams involved get more and more expensive.
Automation provides the answers to the following questions:
By applying scalable network automation, the incident response workflow can be shifted to the left – with tier 1 engineers addressing more complex issues much faster and more experienced engineers sharing their knowledge to accelerate troubleshooting while allowing them to focus on more complex network issues.
Automation is leveraged in each step of this workflow; from the moment an event is detected all the way through postmortem analysis. The goal is to reduce mean time to repair (MTTR) and make more effective use of every member of the operations teams during this response.
For more on this topic, join us at the NetBrain Webinar titled “How to Automate the Resolution of EVERY Ticket” on December 3, for more information visit https://www.onug.net/how-to-automate-the-resolution-of-every-ticket/