Skip to main content

Audit History

Use Audit History to review management operations and configuration changes.

An entry records the timestamp, target name, service, action, signed-in username and reported result, with sanitized error details when available. Date and action filters help narrow an investigation. The view shows the most recent 250 matching operations.

Read the outcome with the current state​

A recorded command success describes the completed management command. Check the service's current state and website health afterwards. Application startup or downstream recovery can take additional time.

If a request times out, inspect the actual service before trying again. A systemd job may continue after its client has stopped waiting.

Local storage​

Audit history belongs to the saved server registration and stays in the local state directory. Removing a saved server archives that registration's app list and history.

Keep backups private. The local app account can write these files, so an independently retained copy is needed if your organization requires an audit record outside that account's control.

Do not share entire audit directories in a public issue. Include only the minimum sanitized details necessary to explain the problem.

Security · Settings · Update and removal.