WIP: Implement alert mapping parsing from YAML
What does this MR do?
Spike implementation for the backend part of #224632 (closed) and #220402 (closed) as described in #220402 (comment 366803569)
Notes
-
Implement a concise and verbose YAML format stored in .gitlab/alert_mapping/<provider>.yml -
Implement a controller receiving a alert payload and match against configured alert mappings to create a generic alert - route:
<project_path>/-/alerts/notify/<provider>.json
- route:
-
Expose GraphQL query and mutation for showing/editing mapping from frontend
Caveats
- Won't be merged since it's a spike; hence
WIP: - Almost not specs
🤠 - Contains
🐛
Screenshots
| Alert mapping | Submit custom payload | Alert details | Incident Issue |
|---|---|---|---|
 |
 |
 |
 |
Does this MR meet the acceptance criteria?
Conformity
-
Changelog entry -
Documentation (if required) -
Code review guidelines -
Merge request performance guidelines -
Style guides -
Database guides -
Separation of EE specific content
Availability and Testing
-
Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process. -
Tested in all supported browsers -
Informed Infrastructure department of a default or new setting change, if applicable per definition of done
Security
If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:
-
Label as security and @ mention @gitlab-com/gl-security/appsec -
The MR includes necessary changes to maintain consistency between UI, API, email, or other methods -
Security reports checked/validated by a reviewer from the AppSec team
Edited by 🤖 GitLab Bot 🤖