This page details the Jobs, Queues, and Robot Logs data that Insights ingests. For information around the Manual Values explores, see Templates.
データは、Explore に表示されます。Explore は、その中のフィールドに対応する汎用エンティティと考えることができます。たとえば、Orchestrator のジョブに関するダッシュボードを構築するには、[ジョブ] 検索画面を選択します。各検索画面には、対応するデータを含むビューが表示されます。Explore 内で関連するデータにアクセスできます。つまり、[ジョブ] Explore からのロボット ログへのアクセスなどが可能です。
| 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. See Job States for all available states and their descriptions. Note: 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 StartTime and EndTime. |
| Folder | Folder where the job is defined. |
| 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 (see Job States). |
| Total Suspended Time in Seconds | The time of jobs, in seconds, spent in a suspended state in seconds (see 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. |
注
Orchestrator 経由でキューの暗号化を使用している場合、[固有データ]、[分析]、[出力] の各データ フィールドの分析をレポートすることはできません。暗号化機能が有効化されている場合、これらのフィールドを使用するダッシュボードのデータは利用できません。
[固有データ]、[分析]、[出力] のデータ フィールドは v22.10 より非推奨になります。ただしカスタム変数を設定すれば、ビジネス メトリックに適した方法でこれらのフィールドを使用したダッシュボードを作成できます。
Insights の非推奨化のタイムラインをご覧ください。
| 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: Successful Failed Abandoned Deleted |
| 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 Start Processing Date and End Processing Date. |
| 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, 0 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. |
| Output Deprecated and no longer supported after the 2022.10 release. You can still create Dashboards using these fields in a manner that fits your business metrics, by configuring Custom Variables. See Insights deprecation timeline. | A collection of key value pairs containing custom data upon successful processing associated with the transaction. See here for details. |
| Analytics Data Deprecated and no longer supported after the 2022.10 release. You can still create Dashboards using these fields in a manner that fits your business metrics, by configuring Custom Variables. See Insights deprecation timeline. | A collection of key value pairs containing custom data for analytics purposes associated with the transaction. See here for details. |
| Specific Data Deprecated and no longer supported after the 2022.10 release. You can still create Dashboards using these fields in a manner that fits your business metrics, by configuring Custom Variables. See Insights deprecation timeline. | A collection of key value pairs containing custom data associated with the transaction. See here for details. |
| Reviewer User Name | The user name of the assigned reviewer, if any. |
| Queue Id | The numerical identifier of the queue, comprised of QueueName, OrganizationUnitId. |
| Folder | The folder on which a queue item was executed. |
| 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. |
| 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 Deprecated and no longer supported after the 2023.4 release See Insights deprecation timeline | 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 Deprecated and no longer supported after the 2022.10 release See Insights deprecation timeline | The severity level at which the message was logged. See 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. |
11 日前に更新