CDN support for PIWIK analytics platform
Description
The use of PIWIK analytics proves very useful, however if sites are opting to use a CDN to speed up GitLab they will be penalized by the continued loading of the piwik.js
file from the analytics tracking server. This continued loading often adds considerable delay.
Proposal
Add an additional key piwik_cdn_url
and create an optional loading mechanism that renders the _piwik.html.haml
to use a CDN url for fetching the javascript if the key is present.
Links / references
- https://gitlab.com/gitlab-org/gitlab-ce/blob/master/app/views/layouts/_head.html.haml
- https://gitlab.com/gitlab-org/gitlab-ce/blob/master/app/views/layouts/_piwik.html.haml
Overview
- What is it?
- The option to cache the piwik javascript asset on a CDN instead of constant fetches to the analytics server.
- Why should someone use this feature?
- If they are trying to increase performance and loading speed of the GitLab product by leveraging a CDN.
- What is the underlying (business) problem?
- The loading of the piwik.js asset from the target analytics server adds substantial overhead.
- How do you use this feature?
Use cases
To provide the option for additional scale and speed for someone using piwik analytics with a CDN.
Feature checklist
Make sure these are completed before closing the issue, with a link to the relevant commit.
-
Feature assurance -
Documentation -
Added to features.yml