Open tonypowa opened 5 months ago
This issue is a test copy of an issue in another repo. Original issue: https://github.com/grafana/grafana/issues/#83448
Hi @tonypowa, it looks like the issue might be related to an alerting bug introduced in the version 10.3.3. As it impacts alert functionality and not a specific datasource, the most suitable project for this issue seems to be the Alerting project. It would be best to raise this problem there so that it can be addressed by the team specializing in alerting features.
Summary: After upgrading to Grafana 10.3.3, multiple alerts from different data sources began failing with errors about frames not being uniquely identifiable by their labels, and reverting to version 10.2.3 resolves the issue.
Elaboration:
Hi @tonypowa, thank you for reporting this issue! In order to fully understand and address the problem you're encountering with Grafana after upgrading to 10.3.3, we need a bit more information. Here are some questions that can aid us in diagnosing the issue more effectively:
Once we have this additional information, we'll have a much better chance of pinpointing the issue and providing a solution. Thank you for your cooperation! 🛠️
What happened?
We recently attempted to upgrade from 10.2.3 to 10.3.3 for the recent security fix. Unfortunately we quickly saw that this caused errors with multiple alerts and from multiple datasource types. The error is:
Revert back to 10.2.3 fixes the issue.
I found another person having the same issue:
https://www.reddit.com/r/grafana/comments/1ay5egy/getting_this_alert_error_in_grafana_1033_what_am/
What did you expect to happen?
alerts to continue to function
Did this work before?
yes
How do we reproduce it?
upgrade to 10.3.3
check alerts for above error
Is the bug inside a dashboard panel?
no
Environment (with versions)?
Grafana: 10.3.3
OS: mac
Browser: chrome
Grafana platform?
Kubernetes
Datasource(s)?
No response