Sandbox Listing Page

The container-based and non-container-based sandbox that are created within a project will appear on the Sandbox listing page. The configuration options for creating a sandbox can be accessed using the plus icon. For more details, see Creating Sandbox →

The information and actions displayed for the listed sandbox are explained below:

Name #

This column displays the Name and State of the listed sandbox. User can hover over the state icon to check if the environment is container-based or non-container-based.

On the listing page, the container-based and non-container-based sandbox along with their states can be classified as shown below:

The states that are possible for all types of sandbox are represented using below color codes:

Green: Active state.

Yellow: In-Progress/Launching state.

Orange/Red: Failed state.

Grey: Stopped state.

Icon	Sandbox Type
	Container-based sandbox
	Non-Container-based (Python, PySpark and Scala) sandbox
	Non-Container-based (VS Code) sandbox
	Non-Container-based (RStudio) sandbox

User #

This column displays username who has created the sandbox.

Hardware Tier #

This column information is only applicable for a container-based sandbox.

It displays the hardware tier (i.e., Small, Medium, Large or Custom) information which was specified during sandbox configuration.

CPU/Memory #

This column displays sandbox CPU/memory utilization information out of the allocated hardware tier.

Launched #

This column displays the time since the sandbox was last launched.

Accessed #

This column displays the time since the sandbox was last accessed.

Actions #

This column provides user with certain set of actions that can be performed on the listed container-based and non-container-based sandbox.

Given below are the actions for the container-based sandbox:

View Details #

The user can access logs for the sandbox with this option.

In the logs tab, there are options available to list the required number of lines, filter the log results based on user input and also an option to clear the log results.

Stop/Relaunch #

The user can stop an active sandbox with the stop action. Upon termination of Sandbox, the user will be notified via an email.

The user can relaunch an inactive sandbox with this action. The configuration can be edited before a sandbox is relaunched.

Delete #

The user can delete the existing sandbox with this option.

Given below are the actions for the non-container-based sandbox:

Generate Executable #

Option to initiate generation of the PEX file for the desired Sandbox.

It will only be enabled when a sandbox is in an active state.

Given below are the next set of actions that will appear for further user action, once the Generate Executable option is clicked:

Export Status #

In-Progress: PEX file generation is in-progress.

Completed: PEX file is generated successfully and is ready for download.

Failed: PEX file generation has failed.

Download #

Option to download the generated PEX file by either of the following ways:

NFS: User can select the NFS option and export the PEX file by providing the desired NFS path.

HDFS: User can select the HDFS option and export the PEX file by providing the desired HDFS connection and path.

Desktop: User can select the Desktop option and download the PEX file.

Relaunched Sandbox List #

The sandbox that are relaunched from the Sandbox listing page will appear in this section. The user can search for the relaunched sandbox in the available search bar.

The information that is displayed for the relaunched sandbox is explained below: