- Accounts & Connection Management
- Data Management & Analysis
- Price Monitoring
- Charting
- Trading
- Scanners
-
Builders
-
Manual Strategy Builder
- Main Concept
- Operand Component
- Algo Elements
-
Use Cases
- How to create a condition on something crossing something
- How to create an indicator based on another indicator
- How to calculate a stop loss based on indicator
- How to submit stop order based on calculated price
- How to calculate a current bar price using a price type from inputs
- How to Use a Closed Bar Price
- Automatic Strategy Builder
-
Manual Strategy Builder
- Autotrading
- FinScript
- Trade Analysis
- Media Feeds
- Logs & Notifications
- UI & UX
The Log Viewer module in the Automatic Strategy Builder (ASB) is a vital tool for monitoring and diagnosing various events and actions within the application. It captures and displays different types of messages from various parts of the application, helping users understand the internal workings and identify any issues.
Types of Messages
The Log Viewer categorizes messages into several types, each serving a specific purpose in terms of information and debugging:
Â
Trace Messages
- Description: Trace messages provide detailed information about the execution flow of the application. They are used to trace the path of code execution, offering granular insights into the operations performed.
- Purpose: These messages are particularly useful for developers when diagnosing specific issues or understanding the detailed workings of the application.
Â
Debug Messages
- Description: Debug messages offer information that is useful for debugging purposes. They provide insights into the application's state, including variable values and the outcomes of certain operations.
- Purpose: These messages help in identifying bugs and understanding the behavior of the application during development and troubleshooting.
Â
Info Messages
- Description: Info messages provide general information about the application's operations. These messages typically confirm that certain tasks have been completed or provide status updates.
- Purpose: They help users and developers stay informed about the normal functioning and progression of tasks within the application.
Â
Warning Messages
- Description: Warning messages alert users to potential issues that are not critical but may require attention. They indicate situations that could lead to problems if not addressed.
- Purpose: These messages help in preemptively identifying and mitigating issues before they escalate into more serious problems.
Â
Error Messages
- Description: Error messages indicate critical issues that have occurred within the application. These messages often highlight failed operations or unexpected conditions that need immediate attention.
- Purpose: They are crucial for identifying and resolving errors that could impact the application's functionality or performance.
Â
Using the Log Viewer
The Log Viewer is designed to be user-friendly and informative, providing a comprehensive view of the application's internal messages. Users can filter messages based on their type, allowing for focused troubleshooting and analysis.
Â
Log Reports Storage
Generated log reports are stored in the following directory:
Replace XXX with your specific user name. This path ensures that all log files are organized and easily accessible for review and troubleshooting.
Â
Summary
The Log Viewer module in the ASB is an essential tool for monitoring the application's internal events and diagnosing issues. By categorizing messages into trace, debug, info, warning, and error types, the Log Viewer provides users and developers with detailed insights into the application's operation and state. This module is crucial for ensuring the smooth functioning of the ASB and for efficiently identifying and resolving any issues that arise.
- Accounts & Connection Management
- Data Management & Analysis
- Price Monitoring
- Charting
- Trading
- Scanners
-
Builders
-
Manual Strategy Builder
- Main Concept
- Operand Component
- Algo Elements
-
Use Cases
- How to create a condition on something crossing something
- How to create an indicator based on another indicator
- How to calculate a stop loss based on indicator
- How to submit stop order based on calculated price
- How to calculate a current bar price using a price type from inputs
- How to Use a Closed Bar Price
- Automatic Strategy Builder
-
Manual Strategy Builder
- Autotrading
- FinScript
- Trade Analysis
- Media Feeds
- Logs & Notifications
- UI & UX