### Problem to solve In https://gitlab.com/gitlab-org/gitlab-ce/issues/51963, we are adding support for Prometheus at the group-level and NOT including support for alerts. Here we implement support for alerts from group-level prometheus clusters. ### Intended users <!-- 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/ --> ### Further details <!-- Include use cases, benefits, and/or goals (contributes to our vision?) --> ### Proposal With the alerting feature, sharing a Prometheus server between projects has gotten more complex. 1. We dynamically build the Prometheus configuration, based on the configured alerts. 1. There is also a webhook setup on the GitLab side, to receive any notifications of triggered alerts. I *think* this is at the project level. So in order to support Prometheus at group level, we will need to: 1. Aggregate the needed alerts that need to be configured across all the group's projects. 1. Potentially configure each alert to notify the existing project webhook, or define a new group webhook endpoint. ### 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. --> ### Links / references