-
Notifications
You must be signed in to change notification settings - Fork 377
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Bug] Unified Alerting Not Working #855
Comments
@celestialorb what Grafana version are you using? I believe it has to be at least v8.0.0. You can override the base image if Grafana that the operator deploys. |
I'm using Grafana 9.3.0. |
@celestialorb wasn't unified alerting deprecated in version 9? We are not grafana maintainers so we don't know all possible grafana configuration options. I look at the docs and it seems like it's missing the To add this it's a simple fix and we are happy to take PR:s |
If I recall correctly, unified alerting was opt-in in Grafana 8 and then made the default in Grafana 9. I can take a look at crafting together a simple PR for it. |
I'm like 100% sure that had read it somewhere but I guess I misunderstood it and after the grafana homepage update I'm unable to find anything about it more or less. Sorry about that. Looking forward to your pr @celestialorb |
Describe the bug
When enabling unified alerting for a Grafana deployment I still receive one alert for each replica of the deployment.
Version
v4.7.0
To Reproduce
Steps to reproduce the behavior:
Expected behavior
I expect that enabling unified alerting in the Grafana spec would provision a Grafana deployment/configmap with proper unified alerting.
Suspect component/Location where the bug might be occurring
I suspect this is being caused by not providing the
ha_peers
configuration underunified_alerting
in the config map. If the operator can manage a service for the Gossip protocol and set that service to theha_peers
I believe that might resolve the issue. This should be similar to how the Helm chart solves it.The text was updated successfully, but these errors were encountered: