Skip to navigation

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

You want to…Use
Find out who changed or deleted a resourceActivity Logs, filtered by service and searched by resource name
See why an action failedActivity Logs with Status set to Failed; open the event and read Reason
Check what an API token didActivity Logs, searched by the token’s name
Watch one VM’s CPU, disk and networkThe VM’s Monitoring tab, not Activity Logs
See what you’re being chargedBilling and usage
Keep events for longer than 90 daysExport them to CSV regularly

How it works

  1. Each IBEE service records an event when someone, or IBEE itself, acts on your organization’s resources.
  2. The event stores the time, the action, the resource, the actor, and the result.
  3. 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

1

Open Activity Logs

Open your organization (its Workspaces page). In the sidebar, under Organization, click Activity Logs.

2

Pick a time range

In Time range, choose Last 24 hours, Last 7 days, Last 30 days (the default) or Last 90 days.

3

Narrow the list

Type a user, resource or action in the search box (User, resource or action). Set Service, Status and, if the organization has more than one workspace, Workspace. The list reloads as you change them.

4

Open the event

Click a row to expand its details. Click Copy next to Reference to copy the event ID.

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:

ColumnWhat it shows
TimeWhen it happened. Hover for the full date and time.
ActionWhat was done, for example a create, update, restore or delete
Product / resourceThe resource, its type and context, for example Volume · on web-01
ActorWho did it: a team member, an API token (with its name), or a system or service action that IBEE performed
Source serviceThe IBEE service that recorded it
StatusSucceeded, Failed, In progress, Accepted or Cancelled

Expanding a row adds:

DetailWhat it shows
WorkspaceThe resource’s workspace, when it has one
ActorName, email and the IP address the action came from
ChangedThe fields that changed, for an update
ReasonFor a failure: the error code, the HTTP status and, for bulk actions, how many items failed
ReferenceThe event ID. Include it when you contact support about an event.

The filters:

FilterOptions
ServiceAll services, Compute, Storage, Network, Billing, Organization, Security, Registry, Support, Email
WorkspaceAll workspaces, or one workspace
StatusAll statuses, Succeeded, Failed, In progress, Accepted, Cancelled
Time rangeLast 24 hours, Last 7 days, Last 30 days, Last 90 days

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

Value
How far back you can look90 days (Last 90 days)
How long events are kept90 days
Events per page50, then Load more
Rows per CSV exportUp to 10,000
Who can viewOwner, Admin, Technical, Collaborator

Events older than 90 days are removed. Export the events you must keep for longer.

Troubleshooting

You seeWhat it meansWhat to do
”No activity in this period.”Nothing was recorded in the time rangeChoose a longer range, up to Last 90 days
”No activity matches these filters.”The search or filters exclude every eventClick Clear filters, or set each filter back to All
”Export exceeds 10000 rows; narrow the date range or filters”The export is larger than 10,000 eventsPick a shorter time range or add a filter, then export again
Export CSV is greyed outThe list is emptyWiden the filters first
”You don’t have access to this activity.”Your role doesn’t include activityBilling members can’t view it; ask an Admin
”Couldn’t load activity.” or “Couldn’t export activity.”A temporary errorClick Retry or Refresh
Activity Logs isn’t in the sidebarYou are inside a workspace, or you have the Billing roleGo back to the organization’s Workspaces page
An event you expect is missingIt is older than 90 days, or your role or workspace scope hides itAsk an Admin to look