The unexpected and sudden shift to remote working introduces a new set of problems within the incident response space. And while each organization needs to take its own unique circumstances into account, this post outlines the best practices and steps that can be taken in the right direction in keeping operations both productive and proactive.

Here's a curated list of “Must Read” books specific to the Incident Management space, suggested by folks from the SRE and DevOps community to help you understand what changed their perspective of software engineering as a role.

Monitoring has moved from a simple proactive practice to a necessity on any product launch checklist. It is crucial to pick a tool that meets your observability needs & ensures reliability of your service to your customers. Over the years, with an increase in adoption of DevOps and SRE practices, Monitoring has moved from a simple proactive practice to a necessity on any product launch checklist.

In this blog, Danny Mican, a Senior Site Reliability Engineer, outlines how to implement SLOs from scratch using the IIDARR process. He also states it is extremely crucial for your SLOs to be actionable and is always following a feedback approach as it will play an important role in the debate of Features Vs Technical Debt.

Hrushikesh is passionate about making a complex design with simple and reliable solutions. He is technology and platform agnostic and doesn’t believe in limiting himself to just a few. He started his career in 2006 with a Media company where he was responsible for introducing new technologies along with driving a team to deliver quickly. He does not limit his role to just development and operations and loves exploring everything in the tech space.

What you absolutely must know when responding to an incident is what kind of impact it has on customers and how negatively it can affect your team. This is typically addressed by following some kind of incident classification, usually “incident severity levels”, to indicate the importance of every incident - that is, to understand how seriously various stakeholders are affected and to route the incident differently if necessary.

It shouldn’t take you more time than a few seconds to understand your on-call schedule and rotations and how you could make changes to it. It is important for on-call scheduling and alerting tools to make this as simple as possible. If you’re spending more than a few seconds to understand what your on-call rotations are going to be like for the next day or week or month, then you need to start looking for a better on-call management tool.