Skip to main content

What can we help you with?

Search

Logging

Sergei Ostapov
  • Updated

Introduction

Studio Pro features different types of logging. Logs can reflect the system state and provide the information, necessary for debugging or analyzing the execution of workflows.

Studio Pro records logs in multiple places depending on whether the workflow is saved to a .neek file or not.

  • Unsaved .neek files save their logs in C:\Users\{username}\electroNeek\logs\
  • Saved .neek files save their logs in {neek_file_location}\logs\{neek_file_name}\
    • For example: if your .neek file is located at C:\Users\Administrator\Desktop\Test\Test.neek your log folders would be at C:\Users\Administrator\Desktop\Test\logs\Test

The workflow logs are accessible through Studio Pro. It will open the correct location both if the workflow is saved or not.

1en.png

 

Types of Logs

Studio Pro maintains logs for the console (within Studio Pro), exceptions from running Studio Pro, autologs (when enabled) of your system’s information, Studio Pro configuration, and every step of the execution of bots.

 

Autologs

The autolog file is the main and the most important source of information that you can receive and send to the Support Team in order to solve a certain issue. 

It contains all the information in regard to your machine specifications, Studio Pro’s and its components versions, and every step of the workflow as well. Thus, it is the most detailed log file created automatically. 

There is a certain structure of the file:

  1. Environment information (OS version, components versions, etc.)
  2. Information describing every step of the bot. The start and end steps of the bot execution are also recorded. 

The information is displayed as: “Time of log-message - JSON”, for example:

16:26:46.328 {"programs":[{"program":"InternetExplorer","version":"11.789.19041.0"},

{"program":"Chrome","version":"91.0.4472.124"},

{"program":"1C"},{"program":"ElectroNeek Studio","version":"5.6.11.0"},

{"program":"ElectroNeek Robot","version":"5.6.11.0"},

{"program":"msedgedriver.exe","version":"79.0.313.0"}],"windows":{"caption":" Windows 10 Pro","version":"10.0.19042","csd_version":0,"os_architecture":"64-bit"},

"cpu":{"name":"AMD Ryzen 7 3700U with Radeon Vega Mobile Gfx","number_of_cores":4,"number_of_logical_processors":0,"number_of_logicalprocessors":8},

17:03:21.706 {"activity_name":"START","file":"C:\\Users\\owlyo\\Desktop\\Bot Text\\Text bot.neek
","script_id":"b8c90d98-e2a5-49c2-9ddd-28d77172bb59","memory_usage":117484,"version":{"launched_by":"5.6.11","created_in":"5.6.11","updated_in":"5.6.11"},"start_time_iso":"2021-06-29T12:03:21.692Z","activity_group":"General","end_time_iso":"2021-06-29T12:03:21.693Z","duration_ms":1,"status":"success","error_message":null,"output_result":null,"executed_branch":"next","parameters":[{"name":"version","value":"4.0.0"}

 

Studio Pro Autologs

To enable that type of logging, navigate to “Settings” → “Execution” and enable the “Automatically create logs for each run” option. 

2en.png

 

The autolog file will be saved in the same directory as the workflow. 

For example: 

C:\Users\Username\Desktop\Project 1\logs\Project 1\studio_autologs

 

As of the 8.5 version, autologs contain the following information:

Environment information:

  • Standalone or Dependent
  • Application version
  • Google Chrome/MS Edge version
  • Webdriver version
  • Extension's version
  • User information:
    • Region
    • uID
    • License
    • Permissions

Events:

  • Process flags
  • Login - with a link to a .neek-file link
  • Logoff
  • Start workflow
  • End workflow
  • Messages from the Studio Pro console

Network events

  • Failed requests with URL, parameters, message
  • Connection to sockets (with URL)
  • Socket connection failures (with URL)

 

Bot Runner Autologs

The same can be applied to the ElectroNeek Bot Runner application. Navigate to this article to know more about logging in Bot Runner. 

 

Console Logs

All of the information that is displayed in the Studio Pro console while working with the product and while the workflow is running is logged in a separate file. This can be convenient in situations where detailed logging of each action is not required, while the console displays explanatory texts for the user (for example, values of key variables), which allows you to immediately see this in the console log file, instead of searching for this information in the detailed autologs.

 

These logs are located at:

C:\Users\Username\electroNeek\logs\

OR

Under a log folder where the .neek file is saved. For example: if your .neek file is located at C:\Users\Administrator\Desktop\Test\Test.neek,  your log folders would be at C:\Users\Administrator\Desktop\Test\logs\Test

 

The structure of console logs looks like this:

[DATE and TIME] : [MESSAGE TYPE]: MESSAGE

Here is an example:

[2021-06-28T10:00:12.199Z] : [info]: ---------------------------------------------

[2021-06-28T10:00:26.728Z] : [success]: Bot started.

[2021-06-28T10:00:26.730Z] : [info]: Robot start

[2021-06-28T10:00:30.160Z] : [success]: Bot finished successfully, total execution time: 3s 427ms.

 

Exception Logs

Exception logs log the exceptions encountered by Studio when running. These logs typically refer to the environment issues or issues with Studio that do not necessarily coincide with the running of a workflow.

 

Like the other logs, Exception Logs are only located in the ElectroNeek folder located at C:\Users\Username\ElectroNeek\logs\studio_exceptions.

OR

Under a log folder where the .neek file is saved. For example: if your .neek file is located at C:\Users\Administrator\Desktop\Test\Test.neek,  your log folders would be at C:\Users\Administrator\Desktop\Test\logs\Test

 

The structure of the Exception Log file displays the name of an error and the place where it occurred.

 

For example:

Unhandled Rejection at Promise

      getaddrinfo ENOTFOUND account.electroneek.co

Error: getaddrinfo ENOTFOUND account.electroneek.com

    at PortalBackendApi.transformError (C:\Program Files\ElectroNeek\Robot\resources\app.asar\dist\main.js:1:701496)

    at C:\Program Files\ElectroNeek\Robot\resources\app.asar\dist\main.js:1:701043

    at runMicrotasks (<anonymous>)

    at processTicksAndRejections (internal/process/task_queues.js:97:5)

Related articles