# Insights Data Model

> This page details the **Jobs**, **Queues**, and **Robot Logs** data that Insights ingests. For information around the Manual Values explores, check [Templates](https://docs.uipath.com/insights/automation-suite/2024.10/user-guide/templates).

This page details the **Jobs**, **Queues**, and **Robot Logs** data that Insights ingests. For information around the Manual Values explores, check [Templates](https://docs.uipath.com/insights/automation-suite/2024.10/user-guide/templates).

The data is surfaced via **Explores**, which you can think of as a general entity that corresponds to the fields within it. For example, to build dashboards around Orchestrator jobs, pick the **Jobs** Explore. Each Explore surfaces **views** that contain the respective data. You can access related data from within Explores, i.e. Robot Logs are accessible from the **Jobs** Explore, etc.

Two terms, **dimension** and **measure**, are often used in the Insights data model tables.

Dimension : Dimensions are the fields on a table, the attributes of your data. For example, the **Country** dimension indicates the country (France, Germany). You can aggregate these attributes and use measures for them. For more information on dimensions, check the official [Looker documentation](https://cloud.google.com/looker/docs/reference/param-field-dimension?hl=en).

Measure : A measure is the calculation that is done on a dimension, on a field of table. This is a numerical attribute of your data, such as *sum*,*average*, *min*, or *max*. For more information on measure, check the official [Looker documentation](https://cloud.google.com/looker/docs/reference/param-field-measure?hl=en).

## Jobs

[Jobs](https://docs.uipath.com/orchestrator/automation-cloud/latest/user-guide/about-jobs)

 <colgroup>
  <col/>
  <col/>
 </colgroup>
 
  
    Dimensions 
    Description 
  
 
 
  
    Process Version 
     The version number of the process the job belongs to.  
  
  
    Robot Name 
     The name of the Robot that executed the job.  
  
  
    Robot Type 
     The type of robot that executed the job. The available options are: 
      
         Attended 
         Unattended 
      

  
  
    Host Machine Name 
     The name of the machine where the robot executed the job.  
  
  
    Job Id 
     The row ID of the job event in the Orchestrator database  
  
  
    Job State 
     The status of the job. Check  Job States  for all available states and their descriptions.  Insights only ingests terminal states (i.e. successful, stopped, and faulted).  
  
  
    User Name 
     The name of the Orchestrator user that ran the job.  
  
  
    User Type 
     The type of user type that executed the job. The available options are: 
      
         RPA Developer 
         RPA Developer Pro 
         Citizen Developer 
         Attended User 
      

  
  
    Creation Time 
     The time when the job was created.  
  
  
    Start Time 
     The time when execution of the job began.  
  
  
    End Time 
     The time when execution of the job finished.  
  
  
    Job Source 
     The triggering event for job execution. The available options are: 
      
         Manual 
         Schedule 
         Other 
      

  
  
    Environment Name 
     The Environments where the job was executed.  
  
  
    Process Name 
     The name of the  process.  
  
  
    Process Display Name 
     The  display name  of the process as entered in Orchestrator.  
  
  
    Job Duration in Seconds 
    The duration, in seconds, of the job execution. Computed as the difference between <code>StartTime</code> and <code>EndTime</code> . 
  
  
    Folder 
     Folder where the job is defined.  
  
  
    Process Manual Values 
    Display the Manual Time, Manual Cost, and Custom columns as configured in the ROI dataset. 
  
 

 <colgroup>
  <col/>
  <col/>
 </colgroup>
 
  
    Organization scoped view 
  
  
     Dimensions  
     Description  
  
 
 
  
    Folder per Tenant 
    The name of the tenant followed by the name of the folder where the job is defined. This is only available in Organization scoped views. 
  
  
    Tenant Name 
    The name of the tenant where the job is defined. This is only available in Organization scoped views 
  
 

The Job views are associated with the following **Explores: Jobs, Process ROI, Queue ROI, Robot Logs, Jobs -Org, Process ROI - Org, Queue ROI - Org, Robot Logs - Org.**

| **Measures** | **Description** |
| --- | --- |
| **Faulted Jobs** | The number of jobs with the `Faulted` status. |
| **Faulted Rate** | The % of jobs with the `Faulted` status compared to the total number of jobs. |
| **Processes Ran** | The number of processes that have reached a final status of `Successful`, `Faulted`, or `Stopped`. |
| **Success Rate** | The % of jobs with the `Successful` status compared to the total number of jobs. |
| **Successful Jobs** | The number of jobs with the `Successful` status. |
| **Time in Pending in Seconds** | The amount of time all jobs spent in the `Pending` and `Resumed` states, meaning how long it took from the moment the job was queued until it actually ran on the robot (check [Job States](https://docs.uipath.com/orchestrator/docs/job-states)). |
| **Total Suspended Time in Seconds** | The time of jobs, in seconds, spent in a suspended state in seconds (check [Job States](https://docs.uipath.com/orchestrator/docs/job-states)). You can use this measure to calculate the total time spent on a particular process by subtracting the time spent in a suspended state, in long-running workflows. |
| **Total Run Time in Seconds** | The total processing time of all jobs in seconds. |

### Process Application

This view, part of the **Jobs** explore, matches processes to specific apps that it interacts with.

:::note
* If you are deploying multiple packages within the same folder using,
inconsistent results may occur while using the Process Application view due to joins with the process name. To fix this, we strongly suggest using the **Process Display Name** for your visualizations. This ensures uniqueness within the context of a folder, leading to more consistent and accurate results.
* You should only use the **Process Application** view when you want to check
which processes interact certain applications.
:::

| Data | Description |
| --- | --- |
| **Application Name** | The name of the application. If it's a web application, it will be the browser name. If the application name is a dynamic parameter, the name will be unknown. |
| **Application Name Or Url** | It's a URL if the application is web application, otherwise it's the application name. It shows as unknown if both application and URL are dynamic parameters. |
| **Application Type** | The type of application. |
| **Application Url** | URL of the web application. It's displayed as unknown if it's parameter. |
| **Folder** | The folder where the process is located. |
| **Package Creation Date** | The date when the packages was created. |
| **Package Id** | The ID of the package. |
| **Process Creation Date** | The date when the process was created. |
| **Process Display Name** | The display name of the process. It's updated when the process package version is updated. |
| **Process Id** | The ID of the process. |
| **Process Name** | The name of the process package. |
| **Process Version** | The active version of the process package. A process can have multiple versions and it's the active version or the last configured version. |
| **Process Version Creation Date** | The date of when the process’s version is updated. |
| **Process Version Id** | This is updated when the package is updated in the process. |

The Process Application views are associated with the following **Explores: Jobs, Jobs - Org.**

Table 1.

| Measures | Description |
| --- | --- |
| **List of Unique Application Names** | Concatenates all unique application names. |
| **List of Unique Process Display** | Concatenates all unique process displays. |
| **List of Unique Process Names** | Concatenates all unique process names. |
| **List of Unique Urls** | Concatenates all unique URLs. |

## Queues

[Queues](https://docs.uipath.com/orchestrator/v0/docs/about-queues-and-transactions)

 <colgroup>
  <col/>
  <col/>
 </colgroup>
 
  
    Dimensions 
    Description 
  
 
 
  
    Priority 
     The priority of the queue item defined when setting its properties from Studio.  
  
  
    Queue Item Id 
     The auto-incremented row ID of the queue item in the Orchestrator database.  
  
  
    Queue Name 
     The name of the queue.  
  
  
    Processing Status 
     The status of the queue item. The available options are: 
      
         Abandoned 
         Deleted 
         Failed 
         Successful 
      

  
  
    Review Status 
     The review status of the queue item.  
  
  
    Robot Name 
     The name of the robot that processed the queue item.  
  
  
    Robot Type 
     The type of robot that executed the job. The available options are: 
      
         Attended 
         Unattended 
         NonProduction 
         Testing 
         Other 
      

  
  
    Creation Date 
     The time the queue item was created.  
  
  
    Start Processing Date 
     The time the robot began processing the queue item.  
  
  
    End Processing Date 
     The time the robot finished processing the queue item.  
  
  
    Transaction Duration in Seconds 
    The processing time, in seconds, of the queue item. Computed as the difference between <code>Start Processing Date</code> and <code>End Processing Date</code> . 
  
  
    Seconds In Previous Attempts 
     The time, in seconds, of all attempts to process the transaction.  
  
  
    Retry Number 
    The number of times the processing of the transaction has been attempted. For the first attempt, <code>0</code> is displayed. 
  
  
    Defer Date 
     The earliest date and time the queue item is available for processing. If empty, it can be processed immediately.  
  
  
    Due Date 
     The latest date and time which the queue item must be processed by. If empty, it can be processed at any time.  
  
  
    Progress 
     Custom progress information for queue items with status InProgress .  
  
  
    Processing Exception Type 
     The type of the exception thrown when processing fails. The available  exception types  are: 
      
         ApplicationException 
         BusinessException 
      

  
  
    Processing Exeption Reason 
     The details of the exception thrown when processing fails.  
  
  
    Reference 
     The user-specified value for identification purposes provided when  adding the queue item in Studio.  
  
  
    Reviewer User Name 
     The user name of the assigned reviewer, if any.  
  
  
    Queue Id 
    The numerical identifier of the queue, comprised of <code>QueueName, OrganizationUnitId</code> . 
  
  
    Folder 
     The folder on which a queue item was executed.  
  
  
    Queue Manual Values 
    Display the Manual Time, Manual Cost, and Custom columns as configured in the ROI dataset. 
  
 

 <colgroup>
  <col/>
  <col/>
 </colgroup>
 
  
    Organization scoped view 
  
  
     Dimensions  
     Description  
  
 
 
  
    Folder per Tenant 
    The name of the tenant followed by the name of the folder where the job is defined. This is only available in Organization scoped views. 
  
  
    Tenant Name 
    The name of the tenant where the job is defined. This is only available in Organization scoped views 
  
 

The Queues views are associated with the following **Explores: Process ROI, Queue ROI, Queues, Process ROI - Org, Queue ROI - Org, Queues - Org.**

| **Measures** | **Description** |
| --- | --- |
| **Avg Queue Wait Time in Seconds** | How long it takes, on average, between when all queue items were created and when a robot started processing them. |
| **First Pass Yield % Per Queue** | The percentage of time that the queue item was successful on its first try at processing (retry number =0). |
| **Queue Count** | The number of queues with data processed on this tenant. |
| **Queue Item Count** | The number of queue items processed on this tenant. |

## Robot Logs

[Robot Logs](https://docs.uipath.com/orchestrator/v0/docs/about-logs)

| **Data** | **Description** |
| --- | --- |
| **Id** | The auto-incremented row ID of the log in the Orchestrator database. |
| **Timestamp Date** | The time the logging was executed. |
| **Machine Id** | The `Id` of the machine that generated the log message. |
| **Machine Name** | The Machine Name. |
| **Process Name** | The name of the process that generated the log message. |
| **Process Version** | The version number of the process the job belongs to. |
| **Windows Identity** | The user under which the robot generating the log message was logged in. |
| **Robot Name** | The name of the robot that generated the log message. |
| **Raw Message** | `JSON` output from the execution log. |
| **Transaction Id** | The key of the associated queue item. |
| **Transaction State** | The state of the transaction. |
| **Transaction Status** | The status of the transaction. |
| **Message** | The logged message. |
| **Level** | The severity level at which the message was logged. Check [Logging Levels](https://docs.uipath.com/orchestrator/v0/docs/logging-levels) for details. |
| **Log Type** | Generated according to the process designed by the user in Studio, when using the Log Message activity or the Write Line activity.  These logs have a value of `User`. |
| **Queue Name** | The name of the queue. |
| **File Name** | The name of the file that created the automation. |

The Robot logs views are associated with the following **Explores: Jobs, Process ROI, Queues ROI, Robot Logs, Jobs - Org, Process ROI - Org, Robot Logs - Org.**