-
Notifications
You must be signed in to change notification settings - Fork 13
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
Dashboard with panels from multiple data sources errors with "-1. Message: Query error: -1 Request was aborted" #259
Comments
I have been facing this issue for a few months. Please fix it soon. |
Hi! I just picked this up to investigate. As a workaround for now, you can set the |
Thanks @iwysiu. Is this feature toggle available for regular Grafana Cloud paid customer? Not sure we are at "Grafana Cloud Advanced" |
Hi @jovezhong ! You should be able to file a support ticket and they'll handle it for you (I double checked and it should still be fine) |
Hi! I just released v2.13.5, which has the fix for this. |
Thanks, I confirmed the fix works well. I just upgraded to 2.13.5 on my Grafana Cloud (glad to see I can click Update directly, without having to go to Grafana admin website). After 1 min, the upgrade is done and my dashboard with multiple athena sources can work well. |
What happened:
Setting: a dashboard with at least two panels with different Athena datasources.
Each panel individually contains a query which has results.
When displaying both panels, when dashboard is refreshed, only the final panel will not have the error "-1. Message: Query error: -1 Request was aborted"
What you expected to happen:
All panels should not have an error while refreshing dashboard.
How to reproduce it (as minimally and precisely as possible):
For the squad, here is an example: https://clouddatasources.grafana.net/goto/7nO7sU94g?orgId=1
Screenshots
Screen.Recording.2023-07-06.at.18.11.05.mov
Anything else we need to know?:
Same behavior locally (v2.10.1) and on Grafana Cloud (v2.9.6)
Environment:
The text was updated successfully, but these errors were encountered: