User Action Log
The User Action Log provides a centralized view of activities performed within your CloudRaya account.
It is designed for operational visibility, basic security monitoring, and change tracking across your cloud resources.
Purpose of User Action Log
The User Action Log helps you:
- See who performed an action
- Understand what action occurred
- Know when it happened
- Identify which resource was affected
- Check whether the action succeeded or failed
This log covers actions across both platform services and managed resources.
Accessing User Action Log
You can open the User Action Log from:
- Click your profile avatar
- Select User Action Log
The log is account-wide and is not limited to a single Project.
Page Overview
Filters
Filters help you quickly narrow down log entries.
Available filters include:
- Date — filter actions by time range
- Object — filter by resource type
- Status — filter by action result
Supported Object Types
You can filter actions for the following resource categories:
-
User
-
Project
-
SSH Keypair
-
Virtual Machine (VM)
-
Kubernetes
-
Storage
-
Snapshot
-
User Template
-
Public IP
-
Private IP
-
VPC
-
VPC Network
-
Load Balancer
-
User VPN
-
Object Storage
-
Image Repository
-
Managed Service
Log Table
Each row represents a recorded action.
A log entry includes:
- Timestamp — when the action occurred (based on your UI timezone)
- Description — what action was performed
- Object — the resource or service involved
- Status — the outcome of the action
Examples of Logged Actions
Typical events recorded include:
- Creating or deleting Virtual Machines
- Creating Projects
- Assigning Public or Private IPs
- Modifying VPC or network settings
- Deploying Kubernetes clusters
- Provisioning storage or snapshots
- Managed service lifecycle actions
Both user-initiated actions and platform provisioning events may appear in the log.
Status Indicators
Each action can appear as:
- Pending — action is queued and not yet processed
- Processing — action is currently in progress
- Success — action completed successfully
- Failed — action did not complete as expected
This helps you quickly identify incomplete or problematic operations.
Security & Compliance Notes
- Log entries are read-only
- Actions cannot be edited or removed by users
- Logs support basic audit and investigation workflows
- Useful for operational reviews and troubleshooting
The User Action Log is not a full security event monitoring system, but provides platform-level visibility into resource and service changes.
Best Practices
- Review logs after major infrastructure changes
- Use filters to isolate failed or pending actions
- Monitor access-related and provisioning events
- Keep logs as part of your operational review process
- Combine with Billing and Monthly Usage History for full account visibility
Related Guides
📄 Invoices