Log Management
Overview
The Logging page serves as a centralized audit trail for tracking all significant user and system events. It provides visibility into who did what, when, and where across the platform.
Main View Layout
Each log entry is displayed in a row with the following details:
- Type: The nature of the event (for example, "Login", "Logout", "Created identity", "User updated").
- Time: The exact timestamp when the event occurred.
- User: The username or user ID associated with the action.
- Description: A simple explanation of what occurred (for example, “User CHZ signed in”).
Pagination
Use the navigation buttons at the bottom to move between pages. Logs are displayed in chronological order, with the newest events at the top by default.
Filter Panel
Clicking the filter icon (orange funnel) opens an advanced filtering window, allowing you to narrow down the logs. You can filter by:
- Date (from / to): Set a date range to view logs within a specific time window.
- User: Filter logs by a specific user.
- Minimum log level: Filter based on the severity or importance of events.
- Log type: Focus on specific event categories.
Clicking Apply confirms and applies the filters and Close cancels the filter panel without applying changes.
Log Details
Clicking any log entry opens a detailed view in JSON format. This is useful for support or advanced debugging.
Some example fields include:
- source_entity: User or system entity that performed the action.
- type: Event type such as "users.actions.login".
- timestamp_ms / written_timestamp: Millisecond precision timestamps.
- user_name / login / directory_name: Contextual metadata about the event.
- log_entry_id: Unique identifier for the event.
This detailed view helps correlate backend IDs with user-friendly names, folders, and event metadata.
Best Practices
- Regularly review logs for unauthorized access attempts or unexpected activity.
- Use filters when auditing specific users or dates.
- Use the log details view for compliance reporting or technical audits.