Kibana browser compatibility issues

Elastic Stack Elasticsearch
1

My first attempt at Kibana 3.1.0 was a little bumpy due to browser issues.
After some reading, I performed the minimal "download, unpack, and point
the browser at index.html. If both Kibana and ES are on the same machine it
will just work."

Not quite! Contrary to all of the "don't set this to localhost", the
default setting in config.js resulted in a "can't find Elasticsearch"
error, while the second setting produced no errors:

Fails to find elasticsearch on the local host: elasticsearch:
"http://"+window.location.hostname+":9200",
No errors resolving Elasticsearch: elasticsearch: "http://localhost:9200",

However... Even the second setting produced a completely blank, utterly
useless, though error-free window inside Chrome Version 35.0.1916.114
("Chrome is up to date") on Mac OS X Mavericks.

For completeness, I tried Safari Version 7.0.3 (9537.75.14) (note: every
possible Mavericks update has been applied to this MacBook). Same blank and
useless window as with Chrome.

But the second configuration (using localhost) works fine under Firefox
Version 29.0.1 ("Firefox is up to date") on the same Mac OS X system,
exposing all of the cool Kibana features described elsewhere. So the
remainder of my initial exploration was, and will continue to be, in
Firefox.

However, the first configuration setting (the default found in the
config.js file) produces the same error on all browsers. And the second
setting is the only one that works, but only when using Firefox. Safari is
so far-i from correct, and Chrome is pitted. Not sure why; javascript is
enabled on Firefox, Chrome, and Safari.

Brian

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/c0035746-d382-4859-b9f1-3c1d3b70e699%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

2

If you simply point the browser at the file system index.html, in my
experience, that only works in Firefox (and only if you explicitly do
http://server:9200"). The Kibana default assumes that you actually run
Kibana from a web server (or as an ES site plugin if you prefer) and that
ES is accessible from the same host as where Kibana is being served from.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/a6956b4b-757e-40c2-834d-5ed26cbd6d70%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

3

We are using Logstash-Elasticsearch-Kibana and just want to be able to open
the index file in Kibana. What is the necessary plugin that will allow us
to do this in something other than firefox?

On Monday, June 2, 2014 11:56:35 AM UTC-7, Binh Ly wrote:

If you simply point the browser at the file system index.html, in my
experience, that only works in Firefox (and only if you explicitly do
http://server:9200"). The Kibana default assumes that you actually run
Kibana from a web server (or as an ES site plugin if you prefer) and that
ES is accessible from the same host as where Kibana is being served from.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/303741f3-a5ce-40c0-b9c0-b2284637c92c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

4

Laura,

The simplest way is to install Kibana as a site plug-in on the same node on
which you run Elasticsearch. Not the best way from a performance and
security perspective, but certainly the easiest way to start with an
absolute minimum of extra levers to pull and knobs to turn, so to speak.

So what does that really mean, a "site plugin"?

Assume you configure Elasticsearch to look for plugins within the
/opt/elk/plugins directory.

Then you unpack the Kibana3 distribution within /opt/kibana3. That means
you'll see the following files within /opt/kibana3/kibana-3.1.0:
app build.txt config.js css favicon.ico font img index.html
LICENSE.md README.md vendor

So then create the /opt/elk/plugins/kibana3 directory. Then:
$ ln -s /opt/kibana3/kibana-3.1.0 /opt/elk/plugins/kibana3/_site

Now when you start ES and point it to the correct configuration file which
in turn points it to the plugins directory as described above, Kibana will
be available at the following URL (assuming you're on the same host; change
localhost as needed, of course):

http://localhost:9200/_plugin/kibana3/

Hope this helps!

Brian

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/59b1ac76-d3a5-4b63-bdc6-f617ef8c0627%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.