Audit logs

Open User → Audit Logs. Entries here focus on what changed for accounts and budgets: budget updates, spend deductions, user/key lifecycle events, and Admin edits to users or keys, often correlated to a key or request context.

This is not a full audit trail of every provider/route/settings click in Admin. For configuration change governance, use your change-management process or a separate ops audit trail.

Combine event type, source, reason, actor, and identity filters, then narrow further with an Actor ID, user email, or correlation ID.

Versus request logs

Request logs: per-inference HTTP traces. Audit logs: budget and identity/key lifecycle events.

What to do in Admin

1. Open Audit Logs.
2. Start with a time window, then combine event type, source, reason, actor, and actor-identity filters. Use Actor ID, user email, or Correlation ID for an exact lookup.
3. Expand rows for budget notes, user snapshot deltas, and change details (fields duplicated in the table may be hidden).
4. For a single user, you can also open Users → user detail for related snippets.

Further reading

Deeper field and event definitions live in the upstream docs index: GitHub technical reference.

Next

• System config
• Users