Every log line, in one stream.
Everything your running containers write, interleaved by time. A container that starts or stops joins or leaves automatically. Filter by level, project or container until the line you need is left.
Too much to read?Read the comic: everything the kitchen says on one roll, and a filter that says what it hides →What you can do
One stream
All running containers, interleaved by time, joining and leaving as they start and stop.
Errors and warnings
Show only the lines that carry a level worth your attention.
Search with expressions
Several words that all have to match, !word to leave lines out, "a phrase", or an expression such as /error|warn/i, case-sensitive if you like. In the log tab of a container a stack trace matches as a whole.
One project
Follow only the logs of a single compose project.
Per container
Switch individual containers on and off, and turn everything back on in one click.
Side by side
Each container in its own column instead of one stream. Move a column, pin it to the left so it stays when you scroll sideways, or hide it, from its header. Each column scrolls on its own, or choose one scrollbar: every line on its own row, so what happened at the same time sits side by side.
JSON lines, formatted
A line that is a JSON object shows as its message with the fields behind it, here and in the log tab of a container, also when the object is written over several lines. The numeric levels of pino and bunyan colour the line. Search still looks at the raw text.
The fields of a line
A field of a JSON or logfmt line works in the search box: status>=500, level=warn, user.id=7 or msg~timeout, together with words and expressions.
Stack traces as one item
The lines of a stack trace or a Go panic sit under the line they belong to, as one item that opens with a click, here and in the log tab of a container. Search looks at all of its lines.
stderr marked
A bar next to the lines a container wrote to stderr, if you want it. Off by default, because many containers write everything there.
Filters with a name
Save the search, the levels and, if you like, the container choice under a name, up to twenty, for every machine or only this one. Apply one from the list, from Ctrl+K or on the log tab of a container, and share them as text.
A match in context
Found the line? Show it between all the others, highlighted, and go back to the filter with one click.
Save to a file
The whole log of a container as a file, from its detail page.
A notification on a log line
A rule on an error, a text, an expression or a field in a JSON log, and the app tells you when such a line appears, also on your phone if you like.
A new kind of error
The app learns which error lines a container writes. When one of a new kind appears within a day of an update or a restart, it shows up under Needs attention with an example and a button to the logs, and in the morning report. The first time it sees a container, it only learns.
Side by side
One column per container.
Switch the stream to columns when you want to see what one container does while another is busy. Each column scrolls and follows on its own, and the filters, the JSON formatting and the stack traces work the same way.
Honest filters
The filter tells you what it hides.
Lines without a recognisable level are hidden by the level filter, and the app says so. A stack trace is the exception: it stays with the line it belongs to, so an error keeps its trace. The count of filtered lines is always in view, so an empty screen never looks like a quiet system.
All features