Audit log
Find the account, action, target, and result of a state-changing request.
Open Advanced → Server configuration → Audit log as an administrator when you need to answer who changed a resource or why an action was denied. The dashboard records sign-ins and state-changing requests with the actor, action, target, result, time, client address, and request path. The actor is a browser session or an API key, or the dashboard itself for its own background work.
The page opens on four readings of the last 24 hours: how many changes were made, with a trend across the hours; how many Failed; the People behind them; and Sign-ins, including refused ones. Filters below do not narrow these readings.
Find an event
- Type an account in User if you know who acted. The action box accepts a prefix or name such as
docker.container. - Or select a section chip, such as Sign-in, Docker, Deployments, Databases, Files, Terminal, or Git, to filter by that part of the dashboard.
- Turn on Failures only when investigating a refused or failed action.
- Read the When, Who, Action, Target, and Result columns under Recorded requests. Who shows the client address; Action shows the request method and path.
- Page through older entries as needed. The page loads 100 entries at a time and checks for new ones every 15 seconds; select Show on the new-entries button to bring them into view.
Links from some feature pages open the audit log with an action filter already selected. A dashboard role may permit viewing a resource while preventing its mutation; the backend's result in the audit log is the useful evidence in that case. See the role matrix.