Roy Russo

I used to have an auto-refresh and manual refresh in the old version of the application. The reason I removed it, is because the refresh on large clusters can take...

Isn't this the same layout? Or do you mean just one large table... so column per node?

Ok. Worth consideration for easy comparison. Downside is too many nodes cause side-ways scroll.

Interesting. This may be tricky to add as a pull request, as it will affect non-proxy users. I can talk to @pcasa and see if he can add a context...

Moving to 3.6.0. Depends on having #485 working, so we can test nginx + HQ and close all related issues with reverse proxies.

I can't pull this in to master, as the develop branch is very different. I'm not a JS expert, but I believe this collides with https://github.com/ElasticHQ/elasticsearch-HQ/blob/0a43f042b8202f14bc0c8e13d6d2c9f0a4ccb2c6/ui/src/containers/home/home.controller.js#L40

Related: https://github.com/eventlet/eventlet/issues/371 Try monkey_patch as early as possible, seems to be the recommended fix.

Hi @PurpleBabar , I can look at adding a favicon. The one you posted is too close to the elastic logo... and lately it seems Elastic is a little lawsuit...

Anything in logs?

... so you don't see the `.elastichq` index created? Does the main dashboard have data on it?