NEW: Calculate your ROI from automating your incident management with Blameless. Try it now!

By clicking “Accept”, you agree to the storing of cookies on your device to enhance site navigation, analyze site usage, and assist in our marketing efforts. View our Privacy Policy for more information.

Based on the applicable laws of your country, you may have the right to request access to the personal information we collect from you, change that information, or delete it. To request to review, update, or delete your personal information, please fill out and submit a data subject access request to support@blameless.com.

Deny Accept

The blameless blog

SREview Issue #15 July 2021

Blameless

Blog home

SRE

7/15/2021

July 2021 Edition

Hoping you're headed towards a fun summer season! Stay reliably cool with the latest from the world of SRE. This newsletter shares industry content and an exciting Blameless product announcement. Find our fave tweets and events in the SRE community.

We're hiring! Check out the job openings here.

Tweets that have us twittering

https://twitter.com/jennski/status/1409431558122086400

https://twitter.com/niallm/status/1412486180118085632

https://twitter.com/craigsdickson/status/1407866060511100931

SREading

Top 7 Open Source AIOps Tools: AIOps is the practice of using AI to help manage IT operations. Learn about the potential of this growing field by checking out these tools.

Elephant in the Blameless War Room: Accountability: Blamelessness is a pillar of SRE thought, but how do you uphold this ideal when someone demands blame? Learn how to empathize with blameful people and how to do accountability right.

The SRE Incident Response Game: Want to practice your incident response procedures and have a little fun? Bruce Dominguez breaks down how to play his incident response game.

r/WallStreetBets Incident Anthology: Reddit’s Open Systems: The explosion of trading resulting from reddit’s /r/WallStreetBets was an unprecedented financial event. It also caused unprecedented infrastructure challenges for reddit. See how they responded in this article.

Complete Guide to Service Level Objectives (SLOs) That Work: Want the 101 (and the 102, 201, and more) on SLOs? Our guide will get you up to speed.

Incident writeup as sociological storytelling: Lorin Hochstein presents a new perspective on incident writeups: your goal is to describe the context so that readers understand why the responders made the choices they did.

Give it a whirl - SLOs Just Got Better

New! Updates to our newly released SLO capabilities. Error Budgets! Get more control and flexibility with notifications and alerts. You decide when you’re alerted as budget thresholds change. Also we support:

Native integration with New Relic’s APM
Tracking all NR metrics
New Relic Query Language support
Historical data ingest so you’re always up-to-date on SLIs.

Events

July 20 at 8 AM PDT

Blameless Bi-Weekly Demo

Check out a live demo of Blameless. Plus, get a sneak peek of something new we’ve been working on.

“We started using Blameless about a year ago, and transformative is the only way to describe it. There’s not one person on our team that is pulled into an incident and doesn’t know what to do and where to go and how to solve it.”

David Levinger, VP Cloud Optimization, Machinify

"I have less anxiety being on-call now. It’s great knowing comms, tasks, etc. are pre-configured in Blameless. Just the fact that I know there’s an automated process, roles are clear, I just need to follow the instructions and I’m covered. That’s very helpful."

Jean Clermont, Sr. Program Manager, Flatiron

"It’s amazing what Blameless's customer support brings to the table. Our CSM always gives 110%. He goes above and beyond for us in every way possible. We are very comfortable knowing that he is on top of our questions and concerns every day."

Ethan Cohen, Sr. Manager, SRE, Agero

"I love the Blameless product name. When you have an incident, "Blameless" serves as a great reminder to not blame anything or anyone (not even yourself) and just focus on the incident resolving itself."