Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Inconsistent Event Total #14872

Closed
rjxp opened this issue Sep 9, 2019 · 1 comment
Closed

Inconsistent Event Total #14872

rjxp opened this issue Sep 9, 2019 · 1 comment
Labels
answered For when a question was asked and we referred to forum or answered it.
Milestone
3.12.0

Comments

@rjxp
Copy link

rjxp commented Sep 9, 2019 •
edited

I have an inconsistency in the presentation of events: For the period 2019-06-04 to 2019-06-14 (range1), the graphical interface outputs 908,740 events for an event. If I increase the period to 2019-06-02 to 2019-06-14 (range2), I get 425.874 (with otherwise the same settings for area and segments). See screenshots range1.png and range2.png:

range1

range2

If I export the data of the time series, I get the correct sum for the first/shorter period (range1) by adding the fields nb_events. For the second period (range2) I get 1,085,064 > 908,740 > 425,874, whereas the dataset for day 2019-06-02 is completely missing. The numbers in the export also match the values you get in the user interface of the time series when hovering over the corresponding day, where the graph for 2019-06-02 drops to zero.

Confidence in Matomo's numbers thus decreases enormously. Actually, I always have to validate the overview values against the export data, which would be very unwieldy. Is there a possibility to check my database against further inconsistencies of this kind?
@tsteur
Copy link
Member

tsteur commented Sep 10, 2019

@rjxp I recommend you invalidate the report for the date range showing a too low value as described in https://matomo.org/faq/how-to/faq_155/ The data should then be archived again and I suppose it will show the correct value then. Hard to say why it doesn't show it the first time there could be many reasons like maybe your server had an issue with archiving etc. Feel free to comment if it still doesn't work after invalidating the report. From our side things are looking good so when the report is invalidated, it should definitely show the correct value.

@tsteur tsteur closed this as completed Sep 10, 2019
@tsteur tsteur added the answered For when a question was asked and we referred to forum or answered it. label Sep 10, 2019
@mattab mattab added this to the 3.12.0 milestone Oct 27, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
answered For when a question was asked and we referred to forum or answered it.
Projects
None yet
Milestone
3.12.0
Development

No branches or pull requests
3 participants
@tsteur @mattab @rjxp