4.0.7 - Improved error handling for tracking requests
4.0.6 - Started using flushDB instead of flushAll for Redis
4.0.5 - Translation changes
4.0.4 - Clarify inline help for "Queue enabled" config setting
4.0.3 - Replace Redis::delete() with Redis::del() and fix a warning
- Support new option
--force-num-requests-process-at-once to the process command
4.0.1 - Improve compatibility with PHP 7.4
4.0.0 - Compatibility with Matomo 4.0
3.3.5 - Improve update script to first add primary key and then remove index
3.3.4 - Use primary key instead of a unique index for mysql backend for better replication
3.3.3 - Add possibility to ignore queued tracking handler and track request directly into the database
3.3.2 - Send branded HTML email
3.3.1 - Support MySQLi adapter
3.3.0 - When using 3rd party cookies, the 3rd party cookie value will not be overwritten by local site visitor id values
3.2.1 - Faster queue locking - More debug output while processing
- Added possibility to use a MySQL backend instead of redis
- New option
queue-id for the
queuedtracking:process command which may improve processing speed as the command would only focus on one queue instead of trying to get the lock for a random queue.
- Various other minor performance improvements
- New feature: Get notified by email when a single queue reaches a specific threshold
queuedtracking:monitorwill now work even when the queue is disabled
idSiteset. The same behaviour was changed in Piwik 2.14 for regular bulk requests.
queuedtracking:lock-statusthat outputs the status of each queue lock. This command can also unlock a queue by using the option
queuedtracking:print-queued-requeststhat outputs the next requests to process in each queue.
./console queuedtracking:processthe Tracker debug mode will be enabled and additional information will be printed to the screen.