<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Kibana Elasticsearch on Roger Welin</title><link>https://rogerwelin.github.io/categories/kibana-elasticsearch/</link><description>Recent content in Kibana Elasticsearch on Roger Welin</description><generator>Hugo -- 0.155.0</generator><language>en-us</language><lastBuildDate>Fri, 06 Mar 2015 19:19:43 +0000</lastBuildDate><atom:link href="https://rogerwelin.github.io/categories/kibana-elasticsearch/feed.xml" rel="self" type="application/rss+xml"/><item><title>How to install and run Kibana4 on a elasticsearch tribe node</title><link>https://rogerwelin.github.io/2015/03/06/how-to-install-and-run-kibana4-on-a-elasticsearch-tribe-node/</link><pubDate>Fri, 06 Mar 2015 19:19:43 +0000</pubDate><guid>https://rogerwelin.github.io/2015/03/06/how-to-install-and-run-kibana4-on-a-elasticsearch-tribe-node/</guid><description>&lt;p&gt;Not long ago Kibana 4 was released and I think it&amp;rsquo;s a major improvement in relation to the previos version of Kibana. Some changes worth mentioning is that Kibana 4 now runs a node js web server, Express, while Kibana3 was just plain js files that you had to serve in a httpd or nginx. This really is a great improvement! In kibana3 elasticsearch web port 9200 had to be reachable by the client, not an ideal solution as this is something you want to limit as it enables anyone to just do a curl -XDELETE. The workaround was to make a lot of proxy rewrites in the webserver serving kibana - Workable but felt more of a hack than a good solution. Running kibana server side reduces that hassle. &lt;!-- more --&gt;&lt;/p&gt;</description></item></channel></rss>