Activity Logs
See what SnoozeDB changed, what your team changed, and where to look when an action fails.
What gets recorded
The Activity log keeps two histories with different purposes.
Automation logs
Start, stop, and removed-resource events for managed RDS and EC2 resources, including the result returned by the operation.
User logs
Changes made by people, such as syncs, triage decisions, schedule edits, locks, organization settings, invitations, role changes, and generated scripts. Only owners and admins can view this tab.
Read an event
Start with the timestamp and action, then use the remaining fields to understand its scope and outcome.
| Field | How to use it |
|---|---|
| timestamp | When SnoozeDB recorded the event. The log page identifies UTC timestamps where applicable. |
| resource | The affected resource and, for automation logs, its RDS or EC2 type. |
| action | The operation that was attempted or the user change that was made. |
| status | SUCCESS means the automation operation completed; ERROR means it did not. |
| message | The operation detail or error returned for an automation event. |
| actor | The signed-in user associated with a user activity event. |
Filter and export history
Search by resource or message, narrow the date range, then filter automation events by resource type, action, or status. User events can be filtered by person and action.
Export the filtered result when you need to review it outside SnoozeDB. Keep the export with the same care as any operational audit data.
Diagnose an automation problem
Find the expected boundary
Filter to the resource and the date when its schedule should have started or stopped it.
Read the latest matching event
Check the action, status, and message. An ERROR message is the best starting point for an AWS permission or state problem.
Check the current policy
Confirm the resource is managed, unlocked, and attached to the expected schedule and timezone.
Refresh before retrying
Run a sync when the SnoozeDB state no longer matches AWS, then verify the next operation in the log.
Audit boundaries
Troubleshooting
- No matching event: clear filters, widen the date range, and verify the active organization.
- No User logs tab: only organization owners and admins can view user activity.
- Repeated ERROR events: inspect the message, then verify the AWS role permissions and resource state.
- Unknown resource identifier: run a sync and check whether the resource was removed or renamed in AWS.