In our recent “IT Ops Demystified – Event Chaos or Enrichment?” webinar our field CTOs discuss how enrichment can help reduce operational costs by an order of magnitude. Here is a quick overview of all the goodness that you’ll be watching.

Site Reliability Engineering (SRE) is a practice for managing the reliability of systems that began at Google in the early 2000s. Ben Treynor Sloss from Google started the first SRE team and coined the name.

Most companies today compile a set of metrics for their product teams to regularly report on to the company management. This includes a variety of product performance metrics(usage frequency, churn rate, NPS, etc.). But a lot of them struggle a bit with product discovery activities. So how do your track discovery?

I can tell you the day I knew I would be a Systems Administrator (the term SRE hadn’t been invented yet.) My Linux professor, a brilliant engineer at NASA, said: "The best system administrators are the laziest." He went on to qualify that statement but I had stopped listening. My fate was sealed.

With the difficulties we’re facing during this time, it can be difficult to keep up with the increasingly vast demand for our services. You need to make use of all the tools in your toolbelt in order to conserve your team’s cognitive resources. Two ways you can do this are through automating toil from your processes and prioritizing with SLOs.

In the second part of our "SLOs for AWS-based infrastructure" blog , Gigi Sayfan dives deeper into understanding the landscape of AWS compute by using the lens of Kubernetes to compare and contrast & covers in detail setting of SLOs for ECS, EKS, Fargate, and Lambda based services.

If you’ve been following the U.K. healthcare landscape, you would know that the country has been considering replacing pagers for the longest time. This may soon materialize, partly accelerated by the challenges that doctors are facing during the COVID-19 pandemic. The pager replacement initiative not only signifies a pivotal shift from the aging infrastructure, but it also indicates how pagers have failed to thrive in today’s unprecedented times.

Between COVID-19 and the typical summer slow down, offices are emptier than they’re ever been. With team members taking some much-needed time off, it’s important to know how your team will be affected. Here are some tips to help your teams function during this time of flux.

Constantly talking to your users about their business problems and incorporating those solutions is key to the success off your product and company. There are many ways to incorporate the voice of your users into your product planning. Formulate an experience brief that’s less than 2 pages, or a 5-minute clip of user interviews. The best is to have devs in the interviews and discovery activities with you as well.

PagerDuty sat down with J. Paul Reed, a Senior Applied Resilience Engineer at Netflix, for an Ask Me Anything (AMA) to discuss best practices around postmortems. Reed is a prominent speaker and advocate of DevOps and operations complexity, and has over 15 years of experience in release engineering. His background in tech, along with his previous work at companies like Mozilla and VMware, give him a unique perspective into the inner workings of innovative organizations.