Missing connection between metric/event and feature it is tracking
Problem
Currently there is no way to automatically map a feature to corresponding event/metrics. This makes it challenging to track and understand what percentage of our features have instrumentation in place. More details here
Desired Outcome
Create a way to record connection between metric/event and the related feature from features.yml in a scalable and verifiable manner
Proposed Solution
In Scope:
- Add
associated_metrics
as additional property to features.yml - Add validation to make sure metrics added in features.yml are actual metrics (if possible)
- Add Monte Carlo alert if metrics in feature.yml either do not exist or are no longer active (blocked by https://gitlab.com/gitlab-data/analytics/-/issues/20482)
Example excerpt from feature.yml
---
- title : "Issue Board Assignee Lists"
description: "Issue board lists that pull in issues assigned to a given user"
screenshot_url: 05-issue-boards.png
link_description: "Documentation about Issue Board Assignee Lists"
link: https://docs.gitlab.com/ee/user/project/issue_board.html
category:
- team_planning
+ metrics:
+ - usage_activity_by_stage_monthly.plan.assignee_lists,usage_activity_by_stage.plan.assignee_lists
+ - counts.assignee_lists
gitlab_core: false
...
How to verify
- Metric mapping for
Issue Board Assignee Lists
can be added - Mispronouncing metric title in in features.yml leads to Monte Carlo Alert
Further actions needed
- Should be mentioned to product groups
- Should be mentioned to Customer Success
Edited by Sebastian Rehm