Audit log
Overview
The audit log records every user action in your organization. You can trace who did what and when (creating or deleting resources, sign-in attempts, permission changes, etc.), which is useful for security audits and troubleshooting.
Prerequisites
User.UserAudit.READpermission. Among the built-in roles, only Owner has it.
How to open it
In the left sidebar, click Audit Log. The menu is not shown to users without permission to view it.
What's shown
| Column | Description |
|---|---|
| Created | When the activity occurred |
| Category | Kind of action (e.g. Resource Created, Sign In Success, User Role Updated) |
| Email of the user who performed the action (with user ID) | |
| IP Address | Client IP that issued the request |
| User Agent | Client browser / SDK info |
Expanding a row reveals the JSON detail for the action, including which resource was changed and how.
Filtering
Use the filters in the top-left to narrow the log:
- Period:
start dateandend date(date picker) - Email: a specific user (autocomplete, minimum 2 characters)
- Category: a specific action category
Categories
Recorded categories fall into roughly 5 groups (UserAuditCategoryEnum).
Resources
| Category | Meaning |
|---|---|
| Resource List Retrieved / Resource Retrieved | GET on VMs, storage, etc. |
| Resource Created / Updated / Deleted | Changes to VMs, storage, or network resources |
Users / permissions
| Category | Meaning |
|---|---|
| User Created / Updated / Deleted | Organization-user changes |
| User Updated / Password Change | Changes to one's own account |
| User Invitation Started / Completed | Invitation sent and accepted |
| User Role Created / Updated / Deleted | Changes to RBAC roles |
Authentication
| Category | Meaning |
|---|---|
| Sign In Success / Sign Out | Normal sign-in / sign-out |
| Password Failed / OTP Authentication Failed | Authentication failures: key security signal |
| Too Many Sign In Attempts | Lock-out threshold reached |
| Oauth Sign In Success | Sign-in via SSO |
| Password Reset Started / Completed | Reset flow |
| Session Refresh | Token refresh |
Access tokens
| Category | Meaning |
|---|---|
| Access Token Created / Retrieved / Deleted | API-token lifecycle |
Notices
| Category | Meaning |
|---|---|
| Notice Retrieved / Notice List Retrieved | History of viewing organization notices |
Use cases
Tracing an accidental VM deletion
- Filter by Category =
Resource Deleted - Narrow the time range to around when it happened
- Confirm the deleted resource ID and name in the JSON detail
Diagnosing a cost spike
- Filter by Category =
Resource Created - Pick the time range covering the billing spike
- Identify who created the large instance
Monitoring suspicious sign-in attempts
- Filter by Category =
Password FailedorOTP Authentication Failed - Look for repeated occurrences from the same email or IP
- Force a password reset on the affected user if needed
Auditing API token usage
- Filter by Category =
Access Token Created / Deleted - Investigate any suspicious issuance → revoke immediately
Next steps
- Usage: cross-reference cost changes with the audit log
- Role-based access control (RBAC): design permissions to prevent abnormal actions in the first place
- Access tokens: issue and revoke tokens