Skip to content
Distromotion Admin Docs

Event Logs

The Event Logs page provides administrators with a comprehensive record of system activities and user actions. This is an essential tool for monitoring platform health, troubleshooting issues, tracking user behavior, and ensuring security.

Overview

Event logs capture a wide array of actions and system events occurring within DistroMotion. Each log entry typically includes a timestamp, the user or system process responsible for the event, the type of event, and relevant details.

From a technical standpoint, the system utilizes a dedicated logging mechanism, likely integrated with Pocketbase, to record these events. These logs are stored securely and are accessible to administrators through the admin panel.

Key Information Tracked

Event logs typically track, but are not limited to:

  • User Actions: Logins, logouts, password changes, profile updates, content uploads, content takedowns, payout requests, etc.
  • System Events: Automated processes (like cron jobs for report processing or payout generation), errors, warnings, successful operations, database changes, API interactions.
  • Administrative Actions: Changes to system configuration, user role modifications, manual data interventions, etc.
  • Security Events: Failed login attempts, potential security breaches, access to sensitive data.

How Event Logs Work (Simplified)

  1. Event Trigger: An action is performed by a user or the system (e.g., a user uploads a song, a scheduled task runs).
  2. Log Generation: The system identifies this as a loggable event.
  3. Data Capture: Relevant information about the event (who, what, when, where, and sometimes why/how) is collected.
  4. Log Storage: This information is formatted into a log entry and stored in a dedicated database table or log file system, managed by Pocketbase.
  5. Admin Access: Administrators can view, filter, and search these logs through the “Event Logs” section of the admin panel.

Accessing and Using Event Logs

To access event logs:

  1. Navigate to the Event Logs section in the staff admin panel.
  2. You will typically see a list of recent events, often with options to filter by date range, event type, user, or other criteria.
  3. Use the search and filter functionalities to narrow down the logs to find specific information.

Importance for Administrators

  • Troubleshooting: When users report issues or unexpected behavior, event logs are the first place to look to understand what happened, when, and by whom.
  • Security Monitoring: Regularly reviewing logs for suspicious activity (e.g., multiple failed login attempts, unauthorized access attempts) is crucial for maintaining platform security.
  • Auditing: Event logs provide an audit trail for user actions and system changes, which can be vital for compliance and internal reviews.
  • Performance Monitoring: Certain system event logs can help identify performance bottlenecks or recurring errors that need attention.
  • Understanding User Behavior: Analyzing logs can provide insights into how users interact with the platform, which can inform feature development or UI/UX improvements.

Best Practices for Using Event Logs

  • Regular Review: Don’t wait for an issue to arise. Periodically review event logs to stay informed about system activity.
  • Understand Log Details: Familiarize yourself with the common types of log entries and the information they contain.
  • Use Filters Effectively: Learn to use the filtering and search capabilities to quickly find relevant information.
  • Correlate Events: Sometimes, understanding an issue requires looking at a sequence of related events.
  • Report Suspicious Activity: If you find any logs indicating potential security threats or critical errors, report them or investigate further as per your operational procedures.

By effectively utilizing the event logs, administrators can gain deep insights into the platform’s operations, ensuring stability, security, and a better user experience.