We would like to propose an enhancement to the current log management system in TSplus Remote Access, to improve centralization, configuration robustness, and overall maintainability.
Current issues:
- Log files are spread across multiple folders, making them difficult to centralize or monitor
- The log configuration file currently combines:
- technical settings for the log4net library
- file management parameters (log path, size, retention, verbosity level)
- These configuration files may be overwritten during a TSplus Remote Access upgrade when the log4net library evolves, leading to a loss of any custom configuration..
Proposed improvements:
- Separate the configuration into two distinct files:
- One file dedicated to log4net library settings (dependencies)
- One file for log file management parameters by module (file location, file size, retention policy, verbosity)
- Store global log settings:
- Either in the Windows Registry (HKLM\Software\Digital River\JWTS\Logs)
- Or in a separate configuration file (e.g. C:\ProgramData\TSplus\Logs\global-config.json)
Expose these settings in the Admin Tool:
- Add a new "Advanced > Logs" tab that displays log settings per module
- Allow specifying a centralized log folder, including UNC paths (e.g. \\server\logs\TSplus\) to support open-source log collection tools such as ELK, Graylog, or Wazuh
Benefits:
- Easier centralization and monitoring of logs
- Custom configurations preserved during updates
- Better compatibility with log aggregation and analysis tools
Clearer, more maintainable setup aligned with industry standards. We believe this improvement would provide real value for administrators, especially in multi-server environments and for managed service providers (MSPs).
Best Regards
