Skip to content
>devspeak
← glossary
level 2Bugs & Debugging

Logs

also: log, log file, log files, server logs

A running record your app writes as it works, noting what happened and when, like a diary you can read later.

a bit more technical

Timestamped text entries written by an application or server as it runs, usually tagged with a level such as info, warn, or error. Logs are the main way to see what happened in a system you can't watch directly.

picture it

A ship's logbook. The captain notes course changes, weather, and problems as they happen. After a storm, you read the log to piece together what went wrong.

why it matters

When something breaks in production, logs are often the only evidence. Pasting the relevant log lines to your agent turns a guessing game into an investigation.

what your agent might say
agent
The logs show the payment notification arriving at 14:02 but no 'order saved' entry after it. The failure happens between receiving it and writing to the database.
how you might use it
you → your agent
Here are the logs from the last failed signup. Read them and tell me which step failed before you suggest any changes.
common mistake

Thinking logs record everything automatically. They only contain what the code was written to log. If nobody logged a step, there's no record of it.

builds on