The countly web analytics project looks like a more-free substitution for Google Analytics, which is currently the only proprietary component in the Recipe Radar stack.
This assessment is based on the fact that countly-server component is licensed under a minor modification of AGPL, it supports session and event tracking, does not require the use of cookies, and provides Docker images which can be deployed in Kubernetes.
The countly project does provide an Android application for analysts to view data conveniently from their mobile devices, although this app doesn't appear to be open source, unlike the server.
Migration would involve:
Adding a persistent mongodb server instance to the Recipe Radar infrastructure
Creating a mongo Kubernetes service to meet the requirements of the countly-server components
For each of the countly services (countly/api, countly/frontend)
The countly web analytics project looks like a more-free substitution for Google Analytics, which is currently the only proprietary component in the Recipe Radar stack.
This assessment is based on the fact that
countly-servercomponent is licensed under a minor modification of AGPL, it supports session and event tracking, does not require the use of cookies, and provides Docker images which can be deployed in Kubernetes.The
countlyproject does provide an Android application for analysts to view data conveniently from their mobile devices, although this app doesn't appear to be open source, unlike the server.Migration would involve:
mongodbserver instance to the Recipe Radar infrastructuremongoKubernetes service to meet the requirements of thecountly-servercomponentscountlyservices (countly/api,countly/frontend)haproxyrouting as-neededcountlyanalytics event handlers to the openculinary/frontend applicationcountly