System Logs

System Logs¶

Mythradon automatically captures and records processing issues in the System Logs (LogMyth entity), providing a clear and traceable history of errors and exceptions across the platform. These logs are essential for troubleshooting and monitoring system health, particularly for backend operations.

The System Logs include detailed information on errors arising from various critical processes, such as:

Payment Gateway Processing – Captures transaction failures, integration errors, or timeout issues when communicating with external payment services.
Business Hours Calculation – Logs discrepancies or calculation issues related to business hours, affecting time-sensitive workflows and SLA tracking.

This centralised logging helps administrators and support teams quickly identify, investigate, and resolve issues—ensuring minimal disruption to business operations.

Issue Management and Collaboration¶

The System Logs not only capture errors but also support active issue management and collaborative resolution workflows. Each log entry includes tools to help track and resolve problems efficiently:

User Assignment - Log entries can be assigned to specific users or team members responsible for investigating and resolving the issue.
Status Tracking – Each entry includes a status field to reflect the current stage of investigation (e.g., New, Investigating, Closed).
Resolution Notes – Users can document findings, actions taken, and final resolutions directly within the log entry for future reference.
Follow Functionality – Team members can "follow" specific logs to receive updates, ensuring visibility and collaboration on high-priority issues.

These features transform the System Logs from a passive record into a dynamic tool for operational accountability and continuous improvement.

Audit History and Internal Communication¶

In addition to tracking and managing issues, the System Logs entity also includes Streams, which provide:

Audit History – A complete, time-stamped record of changes made to each log entry, including updates to status, assignments, and resolution notes. This ensures full traceability and accountability throughout the investigation and resolution process.
Internal Communications – A dedicated space for team members to add comments, ask questions, and share updates related to the issue-keeping all discussions and decisions in one place.

Streams make it easy to maintain context, collaborate effectively, and ensure that nothing is missed when resolving critical system issues.

Accessing System Logs¶

By default, the System Logs are not visible on the main navigation menu to keep the interface streamlined for general users. However, access can be easily enabled for system administrators or support personnel.

To make the System Logs accessible:

Add the Logs menu item to the main navigation menu via your system configuration settings.
Ensure the appropriate permissions are granted to users or roles who need access to system-level diagnostics and error tracking.

Once added, administrators can view, manage, and investigate log entries directly from the menu-enabling faster issue detection and resolution.

Creating System Logs¶

The System Logs can be programmatically populated to capture errors, warnings, or other relevant events that occur during system processes. This is particularly useful for custom automation, workflow tracking, or advanced troubleshooting.

To create a log entry, use the RecordCreate formula function. This allows you to:

Log custom error messages when exceptions occur in your processes.
Record key diagnostic details (e.g. process name, user context, error code) for future analysis.
Create informational entries for tracking non-critical events or checkpoints in automated workflows.

By integrating RecordCreate with your business logic, you can ensure important operational events are captured in the System Logs, enhancing visibility, accountability, and support readiness.

Searching the System Logs¶

When you access the System Logs, you'll be presented with the System Log List View, a powerful interface designed to help you quickly locate and review log entries relevant to your investigation.

This view includes a comprehensive set of search and filter fields, enabling you to narrow results based on a wide range of criteria:

Affected User – Identify logs linked to specific users who experienced the issue.
Assigned User – Filter by the person responsible for resolving the issue.
Created At / Modified At – Search logs based on when they were created or last updated.
Modified By – Track who last made changes to a log entry.
Process / Sub Process – Focus on errors related to particular system processes or subprocesses.
Related Entity ID / Type – Locate logs associated with specific records or entities in the system.
Resolution – Search based on recorded resolution outcomes or notes.
Severity – Filter by the criticality of the log (e.g., INFO, ERROR).
Status – Find logs by their current workflow status (e.g., New, Investigating, Closed).
System Log Number (Name) – Search by the unique identifier or name of the log entry.
Teams – Isolate logs managed by or assigned to specific teams.

These flexible search options make it easy to pinpoint relevant log entries, monitor system activity, and track the progress of issue resolution across the organisation.

Managing Status and Resolution¶

To streamline the administration of log entries, the Status and Resolution fields in the System Logs support mass update functionality. This allows administrators and support teams to efficiently manage multiple log records at once without having to update each entry individually.

Key capabilities include:

Bulk Status Updates - Quickly update the status of several logs (e.g., mark multiple entries as "Investigating" or "Closed") to reflect current investigation efforts.
Batch Resolution Entry - Apply resolution notes or standardised outcomes across multiple related logs, saving time and ensuring consistency.
Improved Workflow Efficiency - Ideal for managing high volumes of logs during system reviews, issue triaging, or post-deployment monitoring.

Mass update functionality ensures that System Logs remain organised and up to date, supporting clear visibility and effective resolution tracking across your team.