@tsteur opened this Issue on April 21st 2021 Member

image

We should at least mention that segments are still processed on demand when browser archiving is disabled (no need to mention it when the browser enforce setting is enabled in the config). This is important because it's not expected from the user perspective that this is the case.

Another option could be also to expose yet another setting in the UI to also disable it for segments. However, more settings aren't always the best and it be quite complicated for users to understand so I'm thinking it might be more like wondering why we don't enforce this directly for segments? I suppose this is because some users might have many segments and it would cause too much load to preprocess them all. However, maybe this problem is solved in the wrong way.

Currently, when segment reports are disabled for browser archiving, then all segments will be created as "auto archive/pre process using the cron". We could change this and by default have a report still be processed in the background but now still give them the option to select whether a report should be processed on demand. Then there would be another setting (might already exist) to not allow selecting segments to be processed in real time anymore (since this is needed by many users including us on the cloud where we don't want to process segments in real time).

This could of course break existing behaviour and would maybe need to be done as part of Matomo 5.

The least we could do would be to show the above message that segments will still be processed in real time under circumstances and this can behaviour can be changed in the ini. We don't want to show this message if the ini to force disable browser archiving for segments is disabled (don't show the message when browser_archiving_disabled_enforce).

fyi @mattab

This Issue was closed on June 27th 2021
Powered by GitHub Issue Mirror