Add database sourced aggregated metric [RUN ALL RSPEC] [RUN AS-IF-FOSS]

added backend devopsgrowth groupanalytics instrumentation sectiongrowth labels

added 1 commit

7869f893 - Add database sourced aggregated metric

1 Warning

For the following files, a review from the Data team and Product Intelligence team is recommended
Please check the product intelligence guide and reach out to @gitlab-org/growth/product-intelligence/engineers group for a review.

ee/lib/gitlab/usage_data_counters/aggregated_metrics/common.yml
lib/gitlab/usage_data_counters/aggregated_metrics/common.yml

2 Messages

This merge request adds or changes documentation files. A review from the Technical Writing team before you merge is recommended. Reviews can happen after you merge.

CHANGELOG missing:

If you want to create a changelog entry for GitLab FOSS, run the following:

bin/changelog -m 53854 "Add database sourced aggregated metric [RUN ALL RSPEC] [RUN AS-IF-FOSS]"

If you want to create a changelog entry for GitLab EE, run the following instead:

bin/changelog --ee -m 53854 "Add database sourced aggregated metric [RUN ALL RSPEC] [RUN AS-IF-FOSS]"

If this merge request doesn't need a CHANGELOG entry, feel free to ignore this message.

Documentation review

The following files require a review from a technical writer:

doc/development/usage_ping/index.md

The review does not need to block merging this merge request. See the:

Metadata for the *.md files that you've changed. The first few lines of each *.md file identify the stage and group most closely associated with your docs change.
The Technical Writer assigned for that stage and group.
Documentation workflows for information on when to assign a merge request for review.

Reviewer roulette

Changes that require review have been detected! A merge request is normally reviewed by both a reviewer and a maintainer in its primary category (e.g. frontend or backend), and by a maintainer in all other categories.

To spread load more evenly across eligible reviewers, Danger has picked a candidate for each review slot, based on their timezone. Feel free to override these selections if you think someone else would be better-suited or use the GitLab Review Workload Dashboard to find other available reviewers.

To read more on how to use the reviewer roulette, please take a look at the Engineering workflow and code review guidelines. Please consider assigning a reviewer or maintainer who is a domain expert in the area of the merge request.

Once you've decided who will review this merge request, assign them as a reviewer! Danger does not automatically notify them for you.

Category	Reviewer	Maintainer
backend	Rubén Dávila (`@rdavila`) (UTC-5, 6 hours behind `@mikolaj_wawrzyniak`)	Alex Kalderimis (`@alexkalderimis`) (UTC+0, 1 hour behind `@mikolaj_wawrzyniak`)