Subshell Docs

Audit log

Review administrative activity in the instance's audit trail.

Before you start

Use an administrator session. Audit records describe actions on the control plane, not every command an agent runs.

Open the trail

  1. In the server dashboard's sidebar, open Settings → Server Settings → Logs.
  2. Select the audit view.
  3. Review the actor, action, target, and time associated with the operation.
  4. Page through results when investigating a sequence of changes.

The audit trail records account creation and recovery, configuration changes, plugin actions, and other administrative work. It doesn't include credentials such as provider client secrets.

Correlate failures

API errors include a code and an error ID. Use the ID to find the matching server log entry, if one exists. The server doesn't log every expected client error, so a missing entry doesn't mean the request succeeded.

Keep timestamps, response codes, and the relevant operation when reporting an issue. Avoid copying authentication headers or secret configuration values.

Limits

The instance stores its own audit trail, so the trail isn't an independent, tamper-proof record. It doesn't capture every terminal command or file change an agent makes.

Next steps

Read Status and logs and Build an API integration.

Edit on GitHub

Last updated on

On this page