Skip to content

Monitor Job Runs

In Wherobots Cloud, Job Runs allows you to monitor the progress of job runs, understand resource consumption, review the execution timeline, and verify configuration settings.

Start a Job Run

This page discusses tracking ongoing or terminated Job Runs. For more information on starting a Job Run, rather than monitoring one, refer to the WherobotsRunOperator Documentation.

Benefits

The Job Runs section of Wherobots Cloud allows you to view and manage all executed Job Runs within your Wherobots Organization.

After starting your Job on Airflow, you can review, filter, or cancel any Job Runs executed within your Wherobots Organization.

Before you start

Before using this feature, ensure that you have the following required resources:

  • An Account within a Professional or Enterprise Edition Organization. For more information, see Create a Wherobots Account.
    • Both Admin and User roles have access to view Job Runs in Wherobots Cloud.
  • (Optional) A Wherobots API key.
    • While you don't need an API key to view Job Runs, you do need an API key to start a Job Run. For more information on initiating Job Runs, see WherobotsRunOperator.

Job Runs Summary View

You can see an overview of your Job Runs, allowing you to monitor and manage your automated spatial data workflows:

  1. Login to Wherobots Cloud.

  2. Click Job Runs.

    Job Run Summary

    The summary view includes the following elements:

    • ID: A unique identifier for each job run.
    • Name: The name of the job.
    • Status: The current status of the job run (e.g., RUNNING, FAILED, COMPLETED).
    • Triggered By: The entity (platform or Organization member) that triggered the job run (e.g., Airflow).
    • Created At: The date and time when the job run was created.
    • Completed At: The date and time when the job run completed (if applicable).
    • Duration: The total duration of the job run.
    • Details: A link to view more detailed information about the job run.

Filter Job Runs

To locate specific job runs, you can filter by job name:

  1. Navigate to Job Runs.

  2. Enter the full or partial name of the desired job within the Job Name field.

    Job Run filter

View Job Run Details

In the Job Runs Summary View, click the Details button next to any job run to view more information about that specific run, including the following:

  • Job ID: Unique identifier for this specific job run.
  • Start Time: Indicates when the Job Run was initiated.
  • End Time: Indicates when the Job Run terminated.
  • Duration: Indicates how much time elapsed between the Start Time and End Time.
  • Triggered By: The system that triggered the job run (e.g., Airflow).
  • Refresh Button 🔄 : Allows you to update the job details with the latest information on-demand.
  • Status: Indicates if the Job is in progress (RUNNING), finished (COMPLETED), or unable to be executed (FAILED).

  • Cancel Button: Allows you to stop an ongoing job.

    Job Run details

Consumption metrics

Each Job Run Details page specifies the consumption metrics and details associated with a specific Job Run execution, including the following:

  • Spatial Units Consumed: Indicates the accumulated Spatial Unit Consumption for this Job Run.
  • Max CPU Utilization: Indicates the accumulated CPU usage for this Job Run.
  • Max Memory Utilization: Indicates the accumulated memory used for this Job Run.

Configuration information

Each Job Run Details page specifies the Configuration information associated with a specific Job Run execution, including the following:

  • General
    • Runtime: Indicates the size of the Runtime associated with the Job Run.
    • Timeout: Specifies the maximum duration the job is allowed to run before being automatically stopped, in seconds. The default is 3600.
    • Region: Specifies the compute region where the Job Run is being executed.
  • Python File Details
    • URI: The location or path of the Python script being executed.
    • Args: The arguments passed to the Python script.

Compare Job Run performance

To compare Job Run performance with different runtime types:

  1. Run a job. For more information on initializing a job and runtime selection, see WherobotsRunOperator.
  2. Run that same job again with either a larger or smaller runtime type.
  3. Review the Detail pages for each executed run to compare performance metrics, specifically:
    1. Duration
    2. Max CPU Utilization
    3. Max Memory Utilization

Cancel Job Run

Wherobots cancels your jobs based on your specification of timeoutseconds in the Job Runs REST API Schema, which defaults to 3600, but you can also cancel a Job in Wherobots Cloud.

To cancel a Job Run within Wherobots Cloud, do the following:

  1. In Job Runs, locate the job you wish to cancel.
  2. Click ... > Cancel.

You can also cancel a Job Run within its Detail page

To cancel a Job Run, you can also go to its Detail page and click the Cancel button.

Job Runs in Audit Logs

If your account is configured to the User(1) role, and you use a service principal-managed API key generated by an Admin(1) in your Wherobots Organization, actions are attributed to the service principal in Audit Logs, with the shown as Admin responsible solely for the API key creation.

  1. For more information on Admin and User capabilities, see Organization Roles.

Limitations

  • Spatial Unit Consumption, Max CPU Utilization, and Max Memory Utilization metrics are only kept for 90 days.
  • Spatial Unit Consumption can take several minutes to display on a run's Detail page.