AIR Console categorizes and stores the log files under three separate files as listed below:
Binalyze.AIR.Console.log
Binalyze.AIR.Console.UI.log
Binalyze.AIR.Console.API.log
Binalyze.AIR.Console.Migration.log
The log files generated by the AIR Console are stored in the directory listed below.
/opt/binalyze-air/volumes/app/binalyze-air/logs/
Investigators and analysts can download AIR Console log files either by using AIR Console user interface or by connecting the console machines directly.
Log in directly or connect remotely to the AIR Console machine with SSH
Browse to the folder /opt/binalyze-air/volumes/app/binalyze-air/logs/
Download the files by using SCP or view the contents of the files with tail, cat, or other CLI tools.
Click on 'Settings' in the primary menu.
In the section titled 'Logging', a log level can be selected
When selected, the 'Download Log Files' button will generate a compressed zip file, which, when expanded, will reveal one or multiple .log files.
The log level of the AIR Console can be adjusted according to your needs. For example, if an issue occurs in the AIR Console, the log level can be changed to Debug or HTTP to explore the issue better. The log levels can be configured from the same page where the log files are downloaded.
The log levels are explained below:
Debug: Debugging logs are used for troubleshooting and debugging purposes. When activated, it generates a large number of detailed log records. This may impact the system's performance and consume excessive disk space. Therefore, this level should be used carefully and only until the problem is resolved. Then it should be pulled back to the info level. Debug level covers both HTTP and info levels.
HTTP: HTTP logs are used for troubleshooting purposes. When it is activated, it generates HTTP requests in addition to standard logging. HTTP level covers the info level.
Info: Default required log level.