---
id: "prereq-observability"
type: "prereq"
source_timestamps: ["00:02:46", "00:02:59"]
tags: ["devops", "sre"]
related: ["claim-observability-insufficiency", "contrarian-observability-is-not-understanding", "quote-observability-vs-comprehension"]
reason: "Required to understand why standard DevOps monitoring tools fail to solve the root problem of Dark Code."
sources: ["s23-amazon-16k-engineers"]
sourceVaultSlug: "s23-amazon-16k-engineers"
originDay: 23
---
# Knowledge of Telemetry and Observability

## What You Need to Know

**Observability** is the modern DevOps/SRE discipline of instrumenting production systems with metrics, traces, and logs so that operators can detect, diagnose, and resolve incidents. Common tools include Datadog, New Relic, Honeycomb, Grafana, and Splunk.

## Why It's a Prerequisite Here

The speaker's central distinction — articulated in [[claim-observability-insufficiency]], [[contrarian-observability-is-not-understanding]], and [[quote-observability-vs-comprehension]] — is between:

- **Observability** = measurement of system health and breakage
- **Comprehension** = understanding of why the code is shaped the way it is

Without familiarity with what observability tools actually do, the speaker's critique sounds like a general anti-monitoring stance. It is not. He explicitly endorses telemetry as valuable. The argument is that telemetry is *insufficient* for [[concept-dark-code]] because measuring breakage does not produce comprehension of the underlying logic.

## Quick Mental Model

```
Observability tells you : THAT something broke and WHEN
Comprehension tells you : WHY it was built this way and HOW to fix it
```

The two are orthogonal. You can have either without the other. Dark code is the case where you have observability without comprehension.