Atlas · building
Logs
The running record of what a program did, and the first place to look when something goes wrong.
In plain words
A log is a program writing down what it is doing, line by line, as it goes. When something breaks, the log is how you find out what happened.
How it works
The Twelve-Factor App defines logs as the time-ordered stream of events from all running processes and services. It says an app should not manage log files itself: each process writes its events, unbuffered, to standard output, and the environment collects them.
Going deeper
Logs are also a gift to an agent debugging your code. Pasting the exact error line beats describing it. Take care with logs that print secrets: whatever the agent reads goes into its context.
Sources
- The Twelve-Factor App: Logs Adam Wiggins
Logs are the stream of aggregated, time-ordered events collected from the output streams of all running processes and backing services.
A twelve-factor app never concerns itself with routing or storage of its output stream. It should not attempt to write to or manage logfiles. Instead, each running process writes its event stream, unbuffered, to stdout.
Quotes were checked against the live pages on 2026-11-12.