Logs, metrics, traces
On This Lesson 4 topics
This lesson is planned. The outline below lists the topics it will cover. The full lesson has not been published yet.
In this lesson
know which signal answers which question.
Planned topics
- Metrics: numbers over time, cheap, good for "is something wrong and how much?".
- Logs: events with detail, good for "what exactly happened here?".
- Traces: one request's path across services with timing, good for "where is the time spent?".
- Use counters for counts; do not log a line per event to count it.
- Keep metric labels low-cardinality (route, status), never user or order ids.
Draft outline details
Demonstration
table: question | signal | Shop example.
Check your understanding
Which signal shows where a request spent its time?
Show answer
A trace.
Practice
Apply this lesson with the module's lab, exercises and quiz.
Marking a lesson complete is optional and you can undo it any time. Your progress stays in this browser.