New suggestion for /orchestration/8.2.0/scripts-deep-dive.html

[Kirizan]

Under the section: Logging in orchestration scripts, while it shows how to use the sandbox.logger, it never tells us where the logs will be placed.

[TomerAdmon]

Thanks @Kirizan 👍 We will add some extra information about the subject.

For now, the CloudShell orchestration package - cloudshell-orch-core is using cloudshell-core for logging. The cloudshell-core package allows us to create a standard logger(qslogger) for all cloudshell packages and shells so all logs will be stored under the same place. For orchestration scripts, the qslogger is creating a folder for every sandbox id and storing all the relevant logs under it. Every orchestration scripts that was executed on the sandbox will have it's on log file with the script name and unique identifier. For example: --- 3b943acf-6eb6-4b55-93ad-6931f7b3d2e6 ----------- Default Sandbox Setup 3.0_31_4B76F04C30D9734D823030A794699E03 ----------- Default Sandbox Teardown 3.0_31_E44EEB519D102F4B95CC00FB2101C0FB

The sandbox logs folder can be found on the following paths: For Windows Execution Server: C:\programdata\QualiSystems\logs For Linux Execution Server: ./usr/share/QualiSystems/logs

Note that logs coming from within python packages can still be stored under the site-packages within the python virtual environment created for the python driver execution.

Thanks for the feedback, Tomer

[TomerAdmon]

@Shnitselon - can we close this one as we added this to the docs?

[Shnitselon]

@TomerAdmon yes