BattaniAudit and operation records
Inspect recorded administration operations by actor, target and outcome.
What the records cover
The Audit Logs page provides a central view of recorded application operations. Data-service and Docker Registry modules also provide their own operation records.
Depending on the operation, details can include user, time, target, success/failure and additional context. Even a connection-test record can help explain when access to a target was attempted.
Investigate a change
- Identify the relevant time range and operation context.
- Use audit filters to narrow the actor or action.
- Open the record details to inspect the target, outcome and available error information.
- For data-service or registry operations, compare the module records and verify the result against actual resource state.
Interpret records correctly
An audit record describes an event recorded by the application. It does not replace independent Kubernetes audit infrastructure, database transaction logs or a complete capture of all system traffic.
Distinguish failed requests from successful changes. Restrict access to records appropriately; changes made outside Battani may not appear in its operation history.