robinong79 / docker-swarm-monitoring Goto Github PK

Can you explain in brief on getting Container/Service logging to Logstash

In order to get the logs from the services/containers to Logstash you need to start them with a different logdriver.

Compose file:

logging:
driver: gelf
options:
gelf-address: "udp://127.0.0.1:12201"
tag: ""

This is great if you are running one host like in the example but if I have 20 hosts it would be nice not to have to copy the dockerdata folder to every host before deploying the stack.

I've been trying for hours to get this to work using volumes rather than bind mounts and I have not been successful.

The issue is with the single file bindings for the config files. From the look of things you can't create a volume that is a file reference (it always treats the volume as a directory).

To make things slightly more complicated I'm trying to come up with a solution using the Azure File Docker Driver so I can reference these files in a cloud share rather than locally on the host.

Any help would be appreciated.

It looks like a new prom/prometheus image was pushed recently that contains many breaking changes with command line args and config file formats. As a quick fix, the docker-compose file could pull from :v1.8.2 instead of :latest.

As a not so quick fix, a lot of this stack would have to be reconfigured to fix the breaking changes.

Elasticsearch dies for me:

# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (mmap) failed to map 2060255232 bytes for committing reserved memory.
# An error report file with more information is saved as:
# /tmp/hs_err_pid1.log
OpenJDK 64-Bit Server VM warning: INFO: os::commit_memory(0x0000000085330000, 2060255232, 0) failed; error='Cannot allocate memory' (errno=12)

How can I change the Heap Size for srvice?