Release 2024-05-28
| Component | Version |
|---|---|
| Web portal (miarecweb) | 2024.5.28.1 |
| Recorder (miarec) | 2024.4.5.0 (not updated) |
| Screen recorded (miarec_screen) | 2024.4.5.0 (not updated) |
| Live Monitoring (miarec_livemon) | 0.1.0.183 (not updated) |
| Screen capture client | 1.1.0.80 (not updated) |
New features
New Job architecture
Key features:
- More robust (better error handling and reporting)
- More efficient (reduce storage usage and increase performance)
- Easier troubleshooting
Add Processing Queue concept
With queues, it is possible to build efficient pipeline for data processing.
Job read records from queue and process them. After processing, a job can optionally push the record to another queue. This allows users to create a complex pipeline.
A queue can be populated by events, for example, when call is created/updated/deleted.
Add new Job data source modes
Job data source modes "Full" and "Incremental" are declared as deprecated.
Instead of them, we provide more efficient data source types "Queue" and "Full mode with continuation token".
Job log is stored in the database instead of the local files on web servers
This improves log file handling in a cluster with multiple web servers.
Errors and warnings are stored in log by default, available for user to review if necessary. More verbose logging can be enabled by user if necessary.
Job details shows the processing records, separately by status "Success", "In progress", "Error", "Aborted", "Skipped"
In the processed record details, users can see all the related logs for such a record.
In case of error during processing call record, a number of retries is limited (3 by default)
A backoff algorithm is used to determine when the processing will be retried the next time for certain record.
This improves robustness of various jobs that may fail due to external reasons like network connection issues.
Add advanced search for all jobs
Add rate limits for REST API (tenant level)
