The Avalex audit log gives you a complete, chronological record of every administrative action taken in your instance. Whenever a staff member creates, updates, or deletes an entity — or performs a privileged action such as generating a registration key — Avalex writes an immutable entry capturing who did it, what changed, and exactly when it happened. This makes the audit log an essential tool for investigating unexpected changes, onboarding new admins, and demonstrating compliance with internal or regulatory requirements.
You need the actions:read permission to view the audit log in the portal or via the API.
Accessing the Audit Log in the Portal
Select Audit Log from the left-hand sidebar. The page loads the most recent administrative actions in reverse chronological order. Each row shows the event name, the staff member who performed the action, and the exact timestamp. Click any row to expand it and inspect the full data payload for that entry.
What Gets Logged
Avalex records an audit entry for every mutation across all major entity types:
Audit Log Entry Structure
Each entry in the audit log contains the following fields:
Example Entry
Accessing the Audit Log via API
You can retrieve audit log entries programmatically using the REST API:
The endpoint accepts an optional limit query parameter to control how many records are returned.
Example request:
Results are returned in reverse chronological order (most recent action first).
Use the audit log to investigate unexpected changes — for example, if a license was modified or a customer was deleted and it is unclear who made the change. You can also export entries via the API to feed into an external compliance or SIEM system.
