KubeCon EU Unofficial SRE track: the talks you cannot miss
There are more than 300 talks at this conference. Check out our SRE-oriented curation for must-see talks in Paris.
Incident Commander Training Strategies: What The Books Don’t Tell You
The Google books offer helpful general principles. In practice, however, you shouldn’t assume they are immediately applicable to your environment. Some companies have comprehensive, high-quality documentation, mature incident response tooling, and more importantly, experienced ICs. However, if your organization is early in the process of establishing the incident response practice, you will need to expand on these principles, so that your response team can handle the chaos with greater ease.
Breaking Down the 2024 VOID Report: “Exploring the Unintended Consequences of Automation in Software”
In an era where automation and artificial intelligence are increasingly integral to software development and operations, the 2024 VOID Report sheds critical light on the nuanced impacts of these technologies. Here, we delve deeper into the report's key findings and explore predictions for the near future, weaving a comprehensive narrative highlighting challenges and opportunities.
Building a Privacy-First AI for Incident Management
Bringing AI into the game, Rootly isn't just playing it safe with privacy; we're setting a new standard. Discover the fusion of cutting-edge AI with uncompromised privacy in incident management
Enhancing Service Reliability: Uniting Rootly’s Incident Management and Backstage’s Software Catalog
We’re happy to announce that Rootly is now live and supported in the Spotify for Backstage Marketplace! In this blog post, we will delve into the key benefits of integrating Rootly and Backstage and why enterprises should prioritize service reliability.
Does Every Incident Need a Retrospective? Here’s What the Experts Have to Say
In December, we held a roundtable discussion among Reliability Leaders on the topic of incident retrospectives. We explored whether they’re necessary, how to build the right culture around them, and what a successful retrospective entailed. As always, we had a wide range of opinions and a few hot takes. We’ve distilled some of the key takeaways from the discussion into this post.
Lessons in Incident Response I Learned While Waiting Tables
Before I stumbled into the tech industry (a story for another day), I spent several years in the customer service world as a server and front of house manager in restaurants. It was in these jobs that I first honed some critical skills that would later lead me on the path to incident response. In this article, I draw comparisons between life in the service industry and IT incident response.
When More Incident Commanders are Better
When incidents reach a heightened level of complexity and scale, Strong argues that companies ought to consider having multiple lead roles present, rather than a single Commander overseeing the entire response. In this post, he breaks down when and how he recommends you consider bringing additional command roles in.
Status Pages 101: How to Create a Status Page You and Your Customers Will Actually Want to Use
Status pages are a simple yet underutilized element of incident communication. Done well, they’re a low-lift way to keep your customers and stakeholders informed when incidents impact them. But without a solid approach, updating status pages can easily become a tedious and often neglected task during incidents. In this post, we’ll cover some tips to get your status page right.
Working Effectively With Executives During an Incident
For many people, the first and only times they interact with Executives is during an incident. It can be an intimidating first introduction! While Execs are first and foremost just people too, they tend to require some specific care when it comes to communication, especially when it involves issues that critically impact your business and customers. In this post, we’ll cover the best practices for communicating effectively with Executives during incidents.