I use grafana 2.1 and created multiple dashboards, templates etc.
I would like to upgrade to grafana 2.6. Is there any way to upgrade to 2.6 without affecting the existing dashboards?
There are no breaking changes between 2.1 and 2.6. In theory upgrading should be a simple matter of installing the new packages. I personally have upgraded from 2.1.3 to 2.5 to 2.6 with no issues.
For windows version, I just had to copy the data/grafana.db and the data/plugins directory from the old installation to the new installation directory. Just make sure the newer version does not have any breaking changes.
You can upgrade Grafana to higher versions for better features and also import your previous dashboard to the new version without any problem by using Import/Export feature.
Related
Playing catch up with Grafana versions, (Kubernetes v1.16.15 clusters)
Currently running in PRODUCTION is very out of date (v4)
I'm only upgrading now, and refactoring all my configs for the "new" provisioning.
Should I just upgrade to v5 and release in PROD, and then incrementally upgrade again to v6?
or skip v5 just straight to v7?
According to the official docs there are some functions/solutions that went deprecated from one version to another. You should take a look when upgrading to make sure that you are ready for it.
Other than that, there are two ways to get your Grafana to v7:
Step by step upgrade:
Backup Database
Backup Grafana configuration file (i.e grafana.ini)
Perform the update/upgrade depending on the chosen method.
If that won't work, you can also do a fresh install on top of an existing one or remove the current version, install the latest one and than check grafana.ini file.
If you choose the 1st option than please notice that it is considered safer to upgrade one major version at the time. Also, the database/configuration backup is always recommended.
EDIT:
If you are using Grafana Community Kubernetes Helm Charts than notice that Upgrading an existing Release to a new major version requires the Helm v3 (>= 3.1.0) starting from Grafana v6.0.0.
Thanks #Wytrzymały Wiktor
I'm taking the "safe route" upgrading v4->v5 first. New functions and configuration change impacts are too great (as I said system is very out of date!)
Re-factoring all my helm charts, and getting old dashboards re-imported to v5 DB,and backing up everything as you advise.
v5 will be released to PROD users, and then will start looking at v6 upgrade soon after.
If I upgrade the angular version of my project to the latest one, do I need to upgrade my ag-grid version also to the latest one to make it work? Or, my ag-grid will work without any change?
Generally, an old version will work without change.
I'm currently using version 20.2.0 with Angular 8 (the current ag-grid version is 23.1.0).
I'm not sure what will happen if you try to use an older version with Angular 9, using the Ivy Renderer. I expect that it will work ok, but I haven't tried it yet.
Hi I am trying to transport data from mongodb to elasticsearch. I have done it by following this tutorial. It is working for elasticsearch version 1.X. But when I tried to do it with version 5.X. plug-ins can't be installed. Can someone help me to figure out a way to do it with version 5.X.
These are the two plugins.
$ES_HOME/bin/plugin -install elasticsearch/elasticsearch-mapper-attachments/1.6.0
plugin --install com.github.richardwilly98.elasticsearch/elasticsearch-river-mongodb/2.0.9
In elastic 5.x+ the installation commands are different. The mapper attachment library you're trying to install has an example here
bin/plugin install elasticsearch/elasticsearch-mapper-attachments/3.1.2
The other library does not mention support of Elastic > 2.x, and its last commit was well before 5.x existed.
If you need to use that exact library, I don't believe you will be able to use anything > 2.x
I have a production mongoDB 2.0 server running on a single machine. I need to upgrade it to the latest version. Would it be possible to just restore the dump from old server into the new server? Or would I have to do it one upgrade at a time?
No, in the general case, absolutely not. Best practice is to upgrade through each major version, following the upgrade instructions in each set of release notes. You can do this without downtime if you are running a replica set, at least from 2.4 -> 3.0 (I'm not as familiar with 2.0 and 2.2 since they are ancient).
How to go about upgrading moodle without all coursefiles going to the legacy folders?
I have tried re mapping files and creating links in the course area to the files that worked, but i am wondering if their any other way of going about it? Possibly upgrading further to 2.3+ could fix this issue?
Yes it is possible to upgrade moodle version from 1.9 to 2.2.
Please go through following url
http://docs.moodle.org/22/en/Upgrading_to_Moodle_2.2