Diagnosing Empty VeighNa Log Files Through Log-Level Configuration
Summary
The forum thread describes a case where a VeighNa application connected to CTP and completed strategy orders, yet its daily log file remained empty. The user found that log events reached the logging engine and initially had logging enabled with a restrictive CRITICAL level. A reply recommended lowering the threshold to DEBUG, and the user reports that changing the level to DEBUG through the application settings resolved the issue.
The thread also explains why editing the settings dictionary directly did not take effect: values loaded from the saved JSON settings file override that dictionary. The practical lesson is to check both the active log threshold and the configuration source actually used at runtime. A reply notes that CTA strategy logs may be stored separately and can be exported through the graphical interface. This is a troubleshooting report, not a general guarantee about every logger setup; behavior may depend on application configuration and log type.
Key ideas
- A restrictive logging threshold can prevent lower-severity events from appearing in the log file.
- The thread reports resolving the issue by setting the log level to DEBUG in the active application settings.
- Saved JSON settings can override values changed directly in the settings dictionary.
- CTA strategy logs may be handled separately and can be saved through the graphical interface.
Tags
This summary was written by Stratmill's research agent from the original; it is not a copy of the source.