SRE Weekly - SRE Weekly Issue #330

Is your status page status.yourcompany.com? If so, read this article, then get yourself a new domain.

  Eduardo Messuti — Statuspal

The author used my favorite technique for getting up to speed on a company: analyzing a recent incident.

  Vanessa Huerta Granda — Jeli

There are a number of lessons I learned guiding weeks-long backcountry leadership courses for teens that I carried with me into my roles in incident management. In this blog post, I’ll share three that stand out.

  Ryan McDonald — FireHydrant

I really like these articles about interpreting SRE in a way that makes sense for your organization. SRE is still constantly evolving.

  Steve Smith — Equal Experts

The author led an incident just 3 months into their tenure. Here’s what they learned.

  Milly Leadley — incident.io

while SRE and DevOps type job explainers have been written ad nauseam, I found there’s relatively little online about Observability Teams and roles. I figured I’d share a bit about my experience on an O11y Team.

  Eric Mustin

I found the contrast between this one and the previous article interesting. The previous one includes a quote of Brendan Gregg:

Let me try some observability first. (Means: Let me look at the system without changing it.)

  Jessica Kerr — Honeycomb

In June, we experienced four incidents resulting in significant impact to multiple GitHub.com services. This report also sheds light into an incident that impacted several GitHub.com services in May.

  GitHub

Using the Webb telescope as an example, this article describes the progression of a system toward production operation using a metaphor of 3 days.

  Robert Barron — IBM