Vault 7: Projects

This publication series is about specific projects related to the Vault 7 main publication.
SECRET//ORCON//NOFORN
16.4 Logging
The Gibson components generate logs recording their activity. Each component
generates their own log files.
Log levels are based on the Python logging levels such that the lower the value, the
more verbose the log. The values are mapped to levels as follows:
Value Level
10 debug
20 info
30 warn
40 error
50 critical
If the logging.running_directory key is defined in the The Gibson configuration, the
components will generate a running log in that directory. Log messages are always
added to the log file for a given component. The log file will roll over every 1 MB.
If the logging.session_directory key is defined in the The Gibson configuration, the
components will generate a session log in that directory. A new session log is
generated each time a component is invoked. Typically, the session logs are
collected using the Log Collector and recombined using the Log Extractor.
136
SECRET//ORCON//NOFORN