Skip to content

GitLab Next

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
GitLab
GitLab
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 34,923
    • Issues 34,923
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 1,236
    • Merge Requests 1,236
  • Requirements
    • Requirements
    • List
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Security & Compliance
    • Security & Compliance
    • Dependency List
    • License Compliance
  • Operations
    • Operations
    • Metrics
    • Incidents
    • Environments
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • CI / CD
    • Code Review
    • Insights
    • Issue
    • Repository
    • Value Stream
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • GitLab.org
  • GitLabGitLab
  • Issues
  • #283175

Closed
Open
Opened Nov 14, 2020 by Haris Delalic@hdelalic🖖Developer

Create one metric for the Import GMAU

Problem

In this epic we added several metrics that count unique users engaging with different types of import actions: projects_imported, issues_imported, groups_imported.

However, the sum of these counts does not represent the true Import GMAU, as these users are not de-duped. Also, having one (well-named) number to track makes it simples to build dashboards and reports.

Proposal

  • Add a new usage ping metric that combines the individual metrics.
  • This metric will count the number of unique users engaging any importer feature.
  • Name this metric clearly, something like usage_activity_by_stage.manage.unique_users_all_imports

The above-described proposal is technically challenging and will be a larger effort, as it combines the users data for projects, groups, and individual issue importers in order to dedupe them to arrive at unique user counts.

Therefore, we will approach this solution by iterating, as follows:

  1. Create a new usage ping that contains unique user counts for project importers only. This can be done much faster, as we already have a similar solution. - #297431
  2. Compare the count for project importers to the counts of issue and group importers to decide if the added precision warrants the additional investment.
  3. If needed, play this issue to instrument the full user counts. Otherwise, cancel this issue.

Out of scope of this issue

  • Update the MAU Dashboard to use the new metric.
  • Clean-up of the current usage pings that contain user counts. - #297432
Edited Jan 12, 2021 by Haris Delalic
Assignee
Assign to
Awaiting further demand
Milestone
Awaiting further demand
Assign milestone
Time tracking
None
Due date
None
Reference: gitlab-org/gitlab#283175