Hi Daniel, In fact the only setting I have in that file is this elasticsearch.url: "http://127.0.0.1:9200";
This is actually causing issues with the way graylog configures the elasticsearch listener but changing this address to the local interface's network address should fix that. That URL should be the only setting required to make Kibana work out of the box. Have a look in /opt/graylog/elasticsearch/config/elasticsearch.yml for the "network.host" and "http.port" settings to see how graylog has configured the elasticsearch listener You can install Kibana on any machine that has network access to the elasticsearch cluster On Thursday, 15 September 2016 04:10:05 UTC+10, Daniel Reif wrote: > > Michael Anthon, > *you could publish your kibana.yml?I am unable to do Kibana find my > ElasticSearch cluster and load messages.* > Em quarta-feira, 14 de setembro de 2016 03:17:44 UTC-3, Michael Anthon > escreveu: >> >> No, you point Kibana at the elasticsearch instance and it "just works". >> There is an option in the Kibana to reload the fields from the indexes in >> case they get messed up (sometimes happens when you change the field >> extractors in a way that changes the types) >> >> On Friday, 9 September 2016 14:52:41 UTC+10, Aykisn wrote: >>> >>> Hello Michael, >>> >>> I'm really interested in this, have been looking for this feature since >>> graylog doesn't support it (yet). >>> I have a question though, do you need to recreate the fields on kibana ? >>> >>> Thanks. >>> >> -- You received this message because you are subscribed to the Google Groups "Graylog Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/graylog2/c5b60ead-35ac-4af0-a19e-ce23d442792c%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
