Hey Nathan, for most flexibility you can read ElasticSearch settings from a elasticsearch.yml file into Graylog2 with the exact same supported parameters like your ElasticSearch nodes. Every graylog2-server tarball ships with a example elasticsearch.yml for graylog2-server that you can start with. Reference it like this in your graylog2-server.conf:
# Embedded elasticsearch configuration file # pay attention to the working directory of the server, maybe use an absolute path here #elasticsearch_config_file = /etc/graylog2-elasticsearch.yml The soon to be released version 0.20.2 of Graylog2 also allows to set the parmeters directly in your graylog2-server.conf: # the following settings allow to change the bind addresses for the elasticsearch client in graylog2 # these settings are empty by default, letting elasticsearch choose automatically, # override them here or in the 'elasticsearch_config_file' if you need to bind to a special address # refer to http://www.elasticsearch.org/guide/en/elasticsearch/reference/0.90/modules-network.html for special values here # elasticsearch_network_host = # elasticsearch_network_bind_host = # elasticsearch_network_publish_host = Hope that helps, Lennart On Wed, Mar 12, 2014 at 2:46 AM, Nathan M <[email protected]> wrote: > I'll try to boil down this overly complicated problem into a few lines: How > do I tell Graylog2 what interface to connect to elasticsearch on? > > I can tell Elasticsearch where to find other cluster nodes, via the > network.host: "_eth1:ipv4_" configuration option, and then I can build a > cluster no problem. But graylog2 can never find that cluster because even > though one node is running on the same server, it's trying to use eth0, > which is a NAT'd interface on the host. > > Even if I tell the elasticsearch node to connect to other IPs (via > discovery.zen.ping.unicast.hosts: ["192.168.x.135", "192.168.x.114"]), it > wants to broadcast that it's connected to the eth0 interface, so the unicast > host definition never find each other. > > Any ideas? Some of the things I've tried: > > server_rest_listen_uri = "http://192.168.x.10:12900"; > server_rest_listen_uri = "http://192.168.x.10:12900/"; > server_rest_transport_uri = "http://192.168.x.10:12900/"; > > When I do this, Graylog2 still drops its ability to connect to the > elasticsearch cluster, etc. > > Thanks in advance! > > -- > You received this message because you are subscribed to the Google Groups > "graylog2" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "graylog2" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
