@jorgeuos opened this Issue on April 23rd 2020

Hi,

On Visitors-->Software

Trying to get e.g. Browser version for any given segment but I get "There is no data for this report." every time for every segment. On our Matomo, we get data for the defaults but not the "Related reports".

See demo site:
https://demo.matomo.org/index.php?module=CoreHome&action=index&idSite=62&period=day&date=yesterday#?idSite=62&period=week&date=2020-04-16&segment=dimension1%3D%3Dcandidate&category=General_Visitors&subcategory=DevicesDetection_Software

I've noticed that sites that has really low number of visits, this works fine. This could perhaps be related to archiving not completed yet.

Any progress in this issue would be beneficial to share.
I will take a look tomorrow.

Br, Jorge

@tsteur commented on April 23rd 2020 Member

Hi @jorgeuos

thanks for creating the issue. Are you only seeing this error on that demo site? I tested it on other sites on the demo (which aren't accessible publicly) and it works fine there. The demo site you are referring to is bit of a special case. Are you having this issue in your Matomo too maybe?

@jorgeuos commented on April 24th 2020

Hi,

Yes, that is why I created the issue, not because of the demo site of course. I will further investigate later today. The time period I would like is months, but this does not even work with days.

Screenshot_2020-04-24_at_07_55_18
Screenshot_2020-04-24_at_07_55_48

@tsteur commented on April 28th 2020 Member

Do you know if browser archiving is enabled?

You can see this by going to Admin -> General Settings.

image

Do you also know if there is maybe a config setting enabled in your config/config.ini.php called browser_archiving_disabled_enforce ? Could you maybe check if there is a line that contains this value? eg browser_archiving_disabled_enforce = 1

Is this the case for all segments or only specific segments? Does it work for some days / weeks / months?

@tsteur commented on April 28th 2020 Member

BTW is it correct that basically all other reports work except for those two?

@jorgeuos commented on April 28th 2020

Hi,
It's a multi cluster setup for >100 million page views, we're maybe using half of the capacity right now. Archiving is triggered by cron, we have different cron jobs scheduled for different periods I think, if I remember correctly. I don't remember exactly how often they are running but basically a couple of times a day.

browser_archiving_disabled_enforce = 1
enable_browser_archiving_triggering = 0

For the second question, yes, all other reports afaik works well. This a report from the Data analyst, not me. Our investigation has left us to dead ends. If you want me to check any other report I'll happily check them for you.

Screenshot_2020-04-28_at_10_38_08

Br, Jorge

@tsteur commented on April 30th 2020 Member

Thanks for this @jorgeuos I'd basically recommend to invalidate the report for that month so it'll be reprocessed see https://matomo.org/faq/how-to/faq_155/ and check if it comes up then. Eg

./console core:invalidate-report-data --periods=month --dates=2020-03-03 --sites=SITEID

We don't have access to your PHP, Matomo, or archiving logs so it's bit hard to tell what happened exactly. You maybe want to log the output of all your archivers to some file (eg by adding > /path/to/logs/archiving.log to your crontab), make sure PHP logs errors, and Matomo also logs information to a file (https://matomo.org/faq/troubleshooting/faq_115/). Such things can help investigating issues.

Hoping this helps. Be great to try the invalidation and see if it then comes up.

@jorgeuos commented on April 30th 2020

Ok, thank you for your answer. I'll take a look over how the logs are set.
Invalidating this report right now could be troublesome for the client, we recently invalidated a long period related to another issue. I'll have to go through it with my colleague, I'll keep watching this report.

@tsteur commented on April 30th 2020 Member

@jorgeuos if it only invalidates that month's period it should in theory only take a minute or so to regenerate that specific archive.

Powered by GitHub Issue Mirror