The future of SRE: STAMP?

[AntonioSousa]

"SRE has always worked to not simply react to failures, but to anticipate and prevent them. But anticipating failures has proven wickedly difficult at Google, a system defined by one of the largest codebases in history."

These two phrases were taken from this link. Wanted to share with you all, as it is something that I also see in all of my clients. Having a "systems" background, this makes total sense to me, and then there are things in this article that make total sense with Dynatrace...

[rgarzon1]

Thank you @AntonioSousa , 

One of the challenges I face is explaining the tangible actions of an SRE. Often, the role of an SRE is perceived as a collection of abstract concepts, making it hard to define actionable tasks. This is where STAMP becomes valuable—it provides a structured framework that translates high-level concepts into practical methodologies. STAMP not only introduces a systematic approach but also offers actionable steps that align with the responsibilities of an SRE, enabling them to implement processes that truly work in complex systems. 

probably its the "future" in big companies and in companies with less personal will keep the RCA and in future RcaCopilot or 5whys 😅.

part of my hobbie its read and collect blogs, logics, articles and put them in a page to the team can study.

after read the article this will be my focus. thank you again