Customers / Cloudlfare
  • Size
  • 415+ Employees

  • Industry
  • Information Technology & Services

  • Location
  • San Francisco, CA

  • Customer Since
  • 2016

Challenges

  • Hyper-growth fueled an increasingly large amount of data, resulting in diluted ability to categorize incidents
  • Communication and escalation built in-house and required manual effort across teams
  • Decentralized data due to security compliance prevented the consolidation of automated incident alerts

Business Impact

  • Increased stability of infrastructure in order to provide more reliable service to customers and guarantee high availability

Benefits With PagerDuty

  • Reduced mean time to-action to incidents from minutes to seconds
  • Streamlined communication across the SRE team for managing incidents
  • Easy detection and prioritization of incidents based on severity
  • Centralized single-source-of-truth for incident management

Cloudflare Reduces Mean-Time-To-Action to Seconds with PagerDuty

As a global cloud-based performance and security solution to over 6,000,000 Internet assets, Cloudflare ensures that customer websites, applications, and APIs are secure, performant, and highly available. In serving over 10% of the world’s Internet traffic, it’s imperative that Cloudflare’s services remain online for customers at scale, while guaranteeing SLA uptime by identifying and resolving incidents, long before operations are ever disrupted. Cloudflare’s Site Reliability Engineering (SRE) team, lead by Michael Daly, sought an incident resolution solution which would help Cloudflare increase the stability of its operations, while delivering a flawless experience for every customer.

Challenges: Visibility, Communication, and Escalation

Cloudflare faced three challenges before adopting PagerDuty. The first was around optics. “We didn’t immediately know when something was broken because the engineering team did not receive automated alerts when an incident occurred,” Michael explained.

The second challenge was in managing incidents. Once a problem was discovered, the engineering team relied on manual processes to address it. Engineers spent time diagnosing the cause of the problem, and if a solution required assistance from another department, SREs were required to contact that person over phone, text, or chat — a duty that became difficult if incidents occurred after working hours or on weekends.

Given Cloudflare’s rapid growth, with less than 800,000 customers in 2013 to over 6 million in 2016, it was becoming difficult for Michael’s team to separate actionable, critical incidents from the growing volume of data generated by monitoring tools. While the team refused to dispose of potentially useful information, they needed to group related symptoms in order to gain actionable insight. Without the assistance of dynamic event management and triage, automation, and other capabilities available from PagerDuty, Michael and his staff had to evaluate the seriousness of each incident manually, a process that was becoming too slow to best serve the exponentially growing number of customers.

Increasing Stability and Response Time with PagerDuty

By adopting PagerDuty, Cloudflare resolved all of these challenges. PagerDuty ensures that Michael and his team are always notified of incidents as soon as they occur and, if an incident should be handled by a different team, PagerDuty forwards the notification automatically to save time.

The Cloudflare SRE team also uses the Operations Command Console, and benefit from capabilities like the highlighting of high-urgency incidents within the Major Incidents Application. As a result, with full-stack visibility into their infrastructure and pattern and anomaly detection, they no longer miss serious events. Michael explained, “When we adopted PagerDuty, we were able to take certain alerts and say to ourselves, this one is really important. We need to deal with it now.”

In addition, other capabilities such as PagerDuty’s HipChat integration made it easier for Cloudflare’s SRE team to streamline communication, collaborate, automate ops-related tasks with commands, learn together, and more when responding to incidents. PagerDuty also eliminated the need for SREs to manually look up contact information for the right expert, as individuals, teams, or business stakeholders can be informed and recruited into an incident in just a click. With PagerDuty, they can get in touch instantly.

Most importantly, PagerDuty reduced the time it takes Michael and his team to take action on incidents, to a small fraction of what it was previously. “Mean-time-to-action has dropped from minutes to seconds,” Michael said, adding that faster response time translates to greater service reliability and better customer outcomes — which is the ultimate goal and reason why Cloudflare sought out PagerDuty in the first place.

 

 

“We had several options, but we chose PagerDuty because we had to do less work to make PagerDuty work with our systems.  It was very nicely formatted, the API just worked, and the output from the app was very easy to interpret.”

Cloudflare Image
Michael Daly, Engineering Manager at Cloudflare