San Francisco, CA, USA
Aug 5, 2022   |  By JP Cheung
When, eight years from now, folks are creating lists of the top IT incidents of the 2020s, there's a good chance that they'll include the Rogers outage of 2022. The failure, which made Internet and cellular network service unavailable for more than 12 million users across Canada, was one of the most significant outages in memory, in terms of both the number of affected accounts and the level of service disruption.
Mature start-ups and scale-ups create wonderful and challenging environments for Engineers. As the product they’re creating matures and the brand becomes a successful one, the user base generally starts growing, and, for some companies, in places they might not expect it to grow. As that happens, new challenges arise for Engineers. One of these challenges is pretty straightforward to guess. Basically having a particular product available throughout different regions of the world.
Jun 30, 2022   |  By Andre King
Ask most SREs how many incidents they’d have to respond to in a perfect world, and their answer would probably be “zero.” After all, making software and infrastructure so reliable that incidents never occur is the dream that SREs are theoretically chasing. Reducing actual incidents by as much as possible is a noble goal. However, it’s important to recognize that incidents aren’t an SRE’s number one enemy.
May 27, 2022   |  By Quentin Rousseau
Site Reliability Engineers (SREs) have a considerable set of tasks to juggle no matter where they work or how long their company has had an SRE practice. But if you’re the very first SRE to join an organization – as many SREs are these days, given that the SRE trend is trickling down into smaller and smaller companies – you face a special group of challenges. You may find it difficult to get buy-in for SRE from other technical teams.
May 13, 2022   |  By Weihan Li
What happens when the tools and services you depend on to drive Site Reliability Engineering turn out to be susceptible to reliability failures of their own? That’s the question that teams at about 400 businesses have presumably had to ask themselves this month in the wake of a major outage in Atlassian Cloud.
Apr 12, 2022   |  By Quentin Rousseau
To embed or not to embed: That is the question. At least, that’s one of the questions that companies have to answer as they decide how to implement Site Reliability Engineering. They can either embed SREs into existing teams, or they can build a new, separate SRE team. Both approaches have their pros and cons. The right strategy for your company or team depends, of course, on your needs and priorities.
Mar 29, 2022   |  By JP Cheung
Site Reliability Engineering (SRE) teams and Platform Engineering teams share similar goals -- like maximizing automation and reducing toil -- and similar methodologies. But they have different priorities, and use somewhat different tools to achieve them. What are SREs, what are platform engineers and how is each role similar and different? This article explains.
Mar 11, 2022   |  By JJ Tang
If you’re an SRE, you might view AIOps with great excitement. By automating complex workflows and troubleshooting processes, AIOps could make your life as an SRE much easier. Alternatively, SREs may choose to view AIOps with disdain. They might think of AIOps as just a fancy buzzword that doesn’t live up to its promises, and that can become a distraction from the SRE tools that really matter. Which perspective is right?
Mar 4, 2022   |  By Andre King
When are you smarter than your playbooks, and when are your playbooks smarter than you? That’s a question that engineers rarely step back to consider. The rational, disciplined parts of our minds tell us that the playbooks we are supposed to follow were carefully designed and tested, and that we should stick to them at all costs.
Feb 17, 2022   |  By Weihan Li
When you think of who uses feature flags, your mind most likely goes to developers. In general, feature flags are closely associated with software engineering. But Site Reliability Engineers, too, can benefit from feature flags. SREs may not be the ones to create feature flags, but they should work closely with developers to ensure that the applications their teams support include feature flags.

Rootly is a turnkey incident response command centre that brings the best reliability practices from Google, Netflix, Amazon to those without a million-dollar budget.

Rootly is an all-in-one platform that streamlines collaboration, communication, and learning. It automates away manual toil engineers suffer through today and captures data-driven insights. With Rootly, companies accelerate their incident resolution and learn how to prevent them in the future.

Teams depend on Rootly to improve their reliability:

  • Collaborate: Seamlessly handoff alerts from PagerDuty to quickly declare incidents from your tool of choice like Slack. Automatically involve all the right teams in seconds, not minutes. Beyond just engineering but loop in legal, support, and sales. With intelligent workflows, no more wondering what team owns which service or who should be responsible for what. Rootly does the heavy lifting for you.
  • Communicate: Build your incident timeline through Web or Slack. Autolink war rooms with our Zoom & Google Meet integrations. Rich and customizable private and public status pages ensure everyone is updated while you focus on what you do best, fighting fires.
  • Remediate: Enrich your timeline with automated Genius workflows. Fetch relevant information as recent git commits of your impacted services. Customize your workflows based on any incident condition.
  • Retrospective: Learn from incidents with beautiful postmortems engineers want to write without the manual toil of copy and pasting. Accurately replay past incidents to help simulate real world disaster scenarios to train engineers faster and keep their tools sharp. Organized and easily shared, not buried in a Google Doc that can’t be found.

All-in-one incident response platform for humans.