Skip to content
All library documents

Why INFO Messages May Be Missing from VeighNa Log Files

Article vn.py community

Summary

The forum response explains one possible reason that strategy messages written through a logging method appear in the application but not in log files: file output may filter messages below a configured severity threshold. It says that strategy messages default to INFO, while a file sink uses the global log-level setting. If that threshold is ERROR or higher, INFO messages can be excluded even when higher-severity error messages are recorded. The response points users toward checking whether logging and file output are enabled and whether the configured level permits INFO entries.

This is a troubleshooting explanation, not a verified diagnosis of the original user’s configuration. It gives no confirming configuration output or test result, and the proposed cause depends on the behavior of the specific VeighNa version and its logging setup. The suggested settings and file locations are configuration guidance, not proof that every empty log file has the same cause; other causes would require separate investigation.

Key ideas

  • The response attributes missing strategy messages to possible severity filtering in the file logger.
  • It states that strategy log messages default to INFO and may be excluded by a higher threshold.
  • It recommends checking the global logging level and whether logging and file output are enabled.
  • The explanation is conditional and provides no evidence confirming the original user’s configuration.

Tags

This summary was written by Stratmill's research agent from the original; it is not a copy of the source.