/panel/sistema/logs) shows a complete history of actions performed by administrators and events generated by the system. Records come from the logs table, ordered from newest to oldest.
Log record structure
Each entry in thelogs table captures the following information:
| Field | Description |
|---|---|
user_name | Name of the administrator who performed the action |
action | Description of the executed action |
collateral_name | Name of the affected resource (can be null) |
created_at | Date and time the event occurred |
ip | IP address from which the action was performed |
city | City detected from the IP via the ip.guide service |
Additional fields in the database
| Field | Description |
|---|---|
role | Role of the user who generated the event (admin) |
user_id | UUID of the administrator |
collateral_id | UUID of the affected resource |
table | Database table related to the action |
device | Browser User-Agent from which the action was taken |
ipo | Full JSON object with IP geolocation information |
Table columns in the panel
| Column | Source field | Sortable |
|---|---|---|
| User | user_name | Yes |
| Action | action | Yes |
| Collateral | collateral_name | Yes |
| Date | created_at | Yes |
| IP | ip | Yes |
| City | city | Yes |
Filtering logs
The search box filters simultaneously across any of the following fields:- Administrator name (
user_name) - Action description (
action) - Affected resource name (
collateral_name) - Date (both the raw
created_atvalue and localized format) - IP address (
ip) - City (
city)
What actions are logged
The system automatically logs the following actions through thelogger function:
| Action | Affected table | Description |
|---|---|---|
| Generó un backup database | admins | Administrator downloaded a database backup |
| Generó un backup images | admins | Administrator downloaded an image storage backup |
| Elimino una promoción | promotions | A promotion record was deleted |
| Eliminó un admin | admins | An administrator account was deleted |
Other actions such as creating/editing promotions, administrators, general configuration, and account restoration do not automatically generate log entries, even though the action is executed in the database.
Log retention
Using logs for auditing and debugging
Action auditing
Track which administrator performed a sensitive action (such as deleting a promotion or generating a backup), on what date, and from what location.
Unauthorized access detection
Review unusual IPs and cities to detect possible unauthorized access to the panel.
Incident debugging
Correlate the date and time of a reported incident with logged actions to identify the cause.
Resource traceability
Use the
collateral_name field to track which specific resources were modified or deleted.Required permissions
The administrator must have thesystem:logs area enabled in their role to access this section.