Skip to content
NEWRunning the LGTM stack with a team of two

Observability, from signal to decision

One shared language for production, from the engineer reading traces to the executive making the call.
reading planes
4
courses
9
interactive tools
14
ObservabilityThe samefactsEngineerArchitectManagerLeadershipSalesBusiness
Everyone arrives by their own road. In the middle, the same facts.

One Tuesday morning, payments slow down on your website. The on-call team searches for an hour. The sales director asks how many sales were lost and nobody can tell him. The scenario is made up, but you may well have lived through it.

MTTL stands for Mean Time To Learn, how long it takes to understand. The name echoes MTTR, the mean time to restore a service after an incident: you can only fix quickly what you’ve first understood. Observability is the ability to understand what is happening inside a system through the signals it emits about itself, such as a number, a message or the path of a request. This site helps shorten that time and get from those signals to decisions, from the on-call team to the boardroom. Why this site →

Not sure where your organization stands? The self-assessment takes ten minutes and suggests an action plan. Otherwise, start from your role:

Read the video text

Observability. Understanding a system from what it lets you see.

A very old idea.

  • Antiquity: In Egypt, nilometers measure the Nile flood to anticipate the harvest and set taxes.
  • 1788: Watt’s flyball governor regulates the steam engine’s speed on its own.
  • 1868: Maxwell describes how these governors work in equations.
  • 1960: Rudolf Kálmán defines observability: inferring a system’s internal state from its outputs.
  • 1988: SNMP: querying network equipment.
  • 1999: NetSaint, later Nagios: monitoring with checks and thresholds.
  • 2010: Google describes Dapper: following a request across distributed services.
  • 2012: Prometheus is born at SoundCloud: labelled metrics, queried on the fly.
  • 2019: OpenTelemetry: an open standard to collect telemetry.
  • Today: Observing AI systems too, which can answer fast and wrong.

From monitoring to observability. Monitoring: Is it working? Metrics and thresholds set in advance. Observability: Why is it behaving this way? Questions nobody planned for. The signals: Metrics, Logs, Traces, Profiles, Events.

The goals: Detect, Understand, Decide, Learn. Shorten the time between the incident and the lesson: Mean Time To Learn.

What is at stake:

  • Business: The cost of outages and of telemetry itself.
  • Organization: The evidence required by NIS2, DORA, the AI Act.
  • People: Sustainable teams and on-call.
  • Business lines: The trust of customers and users.

The layers of observability:

  1. Field: industrial OT, PLCs, sensors, IoT
  2. Network: links, protocols, latency
  3. Infrastructure: servers, storage, GPUs
  4. Platform: containers, cloud, high performance computing
  5. Applications: services, APIs, user experience
  6. Data: pipelines, quality, freshness
  7. AI and models: LLMs, agents, evaluation

Security, Cost and business value: across every layer.

MTTL, Mean Time To Learn: Observability, from signal to decision. www.meantimetolearn.com: Launching on October 7, 2026.

Music: “In the Aftermath”, Michael Rothery (Epidemic Sound).

The interactive layers diagram then takes over. It walks through each layer, from the industrial field to AI models, with what you observe there, the signals, the indicators and the tools.

The same signal says something different depending on who reads it. On-call watches how fast the payment responds. The sales director wants to know how many carts were abandoned at that step. It is the same fact, told in two languages.

Technical signalFor whomWhat it becomes
payment service latencyBusinesscarts abandoned at the payment step
tokens consumed by an AI featureFinancecost per customer conversation
retained traces and logsComplianceevidence that holds in an audit
night alerts per personManagementteam sustainability
measured availability (SLO)Leadershipservice commitment to customers, kept or not

Every article ends with a box saying what the topic changes outside the engineering team.

The full approach →

A lab is a small environment you start on your own machine to try things for yourself. Those published so far are freely available on the Labs & Trainings forge, the public repository where I keep the lab code and the course material. The Labs page says which exist and which are in preparation. My videos, on projects close to MTTL, are on the YouTube channel; a first lab demo, for HPCOBS, is already online with more to come (see Videos).

  1. BusinessRunning the LGTM stack with a team of twoMimir, Loki, Tempo and Grafana are rarely rejected for lack of power. Small teams give up because of everything around them. What that work costs, how a distribution can take it on. And when to choose… · 8 min
  2. PeopleHow do you interview an observability engineer?A short, structured hiring process for observability and reliability profiles: the steps, questions by theme with what a good… · 11 min
  3. PeopleHow do you write an observability job description?The structure of a job description that attracts the right observability and reliability profiles, common mistakes, what the law… · 6 min
  4. PeopleWhich profiles should you hire for observability?Five profiles that keep observability alive, the skills expected at each level up to staff and principal, the management ladder… · 10 min
  5. PeopleHow do you write the job description and prepare the interview?Pick one of fourteen profiles (engineering, management, architecture, pre-sales, product, incidents, detection, consulting), a… · 1 min

To follow new publications: the RSS feed.