[BUG] Tracing dashboard Flame panel error
Search before asking
- [X] I had searched in the issues and found no similar feature requirement.
DeepFlow Component
Grafana Dashbaord
What you expected to happen
Red exclamation mark appears on the Flame panel, reporting error
How to reproduce
Using a deepflow data source A Grafana deployed using templates within a chart Connect to an existing Grafana on your own Except for the difference in yaml (which I tried and should not be related to), the other versions of Grafana are the same, but the only data cannot be generated is the flame. The internal version in the chart has this, while the external version of Grafana does not have this flame
DeepFlow version
Branch:v6.4
DeepFlow agent list
normal
Kubernetes CNI
calico
Operation-System/Kernel version
No response
Anything else
This issue may occur when using an external database
But the Flame panel version 6.2.6 used before was normal
Are you willing to submit a PR?
- [X] Yes I am willing to submit a PR!
Code of Conduct
- [X] I agree to follow this project's Code of Conduct
@rvql @sharang @1473371932 Do you have any insights? Why does this inconsistency occur when connecting two identical versions of Grafana F12 400bad requehst but grafana panel error messege:the expected status code returns 200,the actual return is 500
Updated the latest discovered issues
It seems that Grafana generated two query queries after clicking on them, and the last 400 was an issue with SQL statements, as can be seen in the logs of the last server in the image SQL statements similar to clickhouse do not have the column "AS"?
@1473371932 Please help to solve this problem.
@1473371932 Please help to solve this problem.
Found the reason, the external Grafana initc plugin still uses the 6.2 upgrade to resolve the issue thanks