Curious why Kibana 4.0 is no longer a static webap and why it requires a
Java daemon.
Is this strictly required? I guess I'm fine if it is but why? What does
the Java daemon provide?
The Java daemon is just because it's a Ruby web application running with
JRuby. As the application is Rack-based, you can run it under any
Rack-compatible server if you're prepared to hack about with it.
From my experimentation I got it running under Apache & Passenger and
from what I can tell there's very little that is dynamic; it still is just
HTML/Javascript under the hood. There are a couple of URLs that are dynamic
although I'm not convinced they could be made static too.
It just comes with its own webserver to minimise the barrier to entry.
I put my findings and configuration here:
when I asked if it was possible.
I guess I liked that it was a static webapp as it allows for easier
integration on our end.
Same, I didn't want to run Yet Another Webserver that has fewer features,
etc. etc. and I liked how v3 was easy to deploy & integrate.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.