> ## Documentation Index
> Fetch the complete documentation index at: https://docs.wherobots.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Workload History

> Learn how to monitor and analyze your workloads in Wherobots Cloud using the Workload History feature

export const FontColor = ({color, children}) => {
  return <span style={{
    color: color
  }}>{children}</span>;
};

In Wherobots Cloud, [**Workload History**](https://cloud.wherobots.com/workloads) allows you to monitor the progress of workloads (notebooks, SQL sessions, and job runs), understand resource consumption, review the execution timeline, and verify configuration settings.

## Benefits

The [**Workload History**](https://cloud.wherobots.com/workloads) section of Wherobots Cloud allows you to view all executed workloads within your Wherobots Organization and manage job runs.

<AccordionGroup>
  <Accordion title="Visualize resource consumption">
    Monitor Notebooks, Job Runs, and SQL Sessions to understand how resources are being used across your organization.
  </Accordion>

  <Accordion title="Identify usage patterns and trends">
    Spot trends for capacity planning and optimization by reviewing historical workload activity.
  </Accordion>

  <Accordion title="Track quota usage">
    Stay aware of your organization's quota consumption to avoid hitting computational limits.
  </Accordion>

  <Accordion title="Investigate usage spikes">
    Pinpoint the source of unexpected resource usage and analyze spikes in activity.
  </Accordion>

  <Accordion title="Analyze individual activity">
    Review activity by user or service principal to understand contributions and workload distribution.
  </Accordion>

  <Accordion title="Make informed decisions about resource allocation and cost optimization">
    Use workload insights to guide resource allocation and optimize costs for your organization.
  </Accordion>
</AccordionGroup>

You can review and filter any workloads executed within your Wherobots Organization.

## Before you start

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

* An **Admin** or **User** **Account** within a Professional or Enterprise Edition Organization. For more information, see [Create a Wherobots Account](/get-started/wherobots-cloud/create-account).

## View Notebook, Job Run, and SQL Session workloads

For insight into your workload trends and individual Job Runs, go to [**Workload History**](https://cloud.wherobots.com/workloads) in the left sidebar of Wherobots Cloud.

<Frame caption="**Workload History** overview">
  <img src="https://mintcdn.com/wherobots/UOKw48hYhb4_MiDx/images/get-started/org-images/workload-history-scroll.png?fit=max&auto=format&n=UOKw48hYhb4_MiDx&q=85&s=ec39f7fab09d8b631f490cba99182264" alt="Workload History overview" width="3008" height="1118" data-path="images/get-started/org-images/workload-history-scroll.png" />
</Frame>

<Tip>
  **Hover for details** — Place your cursor over any point on the chart to display a tooltip with the exact quota usage breakdown at that moment.
  Use this to investigate any spikes or trends in resource consumption.
</Tip>

## Workload history overview

Workload History provides two main views to analyze your workloads: [**Chart**](#chart-view) and [**Table**](#table-view).

### Chart view

In chart view, you can see an overview of all your workloads, including Notebooks, Job Runs, and SQL Sessions. The chart displays quota usage as a percentage of your organization's total computing power over time.

In Wherobots Cloud, go to [**Workload History**](https://cloud.wherobots.com/workloads).

The chart displays **Quota Usage** as a percentage on the y-axis over the selected time range on the x-axis. Each area on the chart is color-coded by workload type:

The legend on the right side of the chart identifies each workload type by color.

<AccordionGroup>
  <Accordion title="Time Range Filter">
    View workloads from the last 24 hours, 7 days, 30 days, 60 days, or 90 days.
  </Accordion>

  <Accordion title="Owner Filter">
    Filter workloads by the Organization member or service principal that started them
  </Accordion>

  <Accordion title="Region Filter">
    Filter workloads by the AWS region where they ran (e.g., aws-us-west-2, aws-eu-west-1, aws-us-east-1, etc.)
  </Accordion>

  <Accordion title="Type Filter">
    Filter workloads by type: Notebooks, Job Runs, or SQL Sessions
  </Accordion>
</AccordionGroup>

If you hover over the chart, you can see a breakdown of quota usage over time for Notebooks, Job Runs, and SQL Sessions.

Each workload type is color-coded for easy identification:

* **<FontColor color="blue">Notebooks</FontColor>** (blue)
* **<FontColor color="purple">Job Runs</FontColor>** (purple)
* **<FontColor color="green">SQL Sessions</FontColor>** (green)

### Table view

The table view provides a detailed list of all workloads executed within your Wherobots Organization, along with key information about each workload.

<Frame caption="**Workload History** table view">
  <img src="https://mintcdn.com/wherobots/UOKw48hYhb4_MiDx/images/get-started/org-images/workload-history-table.png?fit=max&auto=format&n=UOKw48hYhb4_MiDx&q=85&s=211685518f838e75fb05601d0610590a" alt="Workload History table view" width="2450" height="178" data-path="images/get-started/org-images/workload-history-table.png" />
</Frame>

The Table view includes the following elements:

<AccordionGroup>
  <Accordion title="Name">
    The name or ID of the workload.

    For **Notebook** and **SQL Session** workloads, click the workload name to copy its underlying workload ID to your clipboard. A tooltip displays the ID inline. This is useful when you need the ID for support or debugging, since these workload types do not have a separate detail page on Wherobots Cloud, like **Job Runs** do.
  </Accordion>

  <Accordion title="Owner">
    The entity that triggered the workload (Service Principal or User).

    <Note>
      If your account is configured to the **User** role, and you use a [service principal](/get-started/wherobots-cloud/service-principals)-managed API key generated by an **Admin** in your Wherobots Organization, actions are attributed to the service principal in [**Audit Logs**](https://cloud.wherobots.com/organization/audit-logs), with the Admin shown as responsible solely for the API key creation.
    </Note>
  </Accordion>

  <Accordion title="Duration">
    The total duration of the workload.
  </Accordion>

  <Accordion title="Time Completed">
    The date and time when the workload completed, or "Running" status.
  </Accordion>

  <Accordion title="Region">
    The AWS region where the workload executed.
  </Accordion>

  <Accordion title="Runtime">
    The runtime size used (e.g., Tiny, Small, Medium, Large).
  </Accordion>

  <Accordion title="Cost ($)">
    The estimated cost of the workload.
  </Accordion>

  <Accordion title="SUs">
    Spatial Units consumed by the workload so far. This information can be delayed by up to 20 minutes.
  </Accordion>
</AccordionGroup>

### Filter workloads

To locate specific workloads, you can use multiple filters:

1. Navigate to [**Workload History**](https://cloud.wherobots.com/workloads).
2. Use the **Filter by name or id** field to search for specific workloads.
3. Apply filters for **Time Range**, **Owner**, **Region**, or **Type** as needed.

## Manage Job Runs

In the [**Workload History**](https://cloud.wherobots.com/workloads) view, click on any Job Run workload row to view more information about that specific execution.

The detail page includes two tabs: **Details** and **Logs**.

### Details tab

The **Details** tab provides an overview of the Job Run’s configuration, runtime environment, and execution metadata so you can:

* Review Spark version, runtime size, and environment details
* Verify scheduling, trigger source, and timeout configuration
* Understand when the Job Run started, ended, and how long it ran

Each Job Run has a **Details** page that provides comprehensive information about the workload execution.

The **Details** tab includes the following information about the Job Run execution:

<AccordionGroup>
  <Accordion title="Job Run Name">
    The name of the Job Run, which is either user-defined or auto-generated.
  </Accordion>

  <Accordion title="Job Run ID">
    Unique identifier for this specific Job Run.
  </Accordion>

  <Accordion title="Status">
    Indicates if the Job Run is initializing (`Starting`), in progress (`Running`), finished (`Completed`), unable to be executed (`Failed`), or stopped because it exceeded its configured timeout (`Timed Out`).
  </Accordion>

  <Accordion title="Start Time">
    Indicates when the Job Run was initiated.
  </Accordion>

  <Accordion title="End Time">
    Indicates when the Job Run terminated.
  </Accordion>

  <Accordion title="Duration">
    Indicates how much time elapsed between the <strong>Start Time</strong> and <strong>End Time</strong>.
  </Accordion>

  <Accordion title="Triggered By">
    The entity that triggered the Job Run (e.g., Airflow, user email).
  </Accordion>

  <Accordion title="Runtime">
    The runtime size used for this Job Run (e.g., Tiny, Small, Medium, Large).
  </Accordion>

  <Accordion title="Runtime Version">
    The version of the runtime environment used for this Job Run. When you specify a version alias such as `latest` or `preview`, the resolved concrete version is shown in parentheses (for example, `latest (1.5.1)`).
  </Accordion>

  <Accordion title="Timeout">
    The maximum duration the Job Run is allowed to run before being automatically stopped, in seconds.
  </Accordion>

  <Accordion title="Region">
    The AWS region where the Job Run executed. Different regions may have different performance characteristics and costs.
  </Accordion>

  <Accordion title="Python File">
    The URI of the Python file executed in this Job Run.
  </Accordion>

  <Accordion title="Environment">
    The Spark configuration details for this Job Run.
  </Accordion>

  <Accordion title="Cancel Button">
    Allows you to stop an ongoing Job Run.
  </Accordion>
</AccordionGroup>

#### Consumption metrics

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

<Frame caption="Job Run consumption metrics">
  <img src="https://mintcdn.com/wherobots/UOKw48hYhb4_MiDx/images/get-started/org-images/consumption-metrics.png?fit=max&auto=format&n=UOKw48hYhb4_MiDx&q=85&s=61f75c7da9863a02a075176dfc50fe6d" alt="Consumption metrics" width="2612" height="392" data-path="images/get-started/org-images/consumption-metrics.png" />
</Frame>

<AccordionGroup>
  <Accordion title="Cost ($)">
    The estimated cost of the workload execution.
  </Accordion>

  <Accordion title="Spatial Units Consumed">
    Indicates the accumulated Spatial Unit Consumption for this workload.
  </Accordion>

  <Accordion title="Max CPU Utilization">
    Indicates the accumulated CPU usage for this workload.
  </Accordion>

  <Accordion title="Max Memory Utilization">
    Indicates the accumulated memory used for this workload.
  </Accordion>
</AccordionGroup>

#### Configuration information

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

<AccordionGroup>
  <Accordion title="Runtime">
    Indicates the size of the Runtime associated with the workload.
  </Accordion>

  <Accordion title="Timeout">
    Specifies the maximum duration the workload is allowed to run before being automatically stopped, in seconds. The default is `3600`.
  </Accordion>

  <Accordion title="Region">
    Specifies the compute region where the workload is being executed.
  </Accordion>

  <Accordion title="URI">
    The location or path of the Python script being executed.
  </Accordion>
</AccordionGroup>

### Logs tab

The **Logs** tab provides real-time access to execution logs for your Job Run including information about:

* File downloads and uploads
* Spark submit commands
* Spark version and environment details
* Warnings and error messages
* Application execution progress

The **Logs** tab includes the following information about the Job Run execution:

<AccordionGroup>
  <Accordion title="Job Run Name">
    The name of the Job Run, which is either user-defined or auto-generated.
  </Accordion>

  <Accordion title="Job Run ID">
    Unique identifier for this specific Job Run.
  </Accordion>

  <Accordion title="Status">
    Indicates if the Job Run is initializing (`Starting`), in progress (`Running`), finished (`Completed`), unable to be executed (`Failed`), or stopped because it exceeded its configured timeout (`Timed Out`).
  </Accordion>

  <Accordion title="Spark UI">
    A link to the Spark UI for this Job Run. Available while the Job Run is in the `Running` state.
  </Accordion>

  <Accordion title="Spark event logs">
    A folder icon button next to the **Spark UI** link opens the Spark event logs for this Job Run in the Storage Browser. Use these logs with tools like the Spark History Server to analyze a Job Run's performance after it has finished. Available when the Job Run produced event logs in your Wherobots-managed storage.
  </Accordion>

  <Accordion title="Search Logs">
    Search through log entries using <code>Cmd</code>/<code>Ctrl</code> + <code>F</code>.
  </Accordion>

  <Accordion title="Log Timeline">
    View timestamped log entries showing the execution progress.
  </Accordion>

  <Accordion title="Copy Logs">
    Copy all log entries to clipboard.
  </Accordion>

  <Accordion title="Download Logs">
    Download the complete log file for offline analysis.
  </Accordion>
</AccordionGroup>

## Compare workload performance

To compare workload performance with different runtime types:

1. Run a workload. For more information on initializing a job and runtime selection, see [WherobotsRunOperator](/develop/run-operator).
2. Run that same workload again with either a larger or smaller runtime type.
3. Review the **Detail** pages for each executed Job Run to compare performance metrics, specifically:

   * **Duration**
   * **Max CPU Utilization**
   * **Max Memory Utilization**
   * **Cost(\$)**
   * **SUs (Spatial Units)**

## Cancel a workload

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

To cancel a workload within Wherobots Cloud, do the following:

1. In [**Workload History**](https://cloud.wherobots.com/workloads), locate the Job Run you wish to cancel.
2. Click on the Job Run to open its detail page.
3. Click the **Cancel** button.

<Tip>
  You can only cancel workloads that are currently in the `Running` state.
</Tip>

## Limitations

The following limitations apply to the Workload History feature:

<AccordionGroup>
  <Accordion title="90-day data retention">
    Workload history data, including **Spatial Unit Consumption**, **Max CPU Utilization**, and **Max Memory Utilization** metrics, is only kept for 90 days.
  </Accordion>

  <Accordion title="Slightly delayed cost and SU data">
    **Spatial Unit Consumption** and **Cost** can take several minutes to display on a Job Run's **Detail** page.
  </Accordion>

  <Accordion title="Quota usage is percentage-based">
    The chart displays quota usage as a percentage of your organization's total computing power.
  </Accordion>
</AccordionGroup>