Skip to content

Audit Logs

Every data change in Metrognome is automatically recorded — who made it, when, and what changed. Audit logs are append-only and cannot be modified or deleted, providing a tamper-proof history for compliance and troubleshooting.

Viewing Audit Logs

Go to Admin → Audit Logs to see the full activity log.

Each entry shows:

Column What It Shows
Timestamp When the change happened (displayed in your browser's timezone)
Table Which data table was affected (e.g., reservations, users)
Record The ID of the specific record that changed
Action What happened — INSERT (created), UPDATE (modified), or DELETE (removed)
User Who made the change, or "system" for automated actions
Source Where the change came from — staff dashboard, member app, or API

If a change was made during an impersonation session, the User column shows an (imp) indicator.

Filtering

Use the controls at the top of the page to narrow down results:

  • Table dropdown — Filter to a specific data table (e.g., show only reservations changes)
  • Action dropdown — Filter by INSERT, UPDATE, or DELETE
  • Search by Record ID — Find all changes to a specific record

Pagination defaults to 25 entries per page.

Entry Details

Click any row to see the full details of that change:

  • Audit Log ID — Unique identifier for this log entry
  • Table and Record ID — What was changed
  • Action — INSERT, UPDATE, or DELETE
  • User and Impersonator — Who made the change (and who was impersonating, if applicable)
  • Source — staff, member, or api
  • Request ID — Correlates multiple changes from the same request
  • Timestamp — When the change occurred
  • Previous Data — For updates, shows only the fields that changed and their previous values. Null for inserts and deletes
  • Data — Full snapshot of the record after the change

What's Tracked

Audit logs capture changes across all core tables including users, reservations, locations, resources, payments, credits, access codes, assets, organizations, and migrations — 43 tables in total.

Changes that don't actually modify any data (e.g., saving a form without making edits) are automatically skipped.

Sources

The Source field tells you how a change was made:

Source Meaning
staff Change made through the staff dashboard
member Change made by a member through the customer app
api Change made by an API client or webhook

Common Lookups

Track changes to a specific record: Use the Record ID search to find all modifications to a user, reservation, or other entity over time.

Investigate impersonation activity: Look for entries with the (imp) indicator in the User column to see what changes were made during impersonation sessions.

Audit a specific table: Use the Table filter to review all changes to a particular data type — useful for auditing sensitive tables like user_roles.

Correlate related changes: On the detail page, the Request ID groups changes that happened in the same API request, so you can see everything that was modified together.