Installation logs

The DataMind Installer can stream one combined feed of every container on the host, including stopped ones, and download the same logs as a plain-text file. Use it when you need everything in one place, or a file to send to support.

Both are admin-only and part of the Installer's API. For one service's log and a job's output on the screens, see Service status; for where logs live and how long they are kept, see Health, monitoring and logs.

Watch the combined live feed

Open the feed at the Installer's address while you are signed in as an admin:

http://<host>:8000/api/deployment-log

One live stream then shows every container on the host, stopped ones included:

• Every line is prefixed with its container: [<container>] <line>. Lines keep their Docker timestamps.
• It opens with about the last 200 lines per container, then follows new output live from there.
• A container whose logs cannot be read shows [<container>] ERROR: <message> lines instead of its output, with An unknown error occurred when the reason is not readable. The rest of the feed carries on.
• If no container gives a readable log, the feed closes straight away.

The feed also takes since, until and containerName; set an until time and it returns that fixed window instead of following new output.

Download the logs as a file

The download takes the start of the window you need:

http://<host>:8000/api/deployment-log/download?since=2026-10-15T08:00:00Z

It answers with a plain-text file named logs-<ISO>.txt, one line per log entry with its container and its timestamp. Blank lines are dropped. No line or size cap is applied: the window you pick decides how much the file holds.

To send logs to support, start since shortly before the problem and leave until unset to take everything since.

These routes follow the Installer API's rules: unknown fields are dropped, and request bodies are capped at 5 MB. They are listed in the API description at /api/docs when it is enabled on the host.

Questions, answered

Does the feed include containers that are stopped?

Yes. The feed and the download cover every container on the host, including stopped ones.

Can I get one container's logs only?

Yes. Set containerName on the feed or the download to limit it to one container.

How far back do the logs go?

The live feed opens with about the last 200 lines per container and follows from there. For older entries, download a window that starts earlier. How long each log itself survives is up to Docker; Health, monitoring and logs covers where logs live and how long they are kept.

Is there a limit on the downloaded file?

No line or size cap is applied. The since and until window decides how much the file holds.

Why does every line start with a name in square brackets?

One feed merges many containers. The prefix says which container a line came from.

What does [<container>] ERROR: ... mean?

That container's logs could not be read. The message says why, or reads An unknown error occurred. The rest of the feed carries on.

Why does the feed close as soon as it opens?

No container gave a readable log. The feed has nothing to show, so it ends at once. For a failed service or update, see Troubleshooting.

Who can open the feed or download the file?

Admin accounts only. Every other account is refused. Roles are set on Users.

Is this the same log as on the Status screen?

It reads the same source, the host's Docker logs. Status shows one service's log on the screen; the combined feed merges every container into one stream and adds the file download.