Create new types of debug lines in the core:archive process #24011
Description
Description:
When running the core:archive process in Matomo, the execution feels opaque. The current PHP archiver logs are vague and primarily report completed work, often long after processing has begun.
The archiver CLI output provides little to no visibility into what is happening while the process is running.
Completion Criteria
This ticket is closed when some or all of the following are visible in the output of console core:archive
- What the archiver is about to process next
- How archive queue items are prioritized
Further, in the early lines of the CLI output from core:archive, it would be great to have the log tell some feedback about
- what behavior to expect if a manual archive is triggered while another archiving run is already in progress
Relevant to prioritization
Improving real-time logging and status reporting for core:archive would make it significantly easier to understand, operate, and troubleshoot long-running archiving jobs.
As Matomo pushes up against the upper limits of what the MySQL bottleneck can allow, this granular control would allow clever admins to set up ever-savvier cron jobs, keeping Matomo competitive as a data solution for very high traffic sites.