Archived reports missing tens of millions of visits from 2020 after update

Lukas · March 4, 2021, 9:28am

Hi,

The only vaguely related issues I know of are

After updating to Matomo 4, UI for 2018 is empty but archive data is present

opened 09:06AM - 28 Jan 21 UTC

Hi, we've recently updated to 4.1.1 (from 3.x) and we're unable to view archi…ved data for 2018, but archive data is present (also calculated nb_visits from archive_numeric). It seems like archived data is still there but somehow not visible on the UI, and we can't really explain why this happen. 2019 is working fine. We also can't just invalidate the archive tables because raw logs are being removed after 365 days. archive_numeric (2018_12, Query is not correct but only to show that data should be there): ![image](https://user-images.githubusercontent.com/1573629/106114492-e491c080-614f-11eb-904f-b8fdbaa9b88c.png) UI: ![image](https://user-images.githubusercontent.com/1573629/106115050-9d57ff80-6150-11eb-88a2-9ac23d71680b.png) Any clue?

and

github.com/matomo-org/matomo

Disappearance of segment archive data during 3.0 => 4.0 update

opened 12:11PM - 24 Jan 21 UTC

OnlineArts

As mentioned in the [Matomo forum](https://forum.matomo.org/t/archiving-of-newly…-created-segments-since-matomo-4/40352), some users are not able to display historical segment data after the Matomo 4 upgrade. We could observe, that after the Matomo 4 upgrade historical data (older than one month) disappeared from segmentation sites. By calling a segmentation overview we get the historical data from exactly one month. For example, opening the segment #1 page on the 2. January leads that all historical data till the 2. December appeared on this page. Opening the segment #2 page on the 15. January -> 15. December. Archive invalidation and manual re-processing does not affect the appearance of historical data. This issue appears in at least Matomo 4.10 and 4.11. No obvious related config parameters changed that behavior. Could that be related to the options from #17129 ? The segmentation in that side id is set to _SEGMENTED REPORTS ARE PROCESSED IN REAL TIME (DEFAULT)_ **Edit**: Ok, the change of the mentioned option to _SEGMENTED REPORTS ARE PRE-PROCESSED (FASTER, REQUIRES CRON)"_ results only that the segments now listed during the ./console core:archive execution. But still did not add historical data. As I see, it is still missing during the processing for the incomplete month of December. Could that be in some kind related to the utf8 to utf8mb4 conversion that I performed after the upgrade?