We need to find ways to bridge the gap between individual contributors and execs so that both points of view are understood and business outcomes don’t get lost along the way.Ī powerful way to do this is to introduce a new executive role: the chief reliability officer (CRO). A dichotomy exists between individual practitioners and executives on various crucial DevOps concepts such as tool sprawl. Ultimately, reliability is a business-level metric. As we move forward, systems are only going to become more complex, so the sooner we embrace the role to get ahead of the next set of problems, the better. SRE is about connecting the dots between different pieces of telemetry as quickly as possible. By accruing data through monitoring and telemetry, we acquire the potential for knowledge. Reliability is about scale, but it’s also about power. Give them interesting work and let them work. They can improve infrastructure and automation, increase reliability, enable a different level of incident management and, if you let them, transform the culture. They can bring a new mindset to the work, looking at day-to-day operations from an objective standpoint. SREs are the agents of internal and external change. Remember, SRE is not ITOps with a fancy title rather, it is a transformative role. Hire site reliability engineers (SREs) at the right time for your organization. So how can organizations go about improving reliability and achieving internet resilience? Here are five suggestions.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |