New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
PageViews missing one date in Report when using date range starting 4/4/16 or prior #10062
Comments
It's hard to tell what is happening here. Is it maybe possible to get access to your Piwik instance and to your database maybe? |
I don't think that will be possible since the install is within our Internal Network. Basically for one Site ID when I pull a date range of anything of 4/04 or prior to current date, the resulting report drops the data for one date (4/08). For example if I put in date range of 4/01 - 4/17 the results do not include 4/08. If I put in date range of 4/05 -4/17, results do include data for 4/08. This also happens if I use selection of "month" April or "year" 2016, the results to do not include data for 4/08. However, the data is in the database when I direct query such as this:
|
Question: is there some kind of reporting process that we can rerun to update the data? |
Yes, this should help I presume: http://piwik.org/faq/how-to/faq_155/ |
To be clear, marking the date as invalid will not remove data for that date from the database? The way it reads it will "reprocess" the reporting for that date... |
It will not delete any logs. It will only invalidate existing report archives. So it is possible to regenerate the archives afterwards |
Following the examples in the article, I ran this command in the Console. Does using "Dry Run" mean it didn't actually run or is just showing me the accompanying SQL queries and it did in fact invalidate the dates? *php ./console core:invalidate-report-data --dates=2016-04-04,2
|
dry run does not actually execute the queries |
Thank you for your advice to invalidate the problem dates and regenerate the reports, it appears to have worked and fixed the reported issue. |
Awesome, thx for letting us know. |
Data for this page started being collected on 2016-04-06. Note that pulling Page views for range of 4/05 – 4/14 shows page views of 1690:
As soon as you back up the range by one day (2016-04-04) and any dates prior to this date, the Page Views drops out the numbers for 4/08 which had 655 views.
What is interesting is that you can hover over the Row Evolution feature and it does show the 655 views for 4/08, they are just not included in the PAGEVIEWS number in the UI.
We are observing this same behavior for all pages within this one Tracking ID pages however we are not observing it for any other tracking sites (ID’s) within Piwik.
Reviewing all error log files and MySQL database files, there are no indications of any issues for the dates of 4/04 or 4/08 and there were no updates to the server on these dates.
Since date of 4/04 appears to be the cutoff date for seeing the issue and is a Sunday, is there an archiving job that is switching to another table to report the views that perhaps didn’t include date of 4/08? Could this repair itself the following week when another archive is created?
Archiving Settings are set to YES for Archive reports when viewed from the browser.
Piwik 2.15.0
Apache/2.4.4 (Win32)
mysqlnd 5.0.10
PHP/5.4.16
The text was updated successfully, but these errors were encountered: