How do I configure v4Debug.dat for enhanced logging?
This article is applied to MetaDefender Endpoint Security SDK (OESIS) releases deployed on Windows, MacOS and Linux systems.
Overview
The v4Debug.dat file enables a logging mechanism that can be used to extract necessary logs. Creating an empty v4Debug.dat file in the deployment folder (Working Directory) of the binaries is usually sufficient to initiate logging. For more specific logging configurations, you can add parameters to the v4Debug.dat file.
Arguments Description
| Argument | Description |
|---|---|
debug_log_output_path |
|
debug_log_level |
|
debug_log_components |
|
debug_log_file_size |
|
debug_log_folder_size |
|
debug_log_time |
|
debug_log_count |
|
Logging output
Resulting log files will follow this format:
v4DebugInfo_[EPOCH_TIME_SECONDS]_[EPOCH_TIME_MILLISECONDS]_P[PROCESS_ID].log
Example: v4DebugInfo_1646211492_1791146406_P6624.log
Sample Configuration
A full sample config is available for reference:
{ "debug_log_output_path": "%userprofile%\\Desktop\\OPSWAT\\", "debug_log_level": "ALL", "debug_log_components": ["ALL"], "debug_log_file_size": 5, "debug_log_folder_size": 100, "debug_log_time": 72, "debug_log_count": 30}If Further Assistance is required, please proceed to log a support case or chatting with our support engineer.
