This epic supplements the work being done to create an information pack about Scalability for the Stage Groups (https://gitlab.com/groups/gitlab-com/gl-infra/-/epics/216). The goal of this epic is to be able to connect resource usage or incident root causes to a feature category. We [already have this in place for Sidekiq](https://docs.gitlab.com/ee/development/sidekiq_style_guide.html#feature-categorization), and would like to extend this to Web and API requests. We will first create a framework to be able to categorize actions and endpoints, then we will perform a first-pass categorization, and we will make this information available in the metrics and logs. The benefit for Stage Groups is that they will have more information available to them about how their feature categories perform on GitLab.com. ### Exit Criteria 1. [x] Web requests are assigned to feature categories on a best effort basis 1. [x] API requests are assigned to feature categories on a best effort basis 1. [ ] Engineers know how to change the attribution (not sure if this is an exit criteria on it's own?) 1. [ ] This change is advertised in: 1. [x] Engineering Week-In-Review 1. [x] `#development` 1. [x] `#eng-managers` 1. [x] `#development-guidelines` 1. [x] `#infrastructure-lounge` 1. [x] Update https://gitlab.com/gitlab-com/www-gitlab-com/-/issues/9061 with status (at the time of completing this epic, the issue had been closed - so will not update further). ## Status 2020-11-20 Feature category information is available for each Rails controller and each API endpoint. This is surfaced in the [web dashboard](https://dashboards.gitlab.net/d/web-main/web-overview?orgId=1). Changes have been communicated with teams. This paves the way for custom dashboards and alerting for stage groups that will be addressed in future projects.