Observability

Transcript

1. Observability
2. Ramez Hanna @informatiq Ramez Hanna @InformatiQ Leading Observability @CriteoEng (we’re always hiring)
3. Ramez Hanna @informatiq Disclaimer This is the result of my learnings from people, books and experience This is my view on the subject, hence you can disagree with me Our understanding of things evolve
4. Ramez Hanna @informatiq “A measure of how well internal states of a system can be inferred from knowledge of its external outputs.”
5. Ramez Hanna @informatiq “ The act of exposing state, and being able to answer 3 questions • What is the status of my system? • What is not working? • Why it is not working? ”
6. Ramez Hanna @informatiq Know what is happening Discover new failure modes (unknown unknowns)
7. Ramez Hanna @informatiq Ceci n’est pas observability Logs Metrics Traces The best observability product
8. Ramez Hanna @informatiq WHY WHAT HOW Ensuring that teams are good at observing their systems We want it to be intuitive, and effortless. Workshops, documentation, integrating tools
9. Ramez Hanna @informatiq You need observability owners
10. Ramez Hanna @informatiq Observability is abut people and practices
11. Ramez Hanna @informatiq People Focus on the people not the infrastructures
12. Ramez Hanna @informatiq Observability owners should raise awareness and spread knowledge about practices
13. Ramez Hanna @informatiq Tools are observability enablers
14. Ramez Hanna @informatiq Remember • Observability is a about people and practices • Observability is not tools, tools are enablers • You don’t need a team, you need people who care
15. Ramez Hanna @informatiq Thank you