Open mtrossbach opened 3 years ago
This actually isn't strictly a problem with the Azure Monitor datasource, but rather due to Azure Monitor being upgraded to use Data Frames, which the Pie Chart panel does not support for queries like this.
I'll move this to the Pie Chart repo so it can be tracked properly against that plugin. In the mean time, maybe consider whether there might be other panels to better visualise your data https://blog.funnel.io/why-we-dont-use-pie-charts-and-some-tips-on-better-data-visualizations
(by the way @mtrossbach, thanks for the detailed report and example generic KQL query - it made looking into this much easier 🙏)
pie chart panel is not working without time field in data query.could you please help me?
What happened: Beginning with Grafana version 7.1.0 we observe a wrong behavior when using the Azure Monitor plugin together with Log Analytics to query a time-series. For us it looks like as if as soon as the data contains more than a datetime + numeric value column the data is not handeled as a time-series anymore. In Grafana versions 7.0.6 and before it is handeled correctly.
What you expected to happen: We would expect that the query result is handeled as a time-series and not as a table if the data contains a datetime column, a numeric value column and a string (label) column. That behaviour is explained in the Grafana docs at: https://grafana.com/docs/grafana/latest/datasources/azuremonitor/#time-series-queries
How to reproduce it (as minimally and precisely as possible): That problem can be reproduced using the two expamples from the Grafana docs link.
To make things easier you can also use the following Log Analytics query and try visualize it using the piechart panel:
Not working in > v7.1.0, while working in v7.0.6:
Screenshot from Query Inspector on v7.3.6: Panel error on v7.3.6:
Panel Data v7.3.6
Screenshot from Query Instector on v7.0.6: Panel on v7.0.6:
Panel Data v7.0.6
Anything else we need to know?: In the Grafana support forum another member had an issue which I think is related to our issue: https://community.grafana.com/t/azure-monitor-updating-queries-to-match-behavior-differences-after-upgrading-grafana/38355 In our case changing the order has no effect.
Environment: