Inspect sandbox logs

When a command in a sandbox fails or returns an unexpected result, start with its process output: the stdout, stderr, and exit status of that one command. Sandbox runtime logs collect the output of every process in the sandbox, along with the sandbox’s own activity, such as the requests its API server handles. Use them to see what happened across a time range. Image build logs record building or importing an image.

Inspect process output

Set up the Baseten CLI, then set SANDBOX_NAME to the sandbox’s name. To read a process’s output: Replace worker with the name used when starting the process, then run the following command to print its stdout and stderr:

baseten sandbox process logs --name "$SANDBOX_NAME" --process-name worker

worker started
worker warning

To read stdout and stderr separately: Run the following command:

baseten sandbox process describe --name "$SANDBOX_NAME" \
  --process-name worker --output json

{
  "exitCode": 0,
  ...
  "status": "completed",
  "stderr": "worker warning\n",
  "stdin": false,
  "stdout": "worker started\n",
  ...
}

For more information, see baseten sandbox process logs and baseten sandbox process describe. For SDK examples, see Run commands in a sandbox.

Inspect sandbox logs

Runtime logs include each process’s stdout at info level and its stderr at error level. The CLI doesn’t read runtime logs; use the dashboard or the API.

To inspect a sandbox’s runtime logs:

Sign in to your workspace at app.baseten.co and choose Sandboxes in the sidebar.
Choose the sandbox.
Choose Logs.
To see earlier entries, choose Live, choose Custom, and select the time range that contains the operation.
To narrow the entries, choose Level and select the levels to show.

Set SANDBOX_TOKEN to a sandbox access token.To retrieve a sandbox’s runtime logs:Replace the start and end times with a range of up to 7 days that contains the operation, then run the following command:

curl --get --url "https://api.baseten.co/v1/sandboxes/instances/${SANDBOX_NAME}/logs" \
  --data-urlencode "start_time=2026-10-15T16:00:00Z" \
  --data-urlencode "end_time=2026-10-15T17:00:00Z" \
  --header "Authorization: Bearer $SANDBOX_TOKEN"

{
  "sandbox_name": "my-sandbox",
  "start_time": "2026-10-15T16:00:00Z",
  "end_time": "2026-10-15T17:00:00Z",
  "logs": [
    ...
    {
      "timestamp": "2026-10-15T16:23:25.400813817Z",
      "message": "worker warning",
      "severity": 17,
      "trace_id": ""
    },
    {
      "timestamp": "2026-10-15T16:23:25.400813579Z",
      "message": "worker started",
      "severity": 9,
      "trace_id": ""
    },
    ...
  ],
  "next_cursor": null
}

The response lists entries newest first, up to 100 per page. A severity of 17 marks an error, such as a line a process wrote to stderr, and 9 marks info. When next_cursor isn’t null, repeat the request with the same time range and set cursor to its value to get the next page.For more information, see Get sandbox logs.

Inspect image build logs

Inspect the build logs when building or importing an image returns FAILED.

To inspect image build logs:

In Sandboxes, choose Images, then choose the image whose build failed.
Choose Logs.

Set IMAGE_NAME to the image’s name.To print image build logs:Run the following command:

baseten sandbox image logs --name "$IMAGE_NAME"

...
2026-10-15T16:02:53Z upload artefacts                  0.75s  (t+10.09s)  scratch   706/32704 MiB
2026-10-15T16:02:54Z upload rootfs (409 MiB, 82 parts)    1.00s  (t+11.09s)  scratch   707/32704 MiB
2026-10-15T16:02:54Z === total 11.09s | rootfs 409 MiB | 82 part(s)

The command prints the image’s latest build, oldest entry first.For more information, see baseten sandbox image logs.

Set IMAGE_NAME to the image’s name and SANDBOX_TOKEN to a sandbox access token.To retrieve image build logs:Run the following command:

curl --url "https://api.baseten.co/v1/sandboxes/images/${IMAGE_NAME}/logs?limit=100" \
  --header "Authorization: Bearer $SANDBOX_TOKEN"

{
  "logs": [
    {
      "message": "=== total 11.09s | rootfs 409 MiB | 82 part(s)",
      "severity": 9,
      "timestamp": "2026-10-15T16:02:54.328265905Z"
    },
    ...
  ],
  "total_count": 99
}

The response contains entries from the image’s latest build, newest first. The default time range is the last 24 hours.For more information, see Get image build logs.

To compare errors with request traffic and resource usage, see sandbox metrics.

Get started

Model APIs

Inference

Frontier Gateway

Training

Sandboxes

Development

Deployment

Engines

Model Labs

Organization

Hosting options

Observability

Troubleshooting

Inspect sandbox logs

Inspect process output

Inspect sandbox logs

Inspect image build logs

​Inspect process output

​Inspect sandbox logs

​Inspect image build logs

Inspect process output

Inspect sandbox logs

Inspect image build logs