Support for Unified Alerting

[siegenthalerroger]

Is your feature request related to a problem? Please describe.

Currently we use a prometheus-operator operated AlertManager and are looking to replace it with Grafana's built-in AlertManager. This would reduce overhead and allow us to enjoy all the nice UI features of Unified Alerting.

Describe the solution you'd like

There should be custom resources for all unified alerting types:

• Alert Rules (generally we'd use PrometheusRules for this, but it's a grafana feature and there are some edge-cases where it makes sense to have rules in grafana not prometheus)
• Contact Points
• Notification Policies
• Templates
• Mute Timings

Describe alternatives you've considered

1. Hacking something together to load provisioning files from git into a custom volume using a git sidecar and mangling the grafana-operator Grafana to load them. We currently do this for Datasources and Dashboards and getting rid of this is the main reason for migrating to grafana-operator.
2. https://grafana.com/docs/grafana/latest/alerting/set-up/provision-alerting-resources/file-provisioning/#file-provisioning-using-kubernetes

Both of these options are valid and do work, however it's not really the point of having an operator if I need to do this.

Context

• https://grafana.com/docs/grafana/latest/alerting/set-up/provision-alerting-resources/
• https://grafana.com/docs/grafana/latest/developers/http_api/alerting_provisioning/#information

[pb82]

The Alerting API is currently still marked as unstable (https://grafana.com/docs/grafana/latest/developers/http_api/). There is also an Alert provisioning API, but they both lack documentation. Is someone familiar with those APIs and could provide some insight?

[NissesSenap]

This issue looks like #911
I have added a bunch of my thoughts in there. @siegenthalerroger we would love to hear your thinking around it. But in short, this isn't an easy feature to add due to the lacking of documentation and unstable API.

[siegenthalerroger]

Oh @NissesSenap it is the same, sorry. Feel free to close this issue.

@pb82 I'll post this on the other one aswell, but I'm fairly sure only the provisioning API would be necessary and that is stable (now? is that v10 or did that happen inbetween).