Metrics update - SMAU and AMAU
Why is this change being made?
-
Updating the metrics page to include the new SMAU definition and adding AMAU definition.
-
Removed the SMAU definition from the telemetry and provided a link to the definition in the metrics page
Background:
The current SMAU dashboards are incorrect:
Self managed - The SMAU is overestimated as it does not count unique users performing actions within a stage. Currently, If 1 user uses 1 feature from a stage, we count every user on the instance as a Monthly Active User for that stage. Usage ping is also struggling to do basic SELECT COUNT(*) on large instances; many of these queries time out on GitLab.com
.Com - SMAU is currently blocked due to:
- User_id is not available for snowplow events
- Structured events are not in place. Currently we have unstructured, self-describing events, which requires parsing through the unstructured data and the process will break whenever the CSS or JS changes on the site, there is no stability in these types of events
The proposal is to fix the time out issue for larger instances on usage ping and update the SMAU definition to be highest AMAU (Actions Monthly Active User) for the stage. The .com SMAU and AMAU will also be based the usage ping data.
Does this MR meet the acceptance criteria?
Conformity
-
Added description to this MR explaining the reasons for the proposed change, per say-why-not-just-what