I just upgraded all my ES systems to 1.0.1 and they seem to be working fine
except for Kibana 3. I had installed Kibana 3 Milestone pre-5 (8512132).
Previously I was using it just with _all enabled. Now when I attempt to use
a filter for "*" and a time filter for the past hour or so, it lists none
of my 3 active indices.
/** @scratch /configuration/config.js/5
* ==== elasticsearch
*
* The URL to your elasticsearch server. You almost certainly don't
* want +http://localhost:9200+ here. Even if Kibana and Elasticsearch are on
* the same host. By default this will attempt to reach ES at the same host you have
* kibana installed on. You probably want to set it to the FQDN of your
* elasticsearch host
*/
elasticsearch: "http://192.168.4.254:9200",
On Wednesday, February 26, 2014 10:26:02 AM UTC-5, Terry Healy wrote:
I just upgraded all my ES systems to 1.0.1 and they seem to be working
fine - except for Kibana 3. I had installed Kibana 3 Milestone pre-5
(8512132). Previously I was using it just with _all enabled. Now when I
attempt to use a filter for "*" and a time filter for the past hour or so,
it lists none of my 3 active indices.
/** @scratch /configuration/config.js/5
* ==== elasticsearch
*
* The URL to your elasticsearch server. You almost certainly don't
* want +http://localhost:9200+ here. Even if Kibana and Elasticsearch are on
* the same host. By default this will attempt to reach ES at the same host you have
* kibana installed on. You probably want to set it to the FQDN of your
* elasticsearch host
*/
elasticsearch: "http://192.168.4.254:9200",
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.