Open the log stream for the stage you are debugging
Keep dependency and compilation output separate from the running process.
Logs
Know what shipped, what is running, and where a release failed.
Build logs, runtime logs, source artifacts, versions, replica health, routes, and workflow runs stay connected in the same deployment path.
Terminal
adios up
adios logs dashboard --build
adios logs dashboard --runtime
adios apps builds dashboard
adios ingress listExample outcome
Trace a dashboard release from source to traffic.
Run adios up, inspect its build output, open runtime logs, list the application versions, and confirm which ingress route points at the current release.
Connect output to deploy state
See which source, build, version, replica, and route a log belongs to.
Inspect from the terminal or dashboard
Use the same operational model without switching between unrelated tools.
Why this matters
A log line without its deploy context only tells half the story.
When build output, process logs, route state, and release history live in different tools, finding the change that broke production becomes a reconstruction exercise.
What changes with Adios
Follow a change from build output to live runtime state
Use build logs to diagnose compilation, runtime logs to understand the process, and route and replica state to confirm what is actually serving traffic.
How it works
Trace the same release from source to live traffic.
- Step 01
Deploy from Adios or the CLI.
- Step 02
Inspect build and runtime logs from the app dashboard or terminal.
- Step 03
Use route, version, replica, and workflow state to understand what changed.
A real use case
Trace a dashboard release from source to traffic.
Run adios up, inspect its build output, open runtime logs, list the application versions, and confirm which ingress route points at the current release.
01
Build logs and runtime logs
02
Replica health and route state
03
Workflow run logs
04
Source artifacts and deploy records
Connected pathReady
- 01
Build
Dependencies and compilation
- 02
Version
Versioned release record
- 03
Replica
Health and process output
- 04
Route
Currently promoted target
Start here
Make the next release easier to understand.
Deploy through one path, then inspect its build, runtime, replica, version, and route state without switching systems.
Keep building
The next pieces usually connected to this one.
Adios Deployments
Keep the build, start, health, region, and resource contract in adios.yaml. Running adios up turns the current source into a version and promotes it when the deployment is healthy.
Explore →Workflows & Automation
Define webhook, event, schedule, or manual triggers and ordered steps in YAML. Each run keeps its status, logs, inputs, outputs, and errors after the original request ends.
Explore →CLI & Local Development
Use the Adios CLI to deploy the current directory, read build and runtime logs, manage platform resources, and sync source both ways with a workspace.
Explore →