Overview
Titled Activity Log — “Complete audit trail of all operations, changes, and events for this virtual machine”. Scoped to this machine only, which makes it far easier to read than the account-wide screen.Navigation: Compute → Virtual Machines → click a machine → Events.
Columns
Sorted newest first by default.
Levels
Filter by All Levels, Info, Warning, Error.
Month grouping
Rows group into collapsible sections by month, each with a summary strip showing Total Events plus Info, Warning and Error counts — and a level block is omitted entirely when its count is zero.Exporting
Export produces a CSV named for the machine and the date.The CSV includes an Event ID column that the table doesn’t display. That identifier is what support will ask for about a specific event, so export rather than screenshot when raising a ticket.
This tab versus the account-wide screen
Common task: find out why a machine restarted
1
Filter to Error, then Warning
A restart with no error before it was almost certainly deliberate. One following an error was not.
2
Read the User column
A username means a person or an automation did it. Empty usually means the platform did — a host failure or a migration.
3
Check for a schedule
If the timing looks regular, check Schedules — a recurring restart is easy to forget about.
4
Cross-check the operation in Jobs
If a user triggered it, Jobs shows the operation and whether it succeeded. Widen the job time window past its six-hour default to cover the same period.
5
Export before the retention window closes
Events are kept for 90 days, stated on the page. If this matters for an incident review, export now.
Empty and error states
Related
Events
The account-wide trail, and its window.
Jobs
Whether the operation behind an event succeeded.
Monitoring tab
Charts, for incidents long enough to appear in them.