Activity log
Activity is the audit log: every sign-in, start, stop, keep-on, approval, tag change and settings change, with who did it, from where, and how it went. Newest first.
Activity is for administrators and auditors. Open it from Activity in the top bar.
What is recorded
| Kind | Examples |
|---|---|
| Sign-ins | Signing in and out, two-step sign-in set up, used or reset |
| Starts, stops and keep-ons | Start, stop, reboot, keep on, turn on, each change of time, Stop it now, Put back on schedule, the automatic stop at the end of a keep-on, and server group starts and stops with each member |
| Tag changes | Drop, re-add and set, with the key and value |
| Approvals | Requests for approval, approvals, declines, withdrawals and requests that lapsed |
| Access | Requests for access, and access granted or declined |
| Bookings | Bookings made and cancelled |
| Remote Desktop | Every .rdp download, with the address and user name it gave, and changes to how machines are reached |
| Settings | Accounts, access rules, friendly names, roles, server groups, settings and backups |
| API tokens | Tokens made and revoked. Actions taken with a token are recorded under the person's name, "with API token name" |
Every action is recorded whether it worked or not. A refused or failed action is recorded with the reason.
Each entry carries:
- when it happened (stored in UTC, shown on your own clock),
- who did it: the person's user name. Timed work, such as the stop at the end of a keep-on, is recorded under the person who set the time,
- the address they did it from,
- what was done, and on which resource, account and region,
- any detail, such as the time a keep-on was set to, the reason given, or "approved by name (request #12)", and
- the outcome: done, or the problem.
An action that was approved is recorded three times: the request, the decision, and the action itself, each under the name of the person who did it.
Reading the page
| Column | What it shows |
|---|---|
| When | The date and time. Click it to open the entry |
| Who | The user name. Click it to show only that person |
| What | The action and its detail. Times in the detail are shown on your own clock |
| Where | The resource ID, and the account ID (click it to show only that account) and region |
| Outcome | Done, or the reason it was refused or failed |
Opening an entry shows everything recorded: the time (with the UTC time beside it), the action and its internal name, the person and their address, the resource and its type, the account and region, the full detail and any problem.
The page shows 100 entries at a time. Show older activity at the bottom loads the next 100.
Filters
| Filter | What it does |
|---|---|
| Search user, resource or detail | Matches the user name, resource ID, account ID and detail |
| Kind of activity | All activity, Starts, stops and keep-ons, Tag changes, Sign-ins or Settings changes |
| Only refused or failed | Hides everything that worked |
| User | One user name |
| Account ID | One account |
| From and To | A date range, both days included |
Clear filters removes them all.
Downloading as CSV
Download CSV downloads what the filters select (up to 50,000 entries), newest first, with these columns: When (UTC), Who, Action, Outcome, Account, Region, Type, Resource, Detail, Error, Address.
Cells that a spreadsheet would read as a formula are written so they are not, so the file is safe to open in Excel.
AWS CloudTrail
In accounts reached through a role, Delegaris makes each AWS call under the role session delegaris-<username>, so CloudTrail in that account shows the person as well. In accounts reached with access keys, CloudTrail shows the key's owner instead.
Keeping a copy elsewhere
To copy the log to an S3 bucket for a SIEM, see Activity log to S3. For keep-on, approval and alert messages as they happen, use the webhook under Teams and webhooks.
For totals over a period rather than individual events, see Reports.