Serverless usage metrics per project

Problem to solve

The primary metric for GitLab's usage is SMAU. Currently, we define SMAU as the number of active Knative installations. This is clearly a bad approximation as it says nothing about real usage of these features, not even the number of projects a given cluster might be used in.

As we provide automatic domains to serverless projects on gitlab.com, we can measure their usage by domain, and find a more meaningful SMAU than Knative installations. Following #35591 (closed), we have the overall number of requests for serverless domains, but we miss user/project level metrics.

In this issue, we would like to add user/project level request metrics to automatically provisioned domains.

This measure is still misleading, as it does not count on-prem and custom domain usage. In these cases we might have data about the settings only, not the number of requests.

Intended users

This feature is for internal use.

Further details

  • we would know who our users are, and might be able to reach out to them for feedback, insights
  • we can learn about usage habits, and optimize our features based on them

Proposal

Permissions and Security

Documentation

Testing

What does success look like, and how can we measure that?

What is the type of buyer?

Links / references

Edited Dec 02, 2019 by Viktor Nagy (GitLab)
Assignee Loading
Time tracking Loading