Skip to content

Activity Logs ​

The Activity Logs module records all user and system actions for auditing and troubleshooting.
It provides visibility into who did what, when, and from where, including changes made to records.

Index Page ​

The Activity Logs index provides a chronological list of all user and system actions.
It shows details such as user, role, IP address, device/agent, log name, event type, subject, and timestamp.
Admins can filter by user, IP, event type, log name, or date range to quickly locate specific activities.
Clicking a row opens the Show Activity Log page with full details of the action.

Filters ​

  • IP Address – Filter logs by originating IP.
  • Batch UUID – Group of related actions, useful for tracking bulk operations.
  • User – Filter by the user who performed the action.
  • Event Type – Filter by type of action (e.g., Created, Updated, Deleted).
  • Log Name – Filter logs by the entity or module name (e.g., tables.updated).
  • From / To (Date Range) – Filter logs within a specific timeframe.

Actions ​

  • Click Row – Opens the detailed log entry (Show page).

Columns ​

  • User – User who performed the action, with role badge.
  • IP Address – Source IP of the action.
  • Agent – Device, OS, and browser info.
  • Log Name – Related module/entity, clickable to view details.
  • Event – Action performed (Created, Updated, Deleted).
  • Subject – Entity affected (e.g., Table #4).
  • Logged At – Timestamp of when the action occurred.

Show Page ​

The Show Activity Log page provides complete details of the selected log entry.

Sections ​

  • User – Name, email, and role of the user who performed the action.
  • Subject – Entity affected (e.g., Table #4).
  • Description – System-generated note describing the action (e.g., Table has been updated successfully).
  • Log Name – Module/entity involved in the action (e.g., tables.updated).
  • Event – The type of action performed (e.g., Updated).
  • Logged At – Exact date and time of the action.
  • IP Address – Source IP of the request.
  • HTTP Method – Method used (e.g., POST, PATCH, DELETE).
  • Agent – Detailed device/browser info (Desktop/Mobile, OS, Browser).

Changes Section ​

A table showing before and after values for each field affected:

  • Field – Database field name (e.g., status, name).
  • Old Value – Value before the change.
  • New Value – Value after the change.

Example Use Cases ​

  • Security Auditing – Track unauthorized changes.
  • Troubleshooting – See what modifications caused an issue.
  • Accountability – Identify which user performed a given action.
  • Compliance – Provide logs for regulatory requirements.

Tenvoro