Local Storage of Studio/Agent Logs

This section introduces the logs generated when using akaBot Studio/Agent.

Contents

1. Explanation
2. Log Output Locations
3. Types of Logs
4. Sending Logs

1. Explanation

When akaBot Studio or Agent performs any operation, several log files are automatically generated, and the logs are written into these files. This section introduces the log output locations and types of logs.

*Note: The operation was confirmed on akaBot Studio version 2.2.0.1. *Note: Some terms may vary depending on the version.

2. Log Output Locations

There are three log output locations. *Insert the OS user running akaBot Studio/Agent where it says "PC Username".

*The json files included are not logs, but they may be necessary for checking configuration information, so they are listed.

If you set Explorer to display "hidden files," you can proceed from Explorer by clicking.

*For the setting method, refer to "Show hidden files (Microsoft)."

Additionally, if you click "Open Log" on the akaBot Studio screen, item 1 "C:\Users\PC Username\AppData\Local\akabot\Logs" will be displayed.

3. Types of Logs

For item 1 "C:\Users\PC Username\AppData\Local\akabot\Logs": The main logs are output from Studio or Agent to this folder and are automatically saved.

Example Log Files:

• yyyy-MM-dd_BotService.log
• yyyy-MM-dd_Studio.log
• yyyy-MM-dd_BotAgent.log
• yyyy-MM-dd_BotExecutor.log
• yyyy-MM-dd_HHmmss_Studio_[WorkflowName].[count].log
• yyyy-MM-dd_HHmmss_Agent_[WorkflowName].[count].log

Some log files may not be generated depending on the execution status.

*The log output timing varies depending on the type of log.

*The maximum size of a log file is about 10MB. When this size is exceeded, the subsequent logs will be output to a new log file.

As new log files are generated, the [count] in the log file name increments by 1.

The types of logs, naming conventions of log files, and log output timings may vary depending on the version of Studio/Agent.

Example for version 2.1.1.2:

Example Log Files:

• yyyy-MM-dd_Activation.log
• yyyy-MM-dd_BotService.log
• yyyy-MM-dd_Studio.log
• yyyy-MM-dd_BotAgent.log
• yyyy-MM-dd_BotExecutor.log
• yyyy-MM-dd_Studio_Execution.log.{count}
• yyyy-MM-dd_Execution.log.{count}

For item 2 "C:\Users\PC Username\AppData\Local\akabot": A "settings.json" file is generated in this folder. Detailed information, including Agent configuration information, is output when the robot is executed by Agent.

*Although not logs, they may be necessary for checking configuration information, so they are listed.

For item 3 "C:\ProgramData\akabot\Logs": The logs output to this folder are similar to those in item 1 "C:\Users\PC Username\AppData\Local\akabot\Logs" but contain more detailed system information.

Example Log Files:

• yyyy-mm-dd_InstallUtil.log
• yyyy-mm-dd_BotService.log

Some log files may not be output depending on the execution status.

4. Sending Logs

When contacting support due to a problem with akaBot Studio/Agent, providing detailed information about the situation and all log files from the date the issue occurred can help resolve the problem. Even if the log files are 0KB (empty), please include them.

When sending, it is helpful to organize the folders to show which folder each log was in and compress them into a zip file.

Example Folder Structure in the Zip File if the issue occurred on July 1, 2022:

Logs

 ┗UserFolder_akabotlogs

  ┗2022-07-01_Activation.log

  ┗2022-07-01_BotService.log

   ・

   ・

   ・

 ┗UserFolder_akabot

  ┗settings.json

 ┗ProgramFolder_akabotlogs

  ┗2022-07-01_InstallUtil.log

  ┗2022-07-01_BotService.log

   ・

   ・

   ・