Navigating Runtime Management

As discussed in the Runtime Management Overview article, Syntasa's Runtime Management Page emerges as a pivotal tool, offering insights and control over the lifecycle of runtime instances within the Syntasa ecosystem. This article covers the following topics:

How to navigate to the RunTime Management Screen?

We can navigate to the Runtime Management screen in 2 ways:

  1.  Using Runtime Page 
    • Click on the hamburger menu (three horizontal lines) in the top left corner of the screen.
    • Under the "Resources" section, select "Runtimes".
    • Next to the "Runtimes" title, you'll see a link that says "Go to Runtime Management". Click on that link.

  2. Using Activity Screen
    • Click on the hamburger menu again.
    • This time, under the "Platform" section, select "Activity".
    • On the left-hand side menu, look for the "Runtime Management" icon (it might be the last option). Click on that icon.

Understanding the Runtime Management Screen

Once you're in the Runtime Management screen, you'll see a table with various columns. Let's break down what each column means:

  • Runtime Template - Displays the name of the runtime template in use. You can learn more about runtime templates by visiting the 'Runtime Management Overview' article and the 'Runtime Overview'.
  • Instance Name - This is the name of the instance being used by an object like an app or a notebook. If a job is run without interactive mode, the instance name will match the runtime template name.
  • Runtime Type (Image Type) - Indicates the type of runtime being used, such as GCP DataProc, AWS EMR Cluster, or Kubernetes container. For Kubernetes containers, the image type value will also be displayed in brackets.
  • Runtime Mode -There are three runtime modes:
    • App-Job: Represents jobs run without interactive mode in applications.
    • App-Interactive: Represents jobs run with interactive mode in applications.
    • Notebook: Represents runtimes used by Syntasa notebooks.
  • Status - Shows the current status of the instance, including Creating, Running, Stopping, Stopped, or Deleting/Deleted (for interactive mode instances).
  • Uptime - Displays the duration for which the instance has been running.
  • Start Time - Indicates when the instance was started.
  • End Time - Displays when the instance was ended.
  • Cost per Hour - Shows the total cost of the runtime template for one hour of usage.
  • Total Cost - Reflects the total cost incurred for running the instance.

Understanding Instances for Each Object

Let's explore how each of the three runtime modes (App-Job, App-Interactive, and Notebook) creates and manages instances:

App-Job

    • It represents jobs run without interactive mode in applications.
    • When a new job is initially executed without interactive mode, it generates a new entry for the instance in the Runtime Management Screen.
    • Upon subsequent executions of the same job using the same runtime template, a new entry is created displaying details of the new instance. Consequently, both the old and new instance details are displayed in separate rows.

App-Interactive

      • Represents jobs run with interactive mode in applications.
      • When a new instance is created under Interactive Mode, it generates a new entry in the Runtime Management Screen, displaying instance details regardless of the number of jobs run using the same instance. You can execute any number of jobs using the same instance, with the screen aggregating the costs incurred for each job.
      • Stopping and restarting the instance from the application will overwrite the existing entry with new details, displaying only the uptime and cost details of the new instance.
      • Deleting the instance under interactive mode and adding a new one will result in the creation of a fresh entry for the newly added instance.

Notebook:

    • Represents runtimes used by Syntasa notebooks.
    • When a new instance is created under Syntasa Notebook, it generates a new entry in the Runtime Management Screen, displaying instance details regardless of the number of Synatsa Notebook using the same instance. You can use the same instance on any number of Synatsa notebooks, with the screen aggregating the costs incurred for each notebook.
    • Stopping and restarting the instance from the application will overwrite the existing entry with new details, displaying only the uptime and cost details of the fresh instance.

Exporting the Runtime Insights

At the top right corner of the screen, you'll find a button to export the complete runtime insights displayed in the table. While Syntasa enables filtering of table data using each column filter, there are scenarios where advanced filtering and total cost calculation may be necessary. Exporting the data to a CSV file proves invaluable in such cases. Here's how to do it:

  1. Navigate to the Runtime Management Screen.
  2. Locate the Export icon at the top right corner of the table.
  3. Click on the Export icon.
  4. A CSV file containing all the table data will be downloaded automatically.