Skip to main content
Open a sandbox in the console to see its activity, system logs, and resource use. You can retrieve the same information through the SDK.

Review sandbox activity

Events describe actions such as creation, sleep, snapshots, and archive. They are returned newest first. Keep the sandbox ID when reporting an issue so its timeline can be found even after deletion.

Read system and application logs

Use system logs to investigate startup or an unresponsive environment:
These logs contain boot output and system messages. They do not replace the output of your SDK commands. For a command, read result.stdout and result.stderr; for a background application, redirect its output to a file and read that file with sandbox.files.read(). You can read system logs while a sandbox is paused or sleeping without waking it. Archived sandboxes do not have live system logs. Each call reads up to 256 KiB.

Inspect resource use

Get recent CPU, memory, and network samples:
Recent samples cover approximately two hours at 30-second intervals. Use history for a longer period or for an archived sandbox:
History uses minute intervals and supports up to 15 days. You can also pass start and end as RFC3339 timestamps. A point with measured=false means a measurement is missing; it does not mean resource use was zero. History and events remain queryable after deletion within their retention periods. Keep an existing sandbox handle to query them after deleting it, or use the HTTP history endpoint with the saved ID. Fetching a deleted sandbox with box.sandboxes.get() returns NotFoundError.

Review organization usage and audit records

Use Console → Usage to compare resource use over time and Audit to review changes made by members and API keys. Audit records identify the action, resource, outcome, and request ID. For an issue you cannot resolve, follow the support checklist.