Archive Topic Map
Observability
Observe to decide. Decide to change. If you change without evidence, you lose the only chance to learn.
Orientation
A curated shelf for study and for retrieval.
Signal discipline
More telemetry is not automatically more truth. Without governance you get cardinality storms, invisible costs, and a system you cannot reason about when it matters.
The Order’s observability posture is simple: small sets of signals that explain causality, saturation, and risk.
- Events explain platform decisions; logs explain workload decisions.
- Metrics reveal saturation and error budgets; traces reveal causal chains.
- Audit logs matter because authorization is part of correctness.
Core texts
Revelation without noise.
Text
FeaturedThe Dark Order’s Guide to Observability in Kubernetes
Logs, metrics, traces, events, audit—and their failure modes.
Text
Codex GigasObservability for People Who Carry the Pager
What to measure, what to ignore, and why governance matters.
Text
Codex GigasTraces, Metrics, and the Reading of Omens
Causality, saturation, and the hard edges of telemetry systems.
Operator practice
Evidence-first workflows that survive incidents.
Related maps
Adjacent shelves for continued study.
Topic map
MapTroubleshooting
Continue with the adjacent shelf.
Topic map
MapOperations
Continue with the adjacent shelf.
Topic map
MapSecurity
Continue with the adjacent shelf.
Canonical link
Canonical URL: /library/topics/observability