table of Contents
Why install elasticsearch-head through Chrome plugin
consult
elasticSearch-head is an open source project on github. The official explanation for it is the elasticserach cluster management tool.
I would like to ask you here, what is the difference between this front-end visual management tool and kibana? Any reply is greatly appreciated.
Why install elasticsearch-head through Chrome plugin
Let ’s first recall what is called cross-domain?
The cross-domain problem is a security limitation of browsers for ajax requests. An ajax request initiated by a page can only be the same path as the current page domain name, which can effectively organize cross-site attacks. Therefore, the cross-domain problem is a limitation for ajax
In other words, no matter how we deploy elasticsearch-head, in the end, as long as we request to connect to elasticsearch through the browser page, cross-domain problems will occur . And if there is a cross-domain problem, you have to change the configuration. For us who are developing locally, it is obviously too much trouble. And access through the plug-in will not cause cross-domain problems, naturally there is no need to change the configuration file
Install in Chrome App Store
Brother, I understand you are also annoyed why the Google App Store cannot be opened. If you can't open it, you can try other ways to install it, and then find the cross-domain 2 lines of configuration code online.
If you just want to open it through Google plug-in, you can chat with me privately, we can communicate, you know ~~
Test connection
To test the connection, you must first ensure that your es background service is started, and then click the browser plug-in, a page will pop up
Enter the address where the ES background service starts. Did the brother see the green in the upper right corner? It's green, we will succeed ~
