When comparing elasticsearch-gui vs ElasticHQ, the Slant community recommends elasticsearch-gui for most people. In the question“What are the best Elasticsearch GUI clients?” elasticsearch-gui is ranked 1st while ElasticHQ is ranked 2nd. The most important reason people chose elasticsearch-gui is:
Elasticsearch-gui is a free and open source GUI client for ElasticSearch. It's released under the Apache 2.0 licence.
Specs
Ranked in these QuestionsQuestion Ranking
Pros
Pro Free and open source
Elasticsearch-gui is a free and open source GUI client for ElasticSearch. It's released under the Apache 2.0 licence.
Pro Cross-platform
Since it's web-based, all you need to run and access the GUI client is a web browser.
Pro Connects to each ES instance (html-based)
Pro Runs as AngularJS client
Can use ElasticSearch as a plugin for AngularJS platform.
Pro Displays basic cluster information
Shows name, number of nodes, number of data nodes, active primary shards, active shards, relocating shards, initializing shards, and unassingned shards.
Pro Allows to explore your ES index
Provides different ways to explore your index, from keyword-based search to facets or filtering options in the query.
Pro Cloud ready
Can be deployed on AWS, Azure and any other cloud service.
Pro Most comprehensive set of tools
Can manage and keep track of ES Datasets in real time, is cloud-ready and has been battle-tested by multiple large companies.
Pro Installation is easy
ElasticHQ is easy to install and accessible from your browser. Can be installed in just 2 commands and will remain running until shutdown. Installation docs can be found here.
Pro Real-Time Monitoring
ElasticHQ allows you to view real-time threads, individual cluster nodes, cluster runtime metrics, and configurations.
Pro Open source
Licensed under Apache 2 can be used and re-distributed without complications.
Pro Cluster management
Complete control over clusters, nodes, indexes, and mappings.
Cons
Con Looks like it's been abandoned
No updates since 2016 (it's late 2018, at the time of writing).
Con Not maintained anymore
Con Error when using SSL and Python 3.6+
This bug is under investigation but is not close to being solved. See here.