One of the most important steps in an incident’s lifecycle is the postmortem. It provides an essential time to reflect on what happened, what could have been done better, and how to build more resilience into a system. But we consistently hear from engineers that incredible toil is typically involved in coordinating stakeholders to write good postmortems.

With Priority-Based Alerting, you can set different notification rules for high and low priority incidents.

Everybody puts value on work. But not all work is the same or valued in the same way. What if we told you there’s a way to gain/protect up to $1 million in new revenue, reduce unplanned downtime by more than 60%, and improve team productivity by nearly 25%? This is where the differentiation of work comes in. Most of our day-to-day work is planned out; i.e., it’s work with structure.

Event and alert severity are extremly important information for an effective alert management and response. Severity information determine the speed of response, needed resource allocation and the action path taken. Naturally, critical alerts have higher priority than major alerts which again overrule minor alerts.

Atlassian and Opsgenie are among the most popular apps in the Okta network this year, according to a new report from the security company. From the report: Okta’s Business @ Work 2020 Report takes an in-depth look at how organizations and people work, exploring industries and customers, and the applications and services they use to harness productivity.

This is the one post I hope you’ll never need. However, should you ever need it, this is your one-stop shop for understanding how to proceed with DevOps incident management. Have you just been attacked? Did the commit go wrong? A CI pipeline went haywire? Don’t worry. I got you.

With most businesses finding it hard to achieve a 99.9% uptime throughout the year, achieving a goal of 99.999% uptime looks daunting to developers. Here’s how to reach 99.99% uptime for your business. It’s like asking someone to build a bridge that would never collapse or a machine that would never break down no matter what. In short, it is a hard goal to achieve but yes it is achievable.

Hiteshwar is an SRE based out of Mumbai, India. His area of specialization is in distributed systems. He works on Kubernetes, running his own custom clusters, maintaining them and creating tools to manage and monitor them. He likes to share his learnings by writing articles and blogs on Medium and Linkedin. He is an active speaker in meetups and developer groups and also teaches DevOps and SRE practices at learning centers.

Here’s a quick checklist to publish articles or guest posts on Fyipe Blog. We invite anyone to publish stories to any of our publications. If you wish to contribute. Please send an email to [email protected] with your draft article. Please make sure your draft article follows guidelines in this post. Here’s what all this means for you as a writer: Educate your readers and teach them something new. Cut all the fluff. Get to the point — fast. Do not waste their time.

A lot of tech companies struggle with creating an effective and efficient on-call schedule internally for their product and service, this results in much longer downtimes when something goes wrong. They often over-burden their team members with repeated on-call duty which results in team member fatigue. Here’s how to create an on-call schedule that your team might love.