Logs, metrics & traces
Correlate three kinds of evidence
Lesson 13 of 20 · 12 min · Module 5: Evidence and tested recovery
Different signals answer different operational questions.
Start this lesson →Free. No installation: you write and run the code in your browser, and it is checked automatically.
By the end, you’ll be able to…
- Use metrics to locate the symptom
- Use logs and traces for context
The idea
This practice runbook is an ordered sequence of the teaching actions named in the task. Each action changes or observes the supplied in-memory scenario.
01Use metrics to locate the symptom
Metrics summarize behavior across time or many requests. A ratio identifies the scale of the symptom but not necessarily the cause of an individual failure.
02Use logs and traces for context
Logs record events; traces connect work within a request across components. Correlating them can reveal which dependency or operation deserves attention.
03Collect before changing the system
The runbook is a Code Temper teaching format, not Ansible or a standard automation product. Its collect actions return the scenario evidence without contacting services.
Your turn
What the checks look for
- Collects every signal
- Does not change the active release
Take this with you
Correlate signals and keep observations separate from conclusions.
Go a little further
Describe which shared identifier would help connect a log entry to its trace.