Incident Playbook: How to Plan for and Respond to Outages
January 10, 2017

Scott Klein
Atlassian

Share this

There's nothing like a major web outage to remind us how much our applications rely on other web services and technologies to function. In late October of last year, a Distributed Denial of Service (DDoS) attack on Dyn, one of the largest Domain Name Service (DNS) providers on the internet, disrupted service for consumer and business applications across the web. This attack shed light on the delicate interdependent nature of the web as productivity and uptime across the world was effected, even for organizations that didn't directly use Dyn as a DNS provider.

For an IT team, it can be a rude awakening when one major service provider's downtime triggers outages of technologies across the web, eventually hitting their application in its destructive path. As we saw with this attack, the disruption of one service can have a domino effect on many others. From an outsiders' perspective, it can make the internet seem like a wobbly house of cards. While you and your IT team might not see it that way, consider how an outage of this magnitude is perceived by your business colleagues and customers.

To alleviate these concerns, it's worth developing an incident response plan so that when another outage inevitably occurs, you are able to show confidence and transparency while managing the incident. Incident response plans can be developed in three steps to ensure you and your team are prepared to not only respond to an incident, but also maintain clear communications with stakeholders to quell panic.

1. Identify and quantify incidents

There doesn't have to be a major DDoS attack for a response plan to come in handy (think bugs in production, broken builds, login issues, etc.). Your team needs to be able to quickly identify and quantify the incident in order to appropriately respond.

If your team can answer these questions to define what constitutes an incident, they will be better equipped to respond:

■ How many customers are impacted?

■ How long does the incident need to last?

■ How degraded is the service and how do you determine severity level?

2. Create an incident communication plan

A well-built incident response plan is largely about effective communication, from who should be included in remediation conversations, to what is communicated to end users.

Consider the following when creating an incident response plan:

■ Identify the incident commander. This person is already at work or on call and available to provide direction during an incident.

■ Establish internal channels for alerting and communicating with teams reacting to the incident. We recommend creating a "war room," or dedicated chat room, to use for the duration of the incident and cut out unnecessary noise.

■ Know how you will communicate with end users. Whichever solution you use, be sure it's reliable and available when you need it. This usually means something that isn't hosted outside your core tech stack, because you don't want your communication forum having downtime when you need it most.

■ Build templates and preset language for common incidents. The last thing you need to worry about during an incident is how to phrase an alert during an already high-tension situation. While every incident is unique, most of them we find fall into a few broad categories: total outage, regional outage, delayed response times, to name a few. By deciding on some stock language for these templates and saving it ahead of time, you'll have more time to dedicate to the incident when it actually happens. This also accelerates the time from detection to communication.
Plan to send periodic updates during the incident to keep the team and stakeholders informed.

3. Communicate with transparency

During an incident, streamlined, transparent communications can free up your team to focus on fixing the problem while ensuring customers have the most up-to-date, accurate information. Even if your outage is the result of a third-party service provider, it's your responsibility to make sure your customers have the right information. While you don't want to play a blame game during an incident, there's nothing wrong with letting your users know that you're waiting on a fix from another provider. This helps your users understand that there isn't a lot you can do.

If the service provider having the outage is communicating with users somewhere, it's smart to direct your users there. During the Dyn outage, we saw a lot of Dyn's customers direct their users to Dyn's service page. This helped clear up the confusion around the interdependencies of these structures and helped users get the right information in the quickest possible way.

Postmortem and evolve

The lifecycle of an incident doesn't end when your application is up and running again, and neither should the actions that your team takes. Include these steps into your response plan to ensure you're covering all of your bases - both now and in the future.

■ After the dust has settled, draft an incident postmortem to explain what happened and what precautions are being implemented to prevent a repeat incident. It's always good to write a postmortem, especially for major outages. This is your opportunity to tell your customers what went wrong and what you're doing to avoid the incident in the future. A good postmortem includes an apology for any inconvenience your service outage may have caused and acceptance of responsibility. Finger pointing (even if it genuinely was another party at fault) is never a good look. Finish off your postmortem by explaining your remediation plan.

■ Conduct a post-incident review with your team to evaluate the processes and strategy enacted during the incident and how those can be improved to better handle future incidents.

There's no telling when the next incident will occur, what the scale will be or what systems will be affected, but if your team is prepared with a incident response plan, they can act swiftly to respond to the issue without the frenzy and panic that typically ensues. And when the next major domino drops and the rest of the world is furiously clicking "reload" and overloading customer service lines, your customers and stakeholders will receive clear, transparent communications the entire time.

Scott Klein is StatusPage Product Manager at Atlassian.

Share this

The Latest

September 22, 2017

UK businesses have attained high levels of business-IT alignment in of all sizes, with IT pros demonstrating strong business understanding and business pros exhibiting strong IT knowledge to increase business performance, according to a new survey by ManageEngine ...

September 21, 2017

The increased complexity of new computing architectures coupled with new application development methodologies – especially in the face of time-to-market and security threat pressures – should make secure UX the first strategic decision for CEOs and CFOs on the path to digital transformation ...

September 19, 2017

IT professionals tend to go above and beyond the scope of their core responsibilities as the changing business landscape demands more of their attention, both inside and outside of the office, according to the Little-Known Facts survey conducted by SolarWinds in honor of IT Professionals Day ...

September 18, 2017

Digital video consumption is viral and, according to a new study released by IBM and International Broadcasting Convention (IBC), more than half of the 21,000 consumers surveyed are using mobiles every day to watch streaming videos, and that number is expected to grow 45 percent in the next three years ...

September 15, 2017

No technology that touches more than one IT stakeholder, no matter how good and how transformative, can deliver its potential without attention to leadership, process considerations and dialog. In this blog, I'd like to share effective strategies for AIA adoption ...

September 14, 2017

Enterprise IT environments are becoming more heterogeneous and complex, with fragmentation permeating cloud infrastructure, tooling and culture, according to a survey recently conducted by IOD Cloud Technologies Research in partnership with Cloudify ...

September 12, 2017

One area that enables enterprises to reduce complexity and streamline operations is their virtual desktop infrastructure (VDI). Virtualization is a linchpin of digital transformation and effectively optimizing an enterprise's VDI is essential to moving forward with digital technologies. Delivering the best possible VDI performance means taking a fresh look at what "desktop" means today. The endpoint, or desktop, now can be a physical thin client, a software-defined thin client, a traditional laptop, a phone or tablet. To reduce operational waste and achieve better performance across the desktop environment, consider these five actions ...

September 11, 2017

In incident management, we often overlook the simple things in favor of trying to do too much, too soon. Why not make sure we've done the fundamentals properly? ...

September 08, 2017
For our Advanced IT Analytics (AIA) Buyer's Guide, we interviewed more than 20 deployments to help us better assess vendor strengths and limitations. So given the abundance of riches to work with, I've decided to illustrate several of the more prominent AIA benefit categories with actual real-world comments ...
September 07, 2017

The Input/Output Operations per Second (I/O) capabilities of modern computer systems are truly a modern wonder. Yet no matter how powerful the processors, no matter how many cores, how perfectly formed the bus architecture, or how many flash modules are added, somehow it never seems to be enough ...