Scenarios section

The Scenarios section is where you compose and operate your scenarios. On the side you have the list of scenarios; in the center, four views of the active scenario.

Create and edit

New scenario opens the editor: name + the micros that make it up.
Edit (top bar) returns to that editor to change its composition.
Delete (item menu on the side) removes the scenario; asks for confirmation.

The four views

Cards — one card per micro with its status, port and mode (native/container toggle).
Table — the same information in rows: status, start, endpoints and mode. Each row’s toggles and links stay inline.
Graph — the who-calls-whom call graph, with each edge’s color according to its resolution (local, cloud or mock). You can zoom in, zoom out and fit to view.

All three offer the same action menu on a micro: it opens from the «⋮» on the card or the row, and with a right click on any of the three (on the graph, over the node). It carries opening the configuration, viewing that micro’s logs, restarting just that one while the scenario is running, opening each published endpoint (API, Swagger, health), opening its repository folder and copying the effective command it starts with.

Dependencies — the local/cloud/mock selector per dependency, with the “requires connection” notice if something points to the cloud. See Dependencies.

Operate the scenario

From the top bar:

▶ Start / ■ Stop — a single button that starts or stops depending on the state. It starts the infra, resolves ports, rewrites URLs and launches each micro; when stopping, it stops micros, containers and infra.
Clean — terminates orphaned native processes and removes residual aseptic-* containers. Useful if something got stuck.
Seed data (scenario menu in the sidebar, with the scenario running) — runs the post-migrate steps of its micros (for example, a seed) after the first migration. It only shows up if some micro declares them.

Debug a micro

Debug (the micro’s action menu, in any of the three views) makes it start with its debugger open on 127.0.0.1; if the scenario is running, it restarts only that micro. It is saved in the scenario, like the mode, and it does not travel when you export it or publish it to the team catalog.

Spring Boot and Quarkus — JDWP, on a port of its own that is remapped if taken (5005 by default).
Node — the inspector, in the process that serves the app rather than in npm (9229 by default).
.NET — attach by PID: the process listening on the micro’s port.
Python — debugpy (5678 by default): the micro starts through it, so its command has to begin with python or with a server that can also run as a module (uvicorn, flask, gunicorn, fastapi, hypercorn). You install debugpy yourself in the repo’s .venv (pip install debugpy).
Go — Delve (2345 by default), with a go run <package> command: it builds without optimizations so variables are visible, and the binary goes to the temp folder, not to the repo. You install Delve yourself (go install github.com/go-delve/delve/cmd/dlv@latest).

If debugpy or Delve is missing, or the command doesn’t have one of those shapes, Debug says so instead of turning on, and the scenario check warns with the command to install it.

Native mode only. The card shows the debugger’s port (or PID), and Copy debugger configuration puts the entry for VS Code’s launch.json on the clipboard. From the terminal: aseptic debug <micro> on|off; without an argument it tells you how to attach, also from IntelliJ.

Run history

Every time you start a scenario, a run is kept until you stop it: when it was, how long it lasted, how it ended (OK, with crashed micros or never came up), each micro’s last state with its errors, and the calls the mocks served. Run history (the scenario menu in the sidebar) shows them with their logs, filterable by micro and by errors: it’s what to look at when “it worked yesterday” and nothing is running anymore.

The last 20 are kept; Pin one to stop it from being pruned. From the terminal: aseptic runs, aseptic runs logs <id>.

Health at a glance

The scenario’s health summary (no issues / starting / with errors) is in the top bar and opens the Status tab of the dock. Each micro goes through the states Stopped → Starting → Healthy (or Unhealthy / Crashed). See Micro states.

Exporting/importing a complete scenario is done from the side menu. See Share a scenario.