Operations | Monitoring | ITSM | DevOps | Cloud

The growth of site reliability engineering (SRE) has demonstrated the need for SRE implementations is here to stay for the foreseeable future. LinkedIn voted SRE jobs as the second most promising positions in the US in 2019, and now as we head into 2022, you can be sure to see the evolution of SRE continue to grow and expand. Below, we’ll get into what SRE is, what SRE engineers do, and how SRE will continue to evolve into the future.

System Administrators (SysAdmins) often represent the core of IT organizations. SysAdmins manage the organization's computing infrastructure, encompassing servers, virtualization, networking, and storage. For many years, the term System Administrator, or SysAdmin, was typically associated with Linux or UNIX systems.

An analysis of SRE job descriptions from 4 companies highlights what businesses actually expect SREs to do.

In the second half of 2021, eG Innovations partnered with the DevOps Institute to conduct an online survey of more than 900+ individuals from Sys Admin, DevOps, SREs, and other IT backgrounds. We asked questions about: Some of the results included: You can download the full survey results here: Cloud Technology Adoption Trends | eG Innovations If surveys and statistics on technology adoption are of interest, we have some other recent ones available, conducted in the last 12 months,.

Many of the concepts SREs take for granted about incident management originated with efforts to fight fires in California in the 1970s.

Unlike traditional IT Ops, the role of the SRE isn’t simply focused on finding and solving technical problems. The big win for today’s SREs is supporting the organization’s strategic innovation initiatives. With the appropriate observability capabilities, it’s possible to quantify the value that software infrastructure contributes to this innovation effort.

An overview of major IT incidents and outages in 2021

The term Site Reliability Engineer (SRE) first appeared in Google in the early 2000s. In Google’s 2016 SRE Book, Benjamin Treynor Sloss wrote that, generally speaking, “an SRE team is responsible for the availability, latency, performance, efficiency, change management, monitoring, emergency response, and capacity planning of their service(s).” This means that the SRE teams at Google decide how a system should run in production as well as how to make it run that way.