-
Notifications
You must be signed in to change notification settings - Fork 28
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
Does updating from Polystat 1.2.11 to last version keeps old panels usable? #405
Comments
the migration is automatic, i would backup your dashboard just in case you run into an issue |
that appears to be a regression, will repro and get it fixed |
Hello @briangann |
There are few things to edit after upgrading. Grafana 11.1 only load polystat 2.0.0 >, so you have to upgrade also polystat panel. Upgrading from panel polystat version 1.12.x to 2.1.x requires few changes in complex dashboards. Upgrading a panel with complex overrides and composites requires to add / at the start and at the bottom of the metric, which before wasn't required. So this problem with metrics can lead to increasing the number of cells. which also lead to an error: Cannot read properties of undefined (reading 'x') if the number of cells excedes the limit configured in the layout section. Metrics changes also afflicts cells colors. i found out that now sometimes value mapping conflicts with overrides. so i used value mapping color setting for the cells color configuration instead of overrides. I hope this could be useful. |
By manually updating, so downloading the package and importing it by hand into the plugin directory, replacing the old one, can create problems with panels made in the previous version of polystat? Or does it automatically convert the old panels and they will be accessible immediately?
Are there other ways to import old panels into the new version? Maybe copy the JSON panel manually to a dashboard in the new version?
Or does it not work because of incompatibilities between versions?
Best regards!
The text was updated successfully, but these errors were encountered: