Activity logs
Activity Logs is your organization’s record of who did what and when: every resource created, changed or deleted, team and billing changes, security events and support activity, with the person (or program) who did it and whether it worked. It answers questions like “who deleted this volume?” or “why did my VM create fail?”, and gives you a record for audits.
When to use it
How it works
- Each IBEE service records an event when someone, or IBEE itself, acts on your organization’s resources.
- The event stores the time, the action, the resource, the actor, and the result.
- You see the events your role allows, newest first, for the last 90 days.
Before you begin
- Role: the Owner, an Admin, a Technical member or a Collaborator. Billing members can’t open Activity Logs.
- What you see depends on your role. Technical and Collaborator members don’t see billing events, and members with selected workspaces see only those workspaces’ events plus organization-wide events. See Team members & access roles.
Find an event
Open Activity Logs
Open your organization (its Workspaces page). In the sidebar, under Organization, click Activity Logs.
Pick a time range
In Time range, choose Last 24 hours, Last 7 days, Last 30 days (the default) or Last 90 days.
The list shows 50 events at a time. Click Load more at the bottom for older events, and Refresh at the top for new ones.
What an event shows
Each row shows:
Expanding a row adds:
The filters:
Public API activity and refused writes
The verified API token identifies its owner and credential in API activity. A tool
name or version reported through User-Agent is informational; it does not prove
who acted.
A write refused during API-key authorization can record a denied security event when the credential secret and owning organization have been verified. Failed filtering and CSV export include these denials. Unknown or invalid credentials cannot be attributed to an organization’s activity.
Ordinary reads are not activity events. A request that issues a new credential is
treated as a write even when its HTTP method is GET.
Activity delivery is best effort. Use the HTTP response and operation status to check the outcome; a delayed or missing event does not change an authorization refusal. Denial events omit the raw request path, query, body and client IP.
Export to CSV
Click Export CSV to download the events that match your current search, filters and time range as activity-<organization-id>-<YYYY-MM-DD>.csv. Open it in any spreadsheet app.
An export can hold up to 10,000 events. For more, export in smaller time ranges or with more filters.
Limits and retention
Events older than 90 days are removed. Export the events you must keep for longer.
