|
@@ -17,6 +17,17 @@ In order make this a reality Grafana upgrades are backward compatible and the up
|
|
|
|
|
|
|
|
Upgrading is generally always safe (between many minor and one major version) and dashboards and graphs will look the same. There can be minor breaking changes in some edge cases which are usually outlined in the [Release Notes](https://community.grafana.com/c/releases) and [Changelog](https://github.com/grafana/grafana/blob/master/CHANGELOG.md)
|
|
Upgrading is generally always safe (between many minor and one major version) and dashboards and graphs will look the same. There can be minor breaking changes in some edge cases which are usually outlined in the [Release Notes](https://community.grafana.com/c/releases) and [Changelog](https://github.com/grafana/grafana/blob/master/CHANGELOG.md)
|
|
|
|
|
|
|
|
|
|
+## Update plugins
|
|
|
|
|
+
|
|
|
|
|
+After you have upgraded it is highly recommended that you update all your plugins as a new version of Grafana
|
|
|
|
|
+can make older plugins stop working properly.
|
|
|
|
|
+
|
|
|
|
|
+You can update all plugins using
|
|
|
|
|
+
|
|
|
|
|
+```bash
|
|
|
|
|
+grafana-cli plugins update-all
|
|
|
|
|
+```
|
|
|
|
|
+
|
|
|
## Database Backup
|
|
## Database Backup
|
|
|
|
|
|
|
|
Before upgrading it can be a good idea to backup your Grafana database. This will ensure that you can always rollback to your previous version. During startup, Grafana will automatically migrate the database schema (if there are changes or new tables). Sometimes this can cause issues if you later want to downgrade.
|
|
Before upgrading it can be a good idea to backup your Grafana database. This will ensure that you can always rollback to your previous version. During startup, Grafana will automatically migrate the database schema (if there are changes or new tables). Sometimes this can cause issues if you later want to downgrade.
|
Torkel Ödegaard