Adios
← PLATFORM / Observability & Logs

See what happened. Find what matters.

When a build fails, your agent needs direct feedback. Adios links build logs, runtime streams, and health checks directly to the workspace, allowing your AI agent to independently diagnose, fix, and verify its own code changes.

IN PRACTICE

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.

Terminal
adios up
adios logs dashboard --build
adios logs dashboard --runtime
adios apps builds dashboard
adios ingress list

HOW IT WORKS

Trace the same release from source to live traffic.

Read the guide ↗
  1. 01

    Deploy from Adios or the CLI.

  2. 02

    Inspect build and runtime logs from the app dashboard or terminal.

  3. 03

    Use route, version, replica, and workflow state to understand what changed.

WHY IT BELONGS HERE

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.

Open the log stream for the stage you are debugging

Keep dependency and compilation output separate from the running process.

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.

What’s included
  • ✓ Build logs and runtime logs
  • ✓ Replica health and route state
  • ✓ Workflow run logs
  • ✓ Source artifacts and deploy records

Make the next release easier to understand.

Deploy through one path, then inspect its build, runtime, replica, version, and route state without switching systems.

Deploy and inspect logs ↗

CONNECTED CAPABILITIES

Keep building.

All features ↗