Operations | Monitoring | ITSM | DevOps | Cloud

A guide to set practical Service Level Objectives (SLOs) & Service Level Indicators (SLIs) for your Site Reliability Engineering practices.

DevOps is the modern convergence of people, processes and tools to create a continuous software delivery stream. Much like the code it produces, the concept of DevOps itself is continuously adapting to encompass new ideas, methods, and technologies. So what can we expect from the DevOps cultural shift in the future? The delivery stream of yesterday was a segmented process, often separating key teams and concepts into silos where people focused on their individual tasks.

History will look back on this period of the 21st century as a pioneering, resilient, and excitingly disruptive time. We’re deep into a dynamic era as the cloud, Artificial Intelligence (AI), IT automation, and digital transformation converge to drive challenges and dazzling opportunities. The sheer force and potential of AI—coupled with unprecedented security risks and ongoing infrastructure advances will shape enterprises for years to come.

As a former incident responder and now as a responder advocate for FireHydrant, I’ve seen the “build vs. buy” debate play out many times. In fact, I even supported the tool that former employers used for managing incidents for years before they decided to buy (more on that in a future blog post).

Why do some organizations excel in streamlining their database operations and applications development while others find it immensely challenging? Why can some database teams embrace agility while others take months of cycles to deploy even a single line of code? What secret sauce can allow some database teams to work smarter (not harder), streamline database development lifecycles better, get to deployment faster, and create an overall stronger alignment across departments?

In this podcast, our panellists discuss the foundations that any team needs to put in place when designing their incident management process. Starting from the basics of defining what we really mean by an incident, to how to set your severity levels, roles and statuses, Chris and Pete share their tips for building solid foundations to run your incidents.