Managing a Workbench Instance
Managing Workbench instances ensures stable, secure, and efficient use of advanced analytics environments within Noreja. Each user operates an individual Jupyter-based Workbench instance, while administrators maintain full visibility and control through centralized management settings. By monitoring instance status, usage timestamps, and lifecycle actions such as stop or restart, organizations can optimize system resources, prevent data loss, and maintain a clean analytical infrastructure.
Each user gets an individual Workbench instance which is started up as soon as the user clicks on Workbench in the main menu. Admin users can see a list of all existing Workbench instances in when clicking on the Settings button in the top-right corner and then navigating to Workbenches in the side bar on the left. It should look like the figure shown below.
The visualized tables lists all Workbench instances and pinpoints the following information:
- ID: This is the technical ID of the Workbench instance. It is only relevant for the technical support in case of trouble shooting.
- User: This is the user name of the person who started and worked with this particular Workbench.
- Created: This is the timestamp at which the Workbench instance was first created.
- Last usage: This is the timestamp at which the Workbench instance was last used. If this timestamp is a long time in the past, you can check whether the instance should be deleted.
- Status: The status can be Started (user can use is for analysis purposes) or Stopped (user can not open it and has to ask the admin to restart the instance).
- Link: Pressing the Link will open up the Workbench instance in an new tab also without the original Noreja menu on the very top. This can be used for long working sessions.
- Actions: Pressing the button Stop will shut down the Workbench instance and put it into the status Stopped. It is important that the work progress has been saved before shutting it down. Otherwise data will be lost and cannot be restored. Pressing Restart will shut down a running instance and start it again. Here, it is also important to save the current work progress before restarting an instance.