Rate This Document
Findability
Accuracy
Completeness
Readability

Log Description

Operation Logs

Operation logs record information about modifications performed on the DevKit framework or other extensions and scheduled tasks of the system. The following operations are logged:

  • Logging in or out
  • Uploading a file
  • Creating a task
  • Creating or deleting a user
  • Locking or unlocking a user
  • Modifying user configuration
  • Changing the password
  • Downloading or deleting a report
  • Rebuilding a software package
  • Setting the maximum number of online users
  • Setting the run log level
  • Changing the historical report threshold
  • Restoring or upgrading the dependency dictionary
  • Restoring or upgrading the software template
  • Periodically deleting operation logs
  • Checking the certificate validity
  • Importing or replacing a certificate
  • Setting the certificate expiration alarm threshold
  • Managing the weak password dictionary
  • Updating the working key
  • Uninstalling, installing, and upgrading subtools

Run Logs

Run logs record necessary information during program running, helping developers or users quickly locate and rectify faults.
Table 1 Log module description

Log Module

Description

common.log

Records necessary information during extension running, helping developers or users quickly locate and rectify faults.

install_plugins.log

Records the installation information of extensions.

operation_log/his_operation_log.csv

Records the operation logs of different users on the Kunpeng DevKit. For details, see Operation Logs.

porting/*.log

Records necessary information during Porting Advisor running, helping quickly locate and rectify faults.

module_log/*.log

Common run logs of plugins:

  • all_asm.log records necessary information when the pure assembly files are scanned and ported during source code porting.
  • inline_asm.log records necessary information when the inline assembly files are scanned and ported during source code porting.
  • makefile.log records necessary information when the make file is compiled.
  • cmakefile.log records necessary information when the cmake file is compiled.
  • prevision.log records necessary information during preprocessing.
  • matricization_check.log records necessary information when matricization check is performed.
  • weakconsistency.log records necessary information when memory consistency check is performed.

affinity/*.log

Records necessary information during Affinity Analyzer running, helping quickly locate and rectify faults.

debugger/*.log

Records necessary information during Compiler and Debugger running, helping quickly locate and rectify faults.

devtools/*.log

Records necessary information during Development Assistant running, helping quickly locate and rectify faults.

java_perf/*.log

Records necessary information during Java Profiler running, helping quickly locate and rectify faults.

sys_diagnosis/*.log

Records necessary information during System Diagnosis running, helping quickly locate and rectify faults.

sys_perf/*.log

Records necessary information during System Profiler running, helping quickly locate and rectify faults.

devkitframework/devkit_framework.log

Records request information about the DevKit framework service, helping developers or users quickly locate and rectify faults.

devkitplugins/devkit_plugin.log

Records request information about DevKit plugin services, helping developers or users quickly locate and rectify faults.

NOTE:

When the run log files of each module reach 100 MB, the log files are automatically compressed into a package as backup and stored in the /opt/DevKit/logs directory. The /opt directory is the tool installation directory, which can be customized during tool installation. A maximum of two compressed packages can be stored on the server. When a third package is generated, the first package will be deleted by default.