Update Elasticsearch License
1,169 words in 7 minutes
Marvel is the official Elasticsearch monitoring plugin. Although it’s free, it requires subscription for a basic license.
The initial trial license lasts for only one month. After the first month, marvel will stop showing dashboard and give you a grace period of 7 days to renew the license. If you do not renew it, not only marvel will not work anymore, but all marvel data will be deleted as well.
Before researching for another handy monitoring plugin, I decide to renew the license first.
Steps to Renew License
According to the document, the steps are pretty simple.
- Register for a new license on official site
- Update license through API
Register for a new license
I will not dive into it too much. Just go to the register page and fill out a form. Then you will receive an email with download link of the license. Download and save the license file.
Update license through API
Elasticsearch has a special license API.
|
|
- <host>: the hostname of the Elasticsearch node (localhost if executing locally)
- <port>: the http port
- license.json: the name of license JSON file
The -u admin
is for Shield users.
Note that for the file you need to specify an absolute path, unless it is under the current path you are running the terminal.
The response will show you some information about the license. For example, if may tell you that the license is not enough to all previous services. If it is enough, you can call the API again with a query parameter acknowledge=true
.
|
|
View License
|
|
This API will get you the license status. Example result is shown below:
|
|
Problem
What if the annoying expiry page still shows? I met this problem after everything in the document is done. So, it is actually not enough to just update license. To fix this problem, I tried to update marvel at the kibana end.
Update Marvel
Update Marvel is fairly simple, you just remove the old one and install a new one.
|
|
Then you can install it.
|
|
Sometimes it will not work because the version. Marvel version should be aligned with Kibana version. For example, if your Kibana is still 4.3.0, you cannot use latest Marvel, which is 2.2.0. You will need to get Marvel 2.1.0 instead.
|
|
If the page still shows, you may restart the cluster.