I’m following this getting-started guide. Mongo and ElasticSearch lift correctly, but the Graylog server does not access ElasticSearch.
This is the
docker-compose configuration I use for it (I’m on a Mac, that’s why I declare the networks additionally):
#command: "elasticsearch -dEs.cluster.name='graylog'"
I’ve got 2 questions:
- Can I review messages w/o having the elastic search running (cuz I could not list/view/find any messages, even though I can see statistics that I have a number of unprocessed messages)
- I believe it’s a networking problem between Graylog and ES. Graylog should be trying to access ES on
graylog-elastic:9200 host instead of on
localhost:9200. Is there a way to specify that?
Okay, I found it…
In the Graylog server, in the
graylog.conf file located in
/usr/share/graylog/data/config/ I added the line:
So, basically, I told Graylog to look for the ES server at a specific URI instead of using the default
You can override that setting with the
GRAYLOG_ELASTICSEARCH_HOSTS environment variable and don’t need to modify the configuration file.
I’ve given the Docker chapter from the documentation an overhaul.
Feel free to check out and comment on PR #348.
The new Docker chapter can be previewed at:
The Quick Start looks much better with the updated commands! Nice work!
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.