Runbooks, also known as playbooks, are documents that walk you through a certain task with specific steps. For example, a runbook for spinning up a new server might ask some questions about the purpose of the server and its estimated load, then lead you to the appropriate instructions and settings. Runbooks ease the cognitive load of these common tasks by clearly outlining the process for each.

Resiliency isn’t something that just happens; it’s a result of dedication and hard work. To reach your optimal state of resilience, there are some crucial SRE best practices you should adopt to strengthen your processes.

In the world of technology, the stakes have never been higher. The move to the cloud and microservices to maximize agility has given way to digital disruptors and unprecedented competitive threats. As distributed systems become increasingly complex, the scale of ‘unknown unknowns’ increases. On top of this, customer expectations are sky-high. The cost of downtime is catastrophic, with customers willing to churn if their needs are not promptly met.

Here’s the second issue of SREview! This monthly zine features epic Tweets, content, and events happening in the SRE and resilience engineering community.

Incident management is a set of processes used by operations teams to respond to latency or downtime, and return a service to its normal state. Incident management practices have long been well-defined through frameworks such as ITIL, but as software systems become more complex, teams increasingly need to adapt their incident management processes accordingly.

During our 2019 Blameless Summit, CEO Ashar Rizqi spoke on his relationship with reliability and how it impacts his personal experiences.

We're proud to announce that this week, we were selected by CIOReview as one of the Top 20 DevOps Solution Providers of 2020 alongside other innovators in the DevOps space such as Chef, Jfrog, Saltstack, Splunk, and Xebia Labs.

Communication during incidents is critical. With the rise of remote work, war rooms are no longer the central hub for all incident communication. Instead, we’re adapting to these new challenges and embracing video conferencing and messaging software in order to stay in tight lock-step with our teammates and collaborators. With this in mind, we are excited to announce that Blameless is adding a new way for you to communicate even faster and more effectively.

Here at Blameless, every aspect of our product has SLOs (Service Level Objects) and error budgets in order to help us understand and improve customer experience. Sometimes, these error budgets are at risk, triggering an incident. While incidents are often painful, we treat them as unplanned investments, striving to learn as much as we can from them. We empower all of our engineers to handle an on-call rotation, no matter how difficult the issue.

Blameless recently had the privilege of hosting some fantastic leaders in the SRE and resilience community for a panel discussion. Our panelists discussed the effects of imposter syndrome especially during high tempo situations, how to use it to our advantage and overcome doubt, and how culture directly affects the availability of our systems. The transcript below has been lightly edited, and if you’re interested in watching the full panel, you can do so here.