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,919
    • Issues 34,919
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge Requests 1,225
    • Merge Requests 1,225
  • 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
  • #234027

Closed
Open
Opened Aug 07, 2020 by James Ramsay@jramsay-gitlab⚡Maintainer

Report combined AMAU for Git write operations via usage ping

Problem to solve

The AMAU counters added by #219956 (closed) are separated by repository type (project, wiki, design), but the total distinct users is somewhere between the maximum and sum of these values. This means we are currently under or over counting Create SMAU for self hosted instances.

On GitLab.com this is not a problem because we can calculate it directly from the database dump.

Proposal

Add a new field that takes the distinct count of all users who performed any Git write operation to the usage_activity_by_stage_monthly section of the usage ping.

Links / references

#219956 (closed)

Assignee
Assign to
13.6
Milestone
13.6 (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: gitlab-org/gitlab#234027