Skip to content

2 min read

About

Who writes MTTL, why and how to contribute.

I am Samuel Desseaux, an observability architect: I help organizations see what is happening inside their IT systems and use it to make decisions. MTTL gathers my notes, methods and recommendations on observability platforms.

In my view, when an observability project goes off the rails, the tool is almost always the last suspect. What actually breaks is a bill nobody saw coming, an on-call rotation that no longer sleeps, a platform nobody feels they own, or an executive committee that cannot see what it paid for.

This site starts from there. Technical topics get serious treatment, with complete configurations tested in a lab, a small environment you start on your own machine. In the courses, a configuration not yet run end to end says so. Each topic is also read from the point of view of finance, the organization and business lines.

Hence the name. MTTR (mean time to recovery) measures how long it takes to restore a service after an incident. You only bring it down once you have cut the time it takes to understand, the mean time to learn that gives the site its name.

I work as an observability trainer and consultant. The courses published here remain free. I declare here any current partnership with a vendor mentioned on this site and every page that mentions its product says so in a “Conflicts of interest” box at the bottom. As of this page’s last update, there is no current partnership. I am the author and maintainer of UniMetry, an open source project discussed on this site.

The labs and course material already published are on the Labs & Trainings forge, the project’s public code repository. To report a mistake, use the “Report an error on this page” link at the bottom of every page or write to me from the contact page.

The source code of the site itself is public on that forge, in the labstraining/mttl repository: every page links to its source through the “View the source of this page” link. What comes next is on the roadmap.

Text is published under CC BY-SA 4.0, lab configurations and code under Apache 2.0.