Plugin execution logging
Plugin execution logging helps to record the execution time of specific plugins, thus enabling you to gather Bot Task processing analytics. Currently, the following plugin data is recorded:
- robotics-flow
- ocr
- OOTB Model step
- automl-train-status
- automl-train-start
General recording rules
A separate record is created for each plugin and each processed HitSubmissionDataItem. This record contains the following items:
- Plugin name
- ID of
HitSubmissionDataItem - Total number of plugin executions in a single Bot Config
- Total time of plugin execution for a single data item
- Number of retry attempts
Table structure
All data is stored in the PluginExecutionLog table:
| Column name | Filed description |
|---|---|
id | Sequential number. |
plugin_name | Name of the plugin as it appears in a Bot Config (for example, robotics-flow). |
data_item_id | ID of HitSubmissionDataItem processed by the plugin. |
execution_time | Total time of the plugin execution in a single Bot Config per HitSubmissionDataItem. There can be more than one plugin appearance in a Bot Config. |
execution_count | Total number of plugin executions in a single Bot Config per HitSubmissionDataItem. There can be more than one plugin appearance in a Bot Config. |
retry_attempt | Taken from the AwsHit table, the processesAttemptCount column |
is_successul | Flag that indicates an exception during the plugin execution. False if any exception was thrown during execution, otherwise, true. |
Each record can be connected with the tracker (used for transaction tracking) via the hit_id column in the DataItemTrackerHitLink table.
Technical details
To save a record to the database, an internal REST service is used. Its path is /v1/internal/analytics/bot-execution-log.
The PluginExecutionLog table is also added to the data management procedure for purging as the table size is equivalent to the size of HitSubmissionDataItem.