Skip to content
Commitpedia
Log in Join & edit

What is a log?

A log is a running record of what a program did and when, written to a file so you can look back when something breaks.

Drafted with AI from official documentation. Scripts were run in a test environment and repository links verified. Awaiting a human check. Did it work for you? Last edited Outdated?

Edit history of What is a log?: 1 recorded edit
Edit history · 1 edit
Type
Article
Edits
1
Editors
1
First issued
15 Oct 2026
Last edit
15 Oct 2026
Reading
1 min

A log is a chronological list of messages that a program writes while it runs: it started, it handled a request, it failed to connect. Think of a ship’s logbook: nobody reads it on a calm day, but after a storm it tells you exactly what happened and in which order. Each line usually carries a timestamp and a severity such as INFO, WARNING or ERROR.

Logs live in /var/log on Linux, in the systemd journal, in the output of docker logs, or in a central tool like Loki or Elasticsearch on bigger systems. The first thing anyone does when a service misbehaves is read its log. Good logs are plain text, one event per line, and rotated so they do not fill the disk.

tail -f /var/log/syslog
journalctl -u ssh --since today
docker logs -f web

See also: What is a daemon or service? and What is a process?

Did this work for you?

No votes yet. Be the first.

If it did not work, the report form below tells the editors what went wrong.

See also

Repos in the wild

History

Every saved edit is kept. The plot on the sleeve draws one line per edit. Open any edit to see exactly what changed.

  1. Dominik +808 chars

Report a problem

Something wrong, unsafe or copied? Tell the editors.
What is wrong?