Guided practice — Find the request that produced the 500 error

Guided practice22 min
Duration
50 to 70 min
Module
5/7
You will build
a complete investigation, from a user's complaint to the exact log line of her request, then the proof that everything is back to normal
Deliverable
a real id_requete tied to its route, its course and its 500 code, and two curves (Prometheus and Loki) that drop back under the alert threshold

How to read this page. Long sections are folded: click "Show …" to open them. Read in order: Objective, In brief, The dataset, First queries, then Loki, in Grafana Explore (L1 to L12) and Prometheus, to cross-check (P1 to P4). The queries are typed in the browser; they are identical on Windows and Linux. For the terminal commands (break, reproduce, repair), open one annex only: A if you are on Windows (PowerShell), B on Linux, macOS, WSL 2 or Git Bash. Annex C is shared.

Preview — the rest of the lesson is for enrolled readers.

Already enrolled with a code?

Your access is tied to your account, not to this link. Sign in with the same email you used in class: your course is waiting, no need to enter the code again.

Sign inNo account yet? Create one
This lesson is part of the “Logs: Loki, Alloy and LogQL” module

The first modules of the course are open to everyone. For the rest you have three options: buy this course once and for all, subscribe, or enter the code handed out in class.

Subscribe — 19 $ US/monthBack to the outline
Are you a student on this course?

The code is tied to your account: sign in or create an account and it will be applied automatically when you come back.

No account yet? Create one