SLOConf Logo
Back to speakers

Yury Niño Roa

SRE Technical Program Manager @ ADL Digital Labs

Bio

Site Reliability Engineer, SRE Technical Program Manager and Chaos Engineering Advocate. Software Engineer with 7+ years of experience designing, implementing and managing the development of software applications using agile methodologies such as scrum and kanban. 2+ years of hands-on experience supporting, automating and optimizing mission-critical deployments. Experience with on-premise and cloud architectures and foundations both on the coding and deploying systems. +1 year as Technical Program Manager of a Site Reliability Engineering Team, designing and architecting software to improve availability, scalability, latency and efficiency. Professor of Software Engineering and Researcher with interest in solving performance, resilience and reliability issues, using chaos engineering and studying human factors, safety on systems and lack of monitoring and observability.

Social Media

Defining a Maturity Model for SLOs

Service Level Objectives or SLOs are a quantitative contract that describes the expected service behavior. They are often used by Organizations to prioritize the reliability, availability, coverage, and other service-level indicators of the software systems. Based on what I have learned defining and implementing SLOs, I have discovered that they are valuable when they are used to build feedback loops in two axes: adoption and automation. SLOs are a process, not a project, which imposes a need for having a framework that helps organizations to adopt a culture based on SLOs. In this talk, I am presenting a framework that allows determining the level of adoption and automation of SLOs. Based on questions related to the amount of convincing: engineering, operations, product, leadership, legal, and quality assurance, we determine the level of adoption. On the other side, considering aspects such as established and documented measurements, the level of user-centric metrics, observability strategies, and reporting toolsets, we determine the level of automation.

Watch Talk