Thanks for the feedback.
As I’ve mentioned in previous replies in this thread, I think there are ways to always have complete tracking of anything, by improving the Matomo integration. Namely we can register XWiki server-side components (or any extension points) to push any type of data to Matomo.
I agree we’d need to evaluate that and that it’s an interesting source. My only worry is that I’m not sure it’s performant enough for very large event volumes. And for that we might need asynchronous queuing systems and stores not on the same machine. But it could probably be refactored to support that somehow.
For the moment the event stream contains incomplete data for statistics. Here are 2 examples:
- Event stream doesn’t log page views
- Event stream doesn’t log feature usage (something we’ll want to support)
Now, ofc we could push new events to the event stream to capture more data. If we do this, we’ll also need to add the concept of event categories so that we can filter out events when displaying the Notifications events for example. Users would not want to see their page views or other user’s page views in their notification tray.
Another option is to not even try to implement a stats store in XWiki and instead push all the data captured to Matomo (for example). I don’t have enough experience with Matomo to know if all the use cases would be filled, if it’s performant/scalable enough (but I’d expect any serious such tool to propose options for scalability), etc. Note that the implementation could be quite generic and work for any analytics tool that offer an API to push custom data to it.
Thx