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
Panel with queries from different sources not working #28114
Comments
Seems like the requests get the same
I'm not familiar with these data sources so I'm going to need some time to find where the root cause is. |
I will continue this investigation on Monday, lot's of other things have come in between :( |
Thanks, I think this was different data sources that were brought together, so maybe something there. The following looks pretty sketchy: grafana/public/app/plugins/datasource/grafana-azure-monitor-datasource/datasource.ts Lines 81 to 109 in 670b851
|
FYI if I do something after the deep clone like:
The request is no longer cancelled. |
@hugohaggmark I think this might not have resolved the issue fully. While it is no longer cancelled, it seems like data is lost. For example with the following there is no data in the fields it seems: However, if I disable one of the two queries, than I get data: |
Oh noes, I'll look into it ASAP. |
I can confirm its working in 7.3.1 release. Thank you guys |
When a panel configured with query from different source in my case query A is application insights and query B is azure log anlytics. In query inspector no data is returned. It seems for different sources grafana is making two requests to
/api/ds/query one for application insights and one for log anytics i can see in browser one query is getting blocked. Tried in both chrome and firefox same result chrome its showing cancelled. This was working fine before , i am not sure which version was running before as this was in kubernetes and when kubernetes cluster upgraded and restarted i think it downloaded a new container version. Attached the screenshot of network call from browser
Grafana version v7.2.0
The text was updated successfully, but these errors were encountered: