Management Logs

The AAM module incorporates a comprehensive Management Log to provide an audit trail of all significant events occurring within the system. This log captures both user-initiated actions and automated system-triggered events related to account monitoring and management.

Log Entry Structure

Each entry in the Management Log consists of the following components:

• Timestamp: A precise timestamp indicating when the logged event occurred, presented in the browser's local time.

• Event Type: This field enumerates the type of action that was recorded. Common action types include (but are not limited to):

  • Enable: Monitor enabled via UI toggle

  • Disable: Monitor disabled via UI toggle

  • Created: Creation of a new AAM monitor

  • Auto-Flatten: Automated flattening event at configured time

  • Reset: Manual monitor reset triggered after a stopped condition

  • Stop Monitor: Monitor disabled due to a threshold being reached

  • Delete: An AAM monitor has been deleted from an account

• Account: Specifies the account that is the direct subject of the logged activity as identified within the client.

• Message: A descriptive message that details what occurred. Messages can originate either from system actions or when adjustments are saved through the dashboard, depending on what caused the log event. These messages will be textually specific, and may not always provide a full explanation as each specific case can be dependent on various system logic, so this is best used for review or basic diagnostics purposes.

Example of a Management Log for actions taken in AAM

Log Generation

Log entries are generated under the following circumstances:

• User-Initiated Actions: Actions originating from user interactions through the CrossTrade Dashboard, including:

  • Monitor creation, modification (thresholds, settings, flattening times), restart, and deletion operations.

  • Enabling/disabling monitors using the on/off toggle.

• Automated System Actions: Actions performed automatically by the AAM system due to the execution of scheduled processes such as:

  • Automated flattening event triggers during the EOD operation

  • Automated "kill" operations triggered by defined profit/loss threshold breaches.

• Automated deactivation actions due to non-flat positions on session open.

Data Handling & Presentation

• Real-time log generation: Logs are pushed and updated asynchronously in the application and may appear as soon as the operations have been resolved in the backend, sometimes causing the pagination or offset to dynamically adjust, or create a minor pause while new records are fetched from the server and rendered.

• Persistency: All Management Log entries are persisted in a server-side datastore, creating an auditable and consistent activity log of actions that can be reviewed on a session-by-session basis. This ensures log records persist over time and over multiple logins from any user platform.

• Pagination: To accommodate larger sets of data, logs are presented with pagination controls to efficiently traverse data.

Purpose & Intended Usage

The AAM Management Log serves multiple crucial functions:

• Auditability: Provides a clear record of all AAM actions, enhancing system transparency and providing an audit-able history for compliance needs.

• Issue Tracking: Facilitates identification and analysis of problems or unexpected behaviors through a detailed account of significant operations.

• Account Management History: Acts as a reference for past actions, helping in the continuous monitoring of individual account activity.

This log is designed for a broad range of technical understanding. A clear log of every significant system activity enhances usability and overall functionality in a manner that enables all users to review and manage operations as needed.