> ## Documentation Index
> Fetch the complete documentation index at: https://docs.nanovm.dev.lithosai.cloud/llms.txt
> Use this file to discover all available pages before exploring further.

# See what's happening

> Every sandbox keeps its own paper trail — events, console logs, utilization metrics, and an org audit log. No setup.

Every sandbox keeps its own paper trail — no setup, nothing to instrument:

```python theme={null}
sb.events()                 # lifecycle timeline, newest first: created, slept,
                            # archived, rebooted, forked… — even after delete.
sb.logs()                   # tail of the serial console (boot output, kernel
                            # messages). Works on paused/slept without waking.
sb.metrics()                # 30 s utilization samples (~2 h): CPU, memory, net.
nv.audit()                  # org-wide: who changed what, with what outcome.
```

`sb.metrics()` with no arguments returns live 30-second host samples for the
last \~2 hours. With `hours=` or `start=`/`end=` (RFC3339, up to 15 days back)
it returns per-minute ledger history instead — including for archived and
deleted sandboxes; a point with `measured=false` is a gap, never a zero.

The console shows the same data: each sandbox has a detail page (timeline,
log tail, utilization graphs), and the org has Usage and Audit pages.

## Sharp edges

An archived sandbox has no live console or metrics — its timeline still
answers. Metrics are measured on the host (the guest is never touched), so a
slept sandbox shows flat CPU rather than waking to be asked.