-
Notifications
You must be signed in to change notification settings - Fork 70
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Existing ElasticSearch cluster #130
Comments
You should try to add a volume with a custom dockbeat configuration file, defining your existing elasticsearch instance(s) as |
Ok, so I can ignore the --link in the launching of the dockbeat container? |
absolutely 👍 |
Ok, here is my dockbeat.yml file : ################### Dockbeat Configuration Example ######################### ############################# Dockbeat ######################################
I have just modifed the "hosts" property. I launch it thriugh this command :
Nothing happens, and when I display docker logs of the dockbeat container I have :
But, as there is no "dockbeat" index created in my cluster I supposed that the container is crashed but I I no error message except this one. |
Is should work only if the dockerbeat container can access to the elasticsearch cluster from inside. Can you go into your container and try a curl 9200?
|
I have access from inside the container to my elasticsearch cluster. |
I am having the same issue - getting 'Error opening syslog: Unix syslog delivery error' when i check docker logs. I have accessed the container and I can access the elasticsearch container: |
@abondoa @cabrinoob Think is not related to your ES cluster. Could you try to set |
@gpolaert Setting |
If I understand your Readme.md, I need to start dockbeat with a --link to an existing elasticsearch container.
Is it possible to connect to an existing elasticsearch cluster (actually an AWS ElasticSearch Service) without starting a sidekick elastic container?
Thank you for your help
The text was updated successfully, but these errors were encountered: