Logs dock

The Logs tab of the bottom dock aggregates the logs of all the scenario’s micros live. It’s the heart of the dock: what you’d see in several terminals, in a single place.

Filter

• By micro — one, several or all. (The system sources also work: engine, mock, docker.)
• By level — All, Info+, Warn+ or only Error.
• Search — the magnifier filters by text within what’s shown.

The filters combine.

Follow the tail

Follow keeps the automatic scroll stuck to the last line. You can make it active by default when launching a scenario in Settings → Behavior.

Pause

Pause freezes the view without losing anything: lines keep arriving and, while paused, a chip next to the counter says how many new ones there are. When you resume —with the same button or by clicking the chip— they all show up in place. With micros picked in the filter, only those are paused and the rest keep running; with no filter, the whole console pauses. What is held counts towards the view’s line limit: if a long pause goes over it, the oldest lines leave the view but stay in the full log.

Actions

• Copy the selected lines to the clipboard.
• View formatted — lines carrying a JSON or XML body show a magnifier on hover: it opens the body in a large viewer, indented and coloured, with the option to see it exactly as it arrived and to copy it. It only shows on those lines; on the rest there would be nothing to format.
• Clear the logs from the view (of the selected micro or all); it does not delete the file, so the exported report and the CLI’s aseptic logs still see everything.
• Open full log — the session file, which keeps all the content (the view only keeps a line limit in memory, configurable in Settings).

From the CLI

aseptic logs [micro] [-f] [-n N] [--errors] [-g pattern]. Without a live engine it still works over the persisted session.log: the logs are still there after something crashes. See Debug a micro that won’t start.