Make default elasticsearch URL use the same protocol as Kibana

[dimas]

Please change

    elasticsearch: "http://"+window.location.hostname+":9200",

to

    elasticsearch: window.location.protocol+"//"+window.location.hostname+":9200",

It should not affect anyone using Kibana over HTTP but will allow it work out of the box with HTTPS. If people moving Kibana to HTTPS there is really no sense to keep elasticsearch on plain HTTP anyway.

[kkirsche]

My only concern is that this would require the user to have ensured they have configured ElasticSearch to use the same protocol that Kibana is using while using http:// works with ElasticSearch's default configuration settings. I could be wrong about that, but my belief is that Kibana should be designed / coded to work with ElasticSearch's default configuration.

[dimas]

I am sure that most people just access Kibana over HTTP so they won't be affected by that change.

If someone removes HTTP access to Kibana and uses HTTPS instead, they probably doing it for a reason. Which of course can be different for everyone but chances are they do not want someone capturing plaintext traffic and seeing all the internal logs of their system.
But it just makes a very little sense to encrypt Kibana's traffic itself while still leaving Kibana to elasticsearch data plaintext as the very same information is availble there. It is only because of that I believe you either move both ports (kibana+elasticsearch) to HTTPS or do not bother doing it with either ot them.

Our case maybe a bit special, I admit. We just put Kibana/ElasticSearch on an Amazon node with a load balancer in front of it. The load balancer is told to do HTTPS termination - so it accepts HTTPS on ports 9292 and 9200 and just forwards these ports to the real server but as plain HTTP. (Kind of typical use of Amazon ELB). So in the end both Kibana and ElasticSearch installed with their "out of the box" configuration - default ports etc. The only problem is that ElasticSearch URL sent back to the browser is taken from config.js and is "http://" so even though the page is loaded from https://kibana:9292, it tries to get ElasticSearch data from http://kibana:9200 which does not work as ELB expects SSL handshake on port 9200.
We replaced this http with https but it really felt like that behaviour should be more "automatic" for the reasons explained above. I hope my explanation makes sense.

Also, to replace the URL we patched config.js right in the logstash.jar. Which is ugly but this, I guess, is only because of our lack of experience with Kibana as we could not find the official way of changing that elasticsearch URL :)

[rashidkpc]

Indeed, I don't see a reason to change the default here, we allow you to configure it as needed.