What are you trying to achieve?
Get the windrose panel working after upgrade to Grafana 8.1.1
Note Same problem on Debian10 Buster
All other panels from the same datasource working correctly
How are you trying to achieve it?
Previous to 8.1 no issues with windrose
sql query works correctly in postgresql
What happened?
no display
What did you expect to happen?
wind speed & direction
Can you copy/paste the configuration(s) that you are having problems with?
Adding a standard default panel, data is displayed correctly
Did you receive any errors in the Grafana UI or in related logs? If so, please tell us exactly what they were.
no gui errors
no log errors
Did you follow any online instructions? If so, what is the URL?
Fresh install of the windrose panel from the grafana site
Looks like it hasn’t seen any development for several years. fatcloud-windrose-panel was written in Angular, and we have since migrated to React. At heart, that’s probably the big issue here…
Hi @mattabrams
Yes thats the panel. As I said it stopped working after upgrading to 8.1.
I assumed as it was on the list it would be functional.
Is there a solution to this problem, a wind rose is obviously very useful to display the wind direction and strength for those monitoring weather stations. I have not yet found an alternative.
Grafana has been expanding its development into IoT and Edge scenarios so I would hope that an updated windrose is on the horizon. I know you are not the only one who wants this plugin
The Plugin and both plots (Scatter, Wind Rose) work on Grafana v8.1.2.
You may need to reconfigure them after the update to V8.
In general the 2 embedded plots are very useful to display winds. What it would need is some more options to configure the legend (closer to the chart)
On 8.3.3
Wind Rose working with
without any problem.
But it’s stops to work with SQL data sources. In parameters for Angle and Distance cannot select necessary metics. But prior to Grafana 8 all was fine.
Any fix?
This is how it is looks with MySQL:
there were some breaking changes with SQL datasources with the release of Grafana 8. Guessing this, plus the age of the plugin and its roots in Angular, are causing problems…
one thing I would try is to play with the Format as at the bottom of the query editor, or fiddling with the prepare time series transformation, which can ease some of these issues:
