Alloy: Docker discovery and label pipeline

13 min
Audience
beginner who has read lesson 01 of this module
Duration
35 to 45 min
Module
5/7
Target skill
read alloy/config.alloy block by block, follow a log line from the container to Loki in Alloy's interface, and diagnose an invalid configuration with the exact message

In one picture

In the archive room of lesson 01, someone has to do the office round, pick up the sheets coming out of the printers, stick on each one the tag of the right shelf, and carry the lot to the archivist. That someone is Alloy. Every five seconds it walks past each Docker container (the round), keeps only those of the lab (the sort), reads what they write on their standard output (the pickup), sticks service and conteneur on everything, and, for the API sheets only, opens the JSON to also stick niveau and code. Then it delivers to Loki. Its round file, alloy/config.alloy, is seventy lines and reads from top to bottom.

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.

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