Debug logging

Enablding debug logging level on MetaDefender Core should only be used when absoluately necessary, and advised by OPSWAT team.

Letting MeteDefender Core operate for a long time under debug logging mode will likely cause performance degradation, out of disk space, and possibly IO bottleneck issue on the system.

Tips: We should only enable the debug logging level when:

  • We already know steps how to reproduce or trigger the issue symptom.
  • Or, we already know the issue will very likely come back very soon.
  • Or, OPSWAT team checked and confirmed there should be more useful information tracked with debug log and relevant to the issue.
  1. To provide debug logs for the OPSWAT support team, the level of the logfile for the given service ometascan must be set to debug (see how at MetaDefender Configuration).
  2. Next, execute the scenarios requested by the support team, and collect the generated log files from the configured location (see how at How to Create Support Package?).
  3. After that the log level should be set back to info. In debug level the size of the logfile will increase significantly.

For information on how to interpret the log files consult: Log message format

Type to search, ESC to discard
Type to search, ESC to discard
Type to search, ESC to discard
Next to read:
How to Read the Metadefender Core Log?
On This Page
Debug logging