trace docs

docs/log-viewer.qmd

@@ -131,8 +131,8 @@ The log levels and their applicability are described below (in increasing order
 | Level | Description |
 |------------------------------------|------------------------------------|
 | `debug` | Detailed information, typically of interest only when diagnosing problems. |
+| `trace` | Show trace messages for runtime actions (e.g. model calls, subprocess exec, etc.). |
 | `http` | HTTP diagnostics including requests and response statuses |
-| `sandbox` | Show commands sent to manage and execute code in sandboxes. |
 | `info` | Confirmation that things are working as expected. |
 | `warning` | or indicative of some problem in the near future (e.g. ‘disk space low’). The software is still working as expected. |
 | `error` | Due to a more serious problem, the software has not been able to perform some function |

docs/tracing.qmd

@@ -41,7 +41,7 @@ inspect trace anomalies
 
 You will first see currently running actions (useful mostly for a "live" evaluation). If you have already cancelled an evaluation you'll see a list of cancelled actions (with the most recently completed cancelled action on top) which will often also tell you which cancelled action was keeping an evaluation from completing.
 
-Passing no arguments shows the most recent trace log, pass an explicit trace log name to view another log:
+Passing no arguments shows the most recent trace log, pass a log file name to view another log:
 
 ``` bash
 inspect trace anomalies trace.log.1.gz