CrossTrade Docs
CrossTrade.io
  • Welcome!
    • Set Up Guide
  • Getting Started
    • Installation
    • User Dashboard
      • XT Control Panel
      • Command Tester
      • Command Builder
    • Alert History
    • TradingView Alerts
      • Dynamic Variables
      • XT Alert Builder
      • Example Indicators
      • Example Strategies
    • VPS Connection Guide
  • Webhooks
    • Overview
    • Commands
      • Place Order
      • Flat Place Order
      • Close Position
      • Reverse
      • Reverse Position
      • Flatten Positions
      • Flatten Everything
      • Cancel Order
      • Cancel Orders
      • Cancel All Orders
      • Cancel Replace
      • Change Order
      • Close Strategy
    • Advanced Options
      • Multi-Account Placement
      • Flatten First
      • Require Market Position
      • Max Positions
      • Bracket Orders
      • Percentage and Tick Prices
      • Limit Order Timeouts
      • Trading Window
      • Bypass Trade Windows
      • Delay Timer
      • Rate-Limiting
      • Alert Commenting
      • Kill Switch
      • Notes
    • Examples & Use Cases
    • Troubleshooting
  • Account Manager
    • Overview
      • How It Works
      • Dashboard
      • Global Settings
      • Frequently Asked Questions (FAQ)
    • Monitors
      • Profit/Loss Thresholds
      • Minimum Profit Drawdown
      • Trailing Drawdown
      • Advanced Usage
    • Account Settings
      • Auto-Flattening
      • Trading Windows
    • Management Logs
  • NinjaTrader
    • ATM Strategies
      • Creating ATM Template
    • Optimizing NinjaTrader Performance
    • Enabling Multi-Provider Mode
  • CrossTrade API
    • Overview
    • Authentication
    • Rate Limiting
    • Webhook Trading
    • Accounts
      • GET Accounts Summary
      • GET Accounts
      • GET Account
    • Positions
      • GET Positions
      • GET Position
      • POST Close Position
      • POST Reverse
      • POST Reverse Position
      • POST Flatten Positions
      • POST Flatten Everything
    • Orders
      • GET Orders
      • GET Order
      • GET Order Status
      • POST Cancel Order
      • POST Cancel Orders
      • POST Cancel All Orders
      • POST Place Order
      • POST Flat Place Order
      • POST Replace Order
      • PUT Change Order
    • Strategies
      • GET Strategies
      • GET Strategy
      • POST Close Strategy
    • Executions
      • GET Executions
      • GET Execution
    • Quotes
      • GET Quote
  • Changelog
    • XT Versions
    • All Updates
  • Affiliate Program
    • Media Kit
  • Social Links
    • Discord
    • TradingView
    • YouTube
    • X (Twitter)
    • Instagram
    • Facebook
    • Reddit
    • Website
    • Blog
Powered by GitBook
On this page
  • Log Entry Structure
  • Log Generation
  • Data Handling & Presentation
  • Purpose & Intended Usage
  1. Account Manager

Management Logs

PreviousTrading WindowsNextATM Strategies

Last updated 2 months ago

The NAM 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 NAM 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 NAM monitor has been deleted from an account

    • Edit: A configuration changed occurred in the 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.

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 NAM Management Log serves multiple crucial functions:

  • Auditability: Provides a clear record of all NAM 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.

Example of a Management Log for actions taken in AAM
Rows of continuous monitor Management Logs shown for CrossTrade's Active Account Management software