### Problem to solve <!-- What problem do we solve? --> The monitoring dashboard in the self-monitoring project does not display any metrics out of the box since it only displays metrics if there are deployments to an environment. Displaying metrics of the GitLab instance on the monitoring dashboard would allow admins to view resource usage and other metrics without leaving GitLab. It will also further the goal of using monitor features for self-monitoring. ### Intended users * Sasha, Software Developer, https://design.gitlab.com/research/personas#persona-sasha * Devon, DevOps Engineer, https://design.gitlab.com/research/personas#persona-devon * Sidney, Systems Administrator, https://design.gitlab.com/research/personas#persona-sidney <!-- Who will use this feature? If known, include any of the following: types of users (e.g. Developer), personas, or specific company roles (e.g. Release Manager). It's okay to write "Unknown" and fill this field in later. Personas can be found at https://about.gitlab.com/handbook/marketing/product-marketing/roles-personas/ --> ### Goal This epic has 2 goals in mind: 1. create a gitlab self-monitoring dashboard 1. Document how to add additional metrics to improve the user experience ### Further details 1. Create a special case to load a different default dashboard for the self-monitoring project. 1. Add the following metrics to the dashboard (see https://gitlab.com/gitlab-org/gitlab/issues/38038#note_260119683 for more details) * Web Traffic - Error Ratio * API Traffic - Error Ratio 1. Document how to add additional metrics. 1. Remove the feature flag so users can install the Self-Monitoring project. ### Proposal <!-- How are we going to solve the problem? Try to include the user journey! https://about.gitlab.com/handbook/journeys/#user-journey --> ### Permissions and Security <!-- What permissions are required to perform the described actions? Are they consistent with the existing permissions as documented for users, groups, and projects as appropriate? Is the proposed behavior consistent between the UI, API, and other access methods (e.g. email replies)? --> ### Documentation <!-- See the Feature Change Documentation Workflow https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html Add all known Documentation Requirements here, per https://docs.gitlab.com/ee/development/documentation/feature-change-workflow.html#documentation-requirements --> ### Testing <!-- What risks does this change pose? How might it affect the quality of the product? What additional test coverage or changes to tests will be needed? Will it require cross-browser testing? See the test engineering process for further guidelines: https://about.gitlab.com/handbook/engineering/quality/guidelines/test-engineering/ --> ### What does success look like, and how can we measure that? <!-- Define both the success metrics and acceptance criteria. Note that success metrics indicate the desired business outcomes, while acceptance criteria indicate when the solution is working correctly. If there is no way to measure success, link to an issue that will implement a way to measure this. --> The GitLab self-monitoring project will be able to display metrics of the GitLab instance on the monitoring dashboard out of the box. The metrics themselves can be defined in another issue. ### Links / references