ConceptsLogs & events
The three logs
Ferry has a deploy log, a runtime log and a job log. Each one has its own place.
| Log | What it has | Read it |
|---|---|---|
| Deploy log | The build output and the deploy steps of one deploy | ferry logs --deploy ID |
| Runtime log | What the containers of the service write to and stderr | ferry logs NAME |
| Job log | The output of one job run | ferry logs --job ID |
Where a log is, and how long
| Log | Place | Kept |
|---|---|---|
| Deploy log | <data-dir>/logs/deploys/<deploy id>.log | Until you delete the service |
| Runtime log | In Docker | As long as the containers exist. Docker rotates it at 10 MiB × 3 files for each container (the default). |
| Job log | <data-dir>/logs/jobs/<job id>.log | For the newest 100 runs of each service |
The parts of a line
09:38:31 ==> Starting 1 instance(s)
09:38:31 [2fa90d] docker-echo listening on :8000Each line has a timestamp and a stream: stdout, stderr or system. A line of a runtime log also has its instance.
The messages of Ferry are system lines. They start with ==> .
Ferry can stream each of the three logs live with Server-Sent Events. See Stream logs with the API.