Plugins execution logging
Plugin execution logging helps to log execution time of specific plugins, thus enabling you to gather Bot Task processing analytics.
Currently, the following plugin data is recorded:
- robotics-flow
- ocr
- automation-extract
- automation-get-eval-result
- automation-start-eval
General recording rules
A separate record is created for each plugin and for each processed HitSubmissionDataItem.
This record contains:
- Plugin name
- ID of
HitSubmissionDataItem - Total number of plugin executions in one bot config
- Total time of plugin execution for one 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 plugin like it appears in bot config (for example, robotics-flow, automation-extract) |
data_item_id | ID of HitSubmissionDataItem processed by the plugin |
execution_time | Total time of plugin execution in one bot config per one There can be more than one plugin appearance in the bot config. |
execution_count | Total number of plugin executions in one bot config per one There can be more than one plugin appearance in the bot config. |
retry_attempt | Taken from 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 Tracker (used for transaction tracking) via the DataItemTrackerHitLink table > the hit_id column.
Technical details
To save a record to the db, an internal REST service is used. Its path is /v1/internal/analytics/bot-execution-log.
The PluginExecutionLog table is also added to the Data Purge procedure as the table size is equivalent to the size of HitSubmissionDataItem.