Resources

Wondering about software reliability metrics? We explain the important metrics you need to track.

On call doesn’t have to suck. Right? Some vendors even have this as a tagline. Truth is some on-calls do suck (a little) especially if it’s a Sev0. Ever been in a chaotic on-call environment? Unclear on who’s doing what and how to run the playbook. Is there a playbook? This session shares approaches that simply work and more importantly how teams learn and improve over time. From living through inevitable incidents and reviewing retrospectives, everyone up-levels and learns. Happier DevOps teams, happier customers. Presented by Paul Chu, Head of Customer Success at Blameless.

A retrospective (or post-mortem) is a critical part of Incident Response. If you don’t document, share, and learn, everyone misses out on a critical learning opportunity. Retrospectives are designed to help teams collectively learn, iterate, and improve. It involves taking the time to story-tell exactly how an incident took place and discussing how to do better next time. The key is to shine new light on processes, tools, and systems so that you know how to fine-tune.

In SRE, a core message is that failure is inevitable. No matter how much you prepare, there will always be incidents you can't foresee. This doesn't mean preparation is useless, though. This talk will focus on one extremely valuable type of preparedness: having backups and restoration processes for the worst disasters. When your system experiences a total outage, an effective option is often to switch to a backup system before trying to solve the issue itself. This will restore service as fast as possible. However, just making backup systems isn't enough. This talk reveals complacency and blind spots when it comes to backup systems. Many organizations feel comforted by having created backups, but aren't actually prepared to use them. There will be practical advice given on how to improve backup systems for organizations of all sizes. The talk will cover looking at backup systems from the perspectives making them more reliable, more robust, and more resilient - based on the definitions given by Dr. David D. Woods. In order to make the advice inclusive, there won't be much technical detail. Instead, the focus will be on mindsets and strategies. Black swan events are highly impactful incidents that are so unlikely or unimaginable that effort isn’t made to prepare for them. You'll learn how to conduct thought experiments of "meteor strikes" and other worst-case scenarios, such as ransomware, to feel ready for other problems you can't yet imagine. You'll also see how backup systems can still be useful for such disasters. This is how a resilient backup system is created - one that can still handle what falls outside your expectations.

Wondering about DevOps Tools? We explain the best tools for every step of the DevOps development process.

Wondering what DevOps Methodology is all about? We will explain what it is, how it works, and the principles and processes that make it successful.

Alerts go off. Acknowledge it’s real! Start an Incident. Blameless and PagerDuty work brilliantly together. Blameless has a bi-directional PagerDuty integration to access on-call assignments and escalation policies from within the Blameless product to find and allocate the right engineers on-call. Bring your questions and energy. Excited to share new Blameless updates!

Wondering about Cloud-Native Development? We explain what cloud-native development is and how it can help build fast and reliable applications.